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.
Related
DNN 09.09.01 / 2sxc 11. 22.1 / Image Gallery v5
App installation without problem, but when you click on image to show in Fancy box - you got message; The requested content can not be loaded. Please try again later.
I tested this with 2sic DNN Instant Bootstrap 4 theme and it is working just fine.
However, on this site I am using other DNN Theme ("Professional" Theme from DNNVista, Bootstrap 3, link; https://store.dnnsoftware.com/home/product-details/professional-15-colors-mega-menu-bootstrap-responsive-dnn-6x-7x-8x-dnn-9x) and this error occurred every time I click on a single photo.
I am aware that this Theme is full of bugs and I probably wasted 99$ for it, but would like to find out what is wrong and try to fix it in this particular Theme.
But - I don't know where to start, because there is no errors in Admin Log.
Any similar situations or ideas, please?
(sorry if I did not express my self clearly - English is not my Mother Tongue. Please ask if you need clarification)
UPDATE:
I found that, from some reason, hyperlinks for pictures are parsed without question mark after filename, but can't find a reason for such behaviour because everything is correct in app template.
Just a guess - probably you have some JS replacing other JS - like Fancybox being loaded 2x in different versions. Best check the Chrome-Network to verify.
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.
This is my first time working with Magento and here is what happend: I spent two days reading the documentation and tweaking the settings to fit my needs. I then installed this theme:
http://themeforest.net/item/decostore-magento-theme/1876494?WT.ac=category_thumb&WT.seg_1=category_thumb&WT.z_author=8theme
The problem is that the theme didn't work the way I was expecting and now I'd like to rollback to the default theme and completely remove everything added by this theme to my installation.
Unfortunately, I didn't backup the installation and database before I installed the new theme and I have no idea where to start.
Thanks in advance.
1. Switching back to default theme
Go to the admin area and then system > configuration > design
Change "Current Package Name" to 'default' and make sure all inputs under the "Themes" section are empty. This will return you to the default theme.
2. Completely remove everything added by this theme
I take it from your question that you are not using any form of source control. Might be an idea to look into this for the future :)
Magento 1.7 has introduced backup and rollback features so you may also want to check that out.
If this is the case, backup everything before you start removing files and directories as described below
Anyway, to completely remove all files and directories added when you installed the module, unfortunately it will simply be a case of manually finding the files and directories deleting.
The easiest way to do this will be to find the original source code you received when you purchased the theme and removing the corresponding files from your site. When removing directories be careful to only remove those specific to the theme - It will have been sent to you structured so that you can easily drag straight in to your web root - so will contain some other directories required by Magento, simply to give it the correct hierarchy.
At the very least there will be files and folders specific to the theme located in the following directories:
app/design/frontend
skin/frontend
js
and also most likely some more in the following:
app/etc/modules
app/design/adminhtml
app/locale
I know the result for this can be different for everyone, but in case someone else comes across my specific case, it was the N98 folder under app/code/community/N98 that caused the problem. Particularly their CustomerGroupCheckout plugin as shown here: https://github.com/amenk/N98_CustomerGroupCheckout
Removing the N98 folder brought back the configuration page.
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.