A-Z Hosting

And will still be 100% incompatible with 1.6 theming. Thus a whole new look and feel must be built and charged for. That is once the 1-click finally works and can read md5 files. Right now I can't even upgrade 1.7.2.1 to 1.7.2.2 running the latest stable 1 click version. And no I won't be relasing a non working shop either. That's why I've been on the forums. ;-) This is a new build. Only thing I am changing is a Miva Merchant store from 1999. I guess technically the old one is still running, but sure looks like a 90s build and hasn't had many orders because of it.

Oh you mean I was going to be the first! According to the forums here many are trying to. I was trying to, and hopefully still am. I just could NOT get this customer to understand. "It's 1.7.2 and says it's stable. If you can't handle the job maybe I should find someone else." You know the routine. Mostly the issues so far are things seller wouldn't notice, though the developer would. Inability to import, inability to 1-click upgrade, various other nasty quirks that cause migraines. Then last night what set me off was one the seller would notice, pagination in backend categories doesn't work and you have to set it to view 1000 so you don't actually need to paginate. I mean come on that's a query issue not a template engine issue. But yes the impression is that it is being used in production. I would go back to 1.6 but can't justify it since there is no upgrade path. Just can't see charging a customer thousands to build a store that has no future without a complete overhaul. Magento did the same with their 1.9 so can't really expect them not to do the same again either. Perhaps the days of free opensource ecommerce one can rely on has come to an end.

That's a fix of course. I'm sure you're aware of how hard it is to explain to a seller that you're going to install a 1.6 store for them, because 1.7 is a developer only version. Then try to explain that there is no upgrade path. They frown a little when you tell them you're installing a Dead End. First thing out of their mouth is the word Magento. Now I'm even worried that there won't be an upgrade path from 1.7 > 1.8 if they are throwing out Smarty completely. What was so wrong with Smarty? I kind of liked it. Though I haven't dug into symphony yet, aside what I read from error messages.

Looking at the topics in the forum, banging my head from my current install, not seeing any answers to major issues, nobody chiming in from Prestashop. Bruno WTF man? Is Prestashop 1.7 the end? How long can I stick with the 1.6 fork? Cause I can NOT install another 1.7 and expect to actually make money. End users are hating it and so are we. When can we expect some improvements? You're at 1.7.2 and still haven't fixed any of the major issues from the alpha. Lets go back to a more stable 1.4 and start over maybe. Here's an old favorite that is now showing up again with a 500 error from clicking on import. [Wed Sep 13 03:54:56.668833 2017] [:error] [pid 19481:tid 139942680045312] [client 162.252.6.241:64452] PHP Fatal error: Class '' not found in /home/xxxxx/sssss.com/classes/cache/Cache.php on line 131 The list is huge, but I posted that one just to give the thread a purpose.

Thanks for reeling me in. Yes I will add that it is highly unlikely that a merchant would have only one item in a category that has configured features. So it doesn't have any real world production effects. It does have effect on the developer who is trying to configure his filters and not seeing any show up. The issue isn't documented so one could run in circles for hours (i only wasted one ;-) ) trying to find the issue. So I will document it here. DO NOT expect to see your filters work unless you add at least two (2) features and values to two (2) products within the same category you are creating the filter template for. 2 features for 2 different products is the answer. As you add additional features make sure they also belong to at least two (2) products within the category, or those additional feature filters won't show up either.

Yah but that is still a bug. It's faceted search not product comparison. There shouldn't have to be 2 or more products. Just throwing my $0.02 out there.

If you check the new 1.7 code it is chmoding just about every folder 777. I have tagged 1.7 as do not use on my systems. Isn't PS supposed to be creating secure eCommerce software? I'm pretty flabbergasted. Did they fire a bunch of people between 1.6 and 1.7?

Not for no $550. WTF?!!! That thing better wash my car for me every saturday morning.

No ideas from anybody?

