the.rampage.rado

Buy Warehouse from Themeforest - costs pennies for what you can do with it. The latest 1.6 version works just fine with 1.0.6

The quick menu is working it's magic but it fails to give you warning about your current setup. It could be just like the maintanence mode - if it's on - give warning. That way we can receive notification if those two settings are not ON. The rest of the options in Performance are just additions and give little trouble when editing is in force. Sometimes I fail to update my translations with cache on, CCC never does any trouble and when it's set it's set for good, media servers are the same, template compilation too.. But as @dosbiner said - it will be nice feature for the future not high priority, we're just chatting... :)

I had to install the module couple of times but now the URLs are working again. No edits to the code. I had problems with the URLs and the posts giving 404

@lesley - yes, I forgot from where I learned it and thus failed to give you credit!!! Sorry! It's really good addition.

I think they will not boost any performance. Only if you're on the modules page in BO they get scanned so the gain (which I believe is very low) is only visible there. @dosbiner - thank you for your suggestion, I'll give it at try!

Thank you!!! Also - one more thing - how I can automatically exclude .md files from uploading with Filezilla?

Oh you mean on theme install.... Hmmm strange... I can't test that now, I don't have clean setup in fron of me.

I believe I can but just to double check: - block currencies - I only have one currency - will it affect the core if I remove it from server? - block search - I use theme provider's search box - community theme configurator - I don't use this theme - theme configurator - what does it work anyway, never installed it? OK to remove? At the moment I have 43 modules installed - most of them are theme related.

Yes, this would be awesome! Like little red/yellow/green lamp. Where the different colors show the following conditions: - red - all off - yellow - smarty on, caching off - green - smarty on, caching on And little popup notification on mouseover with short description on what does it mean. On click - referral to Performance page. Honestly 50% of the time I have to turn off my caching (when translating or editing front end) I forget to turn it on... :) This will really help!

Did we find solution for SimpleBlog URL issue? Best regards, Radoslav

Just installed 1.0.6 and WH 3.8.7 - no errors or white screens on module install. Please can you tell me what module does you trouble?

I want to use this: ```php/* Debug only / if ($_SERVER['QUERY_STRING'] == 'error') { define('_PS_MODE_DEV_', true); }else{ define('_PS_MODE_DEV_', false); } / Compatibility warning */ define('_PS_DISPLAY_COMPATIBILITY_WARNING_', false); if (_PS_MODE_DEV_ === true) { @ini_set('display_errors', 'on'); @error_reporting(E_ALL | E_STRICT); define('_PS_DEBUG_SQL_', true); } else { @ini_set('display_errors', 'off'); define('_PS_DEBUG_SQL_', false); } if ($SERVER['QUERYSTRING'] == 'profile') { define('PSDEBUGPROFILING', true); }else{ define('PSDEBUGPROFILING', false); } ``` in my defines.inc.php but when I replace the coresponding lines in the file I can't install modules. It gives 'this functionality has been disabled'. I would like to use this function that way instead of the BO option because it quicker and more convenient.

Yes, I can confirm that running w/o full cache TB is times faster than PS... So don't worry - they will fix it soon and it will become even better!

ZenCart is dead from at least 6-7 years. You should have migrated to PS a long time ago -> lots of lost customers...

I've migrated one store and installed cleanly one other - no issue on both with 3.8.6 and 1.0.5. I don't know about 3.8.7..

For me supporting 7.1 is enough but if you want to present this CMS as more advanced and more modern than 1.6 then this have to be done. If you have few issues with the most used themes in the marketplaces I can't imagine that those issues can't be ironed out in few hours and then everybody can use the latest and greatest php with their current themes. I know that iqit is refusing support for Tb for now but I can't imagine they will stick to this opinion much longer if you gather community. And how you can get more users - it's important to support the newest versions of all parts of this platform. And why do you wait for 1.1.x to start removing legacy (before 1.6) code from the core? Also the full caching needs some fixes and more testing. And probably the most important part is trust in you - people should know that if they migrate their shops will have life ahead without need for custom migration to another system. I think that currently the trust is not very high as one of the first developers is not getting around and the fixes done in the recent versions are more cosmetic than bugfixes and improvements...

The 128 mb issue is server related - contact your host and they will fix it for you. PS/TB has no control over it. But in any case - you're running your shop with toooooo many modules!!!

You have emails in each theme also - they get used first.

Why you run with smarty compilation : auto?

Run your setup on php 7.0 - it's completely fine as when running on 5.6 but the speed is really good... 7.1 and 7.2 still have some issues here and there with tb/ps

Just use https so you can use http2 and enter once ot twice the full url in the bar and then the browser will keep it...

https://github.com/thirtybees/thirtybees/issues/558

https://github.com/thirtybees/thirtybees/issues/558 - I've made this issue because recently stumbled upon this issue... Please vote for it...

For me the test works but the contact form can be filled be not publishing the captcha. The other forms like login and admin login are working as normal. I had tons of russian spam and had to install another module. Probably this otherwise perfect one have to be checked for bugs. I can offer my shop if you want to see the issue i describe.

@mockob said in Say hello to release 1.0.5!: You are completely right @doclucas! I hope you will decide to stay on the project and participate with your skills, because developers are what the project needs most! With all my respect to all that participate with code, I think the project is going to die really soon without the main person behind it @mdekker The reason for the recent bugs is mainly because the developers currently committing code are not so familiar with the core and make some unintentional errors. And I think it is time for clear statement from @mdekker if he will continue supporting the project, because many are worried even if they don't say it aloud. I think he's very busy. He's still contributing in the modules of TB but I can imagine he's busy and thus not so active here and on the main repo.