14

As far as I can see/know this table is included in the event log_log_clean_after. If you look under the file app/code/core/Mage/Reports/etc/config.xml you will see the following snippet. <events> <log_log_clean_after> <observers> <reports> <class>reports/event_observer</class> ...


12

I found the secret ingredient.. and it is Mage::app()->loadArea('frontend'); <?php include_once "app/Mage.php"; umask(0); Mage::app()->loadArea('frontend'); $layout = Mage::getSingleton('core/layout'); //load default xml layout handle and generate blocks $layout->getUpdate()->load('default'); $layout->generateXml()->generateBlocks(); ...


11

I put some research in this some time ago as we also had issues with that table. report_viewed_product_index is used for the recently viewed products. If you don't use this feature: Go and truncate :-) If you use the recently views products functionality, check if your cron is set up correct. The entries for visitors that do no more exist in the log/visitor ...


9

In short, yes. CE 1.7 is still vulnerable to those specific attacks because no security release has been issued which contains a patch. In the case of the latter one, a session fixation attack, the change is an upgrade in the security practices which Magento already used to stay in line with current security best-practices. Not something likely to be issued ...


6

The cache is flagged as invalid but not refreshed as a performance decision (flag rather than auto-refresh), if I remember correctly. There was some discussion about this when the behavior was introduced, but it was stated as "by design" by Magento, Inc. (whether good or bad design is left to the viewer!). As a developer though it's possible to observe ...


5

You’re on a great path with that cluster configuration. I strongly recommend a singular server for Redis or Memcached, rather than running instances on each web host. Here’s the full list of configurations I’ve used for a highly available, fault tolerant, distributed, and load balanced LEMP cluster. It includes app/etc/local.xml, the core_config_data table, ...


5

vim app/code/core/Enterprise/Rma/etc/config.xml On line 196 change: <enterprise_rma>Enterprise_Rma_Adminhtml</enterprise_rma> to: <enterprise_rma before="Mage_Adminhtml">Enterprise_Rma_Adminhtml</enterprise_rma> RMA works then


4

As defined in app/code/core/Mage/Authorizenet/Model/Directpost.php, this exception is thrown if any portion of the below evaluates as false: if (!$this->getConfigData('trans_md5') || !$this->getConfigData('login') || !$response->isValidHash($this->getConfigData('trans_md5'), $this->getConfigData('login')) ) { Mage::throwException( ...


4

The answer of philwinkle is fine. In my case additionally the md5-hash which I had set in authorize.net and Magento was too long. It caused a different hash calculation in Mage_Authorizenet_Model_Directpost_Response::isValidHash After I changed the md5-hash into a 10 character string it was working.


4

Apache You're on the right track. Read-balancing across multiple instances gives you maximum concurrency. Read the whitepaper from Nexcess released at Imagine 2013 and tune your Apache properly. Use PHP-FPM. Use fast caches - Redis for FPC, backend cache. Use multiple Memcached, specifically for sessions. Use APC. I've seen some recommendations where ...


4

To upgrade from 1.12 to 1.13 you should do the following steps: Turn off indexing on your old 1.12 site 1) Get a backup of you current live database by doing a MySQL dump. mysqldump -uuser -p -hhost database | gzip > backupofdatabase.sql.gz 2) Setup a new version of Magento with a fresh version of Magento 1.13.1 (on a new website) You can then restore ...


3

