Magento module controller won't update - php

I did some tweaking on a module a guy used for a website he was working on and now I was requested to change one line of code in the controller of that module. The problem: it doens't matter what I do, my changes won't get loaded and Magento uses the old controller code. How do I fix this?
What I tried:
cache management (refreshed it, flushed it, cleared it and disabled it. I have done all of it in any possible order)
checked if I was in the right place to begin with (edited etc/config.xml and Block/view.php these changes did show)
edited etc/config.xml and changed the version number
System=>Configuration=>Advanced=>Advanced and disabled/enabled the module to check if it would reload it
just to clearify the cache management part:
Configuration
Layouts
Blocks HTML output
Translations
Collections Data
EAV types and attributes
Web Services Configuration
Web Services Configuration
are the only rows I have here.
installed Magento version:
Magento ver. 1.8.1.0
If there is anything else you may need to solve this problem please let me know!
I have allready wasted a day on this problem.

Maybe compilation mode is enabled.
Go to System -> Tools -> Compilation and if compilation is enabled, click Run Compilation Proces.

I fixed my problem with a workaround, it seemed that I was able to edit the model.
The code in the controller was never called because he put the logic that actually was called in the Model.

Related

Not able to edit contents in magento from backend after a installing modules

I have site build in Magento 1.7
I have installed a new shipping module Bpost through magento connect. When I installed that, it raised the error that, it is already existing plugin. After that when I accessed the site, the maintenance flag was active.
When I removed the maintenance flag and checked the site, everything seems to be working fine in the front-end. But I am not able to add or edit contents from the back-end. Click is not detecting in the existing lists of contents and when I click on add new (for cms block, page etc) the new section appears, but no action is performed while clicking save.
Why is this happening ? How can I resolve this issue ?
I recreated the site with my backup files to a new location. After that removed all the existing plugins and installed all the plugins. At that time all seems to be working fine. After that I have edited the header.phtml file and added some additional script.
The script was for getting contents and displaying it using script. After that when I run the site and went to backend everything again went to non editable mode. Now I am not able to click or edit any cms contents in the site of static blocks, products etc.
Why is this happening ? How can I resolve this issue ?
In my opinion, the problem comes from a javascript with an error that blocks the rest of the javascript. All buttons use javascript to fire events. With firebug or something similar, check which error is raised in the admin javascript and try to fix it. Using the solution that Niraj Jani gave about disabling module is a good way to check if it is really the module that blocks the javascript. If the problem is linked with prototype, it can come from the definition of blocks in php, the design template or layout...
Have you tried after claering cache?
Take Look at below link and its answer,
In Magento after installing extension Admin panel in unable to load
Delete (or move to another folder) files in /var/www/var/cache
Delete (or move to another folder) files in /tmp
From a shell, run
/var/www/shell$ php indexer.php --reindexall
You've just manually cleared your caches and re indexed your data. See if your system comes back to life.

Magento custom category widget not appearing on stage server

I followed this (first comment),
magento - category name and image in static block? to create a simple widget to display the category image and title from a static block on a CMS page. It works fine on my local MAMP version of Magento Enterprise 1.13.0.2. It's not working however on the stage / test environment Magento 1.13.1.0. (ubuntu).
It doesn't error, it's as though it's ignoring the template file (info.phtml). When I reverted to the default theme I realised I had to copy the template files to the default enterprise folder to get it to work but it did (local version). I have made sure that the template folders are in each of the themes, base, enterprise (default), MyTheme (default (which is enterprise default) & (MyTheme / MyThemeVariant)).
The only setting / configuration that appears to be different between the local and the stage is that pretty url's aren't working on the local. I have looked into the htaccess and it still isn't resolved. On both versions the native Category link Widget isn't working but i'm not sure if that is relevant.
I have disabled any extensions turned the cache off and cleared the index. Still nothing.
I have been looking for the answer, retracing my steps, altering and changing back any setting(s) I think may be relevant for 3 days now so i'm well stuck. Anything anyone can offer to try I will give it a go.
So in Magento Enterprise there is also a full page cache that you can access via the Magento Admin here : System->Configuration->System->advanced->External full page cache settings.
On the page System->Cache management, as well as disabling all the caches you should flush the Magento Cache and the Cache Storage.
You might have a 'cache' called Redis or APC, but I don't think that affects .phtml output. and if you can access the Widget in the back end I don;t think those items are the problem.
Your webserver might have a full page cache such as Varnish but I don't know how to use it or turn it on or off.
Theoretically your webserver headers might be saying 'this page doesn't update so internet providers can store local copies in their caches' - but I would be astonished if that was the case (inspect your header and inspect the Cache-control Expires and Last-modifed headers if you want to eliminate this possibility).
Your browser might have it's own little cache (which you can clear from your browser settings).
If it isn't a cache problem, in my experience .phtml files get skipped if they have PHP errors in them but you have it working on your local dev server. Could it be a file permission issue? Could it be a setting in the widget on your server that is not handled by your widgets .phtml? As alast resort, try changing your widget .phtml to a really simple file like <?php echo('test PHP output'); ?> and see if that renders - try putting the widget on different pages (ie new pages that won't be cached anywhere) and see if that get's everything through.
Could you have a namespace conflict with another module? Eg an XML file is changing your widget block XML name that sets the .phtml template? Does your widget.xml file declare <supported_blocks>...</supported_blocks> which might be excluding the block into which you are trying to render the widget?
What else? You mentioned this widget displays category information: Are you referring to a category that exists on your staging server? It will probably have a different category ID than your dev server and / or check the category is visible in the website and store.
Okay, I think I am out of ideas now.
The problem was that "Block" php file's first letter was lowercase. I changed it from info.php to Info.php and now everything works as expected.
This has been the single most frustrating investigation yet into Magento. The only thing I hope is that it saves someone a whole load of pain.

