havenswift-hosting

Within your store admin, go to Server Info and search to see if IonCube is showing as being installed - as @bsmither said, many hosting companies will already have it installed and if not, then you can often ask them to install it Ian

Thanks @Noodleman - beat me to answering although I do have the excuse that I am in Seville for business meetings ! That plugin is not yet available on the marketplace but is available from our website here : https://www.havenswift-hosting.co.uk/clients/cart.php?gid=19 Ian

A 404 error means file not found so you are using the wrong name or url - double check what the admin.php file has been renamed to so the url should be something like https://www.domain.com/admin_xxxxxx.php Ian

You will need to use the url including the admin_xxxxxx.php file name and not the new admin directory name Ian

I never do an upgrade via the built in link as always do manual upgrades for customer sites, however recent testing on several of our test sites on different servers, failed in both cases. Check the upgrade error log and also the PHP error_log file

Al & rdbms This behaviour has been reported by quite a few people on here (multiple threads asking about the same thing) and is also what I have been noticing with a few of our customers - it doesnt affect many but a handful and havent found any correlation Ian

I must have done well in excess of 400 upgrades since the new renamed admin file and directory structures were brought in and I am sure that @Al Brookbanks has also done at least as many - what you are describing has never happened to me and I am pretty sure that Al would say the same - it can ONLY happen if an upgrade isnt completed correctly whether due to the old bugs in the built in upgrade procedure or by doing the manual upgrade incorrectly. For example you previously said "During this fix, I went ahead and reinstalled cubecart, and it left my old /admin_####/ folder and created a new one." So you already had an /admin_xxxxxx directory and what you did was upload /admin - that is wrong and is what causes your issues. What you should do is upload the contents of /admin to /admin_xxxxxx and then run the upgrade CSRF errors will occur if your admin_yyyyyy.php file and the admin_xxxxxx directory are from different versions

That isnt possible at all if you are following the above instructions ! If you rename the admin.php from the zip file before you upload it so that it matches your current admin_xxxxxx.php and ONLY copy all files and directories from /admin directory into your /admin_yyyyyy directory - then you can delete admin.php and /admin directory from your website files, you cannot possibly be left with those - from what you are describing, you will still have mixed version files on your system If you are unsure, then I can sort it for you Ian

There were problems doing automatic upgrades that have been well documented. The only safe way was to upgrade manually and if you still have the /admin directory then it means you didnt do the manual upgrade correctly ! if you already had the admin_xxxxxx directory then when uploading the files as part of the upgrade you should have copied the contents of /admin in the zip file into your admin_xxxxxx directory - I am guessing you simply uploaded /admin ! So you have been running a 6.1.10 store but with an old admin set of files in /admin_xxxxxx The best way forward would be to simply re-upload all files again taking care to upload admin.php to whatever your new admin_yyyyyy.php file is called and the contents of /admin to /admin_xxxxxx directory. You can re-upload the setup directory and re-run that if you wish if there is any doubt that all database changes havent been completed previously Ian

You have said in a different post that you are from Mexico so why would you be trying to use the Canada Post plugin - unless you ship from Canada maybe ?

If they have different options then they are added separately to the cart as separate products - if you have a product setup with different options, simply try adding with one options choice and then add a second with a different options choice !

As a first port of call, you are always much better off directing support type questions to the developer for commercial plugins and skins. They should know their products better than anyone else and so be able to help quicker plus they have benefited from the sale and so should support the products after this. Ian

Email routing will automatically be set to "Automatic" or sometimes "Local Mail Exchanger" which in 99.99% of cases will be the same thing. You only need to set it to Remote if you are using external MX records pointing away from your hosting company which is effectively what Godaddy are forcing you to do by closing email ports. Some people choose to use gmail or other email service providers, but why should you have to ? Disabling php mail() is standard practice now for security reasons (WHM built in security advisor flags this as a high security risk if it is enabled !) and SMTP should always be used and configured to use SSL / TLS. Email sent via SMTP is much more secure, more likely to be delivered and not rejected or put into spam and isnt complicated to use. So much so, I would recommend that php mail() is removed as an option in CubeCart as it is very likely to disappear as an option in the near future Ian

