This topic has been marked as resolved.
- You must be logged in to reply to this topic.
This topic has 3 voices, contains 32 replies, and was last updated by TB Support 2672 days ago.
Tagged: upgrade problems
ThemeBurn Support › Forums › OpenCart Themes › Kiddos OpenCart Theme › upgrade problems
This topic has been marked as resolved.
Hi, 1) There is a strange JS error on the home page that breaks mobile menu and many other things. Strangely, it comes from the slider. Can you please try to re-save your home slider settings? You could clear theme cache afterwards just for a case. 2) When choosing a menu icon you also have an option to set the the icon spacing. http://i.imgur.com/VVoenyc.png BR, |
|
December 14, 2016 at 1:58 am #54283
|
|
Thank for your guidance. The problems were indeed solved with a slider re-save… |
|
December 14, 2016 at 8:52 am #54299
|
|
I have another urgent problem after this update… I hope there aren’t many more… when i try to edit a product in admin i get Notice: Undefined property: Proxy::getProduct in Please advise ASAP as i am stuck. |
|
December 14, 2016 at 4:23 pm #54315
|
|
It seems that your last issue is not connected with our theme. You can try to change to the default theme to see if it ceases to happen, but this is highly unlikely. Anyway, if the the problem does not occur when you change to the default theme, please, write again here. If it continue to appear, you can try to ask for help in the opencart community forums. Regards, |
|
December 14, 2016 at 4:48 pm #54316
|
|
This problem appeared after i upgraded yesterday as yesterday it worked… so may be not connected to the theme but from what it seems the upgrade of it was the cause… When i change to default theme i get the error from the attachment. And i do not have the BurnEngine CP in the extension. Should it be there or the one from the admin menu is enough? Kind regards, |
|
December 14, 2016 at 5:06 pm #54317
|
|
Maybe some db changes done with the update? |
|
December 14, 2016 at 5:58 pm #54321
|
|
It is clearly a problem caused by the update as i restored an older version, the edit worked. After i applied the upgrade the problem is there. I think it is something related to some change the upgrade does in the database. Can you please investigate, as i have no clue what changes there… |
|
December 15, 2016 at 2:18 pm #54350
|
|
i have reenabled the credentials |
|
December 15, 2016 at 2:22 pm #54352
|
|
I have restored an older database and the problem is still there so in the upgrade process there must be some file modification that brakes the site… |
|
December 15, 2016 at 2:43 pm #54359
|
|
I have just replicated that the problem comes when upgrading… You can test it for yourself i have restored an old version working version on https://giraffe-shoes.ro/themeburn/ Really hope we get to a resolution here as if not i must rollback to the old and full of bugs version and somehow reissue all the orders and other changes done in the week since the upgrade … and this really would suck :/ |
|
December 16, 2016 at 12:26 am #54389
|
|
Hi, we checked your replicated version without upgrading nothing and it seems the edit product does not work and gives the error message you have described above. We even disabled all of the custom modifications, but the error persists. We also don’t see BurnEngine in the opencart modules list. Did you manually modify OpenCart files to prevent BurnEngine module from appearing in the list ? Also, regarding to your questions about the db changes- the update does not make any db changes. It just refreshes the opencart modifications, just like if you refresh them manually (see http://easycaptures.com/fs/uploaded/1156/6573746597.png). So basically if you have a non-working extension it could break something, but this will happen regardless of the upgrade- you just need to refresh the modifications. So, we could try to update BurnEngine in order to see how it breaks the admin product edit, but it seems it is initially broken. If you give us replicated state with working admin product edit, we can check how the upgrade breaks it. Regards, |
|
December 21, 2016 at 5:34 pm #54573
|
|
Hello, I did not do any modification to the opencart modules or to anything in the code for that matter as i am not really a php person, that is the main reason i went for opencart and themes , so i have no clue whatsoever why the module section is not reflecting your theme Now to demonstrate what is obvious for me as in the fact that the theme is the culprit i have just made a step by step printscreen of the upgrade with all the states on every step As you can see i go from a working edit in product section to copy the upgraded content of your theme install/upgrade it from the admin go back to product and… the error is there I have just put a number 1 to 9 for the step orders on each printscreen. ( i will attach them in 3 posts as there is a limit of size or number of files ) In the end i have restored the https://giraffe-shoes.ro/themeburn/ to working state with a working edit on product just so you can have a go for yourselves and try to get to the bottom of this as you can imagine this is already passed the critical point for my business and i need to consider a way of going back to the buggy old version and migrate the current database, ( i cannot just restore an old version of the site because – and maybe this is a hint – when i copy the old version it detects the changed version of burnengine, i guess from the db, and prompts as if it is upgrading and then does some change that fu.. it up). So not even a rollback with a current state database does not seem a good solution … basically i am now depending on you getting this to work in some way … |
|
December 21, 2016 at 10:40 pm #54587
|
|
next files |
|
December 21, 2016 at 10:41 pm #54591
|
|
last files.. ps: feel free to have a look in the code or do whatever you think would solve it as this is really not a nice situation for me. |
|
December 21, 2016 at 10:43 pm #54595
|
|
just to underline the fact that i cannot rollback either this is a printscreen of the theme trying to “upgrade” from 1.1.5 to 1.0.7 and after this the error is there once again and after clearing the modification the site is unusable for good. |
|
December 21, 2016 at 11:03 pm #54599
|