the.rampage.rado

What's the payment method you're using?

Looks promosing! What will be the price?

This is how this mode works back from when PS was cloned. If you want a 'quick fix' - you keep your usual mode but you have to go in every product and select 'available for sell -> No'. If you want to hide 'user info' and 'cart' blocks - simply unhook them. I think this can be done with a qucik db query but I'm not an expert.

If you use it hooked to the side you can use TB version of layered. But I use it on top of product list for all my shops and the merge procedure is too complicated for me so I use the good old moded version that comes with latest WH.

Warehouse seems to work just fine with php 7.2 and TB 1.1.0 if you fix one file and follow the steps in the 1.1.0 topic.

OMG, I knew I'm missing something!!! But why I have made changes to product.tpl and many others over the years and I had no issues with "Never recompile template files"? Fix: - change the order-carrier.tpl file as described above. - in performance set "Template compilation" to any of the later two options. - enable caches - turn back to 'Never recompile template files"

I did disable all caches, cleared them from backend, then manually deleted all the rest files in /cache/smarty. Also disabled cloudflare (put it in dev mode) and used chrome in incognito mode to try and use OPC. Then tried ctrl+r and f5 to probably refresh it's cache if it's stuck. No luck with all this. This is on php7.1 if it makes any difference. Tried php 7.2 - works just the same - error 7.3 - db link error

Exactly the same - no change at all. Like the file was not changed.

Hello @smarterweb just compared your version - it's the same as mine and it's not working for me. @datakick also tried to help with the same fix but with no luck.

Can you send me a link in PM?

Again no luck for me. Can you attach your fixed file so I can compare mine with yours. Probably I'm making some lame mistake. I've turned 5 step checkout but it on it's own have some issues and I would like to return to OPC.

I tried with latest firefox and latest Chrome both of them have no issues displaying the captcha in account creation with the following settings: 1. TB side of things - only account creation, 1.1.0 and Warehouse and on other websites - edge before 1.1.0 and Warehouse 2. module side of things - yes, 0, 0, 0, 0, yes till the end. If you switch to any number above 0 on Login attempts the captcha is shown but ignored - I had the same issue with the module - lots of Russian bot regs but it is a known bug since then. Think @datakick found out. it should be fixed soon.

Probably try to disable/clear your caches before the update?

Yes, sorry, this was a known bug and you've found the solution. :)

In most of these modules you won't see the change (it's internal documents/licensing/etc). Some of them are bugfixes and few of them introduce something new. I don't remember any of them to have any change in behaviour so I don't think you should be afraid to update. BUT YOU SHOULD MAKE A BACKUP OF YOUR FILES AND DB FIRST!!!

I'm reffering to this fix:

I updated to 1.1.0 with latest warehouse but I experience the bug with OPC and the fix does not work for me? Can someone help? It seems I have issue with order-opc, not order-carrier - It's exactly the same issue but strangely this will not fix it.

Is warehouse compatible with 1.1.0? I have some free time these days to fiddle with my shops but can I update safely?

By default TB uses white background and it does fill the image you upload to the specified pre-configured dimentions and ratio with white. If your images have different background color I remember there was fix for that also and it can be aplied to TB aswell. So - go ahead and investigate the option to use TB for your project, I believe you won't be disapointed. :)

Can't you put this code in html and then display this html with the content module?

They are not visible as updates in Modules. Also coreupdater disapeared. Yesterday I was able to update one of my shops but today it's missing from the rest.

If I find time in the following days I'll run few tests. I mean if there are 2-3 commits of fixes in the theme can this be patched are released in the wild as 'unofficial fix'... I'm glad that at least Panda's dev is here and support his clients and the project!

Yes, I know 'he's too busy making big bucks supporting for 1.7' and does not want to make new item and sell few more licenses for TB. If the needed changes are small can they come from the comunity? I believe the theme should keep some form of support because together with Panda it's the most used theme for TB. Any plans for beta stage, final release for 1.1?

It should not be compatible or should not break the compatibility? Because if you update smarty there were controversial opinions if current themes work with the new version you choose. If I remember this was the main issue and you said 1.1 will break some compatibility exactly because of that... Or plans have changed since?