Customer would like to possibly use guest checkout. However, when I enabled it it started changing the $34.95 price of the product to $11.88. This would occur on the Payment page whether it be 3rd party Payflow Pro or Check payment. It adds fine to the shopping cart, displays fine on OPC, but then changes when I get to the Payment page. Sounds to me like something isn't meshing in the database. So I looked for anything that could be referring to the 11.88 in old orders, old carts, old vouchers, mixups with guest or customer ids. I have found nothing. This 11.88 is as it is now deemed.... The Ghost. Anybody have any ideas of where to look next. Customer would like to use Guest Checkout but not at a loss of $23.07 per product. Prestshop 1.6.1.12 Cheers, Wil Hatfield

I thought that I had read that it upgrades the old to the same version of the new already. If not then never mind. I'm done with my import and have some feedback for you. Not all shared hosting packages come with access to INFILE and OUTFILE. Actually the secure ones don't. Special permission needs to be given to access those files. Secondly the ~mysql user shouldn't have access to the user folders so the $basepath isn't writable. Being the host I was of course able to get around this but not everyone has my access. GRANT FILE ON *.* TO 'imako_imakops'@'localhost'; GRANT FILE ON *.* TO 'stagingi_ps1'@'localhost'; flush privileges; That gave the oldshop user and the newshop user access. However, it still wasn't writable in the users' jailed folder. I had to take $basepath out and change it to ./ so that the ~mysql user could write the files, which of course went into it's own ~mysql/ folder. Afterwards I just deleted them from there. I think you could get around all of this if you wrote to temporary tables on the destination shop's database. So instead of writing then reading from copy_shopdata_address.dtx just write and read from a copy_shopdata_address table. After completion drop table. I also think that would do better on benchmarks. Wouldn't that work better or is there something about the dtx formatting that made it necessary? Wil -------------- 14:26:14 oldconn = localhost.imako_imakops = 2532436 new conn = localhost.stagingi_ps1 = 2532435 2 old languages; 2 new languages. Language check ok. Initialization skipped because it had already run Copying tables 1 accessory 0 2 address 44355MySQL error 1: Can't create/write to file '/home/xxxxxxx/public_html/exxxx5ckcmg82/prestools/copy_shopdata_address.dtx' (Errcode: 13 - Permission denied) Generated by URL '/exxxx5ckcmg82/prestools/copy_shopdata.php' with Query 'SELECT `id_address`,`id_country`,`id_state`,`id_customer`,`id_manufacturer`,`id_supplier`,`id_warehouse`,`alias`,`company`,`lastname`,`firstname`,`address1`,`address2`,`postcode`,`city`,`other`,`phone`,`phone_mobile`,`vat_number`,`dni`,`date_add`,`date_upd`,`active`,`deleted` INTO OUTFILE '/home/xxxxx/public_html/eyxxx5ckcmg82/prestools/copy_shopdata_address.dtx' FROM `ps_address`'

That's kind of what I figured on the side of caution. Just wanted to confirm. Thanks for the scripts these have been much needed. You ever thought of turning into a full module? Have the settings all configurable from the destination store side? Adding a few other parameters like "skip old store upgrade", or "upgrade old store to version xxxx", etc? Would be even more awesome for those that don't know how, or don't have the convenience of shell to toss things around. Wil

Good idea thanks. One more question while I have your attention. Once I have things as I want them do you have any ideas on jumping to 1.7.1.0? Will it still ignore the old and just bring over the updated data? Or should I upgrade the old, upgrade the new, and then bring over the updated data? Wil

Hey MusicMaster: So if I have a 1.6.1.12 old shop and a 1.6.1.12 new shop will it skip modifying the old store? I would like to be able to run this pulling from a production install over to a fresh install. Then install theme and extra mods in new shop. Then run it again just before going LIVE to grab new customers and orders accumulated since the first run. Think it will work? Backups will be made of course. Wil

We have to halt updates for our customers. This save issue is now a complete shopping cart killer. Bruno buddy, WTF? Upgraded one subversion to 1.6.1.2 and now no products can be saved. And before anybody tries blaming the host..... LOL Yum was ran last night, we run cloud linux and debugging/profiling says the server is powered by unicorns. So no this isn't a slow host issue.