veganline

No. I uploaded to install on TB1.10 and got I don't know what any of this means, but the Prestabrain web site says that they're doing less work on themes so I doubt they'll put any work into this Thanks for the idea though.

...which turns off on the backoffice>preferences>orders page. (I expect everyone knows that but mention it just in case.)

Now that backoffice>preferences>custom code>add css allows you to tweak styles by default, more shopkeepers might want to shorten the default one page checkout. No changing of files is required; it's all done from the back office where shopkeepers like me are happier making changes. The first step is to do everything possible from backoffice (BO) settings to simplify the checkout form. BO>orders>general>order process type: set to "one page checkout". Enable guest checkout. Turn off all else. BO>modules...>modules..> "block cart" module. configure to turn off "ajax cart" and "upselling", then disable the module BO>preferences>customers set "newsletter registration", "opt in (to special offers)" and "phone number is mandatory" to "no" (unless maybe you need a phone number for a courier) BO>localisation>translations expand all fieldsets and search for "New customer", changing to "Customer" BO>localisation>translations > ORDER-OPC-NEW-ACCOUNT change "delivery address" to "delivery address copies customer name" change "save" to "check address and postage" The second step is to amend the default stylesheets. The trick is to right-click the part of the form you don't want, choose "inspector" in a browser like Chrome which has an option to "copy selector". You copy and paste it to backoffice>preferences>custom code>add css where you can add an extra {display:none;} or {display:block;}. This has worked for me so far in Niara theme and something similar will work for others. -------------------------------------------------------------------- /* CHECKOUT TWEAK for preferences custom code css section*/ #quantity_wanted_p {display: none !important;} /*quantity on product page can be removed. The effect varies a little between themes*/ #cart_title {display: none;} /* saves space to encourage scrolling-down*/ #opc_account_choice {display: none !important;} /*for edge browser*/ #login_form {display: none;} /*everyone uses guest checkout so no login*/ #opc_account_form.unvisible {display:block !important;} /*guest checkout visible*/ #new_account_title {display: none;} /*customer heading*/ /* #customer_firstname label caught below */ #opc_account_form > div:nth-child(13) > label {display: none;} /* #customer_lastname label caught below */ #opc_account_form > div:nth-child(14) > label {display: none;} /* #company caught below */ #opc_account_form > div:nth-child(15) {display: none;} #discount_name.discount_name {display: none;} #voucher {display: none;} #cart-voucher {display: none;} #login_form .box {display: none;} /*includes most of the lines up till vat number */ .date-select {display: none;} /*order and date of birth form*/ #vat_number_block {display: none !important;} #checkoutLogin {display: none;} #logged_checkout {display: none;} #blockuserinfo-login {display: none;} #product_condition {display: none;} #phone {display: none;} #opc_account_form > div:nth-child(25) {display: none;} /*catches the label for phone */ #phone_mobile {display: none;} #opc_account_form > div:nth-child(26) {display: none;} /*catches the label for mobile*/ -------------------------------------------------------------------- The same technique can make payment methods such as a stripe or paypal module visible if enabled for your account and for the country selected. Details will be be different for each payment module. If in doubt, $24 buys the "show payment methods" module from Green Mouse Studio who sell on codecanyon linked from https://thirtybees.com/partners/compatible-modules/ -------------------------------------------------------------------- Added 19/10/19 I didn't think of checking on a mobile emulator like https://www.brickandmobile.com/mobile-emulator/ until reading the post below. I've done a single quick test now, and the same code seems to work. -------------------------------------------------------------------- Added 21/10/19 I tested this guest checkout on Thirtybees 1.01 a few times with the same email address, and it works each time. If I am two customers with the same email address under BO>customers>customers and if I click on myself it says "This customer is registered as a Guest." and has a button to turn me into an account holder; "This feature generates a random password before sending an email to your customer.", it says. Prestashop 1.6.1.23 fails second time: "There is 1 Error(s): An account using this email address has already been registered.", and there are some years-old threads online where people look for a neat answer; there's nothing similar under the backoffice>customers. Site owners have to cut out bits of file to stop the error message. This is a pity because there are CSS editing modules for Prestashop like the free one from DH42, and the same style sheet worked otherwise. Added 18/06/20 There is a subtlety. Default settings are full of invites to register an "account", so someone somehow might do it, and account-holders need Thirtybees to have a bug-fix-update file if they are to order again with the same email address but no password. https://github.com/thirtybees/thirtybees/issues/1150 : "An account using this email address has already been registered" preventing purchase where there is only guest orders with that email -------------------------------------------------------------------- Added 30/10/19 If doing this for someone else, I'd translate the labels for phone and mobile to "." in case the lines below change and reveal the labels. For some reason my own form now needs #opc_account_form > div:nth-child(24) {display: none;} /*label for phone */ #opc_account_form > div:nth-child(25) {display: none;}/*label for mobile*/ instead of 25 and 26 as above - I suppose they're sensitive to other changes in the form, or maybe a core file update could effect them too. -------------------------------------------------------------------- Added 03/11/19 DH42 free Prestashop Editor seems to work on a defaullt installation, although not the bleeding edge version. If so, I guess it allows refinement of the code above. It's possible to edit the product.tpl file to take out unwanted stuff until the next code update, and it's possible to add the style sheet to an area like checkout and not to other pages. Thirtybees template selector, based on another DH42 module, allows you to have an self-edited template for any product where you select it; you can have different templates for different kinds or product. I imagine that these survive site code updates. -------------------------------------------------------------------- Added 06/11/2019 "Please log in to see payment methods" shows by default before you choose a country and address, when the system doesn't show a payment method. Even if you don't allow logins. So it's good to translate to "Please choose a country and address to see payment methods". (I thought I'd forced mine to show, but they still hid on the mobile version of the site.) There are other suggestions dotted around on forum threads. Translation has to be repeated if you change themes or allow another language. -------------------------------------------------------------------- I hope this helps other shopkeepers, and if I have written it badly then improvements are welcome. Maybe it could be built into a future theme. -------------------------------------------------------------------- Added 05/04/2020 - Toplakd has writtten a 3 page checkout tweak, altering the checkout.php and templates from the default 5 page checkout. It's a thread with replies over on the themes forum. -------------------------------------------------------------------- added 17/05/2020 About modules. I use Cloudflare, which slows the site down but can be used to offer a free secure server. Cloudflare can guess where in the world a customer is. A free Datakick module adjusts Thirtybees to this information. This can ease the trouble of having to fill-in the country part of your address and confirm before you see postage options; the box can be pre-filled I think. €40 buys a Datakick module that puts the delivery country right at the top of the page and "tries to simplify the checkout flow". There is short youtube video and a try before you buy option. I haven't seen other checkout modules that work like that; they get reviews like these instead. One Page Checkout modules have trouble because the default one works in steps. There are buttons that effect what will be shown at the next step. A button confirms your address before showing the price of postage, which has a logic to it. Another asks you to "please sign in to see payment methods" for the same reason; the cart can have Mastercard's Simplify Commerce enabled for the US and other options again just for Europe; maybe even for wholesale customers v. retail for all I know. If you condense these steps into three columns on a one page checkout they confuse. Knowband's module and others ask shoppers to confirm their address on a button right at the bottom left of the screen where nobody would expect a button. That same module doesn't cope with updates unless you subscribe to their service to update it, and it doesn't simplify; it complicates. The only benefit is a page of switches for some of the {display: none;} changes that you can do for free in thirtybees' back office. That's why a DIY hack helps; beware of expensive imitations --------------------------------------------------------------------

