the.rampage.rado

Just updated the store to edge and did the same checks again - some items worked but most gave 403 for the product images. I moved the watermark code to the end and now every image loads in BO->Products. The save 403 issue in SEO persist no matter if I disable mod_security in htaccess or not (obviously forbidden by my host).

@datakick, today at work I saw your fixes in the module and it was one of the first tasks today to update and check if it works. Unfortunately when the module code is added to the front of htaccess file it gives again the same 403 in product images. But if I move it to the end of the htaccess file they are working fine. The issue with 403 in SEO settings save is persistent. And by just testing it twice I got locked out by modsecurity. What settings are triggering it and what is the issue that makes the pictures work only when placed at the end of the file?

What do you mean by 'uploading images with the old name'? Your product image descriptions include your last domain?

In the end did you receive such fraud payment or they simply said 'i can do this!'?

Do you have stock available for this product. This is a strange bug. Please, share screens from BO and FO!

I think this issue was .htaccess related. Today I noticed that all my images are gone (no changes from my site, probably something from the host) and I deleted and made new .htaccess file. Now it works. Also the original file was not shown in the section in BO. Cleared all caches and everything is OK once again.

Same here. PHP7.4 Litespeed server

Does editing the source code at the checkout page and sending a screenshot to the merchant count? 😄 😄 😄

Same here, not a pain in the ..... but it was working few minor versions ago..

How would you ban by mac address from your shop? 😄

The first issue is not an issue if you have not manually modified them - just update. The second issue is caused by the cache probably. If you click update the first reload might show the old version? They updare corectly or not?

Please, tell me you have barcode scanner with the camera and then stock check option using it and I'll love you! :)

Are you comparing your dashboard stats to G Analytics? If so, please update to the latest edge version and you should see a decrease in the dashboard stats because they used an old mechanism to detect if certain visitor is bot or not. If your site is newer it's normal to have lower conversion 1 sale in 42 real vistits is not bad for start. Of course as a sidenote I would say that high drop rate might be caused by many things and you must observe for patterns.

@smile - can you elaborate on that a little bit? So you're planning an app that sync with our shop so picking and warehousing is easier? If so I have few ideas.

I mean under BO-Preferences-SEO. But this is very strange 'fix'. Probably you had some misconfig in .htaccess and swiching SSL overwrote those rows there. If you have any further questions we will be glad to answer (if we can)! 😉

Share your SEO config in backoffice. Do you see those redirects only on the said pages and do you use multilanguage?

Honestly I will stop trying to advice anything. Make 10 threads a day and talk to datakick only and don't take any further advice...

Are you sure you run redis and the extension is active? It's not visible in php info. Also try running apcu, probably you have free memory and it's slightly faster. Full page cache is broken - better turn it off!

As I advised in other topic - can you share your Performance configuration?

@datakick as we're speaking for php configurations here can you share a guidance on which db drivers to use in order to gain every little bit? Also what extensions are needed for TB and which ones we can safely turn off (other than opcache, apc, imagick, etc...)?

You're not changing it at the right place obviously. Turn on profiling and it will show you 128 mb memory.

I think you confuse the class with the product attributes. Neverthless - just keep your shop on php7.4 for time being. The proposed fix is a demanding job.

The module works great. No need to put the code by hand. Try reinstalling the module and clearing the cache.

Why don't you cron a purge operation at certain intervals with file system?