the.rampage.rado

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?

Are you sure you have exactly the correct API activated for the certain domain permissions? What is said in the browser console?

Just tried your settings - those products are not visible in the sitemap. Why and how will then Google bot reach them?

Preferences->General The Google Maps API is 'free' for up to xxx USD per month but you have to register and activate it. You have monthly credit of xxxx views.

I'll try your setup for few products. What if I have 'available for order' set to Yes and I have no stock? I believe nothing changes in FO?

Might be a long shot but do you have pouplated with your key?

Hello, Many times when I search for sports goods from previous years I open up sites that list those as out of stock and they are hidden in the normal product listings. But google sees this "half-inactive" product and shows a result. I click and open this site, otherwise I would not click this result. Currently I set all old collection items to available - NO and I make 301 reddirect to analog product. So after some time I lose all those results in google. In your opinion what is the best config for such products? Availability - Yes Visibility - Search only or should I continue to 301 to new products? I'm even not sure that the first scenario will result to the same behaviour I described in the start. If I enable search indexation will google 'search' for some products in order to get to those hiden products that are only search-visible?

No issues, not a single commit is reverted in probably one year. Few new minor features and many, many fixes and code improvements, plus as I said couple of security fixes. EDIT: Just keep in mind one quirk in this update - email transport functionality was moved to a module. Nothing is changed but you have to install the module and configure your shop to use it. After update to currentedge there are couple of db fixes aswell. 😉

A quick question.... why don't you update the whole store? Just in the last 2 weeks there are 2 security commits.

Make a file and db backup and update to edge. It should be fixed in to-be-1.5. https://github.com/thirtybees/thirtybees/commit/b13ae185818fa83bb65813fc58bd64a159e36e9f

Currently it's not possible to use layered filter in the search results. It was raised couple of weeks ago and will be soon fixed for the official layered module (soon = sometime in near future as more pressing issues are in the que).

For sure, that's why it's good to have the list of returned articles (categories, products, etc) sumarized in one place so the merchant could go in one by one and fix, add stuff and then populate the new copy in the db. Could this be done? If we don't know when certain product desc was generated we would have to go in one by one and check. Also what happens if we have products that are optimized, can we blacklist certain product IDs that should never be sent to the bot?

What I noticed (at least for my sites) is that google likes not only plain text but tables, bullet points and images in the text. Probably as you said it will be best to just come after the bot and fix few such items, like include a pic, video or table with specifications.

Looking nice! How is the que organized? Can we send requests for some categories only? What about multilanguage (I see the dropdown). In Bulgarian the bot is tragic but hopefully it will improve overtime. You said it takes 20-40 seconds for each query, then the result is saved in the local db, right?