Announcement

Collapse
No announcement yet.

Switch to URI Management then convert to https

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bruce - PhosphorMedia
    replied
    We do it. While for search engines, its not required if all inbound links are using https, but it prevents someone from typing in a url without a protocol and getting the http version. it only take a few minutes if you use Batch Edit mode. (i.e., from the list of User Interface pages, just double click the checkbox, then click once more to check it, then press enter and go to the next one.

    Leave a comment:


  • danceman
    replied
    Thanks - I was reading the conversion process and the site configuration section must be a little old - it doesn't show or cover if the "link to all pages using HTTPS" button should be ticked or not? Should it?

    Leave a comment:


  • lesliekirk
    replied
    Originally posted by danceman View Post
    we are just on a limited budget and didn't realize it could take that long.
    I have a true understanding of limited budgets. You made it through the Miva docs for the URI Management updates. Here's something to help you with the HTTPS conversion if you want to give it a try:

    https://www.miva.com/blog/how-to-con...tore-to-https/

    Leave a comment:


  • Bruce - PhosphorMedia
    replied
    Not directed at Danceman, but for others who might be reading...

    What is also not mentioned is that, once a developer does ANYTHING on a site, its common (and perhaps understandable), that should ANYTHING else go wrong, at the very least, they have to respond to an email assuming it was something the developer did.

    Quick Story: I once had a leaking head gasket in my car. Went to my mechanic (known him for over 30 years) and asked how much to fix it. Said it was $800. Looked at him carefully and said what? (Cause I could do it myself in less than 4 hours.) Then he smiled and said he'd charge me $400. The difference wasn't because I was a friend (as a friend, I'd want him to still make money), it was because he knows I won't be bringing the car back the next day saying "ever since you changed my head gasket, my turn signal don't work...happens all the time.

    Leave a comment:


  • GDesigns
    replied
    danceman No worries, no offense taking on my end. Make sure to update anything Google to HTTPS, run something like XENU link sleuth before (save report (and after) then fix what needs fixing. Make sure to test everything afterwards, including modules, search, continue shopping, etc.

    Leave a comment:


  • danceman
    replied
    Hi everyone,
    I followed the Miva instructions on the SEO to URI conversion and then updated (clicking the button) the htaccess file which I will assume then sets the rule (looks like it did it when I view it) - I've run through the website, shopped it, and everything seems to have been converted (seems to be running alot faster too now) fine. I guess I can't imagine 4 hours to do that, but also understand not wanting to get "burned".

    On the https conversion, I"m trying to think offhand if I even did ONE hard code anywhere (don't know if the template I installed from Miva has some but I'm guessing not) - if I did, it's ONE I believe (from attempting to install a product rating module that doesn't seem to want to work), and from reading on this process of http to https, isn't there a webmaster tool that is used after conversion to quickly find and show anything that isn't https so edits can be made?

    Thank you for everyone's input. I hope it didn't come off as insulting - we are just on a limited budget and didn't realize it could take that long.

    Leave a comment:


  • GDesigns
    replied
    I am pretty sure the 2-4 was us, and yes, we try to look at and catch everything. If it takes less time, we will of course charge less, but I don't want to quote 30 minutes just to tell you, sorry - it's 4 hours because of xyz...
    Hope that made sense.

    Leave a comment:


  • Bruce - PhosphorMedia
    replied
    Originally posted by lesliekirk View Post

    When Bruce mentions "correct access" a developer needs both administrative access and FTP access. It is highly recommended that you take the time to set up separate FTP access for each person that needs FTP access.
    good point...maybe someone with an voice to miva's ear should suggest and 'on-boarding' document that lists not just 'the access' info but a few quick 'best practices' i.e., 'how to engage help' might be one topic :)

    Leave a comment:


  • lesliekirk
    replied
    Originally posted by Bruce - PhosphorMedia View Post
    depends. did the developer actually look at the site and determine what's necessary? yes, it can be done in 10 minutes...but sometimes takes longer. For example, if there are any hard coded "OLD" urls in the site. also, did you create .htaccess/uri rules to change the old style links to the new ones? did you run a link test to ensure everything was done correctly? all these things take up time. heck, its usually at least 15 minutes to get the average store owner to get you the correct access to the site....so yah, maybe...maybe not.
    When Bruce mentions "correct access" a developer needs both administrative access and FTP access. It is highly recommended that you take the time to set up separate FTP access for each person that needs FTP access.

    Leave a comment:


  • lesliekirk
    replied
    I always quote at least 2 hours for an http to https conversion. There are a lot of gotcha's that the store owner might not have thought about. Some stores are loaded in hard-coded links that should be redone. Sure you can use a "catch-all" few lines in your htaccess file, but those links should be updated. I've been doing these types of conversions for a while now (pretty much when Google starting talking about all HTTPS) and no two stores have been the same.

    Leave a comment:


  • Bruce - PhosphorMedia
    replied
    depends. did the developer actually look at the site and determine what's necessary? yes, it can be done in 10 minutes...but sometimes takes longer. For example, if there are any hard coded "OLD" urls in the site. also, did you create .htaccess/uri rules to change the old style links to the new ones? did you run a link test to ensure everything was done correctly? all these things take up time. heck, its usually at least 15 minutes to get the average store owner to get you the correct access to the site....so yah, maybe...maybe not.

    Leave a comment:


  • danceman
    replied
    Still looking for someone to convert from http to https. Also, I'm not calling anyone out, but was quoted 2-4 hours to switch praisewear.com over to URI before doing the https conversion, so I took a crack at it myself and in about 4 clicks, I did it myself in 15 minutes.

    Did I miss something major here that a developer would quote 2-4 hours? I can't believe switching to https would be more then what, 2 hours for a experienced developer?

    Leave a comment:


  • danceman
    started a topic Switch to URI Management then convert to https

    Switch to URI Management then convert to https

    Hello,
    Looking to hire someone to do the above - I can switch to URI before the conversion but just figured would let the developer do it and then convert the site to https. Website is www.praisewear.com. Please email quote to [email protected]
    Thanks!
Working...
X