Recently I ran into a problem regarding Re-index in Magento.
My store has around 40,000 products and If I change a status of a single product, changes are not reflected on frontend as it needs reindexing of all Indexes.
Moreoever reindexing takes a hell lot of time (around an hour) and I am thinking of a permanent issue.
What does "Save on Update" mode in Reindex specifies ? Does it help in reindexing while saving the product ?
Whats the difference between manual update and update on save ?
Please help.
Thanks in advance.
I assume you mean "Update on Save" when you say save on update, also called as "realtime" mode which triggers the re-indexing of product data every time the product has been saved / updated.
Basically in Magento there are only two modes of re-indexing "Update on Save" (Realtime) and "Manual". Their names speak their mode of behavior quite clearly.
In your case, as you have huge amount of products in your store, do the re-indexing through Magento SHELL commands like the following which in turn saves you a lot of time.
SSH to your store and go to shell folder inside your magento root and re-index one by one or all in one shot
php indexer.php --reindex catalog_product_flat
php indexer.php reindexall
Use the "Update On Save" re-indexing mode, it will do re-index on the fly for that single product you have saved.
The magento manual (http://docs.magento.com/m2/ce/user_guide/system/index-management-manual.html)
States:
Set Actions to “Reindex Data.”
Its too bad the options are not available! Do you see those options in your admin pages? If not, is there a reason why it might not show up?
I would like to do update on save, but this is not really practical. I imported a large number of products from CSV.
I tried running the re-indexer from the command line, but by shell directory is missing.
magento missing shell directory
Well, it looks like I am fresh out of ideas! Maybe I should just pay Varien to run Magento Enterprise for me. Afterall, re-indexing is a bit complicated, isn't it?
Related
I'm developing a Magento store and there is a guy that manages the store, we were transferring the store to another domain but the old one was with all products.
The guy went in advanced configurations and disabled all modules in the old Magento installation, even the Mage ones and now the initial page is white and the admin is too, what could I do to solve this problem?
The version of Magento is 1.9.1.1.
So, he disabled all the Mage modules, including REMOVE ENGINE ie Mage Core?
Hmm...
Ok, here's what you do.
Use phpMyAdmin to open core_config_data, sort table by path and look for all the paths beginning with advanced/modules_disable_output/Mage_ and change the value from 1 to 0
Then delete all the mage--? subfolders in var/cache/ so Magento is forced to reload the configuration data out of the core_config_data table.
This should put your engine back in so the old jalopy will run.
We have a Magento site running on version 1.7.0 on the Argento theme that seems to be having intermittent issues with products not appearing. This appears to happen on certain pages and not others.
For example, if you add a product from the homepage or single category pages, it will show immediately as being part of the cart (note, Argento uses AjaxPro for the cart). However, once you navigate to another page, say "My Cart" or "Checkout" the total will show as zero. Doing a hard-refresh on the browser will update the total.
Additionally, if you open the Chrome Dev tools, navigate to "Network" and then check "disable cache" everything runs perfectly.
Things we have tried to resolve this:
Flushing/Clearing/Disabling the Magento cache. Seems to make things slightly better but doesn't clear up the issue.
x-cache-control meta tag. Same as above, issue seems to be less frequent but still definitely appearing.
Turn off AjaxPro. Our initial belief was that this plugin was causing issues, but turning it off has no effect.
Re-Index. Has no effect.
Added $.ajaxSetup({"cache" : false}) at the top of our scripts. This also has no effect.
Any advice or tips on where to look next would be appreciated.
It turns out that our hosting provider had set up the installation with the sessions stored in memcache. We switched this over to file storage in our local.xml and it fixed the issue.
We've recently noticed that only the items in the root folder of a category will show up in the New Products block on the homepage and as results via the Search Box.
I've tried flushing the cache, re-indexing the tables and I've double checked that my date ranges are correct and all items are in stock etc.
Any ideas on how to solve this?
Ok so here's the solution.
It's as simple as disabling the required products and then re-enabling them.
TIP: If doing this in bulk, do NOT do 200 products at a time as it will freeze and you may be locked out of admin. I had a hair raising few minutes by doing that. I restarted my machine and then all was well again.
I have managed to make a csv which imports my products using magmi into my magento store.
All works well but the buy now buttons don't appear unless I go to the product and click save.
I've tried reindexing or clearing the cache but nothing seems to work.
Any further ideas.
I'm using the up to date magento/magmi.
Thanks
Richard
In the importer check the reindexer and the on the fly indexer.
That seems to do the trick!
Richard
I was finally able to upload product images to a website using magento 1.7.0.2 but the images only appear on the front end and not visible via admin panel. I find it rather strange. Can anyone please tell me how to fix this? I have flushed the cache and reindexed several times but no apparent change.
I know this is an old question, but we had the same problem just now.
It seems that the import we did (the .csv file), missed a few fields, therefore entries were missing in the media_gallery table in Magento.
We couldn't repeat the import again, because the customer has already entered new and fixed a lot of the imported products.
We followed the guide here (thnx MagePsycho) to get the things sorted.
The guide needed a litle bit of fixing (manually entering the table names) since we were doing the fix on Magento 1.8, and had a bit of trouble with the table prefixes.