Magento 1.9 – Send orders mails immediately rather than cron

Ab Magento Version 1.9 the order confirmation emails are sent not by Event (So after a successful order) but a mail queue, which is triggered via the cron. In many cases, the order confirmation is therefore only all 15 sent minutes.

not really optimal is just with the order confirmation, because the customer expects this after ordering, to be sure, that has really worked out everything. With invoice mails or shipping confirmations contrast, it's probably not as bad, if they were sent a few minutes later. However, these are still sent by Event - ie directly.

For people who would like to, that the order confirmation will be sent directly after ordering, can retrofit this relatively straightforward.

Hierzu kopiert man die Datei app/code/core/Mage/Sales/Model/Order.php in den Ordner app/code/local/Mage/Sales/Model/Order.php

und sucht dort nach der Zeile

This is commented out or deleted and replaced by this line

Subsequently, then the app / design / frontend /[IhrTemplate]/[IhrTemplate]/template / checkout / open success.phtml and top yet ago closing the ?integrated> following code:

Then eventually clear the cache again. Now the mails coming but directly after ordering.

Update vom 17.02.2017

It struck, that repeatedly order confirmation emails were sent twice. To fix this, changing the success.phtml was undone (s.o.). So if the problem of duplicate email shipment emerge, then remove this adjustment again and change only the order.php.

Used in Magento Version 1.9 Comments? Additions? Notes? Gladly!

Facebooktwitterredditpinterestlinkedinmailby feather
Posted in General problems Magento | Tagged | Leave a comment

Magento – Compare products not working

This as a side note,: We have just converted to a RWD template displaying Vergleichsbox from right to left and then had the problem, that while "said" was, that the product was successfully added to Compare, However, he has not been displayed.

This was all the more comical, as it in 1:1 Testshop worked perfectly.

The solution was: Reload Index. After recharging all indexes the problem was fixed and the products were displayed in the Compare.

Used in Magento Version 1.8 Comments? Additions? Notes? Gladly!

Facebooktwitterredditpinterestlinkedinmailby feather
Posted in General problems Magento | Leave a comment

USEr first! Make your shop great again!

USEr first! Make your shop great again!

When you have made the last time even an order in your shop? And we do not mean the provisional functionality testing, but a CONSCIOUS order. If you still think about it now, it is unfortunately too long ago. If we do not even know himself exactly, how it is, the customer to be with us, how are we to find, what we could do better and should?!

So step 1: CONSCIOUS test items in frontend

This already leads us to the next question: Why users should just with ordered us? What is so special? What added value we offer our customers? What should prevent him from among 10.000² other stores to shop with a similar offer?

Step 2: Find The Special

Also we asked ourselves these questions and following reply found.

Facebooktwitterredditpinterestlinkedinmailby feather
Posted in General, General problems Magento, Magento Extensions | Leave a comment

Imminent warning wave or occupational therapy – Changes Online dispute resolution

Paragraphs jungle

As we all no longer even knew of sheer boredom, what to do, there is finally replenishment in online dispute resolution. From the 01.02.2017 applies the obligation to provide information to participate in the dispute resolution procedures. If you think now: "Everything in the open area, we still have done long ago. "- thought WRONG, the trip goes on. There is even a negative duty to inform. To make it short and sweet, following overview of key features:

Was?

According to §§ 36 and 37 VSBG (Consumer Dispute Resolution Act) have company expanded disclosure requirements regarding the readiness / commitment to participate in dispute settlement proceedings before a consumer arbitration body.

When?

This change occurs from the 01.02.2017 in Kraft.

Who?

online retailer, what NOT operate exclusively in the B2B sector and only then, if they have committed themselves to participate in a dispute settlement procedure. Furthermore, there is an exception for operators, the most 31.12. last year more than 10 have employed persons. This counts the number of employees head, regardless of the agreed working hours.

As?

Informing the consumer is to take place online and in text form. It is important, express yourself clearly and intelligibly. An exemplary formulation for negative information obligation:

"We are neither obliged nor willing to participate in a dispute settlement procedure before a consumer arbitration board."

After a dispute arises, the consumer must in accordance with § 37 VSBG in text form (e.g.. email or fax) the willingness / commitment to participate in a dispute settlement procedure, stating the relevant consumer arbitration board including. Address and website are informed.

Where?

The information should be easily accessible to the consumer. It makes sense, therefore,, the Conditions, the imprint as well as the order confirmation (as email) to use.

Why?

We knew, that this question would come ... As we are in this respect still to answer search, let's go just to the conclusion about.

Fazit:

The law is to 01.02.2017 develop its validity. Whether it is however also bring just anybody benefits, is questionable. But the examination of the subject of information provision seems little not to implement. "Beautiful good day, I surf here degrees on your side. Did you have to 31.12. last year more than 10 Employee?”��

Failure to act is not also help. The jump to the paragraph-train is inevitable, should want to arrive without warning at railway station.

When reading, we recommend on this subject the article in the IT law-firm.

Facebooktwitterredditpinterestlinkedinmailby feather
Posted in General, Paragraphs jungle | Leave a comment

Magento – Own CSS for page, a category or a product

PictureIf you want individual products, Categories or CMS pages an individual design / give your own style, can by the involvement of private, done special CSS file. There are both products under Catalog> Products> Manage (Select product) > Design (or design) > Custom Lyout update as well as categories Catalog> Manage Categories>(choose category) > Own design> Custom Layout Update and also in CMS pages under CMS> Pages> (Select page) > Design> Layout Update XML supports own XML snippets insert. But here you can both own HTML layouts also include your own CSS files.

Thus it is easily possible to create a new CSS and this then involve as desired. To this end, the following code will be used only in the layout update box:

