Timeline for How to update admin routers of custom module for patch SUPEE-6788
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 3, 2018 at 17:38 | comment | added | Darren Felton |
Now the real Problem. Using the other (better) system you had your own namespace defined by using the "FrontName" Tag. You don't have this luxury any more. This is not true. We can namespace our admin controllers through planned routing paths. My approach is to create menu actions as such: <action>adminhtml/namespaceModule_index</action> where namespaceModule matches the extension's namespace/module name. Then inside the controllers/Adminhtml directory create the directory "NamespaceModule" (matching actual values). Put controllers inside that directory and we now have namespaces.
|
|
| Nov 16, 2015 at 16:08 | comment | added | leedch | Mage::log('some text', null, 'invoice.log', true); If the Action is triggered, you'll get a file in /var/log/ Also I found an error in the XML. on the <htmlinvoice> node you forgot the last folder Name of the class, it should be <htmlinvoice before="Mage_Adminhtml">PAJ_HTMLinvoice_Adminhtml_Htmlinvoice</htmlinvoice> | |
| Nov 16, 2015 at 16:06 | comment | added | leedch | @paj Got some things to try out. 1. According to your code your Url should be something like domain.com/admin/print/invoice/order_id/54 The Controller name should be changed. It is highly likely that the name PrintController could be used in some 3rd party extension. I don't think Magento usese that name, but I haven't checked. 2. The Controller Action just uses Echo. I understand Magento's system is too complicated. But a problem could be, that echo simply doesn't work in the controller try adding a Log entry, to see if the action actually gets fired | |
| Nov 13, 2015 at 15:03 | comment | added | paj | @leedch I have updated the github with my latest version - I still can't get this to work despite many hours and multiple attempts. Perhaps you can spot the problem...github.com/gaiterjones/magento-htmlinvoice | |
| Nov 4, 2015 at 20:05 | comment | added | leedch | @paj It is rather difficult to find your problem, as your GIT Repository is still showing the old setup. The instructions needed to change the admin routing are in the other posts here. The problem you're facing will probably be related to you not finding the new URL or having some tiny error in the XML, folder names, file names, class names or similar. If you want someone to look at it I suggest you make a GIT branch where you commit the changes for SUPEE-6788 and provide us a link to look at it. | |
| Nov 4, 2015 at 15:17 | comment | added | Rick Buczynski |
I do agree that it was a luxury to define custom frontNames for admin routes, and will surely miss it. Now we have to contend with greater likelihood of controller collision. Also, are there any performance benchmarks to compare the router's work to match on a unique frontName versus cycling through the before/after stack on Mage_Adminhtml? -- maybe this should be a meta post :)
|
|
| Nov 3, 2015 at 13:00 | comment | added | paj | @leedch I am pulling my hair out trying to figure out why this module will not work when I change the admin routing for SUPEE-6788 no matter what I try I get a 404 error. It's a simple module to print a custom html invoice. github.com/gaiterjones/magento-htmlinvoice | |
| Nov 3, 2015 at 6:16 | comment | added | Jonathan Hussey |
Magento now expects you to move your backend controller classes into a new subfolder called "adminhtml" - this isn't true, the controller can be wherever you want it, it's only under the adminhtml folder in this case because you have defined a starting route of Pulsestorm_Adminhello_Adminhtml in config.xml. You also need to update any admin layout handles, and calls to generates admin URL's like getUrl().
|
|
| S Nov 2, 2015 at 20:48 | history | suggested | George Cummins | CC BY-SA 3.0 |
_Adminhtml is appended, rather than prepended
|
| Nov 2, 2015 at 16:27 | review | Suggested edits | |||
| S Nov 2, 2015 at 20:48 | |||||
| Nov 1, 2015 at 17:14 | comment | added | Fiasco Labs | Heh, once caught a hilarious Magento developer response back in the day on the old MagentoCommerce forums to your "yet even documenting their code" comment. "But the code is self documenting...". Umm didn't pass the perl pod test then, doesn't now. Thanks for the explanation above, I needed it. | |
| Oct 30, 2015 at 9:15 | comment | added | leedch | Ok, done... hope it helps | |
| Oct 30, 2015 at 9:14 | history | edited | leedch | CC BY-SA 3.0 |
added 1853 characters in body
|
| Oct 28, 2015 at 18:47 | comment | added | Claudiu Creanga | can you expand your answer if it works? thanks! | |
| Oct 28, 2015 at 16:41 | history | edited | leedch | CC BY-SA 3.0 |
added 101 characters in body
|
| Oct 28, 2015 at 16:39 | review | First posts | |||
| Oct 28, 2015 at 17:29 | |||||
| Oct 28, 2015 at 16:36 | history | answered | leedch | CC BY-SA 3.0 |