I'm having an issue with a Magento site.
I've setup a new theme, and I'm trying to edit the Product page/template.
I'm editing this file;
/catalog/product/view.phtml
I've got the Template hints enabled, so I know that I'm definitely editing the correct file. However, changes that I make don't come through to the frontend of the site so I'm assume there's some sort of cache problem here?
Any help would be great. Thanks in advance!
EDIT:
Cache is disabled, been flushed and files deleted from var/cache.
Do you have the System > Tools > Compilation Enabled? I had a similar issue earlier today that got resolved by re running the compilation process. Also make sure you have the theme in question set correctly in System > Design.
Have you considered that the section you're editing may lie within a conditional statement (IE: if/else)? If you give an example of what code you're adding and where it may help determine whether this is at fault.
Related
I'm getting an error in the admin page when I try to login, it was working fine and I would like to know if you can please help find out what may be causing the error and how to fix it. The error is:
Fatal error: Class 'Magpleasure_Filesystem_Helper_Data' not found in /home/site/public_html/app/Mage.php on line 546
The admin page is only showing the header and the error line code, the search box but the search box is not giving any results neither. However, the front of the store is working find, no issues in front. Please help, thank you
Best Regards,
Jenny
99% that you were hacked and that you didn't apply the two patches which were released by magento some weeks ago...
I have seen that issue 1 day ago at a client side of mine and they also didn't apply the patch.
check also this: https://magento.stackexchange.com/questions/64461/error-logging-in-the-admin-panel-fatal-error-class-magpleasure-filesystem-help
It also happened to me. Did not install the security patches.
Follow the steps from this post:
https://magento.stackexchange.com/questions/64461/error-logging-in-the-admin-panel-fatal-error-class-magpleasure-filesystem-help
Remove all files: app/code/community/Magpleasure/Filesystem/
Clear your cache, login should be possible now.
Check for new "Admin Users"
Patch your System with SUPEE-5344!
This happened to my site AGAIN, even after removing the magepleasure files, and then installing the 2 security patches.
I looked in the community and local folders as noted above in the way that I fixed this the first time around. This time there was one called Ma2.
I deleted the files from both places and deleted the cache folder contents on the server. I was then able to get the backend again. There was another unauthorized user, deleted it.
There is a remaining problem though. Anybody know where to look to fully delete the problem?
This is Compiler Error edit index.php, there just comment out following lines
$compilerConfig = MAGENTO_ROOT . '/includes/config.php'; if
(file_exists($compilerConfig)) {
include $compilerConfig; }
it will fix now..
This looks like an extension has been installed but not completely. The error is because Magento is trying to find the file Magpleasure_Filesystem_Helper_Data which I guess will either be under code base local or community app/code/local/Magpleasure/Filesystem/Helper/Data.php but the file is not there.
I would suggest reinstalling the extension either by magento connect or locally and deploy to your system and if you are still having issues contacting the developer directly may be your best bet.
In the source code the head.phtml is loaded twice, once the way it should be and once between the content and footer. I replaced all magento's original files on the server and temperary switched to the default template, wich didn't solve the problem.
See the following link:
http://www.qxsystems.net/laptops.html
I asume that the issue is coused by a module or by a magento setting in the backend.
Could somebody provide me with some ways of troubleshooting this issue without removing all modules?
Many thx for any assistance!
PS: A module was to blame: Named 'priceranges'
thx for all the help!
If you have replaced the original files and also changed the template and still no change then it is surely a cache issue. Refresh your cache.
If still doesn't solves your problem then it must be some external modules issue.
If the problem is not solved then give a screenshot of your webpage with TemplatePathHints turned on, then it will be easier to tell where exactly is the problem.
Do Magneto CE extensions work in PE? The extensions I've tried installing in PE aren't working (they install but yield blank screens) and I can't find a straight answer; don't know if it's a problem on my end or if it's built in to Magento. Thanks in advance!!
Short answer is yes. CE modules can function correctly as part of PE, but it will depend greatly on what parts of the functionality it touches.
Things to do for any Magento issues like this:
Ensure the extension is enabled (check to ensure it's output is enabled and it's active) - see this post for reference (the post is how to turn off an extension, but it will point you in the right direction)
Refresh your cache
Ensure logging is on and check your logs for errors
Check your web server logs - where these are will depend on which web server you are running. Apache logs are generally in the error.log file under /var/logs/apache2 or /var/log/httpd
If all else fails, start debugging, by putting Mage::log() entries into the code and seeing what is logged and what isn't
Any extension could possibly work in any version, even if it isn't listed as such. Generally developers of extensions just list the versions that it has been tested in, but that doesn't mean it cant be used in others.
Best way to find out is install the module in your dev environment, and test to make sure it isn't overwriting/breaking any of the existing functionality.
I am working with Magento but i didn't find a very good way to debug my modules. For example, many time, i got a blank page with no php error and no apache error. For example, in backend, if one grid controller isn't well set, i don't have an error.
How to debug Magento module?
It sounds like you want to enable Developer mode. Add this to your .htaccess file:
SetEnv MAGE_IS_DEVELOPER_MODE "true"
You may also want to enable display errors in index.php:
ini_set('display_errors', 1);
The best way I have found to debug is with X-Debug in a local environment. You can also use log files to help debug in a production environment, if your unable to run X-Debug in the environment.
I've got a more detailed posting here:
https://gist.github.com/molotovbliss/2792c6c59410d75e5baf249b76413247
Consider also installing XDebug
This thread is old but useful.
Debugging tools and tricks are important as it saves lots of time of a developer.
Here is a compiled list My company Uses.
Use of Eclipse debugger: Magento is installed on a desktop using Eclipse debugger we apply breakpoints and other debugging tricks.
Use of Bug commerce as suggested in above post.
Use of Mage::log for error log and exception log.Also Magento Report files.
Use of Varien Object getData, debug.
Use of back trace: Mage::log(Varien_Debug::backtrace(true, true), null, 'backtrace.log')
Remote server level debugging.
var_dump PHP function to echo and exit.
If you are (want to be) a real Magento Developer, here is the best combination of IDE and plugin you must use to work on your Magento Projects.
First of all, phpStorm the best IDE you can find.
Exist a very helpful plugin called magicento that you can use auto-complete, find in path magento, create modules very quickly and without issue, other great stuff you can use with that plugin.
Of course need to install Xdebug (be carefully if you already run a project with ioncube, bc you need to make some trick there, Xdebug doens't work properly with ioncube loader).
This last item on the list is something I need to be reviewing but I think should be great to debugging porpoises, MagentoDebugger Chrome App.
Let me know if you need something else or any help installing some of the stuff.
Best,
Alejandro.
You can look in var/log/exception.log or system.log in the magento root. These are the directories for Magento excepetions and logs. Otherwise you might need to increase the php error log level.
Alan Storm created a Commerce Bug to help with some inline development issues.
Please try to use this magento debugger, it's chrome extension. http://w3site.org/magento_debugger it's realy speeds up a work. Just need to configure on the backend once and use Chrome extension.
Here easy to debug blocks, mails. Easy profile your extensions, etc.
Internet Explorer 9 was released today, and I decided to check a few Magento sites we build in the last couple of months to see if everything continues to work with the new version.
But unfortunately it doesn't. I came across one particular problem that is caused by the version of the prototype library which is shipped with Magento, version 1.6.0.3.
It looks like the cancelling events in eventhandlers isn't working.
For example, if you try to log in to a Magento shop, and just leave the login and password fields empty, IE9 submits the form even if there were errors, and the errors disappear after the refresh.
So that's quite a big problem I think.
So my question is: how can we deal with this problem? I see a couple of ways to deal with this:
Wait for Magento to release a new version with fixes
Upgrade the prototype library to the latest version which probably already has fixed the issue
Mess around in the existing library and try to fix the bug in there
Waiting for a new Magento release isn't a good idea because it probably will take a few weeks before there is one, and because it will cause a whole lot of other problems if you are running a very old version of Magento.
Upgrading to the latest prototype library is probably the best idea, but will everything in Magento continue to work with the latest version of prototype, does anybody has any experience with this?
So what's everybody's opinion about this problem?
Any ideas other than mine?
As upgrading Prototype has the potential to break a lot of things in Magento (and, honestly, doing anything in Magento has the potential to break a lot of things in Magento), I created a theme override for my
app/code/design/frontend/{package}/{theme}/template/page/html/head.phtml
file and slapped the following as the first element under the head tag:
<meta http-equiv="X-UA-Compatible" content="IE=8" />
This tells IE to pretend as if it is IE 8, where possible. This solved an issue where, for example, you could not check out and complete the payment process if you only have one payment method enabled, as in IE 9 the fields will all be grayed out.
Note that it really must be the first tag underneath the <head>.
Since upgrading Magento in any way has the potential to cause problems, I feel this is the least intrusive way to solve the issue in the near term.
Solved: http://www.alexanderinteractive.com/blog/2011/10/solving-the-ie-7-ie-9-magento-prototype-validation-bug/
I spent a couple days on this, and discovered the only thing that truly works is disabling things at the form level. This should solve all your problems.
As a quick fix, I think I would take the same approach you are advocating, and upgrade Prototype to a version that does not contain this issue. However, Magento will be coming along with a patch (this is too big to ignore), and at that point, it would be wise to undo your changes and apply the patch they provide to keep in line with normal upgrades.
It is rarely worth it to manually dig in the internals of Magento's JS, so that option seems a bit off to me. There are probably several places where this semantic is used and you may miss some of them.
Hope that helps!
Thanks,
Joseph Mastey
I've updated the prototype.js file to 1.7 and so far it's correct. I dont see any errors. If you apdate and find errors please notify!
The proper fix is in the Magento forums.
In template/catalog/product/view/tabs.phtml, change the line that reads:
ul.select('li', 'ol').each(function(el){
to
ul.select('li').each(function(el){