the.rampage.rado

1.4 should work on php7.4 but push some notices. When you update to 1.4 you could try and update to 1.5 edge on 7.4, this will clear almost all core notices but you'll have to fix any theme/external module ones in order to proceed to php8. I had an issue with cart module tpl files in Warehouse theme, they are fixed now but I'm still not updating to php8.

There should be no breaking changes regarding the theme when updating from 1.4 to 1.5 edge and soon to 1.5 final. There are some inner working 'fixes': Mailer functionality was extracted from core and you should duplicate your settings in one of two new mailer modules Code minification also was extracted from core and you should install the new code minification module (no adjustments needed here), all settings continue to be in Performance tab. You should uninstall tbupdater (not core updater, it should stay), now it's not needed as the module update mechanism was changed and moved to core. Other than that - plenty of performance, security and futureproofing changes that I'm sure you will enjoy. Keep an eye in your error collection module - you might have few notices there but there should be no exceptions.

I gonna post this here as there's no need to swamp github with probable non-bugs. 1. I added second shop to my installation but it was not picking the correect PS_SHOP_NAME. My db was lacking this record despite having the name set up in my BO for the second shop. After adding it manually to ps_configuration with ID 2 it is showing in the end of each page title correctly. 2. My db also lacks PS_SHOP_DOMAIN and PS_SHOP_DOMAIN_SSL for the second shop, despite them being added and visible in BO too. Should I have them in ps_configuration too?

What ThirtyBees version are you rocking?

Few things had to be change in order to allow php8 compatibility and move the project forward. Other than that each and every PS1.6 module I tried this year (I'm using always the edge TB version) has no problems. Of course some 'edge' cases like powerful modules that manipulate stock or other aspects will be affected but I believe if those are so important you might pay additional funds to fix them for TB. TB becomes better and better each day!

@wakabayashi thank you! Any plans to implement this for BO login as we discussed before?

Yes, so probably it's a server issue on my side... 😕

Probably you are correct, looks like this to me too. I'll try to troubleshoot myself and if no luck will get back. Thanks!

Thank you! So you could reproduce this? Regarding my use case of media servers - as you said I only use them for cookie-less delivery of static files and this setup saves from sync issues. Literally all static files are loaded by the media server that way. Could we manipulate those headers on app level or they should be configured on server level? I'll make a github issue later, just want to google little bit more in order to try and find possible fixes.

Hello, Something strange happened yesterday. I updated my store to the latest edge channel and went in to do some products. When I went to see how they look in FO the website was lacking css and js files so only bunch of text. Quickly went back and checked if this is related to some recent change I made but I failed to find something. The error is Cross-Origin Read Blocking notice and it only appears in Chrome (both desktop, mobile, 4 separate devices). It is shown because I use media servers feature. When I remove them everything is working correctly. Not only js and css are blocked but also webp, everything that's loaded by the media servers. Could any of you reproduce this error? I think it's not related to recent changes as of yesterday because none of those are related to this. If so what could you offer in order to fix this issue other than not using media servers? Is this option viable solution in my use case? I have 2 subdomains (s1 and s2) that point to root of my site. That way when TB adds new files (images, css, js) there is no need to sync those per hosts. This worked few years back when every speed test online showed recommendations to less files per host to speed the loading times. Is this the same today? Do we need the media servers and is there any viable speed improvements in your test? Is my setup correct (2 subdomains pointing to the same host)? And if they still give a boost in loading speeds how should we handle this issue? I believe it's a recent addition to chromium but everywhere it's said that this should not break any website, despite that mine is pretty much broken. Edge displays the page correctly but still shows these warnings. https://chromestatus.com/feature/5629709824032768 https://anforowicz.github.io/xsdb-demo/index.html EDIT: and here is a recent addition to chrome 105 (despite that I'm using 114 and it worked yesterday): https://chromestatus.com/feature/4933785622675456 that says everything will be blocked if there is no proper configuration in place (ORBv0.1 blocks all range request responses, unless they come from a URL that ORBv0.1 has earlier recognized (via sniffing, or via mime type) as audio or video.)

Most themest use same code structure in this area, so code could be migrated between themes and with little css hackery things should be fine.

@led24ee very nice suggestions! I like them! Also I would find very useful a table display of all combinations in the product page - those that are not available to be greyed out and those that are available to be selectable. Of course those changes would require theme adjustment.

Here's a google result for exact same error but in Laravel. https://stackoverflow.com/questions/30182984/sqlstatehy000-2002-php-network-getaddresses-getaddrinfo-failed-name-or-ser TB is not able to connect to the DB server. Please, check your settings!

Let's lock this one and continue in the old thread? Is this OK?

What theme are you using?

Regarding those you should be able to translate all front office lines in Localizations->Translations->Front Office. There you translate the majority of well coded plugins, errors, themes, etc. Regarding the browse button I've disabled file uploads but I believe it's text is displayed based on the customer's browser localization settings. If I'm wrong and this is not the case you should also be able to find a string with 'browse' in the same location above. Best regards,

Clients -> Contacts -> edit each messege here in any language you like

I believe that @Smile and @datakick could describe the module best and what could be achieved.

Hi there! The summer is time to relax and unwind (at least here in Europe 😛 ). But it could also be a time fore new ideas. We know that you use TB as part of your business and this gives us hope that you like it. We would like to know what you think of the project so far and ask you for ideas on how and what to implement so we (as a community) could make it better! I tried to gather the most recent topics that floated in the forum, but if you have some nice, new and powerful idea please reach out and I'll edit the pool. Don't forget about our marketplace where you can support developers involved in the project! The core developer team also has set up a backer support platform where you can vow some small (or not so small) amount per month if you like to support the development of the platform! Developing and troubleshooting takes time and resources! Best regards, Rado

I believe he's on 1.4 and the module is not needed there.

Does it happen for each product after that? EDIT: If I remember correctly at one point your hosting plan's storage was full. This is not the case anymore?

As Peter said above - this is most likely a browser/browser cache issue. So please try with different browser or clear cache of the current one and it should be OK. This thread is as old as me but this error is not showing to me currently.

You can check if the suggested fix for this Coreupdater 'issue' in datakick's answers helps showing the correct version and showing the updates:

What happens if you choose your correct php version from the dropdown?

@Uncle, as a start - you have switched to php8 and your TB code version is build for 7.4. You can fix that in coreupdater's settings by choosing the proper version or simply leave it to 'server's version' and check for core updates after every php switch. Please, install error collection module that is shown in your module list and check what error is given there. (you might see some notifications in connection to php 8.0, nothing to worry about if it's not an error.