Yes, I tried allow_url_fopen = On in the php.ini file among all the other likely things and then turned it off again before asking for help! The 1.07 installer worked, and the core update module then updated to 1.1, so all OK. My xilo.net server is the odd bit. It's very fast and cheap but I had to install a database for another program via an app installer - Installatron - before the TB1.07 installer recognized it.

Reason found: Xilo.net, the server company write Quote ...allow_url_fopen is blocked for security. At the moment, there is no way around this but with a few changes we're making internally on the servers, we hope this may be possible in the next coming weeks. TB 1.07 installs & core updater module updates TB 1.08 has an error message on a yellow stripe with a red cross after it, Required PHP parameters PHP's 'allow_url_fopen' enabled: fail TB 1.1 has no error message with a chance of red-herring searches if an optional error shows instead, as on this thread

Traumflug is going to look into my server space, but if you want a separate account i will refund you the first year's £30 for the cheapest shared hosting on xilo.net Their help desk writes "Does the install script rely on using phpinfo for server information by any chance as we block this on the servers for security.Please let us know if that isn't the case and we can certainly look in to this further for you." best John

I'm the same. Xilo.net is a very fast server for the money but does not install TB 1.1 and TB 1.08 after coping with TB 1.07. If there are any questions I should ask their support team, just let me know or ask for logon details. John

Solved! (or identified and worked-around) The optional error messages were a distraction from versions 1.08 and 1.1 not installing where version 1.07 does, as in the thread below, for reasons unknown. Thanks for everybody who has spent time on this and made suggestions. I suppose further solutions belong in that thread.

