-
Posts
162 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Downloads
Articles
Store
Blogs
Posts posted by doclucas
-
-
I would love to know the answer too.
-
@datakick I just tested briefly, no more errors when FPC is enabled. Didn't test thoroughly tho, so not sure if the FPC fully works as intended. Thanks
-
@lesley please do share what happened there once you get this figured. :)
-
Full page caching still not fixed?!
-
That's true too. But, demand can come due to availability. Sometime you gotta take the chance and invest something to see the return. Just thinking out loud. :) I'll try to talk with Tomer, see what he says.
-
Strange, I'll check this out. This kind of modules are a very important thing for this project.
I never tried cart2cart due to their pricing, but I did try some migration modules and never had issues, despite migrating some huge databases. I am sure that most customers would rather pay $120 for a re-usable module (even if they need to re-start the process to continue) than $900 for a limited service that does essentially the same job (and if you are a programmer, you can even improve the purchased module to do even more).
-
cart2cart are insanely expensive and their product offering is normally a one time deal, so if you want to go through the process while developing, and then re-do it while you deploy, it's gonna be crazy. True story - I contacted them to migrate osCommerce shop with 100,000 products to another platform. They quoted a 2-3 business days work with a $900 fee. I bought a module that did the same exact job for a fraction of that price and I re-used it several times while I did the migration. Now, I totally get you want and need that revenue but don't you think that by offering cheaper migration tools to the community - you are going to enlarge the user base, which is something this project needs the most at the moment?
-
why the cart-to-prestashop (or cart-to-thirtybees in our case) modules not neeeded?
-
Did presto-changeo explain why only 10 out of 69 PS 1.6 add-ons they have are available for TB? https://www.presto-changeo.com/28-thirty-bees-modules
-
You gotta improve your selling skills, bro. j/k :) Did they explain why they were reluctant? It's a complete win-win for them. What have they got to lose by mentioning one more cart name for modules they already created?
-
@dosbiner said in Update on thirty bees:
@doclucas said in Update on thirty bees:
I think it would be very wise to: 1) Add a full features comparison table for PS 1.6 vs TB 1.x to the "why us" page. 2) Partner with the major & good quality module developers (such as presto-changeo, Knowband etc.) to add a section for thirtybees on their websites and test their modules for TB compatibility (and adapt them if needed). It's win-win for both them (more revenue) and the platform's success. 3) Add a changelog of all the recent versions, since 1.0.3 till 1.0.6 and moving forward
Great ideas, 4) future road map is a must I think
A road map is already displayed, or at least a placeholder, but it's not set because it probably hasn't been planned yet.
I forgot to add to point 2 - ask those PS 1.6 module developers to report any reproducible compatibility issue with TB so that your dev/s can resolve them. The wider compatibility TB has with PS 1.6 add-ons, the higher chance it has to gain a much wider user base.
-
I think it would be very wise to: 1) Add a full features comparison table for PS 1.6 vs TB 1.x to the "why us" page. 2) Partner with the major & good quality module developers (such as presto-changeo, Knowband etc.) to add a section for thirtybees on their websites and test their modules for TB compatibility (and adapt them if needed). It's win-win for both them (more revenue) and the platform's success. 3) Add a changelog of all the recent versions, since 1.0.3 till 1.0.6 and moving forward
-
Sounds like some AJAX call needs to get fixed/modified.
-
@violinparts
IIRC, I think you must upgrade from 1.0.3 to 1.0.4 first
-
These errors do not seem to be the cause of your error 500. The issue could be http-server (usually Apache) or sql server (usually MySQL/MariaDB) related. If you can fetch their error logs, please post here, or I can have a look at your server for you. Curios.
-
Sounds good. This also emphasizes why keeping TB PS 1.6 backward compatible is so important. Good luck, @lesley :)
-
@lesley said in Call for votes for (or against) upgrading Smarty:
As for the feature requests, we are not implementing any new features into the 1.0.x branch. If we do, we will never leave the branch and will be at 1.0.187 before we know it, with no real core progress.
And what's wrong with that? If the 1.0.x is working very well and well accepted by the community, who said it must be so heavily modified? or even worse - must be upgraded to a core that is no longer backward compatible with PS? Modifying the core components (such as smarty) and refactoring the code for php 7.2+ is already a great move forward. Keeping up with those upgrades while adding more features, modules on the same 1.0.x branch can be very useful for this project and help increase the user base, trust and loyalty.
-
@DaoKakao well said :)
-
I know you already read my opinions, but anyway, I am voting for strategy 1: Upgrade Smarty to the latest version (3.1.32) on the 1.0.x development branch. keep compatibility with PrestaShop 1.6 modules and themes by adapting the "bridging" code (such as code in smarty.config.inc.php) to the new smarty version. If done right, no template and modules will have any issues. The issues reported by @lesley were most likely due to smarty being upgraded without adapting the core to it. As I suggested before, you can also look at PS 1.7 smarty bridges and backport some or all of their changes, as they use the latest smarty. Again, just doing the composer update will surely break things. You must modify the bridging code first. I am happy to beta test it for you when you are ready. You already have quite a beautiful core (especially compared with PS 1.6). It needs a few components upgrades (smarty etc.) and PHP 7.2 compatibility fixes, and it can become a great platform to continue building on.
Also, as @datakick suggested, it may be good, if not too much of a headache, to keep both smarty versions and let users switch between them. If it's too much of a headache, then just do the excellent 3.1.32
Frankly, without being too dramatic, I think that moving to a core that will no longer be PS compatible may become a death sentence to this project at this stage. Watch out!
-
I assume you meant php 5.6.23 and not Apache. :) Thanks, please let us know.
-
@MockoB Prestashop was just an example of a project that I know you are familiar with, which I listed because you wrote "I can’t imagine open source project with CEO, I think that both are completely incompatible conceptions." Not to vouch for their CEO's performance (which may or may not be good, I don't form opinions based on your forum or Safari experiences :rollingonthefloorlaughing: ) . Seems like most people don't know much about large & successful open-source projects and how they are being managed, so I will skip further public discussion about these matters as they seem to lead nowhere productive. If anyone really wants to learn more , I suggest you google projects like: OpenCog, Kubernetes, Magento, Red Hat, Ubuntu, Wordpress and many many more.
-
@MockoB There are practically zillion open source projects with CEOs/CTOs etc. (some are/were doing amazing job and some not so, but I digress). Here is one project you probably know: https://www.prestashop.com/en/press-releases/2018/03/08/prestashop-appoints-alexandre-eruimy-as-its-new-ceo-and-launches-prestatrust-a-traceability-system-based-on-blockchain-innovation
-
@lesley I don't know where the statistic is from, but I sure hope your software will be the #1 ecommerce platform on the market. I will do what I can to help. :)
-
@vincentdenkspel Isn't that book about getting to have great leadership (for example, a great CEO) that inspire people?
Can we use the PS way of profiling and error reporting with TB?
in Bug Reports
Posted
Thanks @lesley