You are viewing this forum as a guest. Login to an existing account, or create a new account, to reply to topics and to create new topics.
"A component is not available to handle your request. Please try again later or use a different URL to access this program."
File: /core/CORE_App/CORE_App.php Line: 253 Error Number: 256
When trying to access index.php
orders.php still works fine.
The last thing I did was add a little css to our skin.
I tried using debugging, but nothing would print to the browser or file.
What debugging options do I have?
It appears to be a database issue - our dev and regular site share a database, and the problem shows for both of them. Is there any issue with sharing a common database?
Last edited by garden1 (02-25-2020 13:55:28)
Offline
You're thinking of someone else. Our V8 had admin.php. Our K9 installation came with orders.php. We installed K9 and used the importer.
https://gardenofone.com/storedev/index.php
https://gardenofone.com/storedev/orders.php
https://gardenofone.com/store/index.php
https://gardenofone.com/store/orders.php
https://gardenofone.com/ccp8/index.php
https://gardenofone.com/ccp8/admin.php
Last edited by garden1 (02-26-2020 10:19:56)
Offline
Oh, you renamed admin.php as orders.php. I understand. This sounds like one or more applications has been disabled on your license key. Possibly from having the same key installed two different locations. Are you using the K9 key in two places?
Offline
That's the case! The store and storedev are (nearly) identical - sharing a common database. Do I need to give up the idea of having a dev site? Is there a folder or subdomain structure I should use so the key is recognized as being used for staging?
Offline
..and you are SO right about the orders.php thing - I'm so sorry. I've typed it so many times that I forgot we had set that!
Offline
For now I've deleted the dev site. Will the license be restored automatically after a fashion?
Never mind on that - After logging in twice to the back-end, the front-end started loading.
..however now it won't render the skin that's selected (it defaults to Flex), and in the back-end I can't get System>Displays> Display Skins nor System>Displays> Install New Display Skin to load. How deep is my hole at this point?
Last edited by garden1 (02-27-2020 01:10:23)
Offline
Run your installer.php script and update PEAR when asked. I believe PEAR is out of date on your install and that's causing the failure to load the Display Skins section in the management interface. The server likely updated PHP at some point and a PEAR update is needed to compensate. That may get the Flex skin working as well.
Offline
The flex skin is working - it's what displays instead of the custom skin that's selected in the back-end. I will update the PEAR anyway, I know our hosting provider was planning to upgrade their php.
Offline
I ran the installer and updated the PEAR but everything was already up-to-date
Reloading the database sorted out the issue with the back-end not loading properly.
..and it looks like the Flex skin that's displaying is indeed correct. When I copied my custom skin into the original site, it apparently did not override files like it was supposed to, and the same skin on the original site hadn't been updated since it was a just clone of Flex..
I have a back-up of the css somewhere - I'll just have to redo the php no biggy.
Last edited by garden1 (02-27-2020 11:10:52)
Offline