Jump to content

havenswift-hosting

Member
  • Posts

    2,752
  • Joined

  • Last visited

  • Days Won

    84

Posts posted by havenswift-hosting

  1. It is very unlikely that a search engine (especially Google) will have old urls cached for more than a few weeks / months at the very most.  What is more likely is that these links may be on another website as links back to you and maybe that website's pages have only recently been added to the index.  Google will see the links on this third party website, cache them and try to follow them and then be getting a 404 as they dont exist

    Ian

  2. 7 minutes ago, harrisorganic said:

    I suggest you do a manual upgrade as others have suggested.

    If you think this is too much then I suggest you talk to Ian regarding hosting or subscribe to Cubecart tech support  and have them install it.

    Thanks for the shout out !  A manual upgrade is the only sure way and part of the problem is that trying to upgrade from one specific version (say 6.1.1 or 6.1.2 etc) to the latest version can create different problems which need different solutions.  You will have a mix of files at different versions, DB may be at correct or incorrect version and the admin renaming may be messed up - hard to tell without looking at the files via FTP

    Ian

  3. 6 hours ago, Nelly111s said:

    thanks for the pointers. On skins, do you think it is worth creating a V6 site with a new skin in an offline copy and moving that, rather than debugging a V5 skin?

    I can find absolutely no reasons to ever continue with a V5 skin - they are not being maintained, are starting to have missing functionality but mostly they are not responsive which is a very poor customer experience which is why Google are penalising sites in several different way.  There are unfortunately only a small number of good V6 skins available but be very aware of those put up a long time ago and not maintained.

  4. Just taken a look at that script and it looks very good - a great contribution !  The warnings about security and protecting it from unauthorised access are important for anyone looking to use it otherwise something could make a real mess of your store but the documentation looks very good !

  5. 1 minute ago, harrisorganic said:

    Thanks Ian,

    Now no more errors in the admin maintenance database.

    You are welcome - remember to check it every now and again after each upgrade, firstly because (hopefully) this tool will continue to get better and highlight things that it currently doesnt and secondly because there is always a possibility of new errors creeping in

  6. 31 minutes ago, Noodleman said:

    I think you need to do a manual upgrade as you've got a mix of file versions on your server. I've seen this happen before recently. I've sent you some instructions in the ticket you opened with me :)

    This will definitely be the problem.  If you were running a version that was already using renamed /admin directory and admin.php files then check and make sure that these files have been updated.  Seen so many stores where a mix of files has happened due to not doing a manual upgrade (or not doing it correctly) and most files will be at the latest version (for example the classes/sanitize.class.php file but the admin_XXXXXX.php file hasnt been updated

    Ian

  7. The other option is if you are interested in moving your hosting, then we provide free and full support for CubeCart as part of our E-Commerce packages, and can sort this out for you.  I will do the migration of your site over to one of our servers for free as well !

    Ian

    • Like 1
  8. 14 hours ago, Dirty Butter said:

    But be warned that I have NEVER seen a forum post on here with two admin named folders in the global.inc.php folder.

    I agree and I have never seen that before and cant imagine a way, unless manually added, how it could happen

    Ian

  9. You will also want to consider using a different skin after doing the upgrade to V6 - some of the V5 skins may appear to work but there are an increasing number of incompatible and missing features.

    Also check what caching method is being used - file will be fine although under V6, you have extra options such as much faster REDIS or Memcached.

    Finally, ensure that all non used plugin, languages, skins are deleted and that for any that are used, you upgrade to the latest version available from the marketplace

    Ian

  10. If you had to change the name of the admin file and directory then the upgrade wasnt completed correctly - did you upload /admin directory as is (the likelihood is that this is what you did) or upload the contents of the new /admin directory into your already renamed admin_XXXXXX directory.

    Check you have 6.1.8 files in the admin directory and if in any doubt, re-upload them

  11. 41 minutes ago, Dirty Butter said:

    As I understand it this should already be required. This is one place in the content.register.php file:  {$LANG.form.required}" required>  should control that.

    That of course depends on what skin you are using but do check that file to see if your skin has that code

  12. It isnt a simple 5 second change as there are multiple core files and areas within CubeCart that need to be changed.  There is a call for this though and a feature request for it : https://features.cubecart.com/topic/uk-counties-no-longer-used-by-royal-mail_8 and also another feature request to make the address layout dynamic based on the country of the customer - see https://features.cubecart.com/topic/dynamically-adjust-address-layout-to-suit-country-format_9

    Voting on one or both of those would help to get it closer to the top of the list of items that will get done

    Ian

  13. 17 hours ago, violinman said:

    What seems to be happening is that the redirect does the correct thing in that it appends the correct url to the domain name but then the SEO Rewrite stuff adds the old URL to the end of that!

    Is their anyway to make sure the SEO Rewriting is disabled for the 301 block?

    If your 301 ReWrites are written correctly and are located in the .htaccess file in the correct location, then they will work and other directives will not be processed.  How did you add these ?  The problem with giving advice on this type of thing is that there is no one simple solution that fits all and each hosting environment / hosting account configuration, can and often is different

    Ian

  14. We are also seeing this on upgrades even from 6.1.7 to 6.1.8 using the built in admin upgrade which was used to test whether it was working again.  I have reported it but no movement, so back to recommending that everyone does upgrades via the manual process - which I personally always use all the time anyway not that this helps any non-technical users

    Ian

×
×
  • Create New...