Can’t add products to new order created in backend

For whatever reason, all of a sudden I can’t add products to orders I create in the backend of my site running Magento 1.7.0.2. I’ve tried everything I could think of (disabling APC, javascript merging turned off, mod pagespeed turned off, no compilation, disabled caching, etc...).
In Chome's Java debugger I do see a lot of DOMExceptions being thrown when I try to create a new order and add products.
Specifically line 3334 in contentscript.js
var c = window.getSelection().getRangeAt(0).cloneContents().textContent;
Throughout the rest of the order creation process I get some in prototype.js and jquery.main.js I’m not sure if these are intended or shouldn’t be thrown. They are in try/catch blocks.
This is really a big pain especially since I have no idea why it just seemingly randomly stopped working. I haven't installed any new extensions and I've tried disabling all the extensions I have.
I've also seen Magento - Cannot add products to a manual order within backend of the Admin Panel which has the same problem but I guess a different solution since I tried replacing prototype.js with the one included in the Magento 1.7.0.2 files. I've never modified the js files.
If no code has changed previously that you are aware, a possibility is your hosting provider may have done an upgrade or update recently causing the odd behaviour.
Also consider trying a different browser, if Chrome/Firefox disable all plugins/modules and use an incognito mode to ensure fresh session/cookies.
With that said, I also found searching just for contentscript.js is mostly around: http://developer.chrome.com/extensions/content_scripts.html
Anyhow here's some steps I would take to help identify the issue:
Developer Mode:
Enable Magento's developer mode (index.php or SetEnv .htaccess)
Enable all system, exception logging in the admin. (System->Configuration->Developer->LogSettings)
Default Theme
Reset your theme/skin to the base/default version.
Disable all Cache
Disable caching, Flush cache storage, disable JS/CSS Merging.
Since you mentioned already tried disabling modules, did that include the community code pool and enabling developer mode?
Disable Local Modules:
Disable the local codepool via etc/local.xml
Disable 3rd Party Community Modules:
Create a new directory called disabled under etc/Modules/ Move all NON Magento standard module XML definitions to the disable directory.
These should get you back to a stock version of Magento and debugging mode to help determine where the problem is occurring. Be sure and also check PHP's logs for any oddities as well.
Sonassi has posted a good guide similar to what I mentioned above here: https://magento.stackexchange.com/questions/428/fundamentals-for-debugging-a-magento-store/429#429
I ended up hiring a developer to find the problem.
It only occurs when the payment method "Bank Transfer Payment" is enabled. A simple fix is to just disable it.
If you need to use this payment method my dev found if you copy app/design/frontend/base/default/template/payment/form/banktransfer.phtml to app/design/adminhtml/default/default/template/payment/form/ it works.
cp app/design/frontend/base/default/template/payment/form/banktransfer.phtml app/design/adminhtml/default/default/template/payment/form/
This is for magento 1.7.0.2

Edit system extensions in TYPO3

I am using the felogin system extensions. Those extensions are part of the default TYPO3 installation and they are stored in typo3/sysext. I know that I can edit them by editing its code directly but I guess it is not the best way of doing it.
How can I "overwrite" those extensions without changing their code?
Shall I create a new custom plugin and copy & paste code of a system plugin I wish to alter?
You could just modify the extension and place a copy in typo3conf/ext/. This directory (so called "local extensions") override the system extensions.
However, you will probably run into trouble when you want to upgrade TYPO3.
Did you find a bug, if so, please report it. If you know, how to fix, then it would be great, if you would push the change into the review system
If you just want to change functionality, modifying existing code is not a really could solution. There's the concept of hooks (which is a clean one) and of XLCASSes, which is somehow dirty (as it can also cause trouble with newer TYPO3 versions). So basically the same as with every other extension.
Steffen

Magento Error when Accessing User Roles Section

I have a Magento site in which there are about 20-25 extensions installed, among which 7 are commercial, which means that those 7 extensions are fully encrypted. Also none of these extensions use the User Roles & Permissions section, in the Admin area.
Now, a few days back, I got into a silly problem which is really taking a toll on me. I wanted to create a new User Role (from System > Permissions > Roles), where I already have 14 other Roles set. Now whenever I click the "Add New Role" button or try to edit any of the existing roles, I get the following error:-
<my-magento-site-domain>: This script is locked to another domain.
What I'm pretty sure is that this error is somewhere related to the use of extensions, but I don't know & can't understand where it is coming from. I have tried to solve this error by disabling all the extensions & clearing the full cache & deleting all the folders in the "/var/" folder, but nothing has happened.
Magento version: 1.3.2.3
I know that Magento upgradation is necessary, but can't do so due to those extensions.
Can somebody please help me in this matter? Any help is greatly appreciated.
When you say that you disabled all the extensions, how did you perform that step? I've found that the System>Config>Advanced status values are often ignored by extensions, as are various other attempts to disable. The only way that you can be certain of disabling the extension (IMHO) is to remove their .xml files from etc/modules.
It sounds like the error that you are getting is a Javascript generated error. You could grep the /js folder to find that error text to see if you can track down the source of the error. Likewise, use Firebug (or Chrome Inspector, choose your browser poison) to debug the JS error. Post what you find here...
One more option is to manually create the new role using phpmyadmin. By inspecting the admin_role table, you'll work out the syntax fairly quickly (e.g. tree_level ="1", role_type = "G". Then see if you can edit the new role through the UI.
Cheers,
JD
You can try with clean magento install without commercial extensions. Add a role and see if this happens. Then add commercial extensions one by one and test when this error occurs.
I assume that you have already searched all magento files (at least non encrypted ones) to see if there is any containing your error message...

Categories