You don't have access to the entity_id before the account is created. What I don't understand is why you need this. As long as the attribute value is going to be HH{entity_id}, why not just create a method in one of your helpers that will retrieve that value when you need it. Something like this: function getSomeCustomerValue($customer) { if (!$...


3

Object,It is not possible First of all ,entity_id is auto increment field which value is assigned to Object after any Object Save. Magento did not provide to created this field to before save. If Magento is provide this feature then this auto increment field value is automatically increase in database whenever data is failed to submit. It will be ...


3

SHORT: It will work with some tweaks/fixes. LONG: It can certainly work. You'll need to fix a few things and make some tweaks but it's not that difficult. At CLS we've prototyped taking RWD as far back as 1.11 with pretty good success. For our work, we've dropped RWD on top of whatever relevant version of Magento and then started fixing bugs as we went. ...


3

core_session is being used to store sessions - this is a poor practice, rather use another distributed session store in multiserver setups to reduce load on the db (Redis, Memcached). If you truncate this table you will lose active sessions. Is it "safe"? Yes. Ill-advised, but safe. enterprise_logging_event_changes controls the EE event log. If you need ...


3

Looking at the files which are relevant for this, I can identify Varien_Data_Collection which is the base class and implements IteratorAggregate, so you can loop over collections using foreach($_productCollection as $product). It does so via the method getIterator() which mainly returns new ArrayIterator($this->_items); In contrast, a level further up ...


3

Using Z-Ray you can totally see if pages are getting into the full page cache. You can even trace down into the functions that run as it generates the caches. Here is a shot of z-ray in action, showing the cache being built: Now compare this to the following shot, where you can see that a lot of the functionality of z-ray is missing, but this is because ...


3

I verified this same issue exists on a separate project also running 1.13.1.0. Here is a more robust version of the above for anyone implementing this as a patch. This should be applied as a proper local rewrite of Mage_Sitemap_Model_Resource_Catalog_Category and Mage_Sitemap_Model_Resource_Catalog_Product, replacing instances of "category" with "product" ...


3

Firsly the model is now Enterprise_UrlRewrite_Model_Url_Rewrite: Mage::getModel('enterprise_urlrewrite/url_rewrite'); Secondly the options have changed slightly to. Options store_id, identifier target_path options description, category_id product_id Note: category and product id are optional only for category and product rewrites So assuming that your ...


3

You're 99% there. You need to call toHtml() on the block, and then echo it out to see the result: <?php // initialize Magento $rootPath = dirname(dirname(__FILE__)); $mageInc = $rootPath . "/app/Mage.php"; include_once $mageInc; Mage::app('admin')->setCurrentStore(0); echo $headerBlock = Mage::app()->getLayout()->createBlock('page/html_header')...


3

The problem was that payment/authorizenet_directpost/trans_md5 configuration was NULL. To fix this set an MD5-Hash in the Authorize.net merchant admin under Settings > Security Settings > General Security Settings > MD5-Hash. Then enter that same value in the Magento Admin under System > Configuration > Payment Methods > Authorize.net Direct Post > ...


3

Neither directly, you should execute cron.sh which in turn will execute both. Running cron.php directly without a sanity check will cause overlapping of crons, duplicate processing and excessive resource consumption. FPC invalidation of content is driven by the configuration defined in Enterprise/PageCache's config.xml.


3

The *_cl tables are the changelog tables. They log all the IDs of products,stock, etc. which are changed. A cronjob should theoretically update the indexes (async indexer) and then delete the entries from the table.


3

In the code I found app/code/core/Mage/Usa/Model/Shipping/Carrier/Ups.php // Shipments Originating in United States 'Shipments Originating in United States' => array( '01' => Mage::helper('usa')->__('UPS Next Day Air'), '02' => Mage::helper('usa')->__('UPS Second Day Air'), ...


2

I'm not 100% sure because I wasn't able to reproduce the issue but meaning an imposter can no longer impersonate a newly registered customer means that until now 'an imposter' could impersonate a newly registered customer. I hope it is just 'semantics' but I think it means what you fear it means.


2

This was confirmed as a corebug, Magento gave the patch and as stated they fixed escaping the js. You can just contact Magento for the patch.


2

I finally found my problem. This line in the SHOW SLAVE STATUS\G Replicate_Wild_Ignore_Table: mydb%.%\_tmp was actually preventing the DB user from dropping and creating the MEMORY tables. I made a change to puppet to remove Replicate_Wild_Ignore_Table from my.cnf and everything was back to normal.


2

I ran into a similar issue, creating custom rewrites (redirects) in Magento 1.13. I only saw them in the admin when I addressed the redirect model rather than url_rewrite. Here is a snippet of what I was using to set redirects on save of my custom entity. //check for existing redirect $redirect = Mage::getModel('enterprise_urlrewrite/redirect') ->...


2

Unfortunately, you can't buy default. And you shouldn't. See here a detailed description of the Gift Registry concept. Usually a gift registry is opened for a specific event and is sent out to the people you know and know you. So if you want to send the gift to some friend you should have his address :). Technically you can get the addresses of the gift ...


2

The Magento documentation on 'upgrading' is basically saying, install a fresh copy of Magento and migrate your changes and extensions across... This isn't upgrading and you really don't need to do this. An absolute must is a safe environment for the developer and store owner to test the upgrade before it goes live, but essentially follow these steps: ...


Only top voted, non community-wiki answers of a minimum length are eligible