the.rampage.rado

Search only means "search in the shop". It does not mean Google search. Tried and tested this - they don't get indexed by Google.

Nope, after updating to edge it should appear in modules list. Do you have thirty bees Updater installed?

You are probably are missing the html templates.

If you look back in the thread you'll find solutions for 'edit' button visible all the time and the country selection removal. Another thing I was thinking was the options of products are not visible in the cart during checkout. It would be nice to have some truncated features/options there.

Install the TB recaptcha module. Also you can lock your folder with a password - they have to bruteforce this password first, if it's strong enought this will cause some server load but not as much as having your admin open to the public. Then you have google's recaptcha, use 'strange' admin email (NOT admin@, sales@, office@ john@, etc) and strong password. I doubt anybody will be entusiastic enough to go through this.

The theme have totally no connection with Core Updater. Could you share the module page when it errors out or you're currently locked out of BO?

You have to have both thirty bees Updater (communication between your site and TB module store, nothing to play here, it works on its own) and Core updater (where the most of playing is) installed. If you had some migration modules from PS you have to remove them as they are not needed.

There are few bugs in some modules but the main advantage is the stock sharing and process management is centralized.

Are you over the set character limit for desc field?

Yes, If you need those. On my first shop in the times of PS1.5 I started with ASM, and recently I switched if off. We're waiting for @datakick's work on the area and the stock inventory module. This will make it complete stock solution. Currently it lacks vital aspects and there are some bugs and quirks (as creating 2 or more orders visible to the customer if the items in one's cart come from different warehouses. This is a feature not a bug. Me and my clients are not enjoying it).

ASM needs more work. It's working but with few faults. Packs in 1.4 and later are working w/o ASM - they automatically calculate pack stock based on pack parts quantities.

Then report to USA so they could finally come to the 'normal' world with dates, time and measures. 😄

OK but this is the 'column' block so basically we were right but you fooled us the whole time! 😄 😛 😛 I saw your initial screenshot as part of your footer. 😄

As last suggestion did you try this from my previous post: ?

Look for "CMS Block". @e-com's solution is the right one, not mine.

Did you clear your caches after the module was uninstalled? The link is shown by this switch: Preferences -> Store contacts -> Display in the footer. When you turn it off, clear your caches.

Where are you seeing them?

In settings part of the modules you can choose target php version. Or leave it on "server version".

I would not buy anything ruzzian these days. Security and moral-wise.... And never use yandex for anything (OCR service, search engine, etc) - they are really closely tied to ruzz gov...

If you don't want to send them out as attachments you can change the templates you want to use and send a link. If you in future change the T&C just change the version number (like T&C-1.1.2.pdf) and leave your old pdfs on the server so the customer are still able to download and check them if needed. You can upload the .pdf s in /downloads/ or make custom folder just for this job. I had 'brochures' back in the years, but I was displaying them in FO.

First of all sanitize your admin folder because it's visible. Currently at what version of TB are you? I believe I was running on 7.0 and 7.1 up until 1.3 so it should be working. You can try setting the update target to Custom target then select 1.2 or 1.3 when you update and see if you can update to this versions first?

At least you have some clue what's going on. You are out of memory. Regarding modules and theme most of them should work OK up to php 7.4 but there will be many notices and deprecations thrown. But this is a problem after your update. Once again @datakick offers paid work for fixing modules.

What could help is to play around with the host settings: max_execution_time max_input_vars memory_limit post_max_size Increase those and try again. Also you can try different php versions - try 5.6 for the migration only. If it works revert back to 7.1 after the migration. Then update gradually to 1.3 put your php on 7.4 and update to 1.4 or edge. @datakick could say more precisely what version was the first non 5.6 compatible. AND ALWAYS KEEP A WORKING MANUAL BACKUP!

@datakick - how can I achieve the same behaviour? Is it possible at all at the moment?