Entering Your URL When You Comment on PFRE

June 14th, 2018

I’ve recently gotten several questions and comments about the fact that to make a comment on PFRE, you have to enter your URL, and why should you have to enter the “http://” part?

So here are some points that explain why this can’t easily be automated:

  1. Some sites must have an http:// and some sites must have an https://. If the wrong one is used, the URL doesn’t work.
  2. Some sites require a “www” while others won’t work with a “www”, depending on how the domain is registered.

A fast, easy way to get the right URL:

  1. Display your site in a browser in a separate tab.
  2. Copy the URL field.
  3. Paste the copied URL into the comment URL field.

Sorry that some find this requirement annoying but since we’ve made this change in April 2015, the discussions on PFRE have been much more civil and when someone makes a comment, you can look at their site to judge their credibility.

Share this

8 Responses to “Entering Your URL When You Comment on PFRE”

  • In this internet world where so many are doing their best to kill the Golden Goose, I think this is a very good idea. I have been on too many FaceBook groups where when they started, discourse was civil and productive. Then a herd of people with anger management issues arrived with truncated vocabularies and it destroyed what was so good about civil disagreement not to mention useful discussions where people knew how to form a sentence and a paragraph. So Larry, keep it up. You certainly have my whole hearted support.

  • Larry, I support you as well! It takes care of the trolls as well. We are a rather tight knit community here. We all like the focus of the group. I am not sure if anyone thought about it…it is ZERO drama here. No one wants it!! I remember at one time some tried and it got shut down quickly since everyone here knows it is counter productive, so….LOL!!!….. nobody responded!! Do not fix something that is not broke…It applies here to! Just keep doing what you are doing Larry! / Cheers!

  • Honestly it’s not a big deal to do this. I would recommend using an app like Dashlane to store commonly entered information. It automatically entered everything I needed and I was ready to submit.

  • Larry,
    this blog has truly made me a much better RE photographer. The positive feedback and suggestions from our fellow RE photographers who are experiencing the same issues has certainly helped.
    I feel this site should continue to be comprised by the professional photographers who are making a living and adding solutions to any problems we all encounter.
    so many people on this site have graciously shared their experiences and problems with this group, and almost all of the feedback, has been positive.

    Thanks for starting this blog

  • Good move. I don’t see why anyone should take issue. The site is for professionals. Professionals have a website…and act professional.

  • I agree, the URL is helpful in keeping the conversation civil. But I am going correct some of the blog information.

    http / https and www / non-www all have to do with how a site is configured. If a site is configured correctly you should be able to use either www or a non-www URL. In addition, http should be redirected to https. Since https uses encryption for security, a https address should never be redirected to a http address.

    If you site doesn’t redirect traffic properly, contact your administrator, web host, or how ever set it up and find out why.

  • I find having to add the http:// everytime a real pain in the backside. When people visit my sites they don’t have to add http:// – just www. etc is good enough. Even with my shop you are automatically redirected to https://

  • Requiring the website definitely cut down on trolls! I hadn’t thought about the http: https: issue and good suggestion to simply copy it from another browser to make sure if not certain what syntax your ISP/web host supports. Http: may be going the way of Flash thanks to Google as they are in the process of giving priority to Https: in searches and overridable non-secure warnings when loading a http” page (like currently get with Flash). No certain of the full implementation date but may want to monitor your own websites for the notifications or search drops. Learned of it recently due to another issue where I had a domain shut down by the ISP host due to a malware attach altering some .php files and involved trademark infringements of some bank I never heard of as well as AARP’s logo. Nasty stuff that I had to get cleaned out before they would reactivate what essentially was a non-developed domain with obsolete files when at my former Broker but now auto-forwarded to my current Broker’s agent corporate web page. It was at that time that I thought of converting my 5 domains to SSL (secure socket layer certificate) https: but don’t want to pay the current host when can get it elsewhere for free.

Comments RSS

Leave a Reply