meinstyle.css is then naturally replaced with the name of your own CSS file. This is then in the folder skin / frontend /[Custom template]/[Custom template]/css stored.

Used in Magento versions 1.7 – 1.9 Comments? Additions? Notes? Gladly!

Facebooktwitterredditpinterestlinkedinmailby feather
Posted in Magento Design | Leave a comment

Magento – Extension of the Base Price Extension, to show the basic price even with quantity discounts

Picture

Due to some requests we now have an extension of "Basepricecreated "extension, which allows the base price even with quantity discounts (animal Prices) anzeigen zu lassen.

It already has the o.g. be installed in the store base price extension and they must be set up and function naturally. With our expansion, the basic prices are then displayed behind the rebates.

If interested, please provide brief contacting.

Used in Magento Version 1.9 Comments? Additions? Notes? Gladly!

Facebooktwitterredditpinterestlinkedinmailby feather
Posted in General, Magento Extensions | Leave a comment

Magento – Column “Payment method” or. “Payment Method” in the bills overview in the backend

By default, the overview of the invoices in the backend is not the column "payment method". They can now but manually add.

A general notice, how to add columns of information in the Admin Grids, This already exists HERE.

Here it is only briefly to a column go a overview in this. For this purpose we take the file app / code / core / Mage / Admin Html / block / Sales / Invoice / Grid.php and copy it to app / code / local / Mage / Admin Html / block / Sales / Invoice / Grid.php

Then we open it up and do the following:

1. The following lines by

(as. Line 57) insert:

2. insert the new column to the desired location between the other columns. We did this by

done. To this end, then only the code is inserted:

And already the new column appears to the payment methods in the Invoice Overview.

Used in Magento Version 1.9 Comments? Additions? Notes? Gladly!

Facebooktwitterredditpinterestlinkedinmailby feather
Posted in General | Leave a comment

Magento – für PHP Version 7 kompatibel machen

Wir haben aufgrund von Serveranpassungen gerade eine PHP-Versions-Umstellung gehabt. Es wurde von PHP-Version 5.6 on 7 umgestellt -ohne Unterstützung der alten Versionen.

Im ersten Augenblick zeigt Magento (Version 1.9.1.1) dann nur noch dies:

Fatal error: Uncaught Error: Function name must be a string in /www/htdocs/app/code/core/Mage/Core/Model/Layout.php:555 Stack trace: #0 /www/htdocs/app/code/core/Mage/Core/Controller/Varien/Action.php(390): Mage_Core_Model_Layout->getOutput() #1 /www/htdocs/app/code/core/Mage/Cms/Helper/Page.php(137): Mage_Core_Controller_Varien_Action->renderLayout() #2 /www/htdocs/app/code/core/Mage/Cms/Helper/Page.php(52): Mage_Cms_Helper_Page->_renderPage(Object(Mage_Cms_IndexController), ‘myone’) #3 /www/htdocs/app/code/core/Mage/Cms/controllers/IndexController.php(45): Mage_Cms_Helper_Page->renderPage(Object(Mage_Cms_IndexController), ‘myone’) #4 /www/htdocs/app/code/core/Mage/Core/Controller/Varien/Action.php(418): Mage_Cms_IndexController->indexAction() #5 /www/htdocs/app/code/co in /www/htdocs/app/code/core/Mage/Core/Model/Layout.php on line 555

Erfreulicherweise kann dies (augenscheinlich) einfach behoben werden. Hierzu wird die Layout.php aus dem Ordner app/code/core/Mage/Core/Model in den Ordner app/code/local/Mage/Core/Model kopiert. Anschließend dann noch die Zeile

search (Line 555 wie aus Fehlermeldung zu entnehmen) und durch

replace.

Anschließend lief das Magento-Frontend wieder problemlos. Weitere Probleme sind frontend-seitig bislang nicht aufgefallen.

Beim Login in das Backend hatten wir noch das Problem, dass die Login-Seite nach Eingabe des Benutzernamens und des Passwortes nur neu geladen wurde. Die eingegebenen Daten waren weg und es gab auch keinen Hinweis auf ein falsches Passwort o.ä.

Hier scheint es sich um ein Problem mit der PHP 7 Version zu handeln, die angeblich bei PHP Version 7 RC3 behoben worden sein soll. Bei uns war es das noch nicht.

Um das Problem zu beheben, haben wir die Datei Session.php aus dem Ordner app/code/core/Mage/Admin/Model in das Verzeichnis app/code/local/Mage/Admin/Model kopiert und (bei uns) in line 120 the line

commented out. Anschließend war auch der Backend-Login problemlos möglich.

Man kann übrigens schon vor der abschließenden Server-Umstellung simulieren wie sich Magento im Falle der Umstellung auf eine andere PHP-Version verhalten würde. Hierzu benötigt man nur Zugriff auf die .htaccess im Basis-Verzeichnis des Magento-Shops.

Standardmäßig ist hier schon (durch das # jeweils auskommentiert)

in den ersten Zeilen vermerkt. Mit diesen kann man dann (je nach Hoster) die Version durch CGI-Verwendung umstellen.

Bei uns wäre es z.B. for the 7.0 Simulation

been.

Es gibt aber z.B. also

was mglw. works. Dies ist wie gesagt abhängig vom jeweiligen Hoster und kann durch Anfrage bei diesem oder teilweise auch durch einen Blick ins cPanel o.ä. in Erfahrung gebracht werden.

Used in Magento Version 1.9 Comments? Additions? Notes? Gladly!

Facebooktwitterredditpinterestlinkedinmailby feather
Posted in General | 3 Comments