roband7

This was covered here: https://forum.thirtybees.com/topic/302/duplicate-friendly-sub-category-urls-from-within-different-categories Looks like there might be small bug in the PS migration, that it forgets to setup the admintab for this.

With clean URLs builtin to thirty bees it´s probably best not to use addons doing the same thing. I´m no saying for sure that´s what causes your problem, but it might be.

Ah, yes, sorry, I forgot about that one symfony package used by thirty bees and your comment about PS 1.7 themes confused me. Did you have have an override for PHP maxexecutiontime in your 5.6 php.ini? If yes maybe this override is missing in your 7.0 php.ini? 30 seconds is the default value.

Symfony and PS 1.7 theme. This looks like a Prestashop install, not a thirty bees install. Wrong forum?

@lesley said in How to add interesting new features to thirty bees while staying PS 1.6 compatible?: Which themes? I have been doing as much outreach as possible with companies trying to get support. If we get the attention of iqit-commerce (Warehouse), tantan199 (Transformer and Panda) and MarekMnishek (Alysum), then a lot is covered, that's the top 4 bestsellers. These are all pretty much one-man-shows with limited time to support both 1.6 and 1.7. And all three have now put loads of hours into new 1.7-only functionality. Their 1.6-based versions will of course continue to work fine with thirty bees.

A new development that further complicates this: The top four selling themes on Themeforest (Warehouse,Transformer,Alysum,Panda) have all recently released 1.7-only updates and have 1.6 in a next-to-nothing maintenance mode. The updates are massive, with loads of features many shops could use. I understand the theme writers, they´re in the same boat as PS, they depend on new module sales to survive. The theme writers also claim they have an easier job adding new stuff to a PS 1.7 based theme than to an 1.6 based theme. It would be interesting if we could get more technical details here. As long as PS stays alive somehow, and as long as thirty bees is still small, I don´t see the big theme writers porting these themes to thirty bees soon. I know @Traumflug has done some work on support for 1.7 themes, but far from finished, it´s hard work.

Your theme will have take responsibility for most of these tags. You don´t want to step on its toes. When adding your own blocks like this I agree with @wakabayashi , use

Most likely it´s a filesystem permission issue. The migration module should of course have given a more specific error message. The server-side logs might help us find the underlying problem. This also makes it easier to improve the migration module.

That error message is just a notification that something went wrong on the server. Do you have access to the server-side PHP log and can show us what was logged there? If this doesn´t make sense, perhaps ask your hosting provider how to see the PHP log?

I've never had any problems with the disqus login. It's the thirtybees login method that doesn't work.

Remember to also test all this on a product with attributes and then change attributes on-the-fly. There's a lot of funky dodgy looking stuff in the updatePrice() function in community-theme-default/js/product.js

I can confirm this, have the same problem. Only way to comment the blog articles is to login using another method than thirtybees.

You say all your code uses https: but in the code you pasted there are still four requests using hardcoded http:

I´m not sure I understand. You write you started with https:// and still got complaints about insecure URL, that doesn´t make sense. Are you sure you don´t have other places than the one you fixed still doing http:// Btw your fix changing this into just // is the correct fix. I just think you might have missed a place.

Those are all external resources. You cannot change their expiration date. Not much you can do about this.

It´s good to do this exercise once a year or so. The credit card processing fees and rates are in a rapid decline these days. I remember a few years back when rates were in the 2-2.5% range. Nowadays we´re paying 1.2% and just had an offer from a new credit card acquirer at 0.9%.

The Omnipay website on https://omnipay.thephpleague.com/ looks like it´s not well maintained. However the source repository on https://github.com/thephpleague/omnipay is still active. So it appears the project is still alive and well from a coding point of view.

FWIW there are some ASM fixes in PS 1.6.1.15 released a couple of days ago. Dunno if they´re any good, but might be worth a look.

For an alternative view on AMP: https://www.theregister.co.uk/2017/05/19/opensourceinsidergoogleampbadbad_bad/

Just for reference, in another project, not related to thirty bees, I implemented an ES based search on top of a database with 180 million records. The ES instance ran just fine on a 4GB low-end server. I think you´re way overestimating how much CPU and RAM is needed for ES on top of thirty bees.

@lesley said in Let's talk about Search!: I have just posted an article about crowdfunding modules, we are going to go ahead with it, but we want the community to be able to vote on which module we pick to test the waters out. You can read the article here, https://thirtybees.com/blog/crowdfunding-modules/ We would be willing to fund two of the suggested modules, but the vote didn´t allow picking more than one, so I picked the most important one for us.

@Traumflug I think perhaps you make ES into something it isn't. From a license, deployment and technological point of view it's basically comparable to MySQL. Meaning you could more or less take all your questions above and replace ES with MySQL. In other words we're not talking about ES as a cloud service, but as a locally installed piece of open source software, just like MySQL.

@wakabayashi said in New theme modules for 1.1.x: @Traumflug said in New theme modules for 1.1.x: Not front office, but anyways: review this large set of statistics modules. IIRC some of them require collecting traffic in the database, which virtually nobody turns on. Stuff like shown on the dashboard page is still interesting, no Google Analytics can show how many products were sold or how many purchases are waiting for being processed. Finally somebody, who says it! I hate this widespreaded opinion, that GA can handle everything. It's helpful to improve your site, but it doesn't tell you a lot about your core business.... On the other hand this area is just too big for thirty bees to reinvent the wheel. I'd rather see us rip all the useless builtin stat stuff out and do a kickass Piwik integration. Piwik runs locally, so it can get a lot tighter integrated than GA, has no privacy and loss of data ownership issues, also comes with plugin support for custom integrations etc.

@Havouza said in New theme modules for 1.1.x: I have said from beginning that the big test for tb will come the day it breaks backward compability with PS. When that happens there must be enough modules and themes, native or commercial to satisfy the merchants. If not they will not switch. To think they will have to because PS problems, well perhaps but again, there is a LOT of alternatives out there I just started a separate topic about this. It's important.

I've been thinking about this, it's an interesting technical challenge. We need to define exactly what it means to be PS 1.6 compatible. The lack of defined APIs makes this a vaguely defined target. Areas for consideration, modules: * The basics of a module, ie. what's needed for a module that does no core class overrides, should be easy enough. * Core class overrides, it's probably just impossible to support it all forever, perhaps inspects some number of the major addons out there, see what's used in practice? * hooks * more? Areas for consideration, themes: * Template names assumed by the core * Smarty variables passed to these templates * Globally available smarty variables * more? Perhaps the best way to document all of this is to write automated test suites that verify the existence and behaviour of these de-facto APIs? This is a lot of hard work. However if it's not done correctly I fear PS 1.6 compatibility will break too soon, before a critical mass of merchants and addon writers have moved over. Just some food for thought...