This issue must be related to the new Magento Email Queue system, that leaves orphan records on the Recipients table. If this is your issue, I send you a fix.
The new Magento Email Queue system manages these two tables: core_email_queue and core_email_queue_recipients. The former one handles the email Messages, and the later one, the Recipients of these ...
Here is what I've done.
I removed the shipping step and used a default shipping method that I know is always going to be available.
Not sure if this is what you need but you can at least use it as a starting point.
Here is my idea.
I created a new module with an enable/disable shipping step config setting, so you can always re-enable the shipping step from ...
Create local.xml file (if it does not exist already) in [your_package]/[your_theme]/layout/ folder and add following code:
Copy the folder
and its content to
(or your package template folder)
Copy the file
Right. I detect problem on Mage_ConfigurableSwatches_Helper_Mediafallback::attachConfigurableProductChildrenAttributeMapping function.
I make some changes on it. This increase performance.
Copy /app/code/core/Mage/ConfigurableSwatches/Helper/Mediafallback.php to
If in your magento system,magento cron jobs are working properly then
you define a cronjob which fire on midnight and clear cache.
<clean_cache_midnight><!-- identifier -->
<cron_expr>0 0 * * *</cron_expr> <!-- run cronjob on midnight -->
I found the "steps to reproduce" and hotfix. Originally we enabled the "Website Payments Standard" payment method and then disabled because we had the problem with "Suspect Fraud" status. Immediately after I disabled the "Website Payments Standard" it turned into "Website Payments Standard (Includes Express Checkout)" and I was not able to revert it back. ...
The other 2 patches (4291 and 1533) were issued for Magento 184.108.40.206 and earlier actually. They are already incorporated into 220.127.116.11, which is why you cannot successfully patch them in 18.104.22.168. The versions listed on the download page are a bit mis-leading.
Your PHP developer should be able to solve the exact problem with this trace, but to explain the Problem:
You have an observer which calls rkt_jscssforsb/observer as singleton (the default) but this model could not be loaded, so it saves false in the registry, which is not recognized by the next call of this singleton as it has the value false, so it is ...
Even though you have installed, the notification will come. You can simply mark as read all those messages.
Also you can check the shop url here: https://shoplift.byte.nl/
If it's all fine, then there won't be any problem at all...
First of all I want to say that the address_type is not used for customer addresses. It is used only for quote and order addresses, so there is no need to use that in order to flag your own address type.
if you need to retrieve only your store finder addresses I have an idea, but later on that.
First, you will need to create a new module to handle your new ...
My guess is the setting of cron.php to run every minute has caused a lot of things to stand on top of each other, ie, not finish before the next task scheduled of the same nature or similar is executed. Since both cron.php would not be aware of each state. The same record could be attempted twice causing some odd exception breaking the queue email sends.
This issue occurs on fresh Magento 1.9.1 installations only.
The problem is that thumbnail attribute is created by Mage_XmlConnect module, which became inactive since 1.9.1.
So you can either fix this by enabling the Mage_XmlConnect module:
Find the <active>false</active> line and replace it with <...
Copying files to local code pool will only work for blocks, helpers and models. You cannot override controllers using this method since they are not autoloaded like other classes.
So the only way to do it is via custom module. You will need following definition in your config.xml
Create your own extension, make it depend on Mage_Core and add this to your config.xml:
<!-- ... rest of your configuration ... -->
<schedule><cron_expr>*/5 * * * *</cron_expr></...
You can solved the problem by downgrading the version number in the table core_resource, as already written.
Alternatively, you can use tools like n98-magerun to trigger all install scripts
It has always solved my problems.
Just edit the ID of the stores in the store_id column in the core_store database table. Because of the foreign keys, this will get updated in almost all of the other tables.
Additionally you should update:
default_store_id column in core_store_group table
As commented, changing your actual database ID's would be a bit radical. Also you would still have to ...
I have built this, in a modular way.
Will post the code on github soon.
PM me if you want the code asap. Otherwise follow me on Twitter @willemwigman to hear when I post the code.
Edit: I've put the code on github https://github.com/...
First you need to know, how your website is identifiable as magento, as there are a big number of possible proves.
basic html structure
magento specifiv css
special js code on product views (assuming you already obfuscate the js files)
some routes special for magento
headers and html head
some file locations usually accessible (licence file, skin path, /js ...
To sort products by rating you can use the following code, taken from this module:
'rating_summary', // alias
'review/review_aggregate', // table
'rating_summary', // field
'entity_pk_value=entity_id', // bind
'entity_type' => 1,
Assuming you cleared cache, flushed apc/OPcache (if in use), ran compilation process (if in use), here is a small list of things to check:
Check if all 1.9.1 files have been copies over
Open app/code/core/Mage/Sales/Model/Order.php and look for queueNewOrderEmail method
If the method does not exist you don't have latest file
If the method exists check if ...
I have a better solution than the one of @marius which doesn't need any rewrites.
You still need to create an own module, there are tons of tutorials for that so I won't explain it here. You have to create an observer and trigger it via the config.xml. You may have to adapt the template app/design/frontend/base/default/template/checkout/onepage.phtml
Your developer hardcoded the "login". I don't know how your code looks like, but it is one of two things:
You are missing this XML:
Load this update on every page when customer is logged in
<action method="addLink" translate="label title" module="customer"><...
Problem in this instance is on these lines
$fromTime = (int) strtotime($rule->getFromDate());
$toTime = (int) strtotime($rule->getToDate());
They are not using Magento time methods to take in to consideration timing zones and in the comparison it uses following line. (Few lines after the above lines)
$coreDate = $this->_factory->getModel('...
The code fix was posted here too Magento debug trace
Note:- the fix is not EE specific fix, it is just magento doesn't provide patches to non ee-users so that is why the person who answered it mentions a patch for EE but I have confirmed it works on CE also
See the part where it says
Magento just provided a patch for this as PATCH_SUPEE-...
Important notes before starting:
For this solution I'll call our PackageName "MyProject" and our ModuleName "Catalog". If you're familiar with Magento extension development you can change these names as you like, otherwise just follow these steps as is and you should have yourself your missing thumbnail field.
If caching is turned off, it is probably ...
And Magento community to the rescue!
See https://twitter.com/willemwigman/status/543047966752538624 &
This Module adds an Ajax event to the new ColorSwatches in Magento 22.214.171.124 When the event ConfigurableMediaImages.updateImage fires up, the original updateImage() function is executed. After this we make an ...