Dear friends, I have a topic that I need to tackle today.
I had thirtybees installed from the start and was quickly sure that it would one day replace our old shop system. After all, I urgently need something new.
So, over the years, many tests have been carried out and adjustments have been made. And of course all shop updates up to 1.5.1.
Please look at the picture, I have this message in coreupdater. I am aware of this and it is correct. I made these changes over the years of testing. These are adjustments that I know about and that I need. It is nothing major.
Why did I change it in the core? Well, it was a test system and I can do that. I can't put it in a module. Can I implement it myself as an override - well, maybe, but since it was important, quick stuff, it was the easiest way to do it this way.
the test system has now been transformed into a productive, live shop. it was created out of necessity and I wasn't ready yet. the old shop system was terminated by the old hoster due to internal disputes about the PHP version and its data structure. thanks old hoster 🙂
so what can I do? up until now the shop updates have worked just like that.
I wouldn't mind entering these changes manually again if there is an update to a new shop version that cannot handle these changes.
up until now this has apparently never been a problem.
what is the thirtybees support like about this? can they package it as an override? is this work for paid hours?
Question
DRMasterChief
Dear friends, I have a topic that I need to tackle today.
I had thirtybees installed from the start and was quickly sure that it would one day replace our old shop system. After all, I urgently need something new.
So, over the years, many tests have been carried out and adjustments have been made. And of course all shop updates up to 1.5.1.
Please look at the picture, I have this message in coreupdater. I am aware of this and it is correct. I made these changes over the years of testing. These are adjustments that I know about and that I need. It is nothing major.
Why did I change it in the core? Well, it was a test system and I can do that. I can't put it in a module. Can I implement it myself as an override - well, maybe, but since it was important, quick stuff, it was the easiest way to do it this way.
the test system has now been transformed into a productive, live shop. it was created out of necessity and I wasn't ready yet. the old shop system was terminated by the old hoster due to internal disputes about the PHP version and its data structure. thanks old hoster 🙂
so what can I do? up until now the shop updates have worked just like that.
I wouldn't mind entering these changes manually again if there is an update to a new shop version that cannot handle these changes.
up until now this has apparently never been a problem.
what is the thirtybees support like about this? can they package it as an override? is this work for paid hours?
4 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now