Seriously though, with those restrictions in place, it is a wonder anyone hosts anything other than a basic website with them !

The line at the end is the most relevant one ! >>You may find it easier to switch to a more enlightened hosting provider.

So have you done that and are they the same ?

Yes you need to increase the memory_limit value for your php version Ian

You have some recent out of memory issues which isnt surprising as your hosting package only allows 32MB which is very low. The issue is image related (the GD library) so you will have some images that are trying to be processed that are taking more memory than your hosting company allows.

Have you recently installed a plugin especially one that is encoded ? If so you may have installed one that is incompatible with the version of ionCube encoder that is installed or maybe you don't have ionCube installed at all. Have you checked the php error_log file ? Ian

Well, as I said, while you can "enable" http/2 through EA4 it will never been used so all you are doing is slowing down every single connection as it attempts http2 and then drops down to http. CENTOS 6 will never have that ability and CENTOS 7.4 still hasnt been released.

Hi Andy The files you are changing will be cached somewhere. Firstly, if making changes ensure that "Enable Caching" is disabled in the Store Settings Advanced tab (remember to switch it back on when you are finished). Secondly, your browser will cache files locally on your PC and it already has a copy of the old file downloaded and will use that - you can force a reload of all files used by typing CTRL-F5 (this is the usual command for most browsers) Ian

The best way is always going to be to do a manual upgrade. There are other threads on here that give the steps on how to do this Ian

If you have just installed a new plugin (Noodleman's one based on our conversation maybe ?) then you have probably installed the incorrect version for the version of ionCube loaders you have on your hosting Ian

http/2 is extremely difficult to implement at the moment so unless you run your own very highly customised server it is unlikely. cPanel (which most people will be running on their server) introduced http/2 in EA3 a short while ago and then in EA4 (which is now mandatory for cPanel) only a couple of months ago. However, this is when it starts to get tricky ! During the initial connection negotiation, if wanting to use http/2, the server and browser needs to establish a secure connection using either the NPN or ALPN protocols. Most versions of OpenSSL only support the older NPN protocol and for a short while that worked and allowed http/2 connections, but Google deprecated NPN in Chrome 51 (followed by almost all other browsers) and only support ALPN effectively breaking http/2 for most of the few people that had implemented it ! The very latest OpenSSL libraries do support ALPN but these havent been adopted by the majority of Operating Systems. So to fully support http/2 you need the very latest OpenSSL libraries in order to support ALPN and these OpenSSL libraries are not yet supported in most Operating Systems - although it isnt too far off. For example, CENTOS (which is the general choice for many and what we use exclusively) is currently on version 7.3 and will be supporting the latest OpenSSL libraries in 7.4 There is one further issue in that there is no upgrade path from CENTOS 6.X to 7 and most hosting servers are running 6.9 which is the latest version available. To upgrade to CENTOS 7, you need to remove all accounts to a second server (obviously ensuring that the specification is OK to run all sites) and then reload the Operating System, reload WHM/cPanel, configure all products and services and keep all fingers and toes crossed that when you move the sites back to the newly reloaded server, they all work ! We are just completing this process on the first of our many servers and it isnt an easy process but something we want to do many so we can support http/2 as soon as CENTOS 7.4 is available ! So the short answer, is that I doubt anyone running CubeCart will be running http/2 which is a shame as it is so much faster ! Ian

For anyone that uses git with CubeCart (or any other packages for that matter), cPanel have been adding a huge amount of functionality which will be included in V68 - see https://features.cpanel.net/topic/allow-users-to-install-websites-from-version-control V68 is already in Edge release status so most people will not have access to it yet, but V68 should be into general release in a few months (V66 has just been released in the last week) Ian