It's there as new, but in the course of digging I might have tried deleting lines 54-7: // public function checkOptionalTests() // { // return self::checkTests(ConfigurationTest::getDefaultTestsOp()); // } so I tried doing that again and got a long error message with stack trace errors that looks familiar. If I restore those lines, I get the usual error screen with the greyed-out "next" button, "please...errors below" and no errors shown Thanks for the idea and for your help

Temporary link to the full detail Apache Version 2.4.41 PHP Version 7.3.8 Set to 7.1.31 for compatibility MySQL Version 10.0.38-MariaDB Architecture x86_64 Operating System linux "Our servers run the latest, stable MySQL server, version 5" Shared server tested for size on previous test Prestashop 1.6 versions, which ran into file permission problems and kept trying to lock me out so I decided to move to thirtybees. Tested past the system compatibility stage for the PS1.6 and 1.7 installer except "cannot open external urls" on 1.6. Not tested on the database. Thanks for the idea. I'll look for incompatibilities.

Thanks for the idea! Same result though: if I comment out line 128 // 'Tlsv12' => false, I get the same result as when I put-in the fake test result, which is "please correct the errors below" but no errors. Oddly enough the code mentions this being an optional test. Is there any way I can learn more about diagnosing and bug-checking? It looks as though something other than the Tlsv12 test is not working, maybe on my server.

Thirtybees on my server doesn't allow this on a first install. I spent a day digging after following the instructions above, which are great, but there is some other layer of security that I can't fool; I can get rid of the bottom half of the error message, but the top half remains and the "next" button is still disabled. I got error reporting started, but messed up somehow because the error_log report stopped but I can always start the install from scratch again. Maybe I should because the results are quite precise. Different work-around got line 166 or 168 in results like this: PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, class 'ConfigurationTest' does not have a method 'testTlsv12' in /home/veganlin/public_html/x/classes/ConfigurationTest.php on line 168 So I need to fool the code into thinking that a proper test has been done, or find some other way to stop it disabling the "next" button. Any help appreciated as I am probably too old to return the favor in bed cheers john PS Experimenting, I somehow got another error message that looked quite helpful, once. If I knew how to get more like this I could probably solve the problem myself. I don't remember what experiment it refers to, but it goes like this: [27-Sep-2019 18:03:06 UTC] PHP Fatal error: Uncaught Error: Call to undefined method InstallModelSystem::checkOptionalTests() in /home/veganlin/public_html/x/install/controllers/http/system.php:83 Stack trace: #0 /home/veganlin/public_html/x/install/classes/controllerHttp.php(197): InstallControllerHttpSystem->display() #1 /home/veganlin/public_html/x/install/trystart.php(34): InstallControllerHttp::execute() #2 /home/veganlin/public_html/x/install/index.php(56): require_once('/home/veganlin/...') #3 {main} thrown in /home/veganlin/public_html/x/install/controllers/http/system.php on line 83 [](https://forum.thirtybees.com/uploads/monthly_2019_09/Untitled.jpg.59760fda0ceb56b2ed379b02a00905a2.jpg)

I should post in the installation forum. Yes; it's the "Refresh" that doesn't work for me. As it is, I press refresh and the page code still says <input id="btNext" class="button little disabled" type="submit" name="submitNext" value="Next" disabled="disabled" /> temporary link

Thanks Dyambee! I'm still stuck on the detail although I'm sure that's part of the problem. If I click "next", nothing happens. If I search the TB1.1 files for "paypal", I find nothing relevant - no paypal module in the modules folder for example. All ideas welcome.

I'm installing and get the error message "Recommended PHP parameters Could not make a secure connection with PayPal. Your store might not be able to process payments." as on the screen shot. I don't want to use the paypal module but can't see how to remove it at this point or make it work. I have checked php settings to match suggested ones on a small server that managed to host prestashop 1.6. The secure server is from cloudflare. How can I carry-on installing? - answers appreciated.

where do I download the .zip file? (The thread on Prestashop has an error message next to the link, and the Prestools site points to the Prestashop thread)

@tbtester Concur to one of your posts a few lines up, but the problem goes both ways. "some fcgi directives needed for to speed up some other processes on the server, like ruby on rails. After disabling them I was able to upgrade." That's a bit short for me, as someone who doesn't know where to start learning this stuff reluctantly. There is something about coders & shopkeepers that makes it hard for us to help each other. As a shopkeeper I think coders expect someone else to pay for the server. NASA funding at least. I don't know what coders say about us shopkeepers but it is probably something similar about expecting free servers and free forum help. Maybe coders should imagine teaching this stuff to students who use free servers like Byethost. If the code doesn't work on a free server, they could write a warning or an explanation. Then the shopkeepers who work close to the edge of what the cheapest fastest shared server can do for their business would have a warning or an explanation ready to see, if they need to upgrade or need some special tekkie trick for working near the limit.