Support community for TTG plugins and products.
NOTICE
The Turning Gate's Community has moved to a new home, at https://discourse.theturninggate.net.
This forum is now closed, and exists here as a read-only archive.
You are not logged in.
Pages: 1
Hi, just updated to Release 2.
http://www.circuitpics.nl/shop/
I followed the guide and "renamed" just in case the old module folders
* backlight/modules/okapi-core/ to .old
* backlight/modules/standard-page/ to .old
The message I receive is:
Backlight
Something went wrong
Unable to find file at /backlight/modules/standard-page.old/StandardPage.oldEngine.php.
Have you removed the standard-page.old module? If so, either copy the module back, or change the template used by this album. in EngineFactory.php on line 319
© 2007 - 2016, all rights reserved.
Offline
Hi,
Rather than renaming, I think it would be better to move those folders completely out of /modules, as that entire folder gets scanned to see what's there. I will often do something like this:
/_disabled_modules
/backlight
... and then move backup modules into the _disabled_modules folder until I decide whether to delete or reinstate them. I front the folder with and underscore just to keep it at the top of my file list, so it's easy to see/find, and so that I know any folder beginning with an underscore is of my own making, and not a part of the application.
Offline
Ok, thanks. I moved them out of the modules folder now into a new "_" named folder.. Though still got that message..
Offline
I'm not sure how you can resolve that. Can you provide me with a Backlight admin login via the Email link under my name, and also a URL to the page where you're getting that error?
This happens because Backlight scans the modules/ directory for modules, and will register any directories that it finds with valid modules, including those renamed *.old.
Offline
Done!
Offline
Thanks! I can't see this error anywhere. Has the problem resolved itself? It may well do so if you had since removed the .old modules and visited the template designer.
If the problem still exists, can you provide a URL (or steps to reproduce) where I can see it?
Offline
LOL! I thought you fixed it. Might be due to caching issues? I had moved the folders into a _foldername so seems to be OK!
Offline
I guess you can say the problem had been solved in code. The Backlight admin page will rescan and update the module database at any point that it needs to refer to them. For example, viewing the template listing, editing menus, and various other scenarios.
So long as the module that Backlight needs at the time exists within modules (and I assume only exists once), then the module list and path information should resolve itself.
Where it could be broken, is between the time of removing a module (even if it had been named as .old) and performing any of the various tasks in the Backlight admin that would resolve the issue.
Offline
Right awesomeness! I think this is a pure example where Backlight stands out!
Many thanks! In the next months I will be transfering my shop in total to the new backlight. Currently I am still on CE3
Offline
Thanks for the kind words! The cart upgrade should be straightforward. Backlight provides a migration tool for CE3 (as well as CE4).
Offline
Thanks for the kind words! The cart upgrade should be straightforward. Backlight provides a migration tool for CE3 (as well as CE4).
Received a CE4 migration optin to get CE3 to CE4 first and then migrate. I am just building from scratch. Takes some time to upload everything but Ill be fine
Got high upload speed, just have to recreate albums on the Publisher. But that is also my chance to change some things
Offline
Pages: 1