Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 27967

Magento Community version 1.9

2
votes
Then don't use PHP7? Magento 1 is not compatible with PHP7. Inchoo's module can help https://github.com/Inchoo/Inchoo_PHP7 but in the end you would need a developer to help port needed modules to PHP …
answered Sep 4 '17 by MartyS Magemojo Support
1
vote
They could be stuck, check var/lock and clear the lock files in there, then restart the indexing via shell to monitor it.
answered May 10 '17 by MartyS Magemojo Support
2
votes
Depending on Apache versus Nginx you will end up with different rewrites. But I would make a vhost for subdomain, first. Then put the rewrite or redirect under that vhost to go to the proper sub-pag …
answered Sep 17 '16 by MartyS Magemojo Support
1
vote
This could have several causes, and its possible a module its interfering. Have you added any recently? Try disabling all of them but the Magento defaults and see if the problem goes away. It could …
answered May 28 '16 by MartyS Magemojo Support
1
vote
Try using magmi, it might work well for you - http://wiki.magmi.org/index.php?title=Main_Page The default import is not the best.
answered Sep 15 '16 by MartyS Magemojo Support
0
votes
This is because the cleaner depends on information in log_ tables to be related to report_event so it doesn't just do a delete from across every table, something like this: sendto(4, "\370\0\0\0\3SEL …
answered Jun 24 by MartyS Magemojo Support
-1
votes
Assuming you have everything else set up correctly, your Nginx server block should probably be more like this, as a complete example. This case is using PHP-FPM though - server { listen 80; serv …
answered Sep 16 '16 by MartyS Magemojo Support
1
vote
500 errors should be in the webservice error log or possibly a PHP error log if you have one. It could be any number of things and its impossible to diagnose from the frontend, unfortunately. HG supp …
answered May 28 '16 by MartyS Magemojo Support
2
votes
Try using n98 to view the cron history and confirm its not being missed , you can also use it to run the manually and confirm it works - https://github.com/netz98/n98-magerun And change the cron.sh t …
answered Jun 6 '16 by MartyS Magemojo Support