havenswift-hosting
-
Posts
2,753 -
Joined
-
Last visited
-
Days Won
84
Posts posted by havenswift-hosting
-
-
That is odd - in my experience it only happens if both exist at the time you try to do an upgrade so maybe your original attempt completed that part of the upgrade and caused that - sounds like it is all good now though ?
-
The problem happens when there are renamed admin directories and files and standard ones as well but if the files are uploaded as I mentioned, it doesn't happen. I think it is supposed to be fixed once stores are on 6.1.6 and upgrading further
-
Your renamed admin directory and admin file should not get renamed if you had followed the instructions ?
-
Yes, they should be removed
-
You are already on 6.1.4 so you already have a renamed admin directory and admin_xxxxxx.php file, so when you upload copy lol files from the 6.1.5 admin directory to your renamed admin directory and copy admin.php over your renamed admin_xxxxxx.php file and then do the upgrade, no need to edit or do anything else
Ian
-
Have you checked the PHP error_log file in your store home directory ? That might give a clue as to what error you are hitting
I always do and always recommend doing manual backups - simply upload all files using FTP or your hosting control file manager making sure you upload all files and directories within /admin to whatever your admin folder has been renamed to (and also do the same for the admin.php file) and run the setup via a browser - foolproof
Ian
-
There are some duplicate indexes, and ideally the incorrect one of these should be deleted as writing two duplicate indexes each time a record is written nearly doubles the amount of time needed for each database write. However, there are also some tables that dont have any indexes at all and these also need sorting out - so each notice needs to be looked at carefully and the appropriate action taken
Ian
-
14 minutes ago, franklinveaux said:
Unfortunately, uploading the module to modules/gateways and then navigating to Manage Extensions does not show the payment extension.
I want to leave ZenCart for a solution that is well-supported and well-documented.
If the module doesn't show, then there has either been an error in the way it has been uploaded or there is a problem with the gateway module itself but without seeing it, that is difficult to say.
In terms of support, CubeCart themselves offer excellent paid support, we offer free support for clients on our E-Commerce hosting plans and this forum provides free and generally fast user contributed support
-
Hi
You must be looking at very old links - if you have manually uploaded the gateway to the modules/gateway directory, then in your admin, navigate to Manage Extensions. There isnt comprehensive documentation for CubeCart although when in admin, there is always a help option which does give quite a few pointers
Ian
-
6 hours ago, cginca said:
Ok, so why would the cart show prices that do not match the price of the product plus the amount of the options?
Impossible to say without seeing your site and knowing how you have setup the options but basic pricing of product options works fine
-
@bsmither while it is true in that a store will generally continue to work if people do nothing about these database warnings (searching will fail in certain circumstances if the wrong type of index or no index is applied) but that isn't to say they don't have a detrimental effect in other areas as well so it is always better to deal with them than simply ignore them.
All the stores that we see that fail (as in don't make enough money to justify the costs / work) are mostly down to store owners that have stores that run "fine" but they don't pay attention to four or five areas. Speed of the website is one of those areas as this affects both user satisfaction and also Google rankings
-
Product options (mostly) work very well and the creation of the options matrix is far superior to most other packages !
It is unlikely to be a skin issue and the fact that you have tried five or six skins supports that, although you don't say what skins you have tried(some old V5 developed skins don't always work 100% and some of the free skins sometimes are less than 100%) or how you have setup your options or actually exactly what the issue is.
Ian
-
Whitelisting 4 rules isn't a major issue although does mean your hosting account isn't protected by those rules at all but then many hosting companies don't implement mod_security at all so you are much better off than them !
4.3.4 upgrade to V6 isn't a major issue although you will need a new skin and also you say you have mods so you would need to look to replace those with V6 plugins - hopefully equivalent ones exist.
If you want some help when you get back from your holidays, give me a shout but in the meantime, enjoy your holidays, probably much needed !
Ian
-
This is a new fantastic tool added in 6.1.5 that indicates problems with your database indexes. You can use phpMyAdmin to alter these and correct them as adding indexes and correcting ones that are wrong will speed up your store
Ian
-
4.3.4 - that is old !
403 errors are generally caused by the software tripping one or more mod_security rules - older software is much more prone to this. However, in this case, it is very likely that something you have added to the description field that is displayed when your store is in maintenance mode is causing the trip. You could try examining or simply deleting everything (best in source mode) and adding some simple text message again.
Your hosting company should be able to identify and offer advice about what the problem is, or simply whitelist that rule and any other ones you may also trip. You may also have an option to switch off mod_security completely for your whole account within your cPanel dashboard and while I don't recommend that long term, you could switch it off, save the settings to switch your store into maintenance mode and switch mod_security back on.
Finding and fixing the problem is by far the best way forward but asking your hosting company to whitelist the odd rule isn't an issue either
Ian
-
Excellent - SMTP always preferred !
-
1 hour ago, Jan T said:
All the SMTP settings failed.
PHP Mailer worked.
While the php mailer may work, you would be much better finding what settings are correct for your site / hosting in order to use SMTP (you will need to enter the correct port and almost certainly enable authentication and enter username and password for authentication) as email deliverability is MUCH better for SMTP than for php mail
Ian
-
1 hour ago, ayz1 said:
What I'm saying is that it's not a 6.1.5 issue as you seem to indicate as your demo website has had the problem for several weeks prior to the release of 6.1.5 so it hasn't developed since being updated to 6.1.5.
@ayz1 I have never said it is a 6.1.5 issue - in fact, I specifically said that we had plenty of clients running 6.1.5 without having the issue ! The https://www.cubecart-demo.co.uk site is not an official CubeCart demo website (which seems to work OK from initial testing) but if you had noticed issues with it for a while, it would be interesting to know for how long and at what version ? My thoughts at this time are that it is a PHP version or more likely an environment issue and rather than anyone being negative, it would be helpful if people that are experiencing the issue, gave details of the setup they are using to narrow down the problem
PPS : in fact, if you check https://www.cubecart-demo.co.uk now, I think you will see that the problem is no longer happening ! I will be able to report tomorrow what the exact cause is
-
11 minutes ago, ayz1 said:
It's not a 6.1.5 issue as it has been like that for several weeks.
So you are saying it is a CubeCart issue ?? Since what version ? We have plenty of clients on 6.1.4 and 6.1.5 without the problem so it is a certain combination of issues
-
@ayz1 that is true but the difference as I said earlier, is that we support not just the hosting but CubeCart as well and so don't blame one or the other and we work closely with @Al Brookbanks to report and solve issues.
There is a problem with that demo site at the moment which seems to have developed since being updated to 6.1.5 and the same problem happens on two other non public test sites that are on that same server - the other two sites are out of the box 6.1.5 installations with no additional plugins or skins so there is no interference. The server that is running these three sites is a test server that doesn't run any client sites and we have multiple clients that have already been upgraded to 6.1.5 on a variety of other servers where the problem doesn't happen, so it appears to be a combination of CubeCart within a specific hosting environment that is causing the problem.
The difference again though, is that we will continue to look into this until the problem is found. Nobody can ever claim that problems with software or hosting don't occur, it is the way that they are dealt with that is important and that is what our clients value
Ian
-
What you have done is ask Google (by creating a new sitemap and also asking them to recrawl the site) to start the process of seeing your new urls. There is no control over how quickly they start or how many urls they add to their index - it can take hours, days, weeks or many months. However, what it doesnt do is remove the old links that were already indexed and now dont exist although Google will eventually start doing that - in fact you dont want them immediately removed What you want is for people clicking on that link after doing a Google search is to be redirected to the new url - that is what a 404 error is and what creating a 301 redirect directive does, preserving any SEO link juice that you have built up.
The other thing you have to consider is whether any other site has linked to your site (this is the main goal of SEO as external links to your website are one of the main ranking factors) using any of those urls that now dont exist - if they have and somebody clicks on that link to get to your site and gets a 404 error instead, that will almost certainly be a lost sale as well as losing the benefit of that link.
Moral of the story, if you ever change a url for something different or remove a url, you should always create a 301 redirect for that url
Ian
-
There is no way to add language translations for product options at the moment but this is certainly something that really needs to be added !
https://github.com/cubecart/v6/issues/1505
-
It is always auto update in my experience but then when I do a manual update, I always copy /admin files and directories into the already renamed admin_XXXXXX directory anyway
-
BSmither meant the skin template files and those can be changed to suit a different layout which is fine if all of your customers are from one country (or use one format as most of Europe except the UK does) but it would be much better if CubeCart could look at the country that the address is for and adjust the format to suit
Ian
Raised a github issue for this https://github.com/cubecart/v6/issues/1504
Product options sets
in General Discussion
Posted
Again, this depends on what skins you are testing ? A bit more information would allow people to help you better !
I dont believe that is the case - I think the problem is not with Foundation or Foundation based skins