Jump to content

havenswift-hosting

Member
  • Posts

    2,752
  • Joined

  • Last visited

  • Days Won

    84

Everything posted by havenswift-hosting

  1. I completely disagree with ayz's statements on this ! Google and other search engines will always see all possible urls and if you have duplicates that lead to the same page (ie the url is shown in the browser and isnt redirected) then this can cause you problems. I have never said you would automatically get a duplicate content penalty but I know from personal experience with a client's site that this can and has been done by Google so for something so straight forward to fix, why not just sort it. There is another good reason for eliminating duplicate url's which is also related to SEO - link juice for that page can and almost ceratinly will be split between each of the url variations - again, why would you ever want to take the chance of that happening when it will seriously hurt your SERPS Ian
  2. Hi Niall As others have said (and it says in my signature), please use our ticket system for support issues as while I am on here most days, there is no guarantee and didnt see your message until just now. I have just seen that we only have a single version available via on the marketplace, so it could be that your ionCube version isnt compatible (or maybe you dont have it installed correctly). Please check PHP Info in your store and let me know - in the meantime, I will get both encoded versions added to the marketplace Ian
  3. 403 errors are most often caused by tripping a mod_security rule (assuming you gave that installed and enabled on your hosting server). Ask your hosting company to check for rules being tripped by your IP address around the approximate times you have been getting the 403 errors. Mod_security can give false positives and these can be whitelisted but this can also be due to older or poorly written software being run Ian
  4. That looks like an old V3 or maybe V4 format URL - were the sites that you have this issue on originally on old versions and do you have that URL added within a document or description somewhere ? Ian
  5. I don't understand the reply from hostmonster support either probably because it doesn't make any sense at all !! The saying "pay peanuts....." comes to mind. The problem you are having is a server hosting issue with php extensions following a change in the php version - only your host can sort it Ian
  6. Agreed ! I did report this as a github issue a long time ago but cannot find the original issue now - it may have been an original V5 issue
  7. If you are on 6.1.1 then you should not have a /admin directory or an admin.php as these should have been renamed to /admin_XXXXXX and admin_YYYYYY.php (where X and Y are random characters). If for some strange reason you do have them, then simply upload all files from the zip file, overwriting everything that is there
  8. No can of worms, both working as expected and means you dont have duplicate content - well not at least from that "custom" url but you shouldnt be seeing the /index.php
  9. And if you cut and paste that url into a browser where does it go to ? If it redirects to your selected domain url for the homepage then you dont have a duplicate url !
  10. Did you put your store into maintenance mode before doing the backup - if not and you did the backup but havent done the upgrade yet, then your backup is 2-3 hours out of date ! You need to upload ALL files from the extracted zip file, overwriting all that are on your website already BUT ensuring that everything from /admin directory goes into your renamed admin_XXXXXX directory. You also need to change the admin.php so it matches you current admin_YYYYYY.php file and then upload Ian
  11. Why would you ever want a custom url for the homepage document ??
  12. It has been covered in quite a few threads on here previously - maybe the best to follow is
  13. You should definitely only ever have one url that points to each page - the homepage is the obvious one but the principle applies to all pages. However, that by itself will probably only be having a relatively small influence on the overall SEO for the homepage. You need to find out where that custom url is being generated and remove it.
  14. The problem is a recently introduced one (not sure off the top of my head but maybe 6.1.0 or 6.1.1) so wouldnt affect any of those upgrades that you have done
  15. No that isn't correct. You need to add 301 redirects to your .htaccess to stop https://www.domain.com/index.php Assuming you have sorted out http to https redirect on all pages (or there is another 4 duplicate pages for the homepage), have you also checked https://domain.com and https://domain.com/index.php as those would be another two duplicate content pages !
  16. In other words don't wait until 6.1.6 is out before upgrading ! The security issues are serious and should be patched by everyone immediately and there is no confirmed release date for 6.1.6 yet. Don't look at this as you having to do two upgrades rather than one as you should really be looking at upgrading after each release anyway !
  17. If you would like to drop me a PM with a detailed list of your requirements, I will take a look Ian
  18. That is about it, yes ! There are a couple of annoying issues in the current version but we have also added a lot of extra functionality to the module. Google also regularly change the feed requirements, and we guarantee to make any required changes as quickly as possible
  19. To upload the files you either need to use an FTP client (apps are available for phones) or use cPanel File Manager. To backup, you can try using the built in routine but this can often fail depending on the size of your store and the settings within your hosting account. A database backup via phpMyAdmin and backing up files manually via FTP or File Manager is best
  20. Have a look at https://www.cubecart.com/extensions/plugins/google-merchant-centre-feed which is our replacement plugin for the standard CubeCart export - it adds a lot of extra features, fixes several issues plus also adds the ability to export in xml format Ian
  21. A 503 error generally means that the server is unavailable and getting one is bad enough but getting lots is a major concern both for the upgrade (which will need re-doing again) but for the future of your website especially as you say you have only just moved ! You need to speak to your hosting company and get an explanation for the cause of the 503 errors and if you want to have a chat with me, we provide specialist CubeCart hosting including free CubeCart support on our E-Commerce hosting packages Ian
  22. The latest version of the Foundation skin is always in the zip file - it isn't available on the extension marketplace
  23. There are well known and well documented problems with recent upgrades that are covered in quite a few different posts - for example If you follow the steps to do a manual upgrade, it will work correctly Ian
  24. Crashed tables in MySQL are almost always due to the MySQL server being stopped incorrectly (i.e. Not shutdown / restarted correctly) and if a transaction was in the middle of being written - somaybe the data was written / updated and the index wasn't. You should check your server and MySQL logs (if it's your own server and contact your hosting company if it isn't) as this in theory should not happen Ian
  25. OK that is what I thought but wanted to make sure. This problem is massively affecting one of our clients but they arent on 6.1.5 yet so am encouraging them to upgrade so they can see if this fixes their issue. They run it at Pending status (and cannot do it any other way for their business) but do have lots of items that are low in stock and also have lots of customers that create orders, come back to them in hours or days later to add / subtract items but also use the back button a lot as well. This results in orders being the wrong amount and in many cases shipping and tax being wrong as well.
×
×
  • Create New...