Today I tried again on a Magento 1.6.1.0 Installing the current (MRG 2.1.12) To install version. Since the installation was very fresh, I risked it to need to install new, if there should be a non-repairable fault ad-hoc.
A tip, I want to give the previously (whether it does what I do not know but it can not hurt): BEFORE calling Connect Manager to complete the backend cache disable.
In the Connect then the resulting link from MRG Installing enter and leave. In my it said in the installation, that the cache could not be deleted, and therefore it was a mistake.
In any case, then, neither the backend nor the frontend available. The error message reads
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Is reported in many forums and blogs, that it is the Payone module and a newer version (as currently contained in the MRG 2.4.9) could solve the problem. So I looked at the current Version of Payone picked out of Magento Commerce. Important here is really to accept the current, up there, nor the 2.4.9 specified. The current one certainly gets, when in “Release Notes” selects the top. In the current case, the 2.5.2, which officially Magento 1.6 supports.
Because the backend was no longer invoke, you have to go directly to the Connect Manager. These call and enter www.IhreDomain.de/downloader/. Then install the latest version of Payone and then possibly even delete the cache via FTP.
Then everything worked again.
Now, however, will probably come soon, the new version of MRG, which is then installed directly because that is not quite optimal yet. The Payone 2.5.2 was indeed installed directly and then it worked again but the Magento Downloader yet 2.4.9 displayed and an upgrade is not possible. Also Locale_Mage_community_de_DE can not be directly 1.6.1.0 upgrade. (Who will then attempt to upgrade again his side can not reach and have the extension Payone again as above. install)
Personally, I do not need to store and can not wait a few weeks- will delete the shop again and install only the extensions, if they are compatible. Better safe than sorry. Not, serious upgrade it later- or other errors are.
Update vom 18.04.2012:
Since there is still no update from MRG, I looked around me again and found something a little, What is perhaps even better than Germany Ready Market: The extension is “German Setup”, is FireGento According to the manufacturer and makes the, what is expected and no longer (such as e.g.. Payone incorporate). The extension creates the CMS / static blocks as Imprint, ABG etc. how it was used by MRG and then hears more or less already on.
All in all, probably a very good alternative, which I have tested so far have not themselves, which sounds very good and the reviews speak for themselves. It can be ordered via Magento Connect, and indeed HERE.
Used in Magento Version 1.6.1.0. Ask? Comments? Suggestions? Gladly!
Hallo Covos,
due to the differences in the versions of Magento 1.5 and 1.6 It is not very dangerous to 1.6 agreed to install extension.
Die PAYONE-Extension 2.4.9 is “not” 1.6 suitable. The same applies to MRG. This is mainly due to the fact that the Magento version with 1.6 Variable names have shortened. If the version 2.4.9 Standing by itself it is installed as well as with MRG to the above. Error.
The extension version PAYONE 2.5.2 is “1.6-sure” and only these should with 1.6. and will be used later. As for MRG I want a quote from undefined here in support CGI / symmetrics bring:
“The latest version of the MRG is one of us only for the version 1.5 released by Magento. We know from various reports about the community issues when used with Magento 1.6.
It is correct, that the current version of the MRG or module dependency to PAYONE 2.4.9 includes. We are the new opportunities created by Magento 2.0 regarding the check module dependencies and deploy after successful verification, a new module on Magento Connect.”
I hope this statement to all owners of a Magento store with the version 1.6 higher and further helps.
Yours sincerely, / Best regards
Timo Kuchel
IT-Consultant & Project-Manager
PAYONE Ltd. & Co. KG
Thank you for this information Mr Kuchel. As Mr. Kuchel emphasized again, I can not as stated above in the article also advise the current version of MRG under Magento 1.6 to use.
The article will be exclusively for those, my need to install the MRG.
I had uninstalled it because of the problems and fear of damages again.
You can also manually deakivieren after installing MRG via the Connect Manager Payone extension, If you do not need them.
just change in app / etc / modules / Mage_Payone.xml following:
true
in
false
Since I currently sit up a few shops with the MRG 1.6er, is actually the simpler solution for me and remains well behind updateable. But as said, Not only so long as one uses Payone.
I probably forgot the tags above 😀
true
in
false
@ Timo Kuchel
for when is a release of “market ready german” planned, with the 1.6.1.0 compatible?
I would also like, I unfortunately just missed this information and I shot my Checkout, Even after uninstall the extension, I'm more into the nciht checkout.. As soon as I would like to checkout, I'm redirected to home..
Greeting
Hi,
There do more detailed information? Forwarded directly to the start after clicking on “Checkout” or only in the checkout area? A few details might help bring this. The best course would be a link to the affected side (you; by PM)
Hi people,
has anyone have an unknowing when the update comes out.. ?
Would be cool if someone could answer ne
Thank you .. 😉
MFG: Kostik
A little tip to:
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Magento created in the root directory, create a flag file in the installation of extensions maintenance.flag (think since Downloader 1.5.x), it is not deleted, if it comes to demolition.
If you delete this file (maintenance.flag in the root directory http://www.xxx.xx/) for FTP (SSH…) sind Front- and back again to reach.
(If a correct installation is running on the downloader, this file will be deleted again),
or you can comment out the following lines in the index.php:
/*
if (file_exists($maintenanceFile)) {
include_once dirname(__FILE__) . ‘/errors/503.php’;
exit;
}
*/
It is up before the installation of a left-downloader in Ext
disable this functionality and.
Settings: Put store on the maintenance mode while installing/upgrading (deactivate)
Possibly. It saves en(r)m one or another spot of trouble, when having trouble with Magento.
Another tip to MGR among Magento 1.6.x installation, If you want to test it, it should in any case the
app/code/local/Mage/Catalog/Block/Product/Abstract.php
with the original file:
app/code/core/Mage/Catalog/Block/Product/Abstract.php
be adjusted.
Similarly, the
/app/code/local/Mage/Wishlist/Block/Abstract.php
with
/app/code/core/Mage/Wishlist/Block/Abstract.php
be adjusted.
So content from '/ app / code / core / Mage /…’ die in '/ app / code / local / Mage /…’ insert and the documented changes from the old / app / code / local / Mage /…
MGR files paste it to the place again.
Method: public function getPriceHtml (…)
PS: all of course also http://www.magentocommerce.com/boards read 😉