This is a stretch but hopefully someone has an idea of what's going on here.
I was working on adding a feature to an extension (Amasty Product Grid Editor) to add the in stock status to the grid and allow in-line editing.
I ultimately got this working, but in the process something odd happened. I now have a problem with a completely unrelated extension (AheadWorks Facebook Integrator).
If the FB extension is enabled, I get almost no output in the browser on any page in the frontend or backend EXCEPT on the product grid in the admin.
On every other page it renders some of the header but bails after it tries to instantiate an instance of the FB Integrator helper class.
It throws this error:
Fatal error: Class 'AW_FBIntegrator_Helper_Data' not found in /var/www/vps_local_5/app/Mage.php on line 520
However, this file is there and all permissions are correct. The only thing I can figure is that in my failed attempts to get the feature added to the product grid I screwed up the database or something, but I have no idea what would cause it to think that a class file isn't there when it really IS.
The site works fine otherwise if I disable the FB extension. If I disable or even revert my changes to the Product Grid extension it still doesn't work, so it's not a conflict either.
I am leaning towards database only because after I got the changes to the Product Grid extension working correctly on my local dev server I copied those files to our remote dev server and it works great with no issues or conflicts with the FB extension.
So I have to believe that it was something in my iterations that broke something but I'm at a loss as to what.
Any ideas?
Try returning the compilation process (Magento Compiler) -- only if you have it currently enabled.
Magento loads from /includes/src/ instead of app/code/local or app/code/community when the compiler is enabled.
Related
Many bugs and errors in 2SXC installation
Can someone please give me some help?
This is supposed to be trivially easy.
I have spent 7 hours on this and got nowhere.
In deploying the module on new DNN install :
DNN PLATFORM
v. 09.02.01 (533)
Install 2SXC into the DNN - Successful
Deploy Content Module on to empty page: Successful
Click circular icon. Popup appears requiring Auto Configure button to be clicked.
Auto-Configure Content for 2sxc 11
Dialog Text:-
Auto-Configure Content for 2sxc 11? (Yes, I do)
install recommended content package? (Yes, I do)
Popup: Do you want to install these packages? (Yes, I do)
- Default content for 2SXC11
It takes about 10 seconds per package. Don't re-load the page while it is installing.
I click OK
1 second later
Popup: An Error occurred.
An Error Occurred
Spinner rotates ad infinitum
Try the help page: It says:-
"Run Auto-Configure and confirm the "are you sure" question, then wait a few seconds. Once you see the confirmation, everything worked". (Oh, No. It certainly did not!)
Installing default content templates
An error occurred.
Looked up the Wiki
Tried to upload the Content Templates .zip file into a Content Module Admin/App. An Error Occurred on the upload. Instruction says: See below for error. (There was nothing below).
Any advice welcome!
What you describe should be really easy - I agree.
My guess is that something has gone wrong in a way that's hard to spot. Maybe an installation once got interrupted or something like that. It should be easy, so I really suggest one of the following options:
Quickly replay the same scenario with a blank DNN to experience how it should work, and to ensure that your PC isn't doing something funny (for example, the file is downloaded by the DNN server, and if your PCs firewall would prevent the IIS from getting files, this would fail).
If that worked, probably just uninstall 2sxc completely and also uninstall the DB (that doesn't happen automatically, because you may just uninstall and want to keep the data) - use https://azing.org/2sxc/l/Kf5yDYQq/uninstall-2sxc - then try again
Ask a friend to play this through once with you
We just installed 2sxc on our development site, I’m super hopeful about it working - especially its ability to generate a json / json api. But! Today I used the Evoq page settings to delete “Content” instances on a test page - after that the “Add Module” to add a new “Content” instance fails - 2sxc’s javascript fails. Mysterious why just removing then trying to add “Content” instances would break 2sxc.
Has opencart 2.1 a cache system apart from modification?
I'm trying to restyle an opencart 2.1 site.
I've modified catalog/view/theme/my-theme/template/product/product.tpl
but I'm not able to see my updates.
The site has only 1 modification that affects Admin area...I've also tried to disable it and update cache, but without success.
I've tried to open site in another browser, but nothing.
Finally I've tried to rename product.tpl to product111.tpl (also in view/theme/default/product)... but the original product page is still loaded.
Does someone know why this happens?
UPDATE : I haven't found a solution, so I made a fresh installation, applied custom theme and then copied modified files... everything is Ok now. If I modify product.tpl, all changes are visible in product page.
If you have vQmod installed there is a vqcache also.
You can check to see if you have vQmod installed like this:
yoursite.com/vqmod/install
It should usually clear itself, but if it doesn't then you can safely rename the vqcache folder to clear it.
The reason I say rename rather than delete is that sometimes a change to the cache will show an error which wasn't spotted when the original change was made and might prevent orders until it's fixed. If you rename then you can place the folder back and it will work again but of course you should fix the error when you can.
I recently migrated my Joomla website from localhost to the test-server and after having completed the database imports and configurations(in configuration.php), the css doesn't seem to load although I can see that the css files have the correct privileges[644]. all I can see is mis-aligned text.
At first, I thought that since my template was custom, the problem lies in it but when I logged into administrator, the same problem occured, although here the text seems properly aligned.
The link to my website is : www.wdwdi.com/calderoni
Please assist.
Try the migration again with AkeebaBackup and the corresponding Kickstart-Script. It never failed in my usage. This will save your time you would use now for debugging.
I've just upgraded Magento from 1.4 to 1.5. The update went (almost) smoothly and admin appears to be all working etc.
The problem is with the theme. Something (a module or some bad code somewhere) is causing memory issues somewhere down the page (Error tried to allocate memory etc). The top layout areas load ok. I know this because I get a fatal error on a deprecated method call and when I correct this error I see the problem
How can I track down the offending code/module?
Thanks
** EDIT ** The admin area is working just fine which is why I am assuming it is theme related
** EDIT ** I see the problem even with different themes
If you can see the problem with the default theme, it's unlikely that the theme itself is causing the problem. This is backed up by the fact that you say that you have the same issue with multiple themes.
Assuming that you made no updates to the core code (right? right?), try replacing your entire core class folder with a clean copy from your version of Magento. Try doing the same with your default theme (if you have edits to the default theme, create a "new" theme with the default code and use that). Then, try again. If you still have problems, it's very likely that some of your custom code is causing the problem.
Hope that helps!
Thanks,
Joe
EDIT: Make sure to disable caching, the Magento compiler, etc.
How do I find out which code section an error occurs in, if the site done on Joomla gives me a White Screen of Death?
I even know which module fails, and under what condition (it is a slideshow module, and it fails when one of the items to display are of video type), but I would like to check what place in the code it fails in, in the hope of perhaps correcting the problem myself (I am not the original developer, and I am not fluent in PHP yet).
You need to enable error reporting in your environment. It is disabled by default due to security concerns. I think the easiest way would be to put the following lines of code in the beginning of your joomla installation's index.php file:
ini_set('display_errors','On');
error_reporting(E_ALL);
After you are done debugging do not forget to remove or comment out those two lines.