Home › Forums › Calendar Products › Community Events › Custom links defaulting to http:// on SSL
- This topic has 11 replies, 2 voices, and was last updated 7 years ago by Thomas Claffy.
-
AuthorPosts
-
March 23, 2017 at 4:49 pm #1259208Thomas ClaffyParticipant
1, So with the new build you are forcing the<my url>events/community/list to be https://<my url)/events/community/list to navigate to the page. Did I miss a document telling me this? How is it guys make these changes and provide no advice on the impact on your end users.? After installing the update, I test my site and sure enough, my custom link for events/community/list did not work. When I save the custom link as <my url>/events/community/list your force it to http://<my url>/events/community/list which no longer works when ssl is enabled. Luckily I realized it was not navigating to the page at all and manually changed the link to https://etc. Please advise where the upgrade document is that advises me of how you are going to break my site with each release? Seriously, I clinch my ass cheeks after making sure I have cleared my bowels before installing your updates because they scare the crap out of me.
2. And the Community Events build number is still 4.4.3? There is no other build available for download.
3. My site does not show correct update links for Pro and Community Events when you do release updates.. They do not give me the extra line with the new build and links to the change log. I sometimes have to install them manually or sometimes they do install when I do the bulk update in spite of no other updates on the screen the build number magically changes. How can that be?
March 23, 2017 at 5:16 pm #1259216BarryMemberHi Thomas,
I’m sorry to hear you’ve had a less than smooth upgrade experience.
My site does not show correct update links for Pro and Community Events when you do release updates.. They do not give me the extra line with the new build and links to the change log.
This is an ongoing bug and you have our apologies. We do hope to address this soon.
And the Community Events build number is still 4.4.3? There is no other build available for download.
I’m not completely clear as to your question.
On February 9 this year we released Community Events 4.4.2. Today we released 4.4.3. Both should be available for you to download on this page. If that is not the case or if I’m misunderstanding your question, please let me know.
So with the new build you are forcing the<my url>events/community/list to be https://<my url)/events/community/list to navigate to the page. Did I miss a document telling me this? How is it guys make these changes and provide no advice on the impact on your end users.?
We didn’t provide advice about this simply because it was not an intentional change and, in fact, is not one I see myself locally.
Can you clarify which links changed, exactly? Were they for example custom links added to a menu from within the Appearance → Menus admin screen, or something else? If you can provide an outline to help us replicate this I’d love to dig in and see if I can get to the bottom of it.
Right now, however, I’m not sure I see the same problem and nor can I identify changes that would have accidentally introduced it.
Thanks!
March 24, 2017 at 5:24 pm #1259871Thomas ClaffyParticipantIt’s a product we call WordPress: https://wordpress.org/
Using Custom Links: http://easywpguide.com/wordpress-manual/appearance/updating-the-menu/adding-a-custom-link-menu-item/
What is HTTPS: https://www.instantssl.com/ssl-certificate-products/https.html
Armed with all of that knowledge, is it possible for you to create a custom link as outlined in my OP in an https/ssl environment and test the issue?
Thanks,
Tom
March 25, 2017 at 7:39 am #1259952BarryMemberHi Tom – thanks for taking the time to share those super links 🙂
Armed with all of that knowledge, is it possible for you to create a custom link as outlined in my OP in an https/ssl environment and test the issue?
Absolutely and – my fault for not being clearer – I already did so but was unable to reproduce. What I was hoping to discover was if you had done something else or if there was an angle I had missed but, based on the feedback in your last reply it sounds like I hit all of the key components already.
Since we’re unable to replicate and are not currently seeing comparable reports from other users, I wonder if this is the result of a conflict or otherwise is specific to your own site?
Here’s what I’m going to do:
- I’ll move this topic from the Event Tickets Plus forum to the Community Events forum – apart from being a better home for Community Events related issues like this one, it may also help others who are experiencing the same thing to find it and chime in (don’t worry, though, the actual topic URL will remain the same so you shouldn’t have problems locating it after it is moved)
- We’ll keep an eye out for any similar reports coming in and see if we can gather the information we need to replicate on our side from there
On your side, how much of a problem are you left with here — is this going to require a large clean-up effort? I’d love to have a better idea of the scale of the problem so we can prioritize accordingly.
Last but not least, I apologize for any further delay: team commitments mean we’ll be operating at a reduced level of service in the week ahead.
March 25, 2017 at 7:51 am #1259956Thomas ClaffyParticipantHey Barry,
A little programmer humor 🙂 Yeah, I’ll keep my day job (they said I have to give them one years notice so they can train my replacement).
Anyway, it took me a whole couple of minutes of scratching my head to figure out the link was not working and then I saw it was http:// and your release notes mentioned https:// so I guessed at the solution. To recreate this you may need the steps my site went thru, i.e., community events was installed in http://, the site was switched to https://, you changed your code breaking my incorrect link. Had you updated the custom link or handled a redirect or WP not forced a fully qualified path, I likely would have never seen an issue.
Probably a Unicorn that only I have so placing the thread in the community events forum may be helpful to some other dinosaur. Cheers. Don’t kill too many brain cells.
March 25, 2017 at 8:03 am #1259958BarryMemberOK, thanks for the update.
your release notes mentioned https://
This is true, though the changes were in relation to static links embedded in the plugin (we link to the wordpress.org forums and other places from the help pages, for example, and updated those to use the HTTPS protocol) — we didn’t implement anything in this release that would impact URLs stored in the database such as post content or custom nav links and we didn’t modify anything relating to the dynamic generation of event URLs.
Again, it is possible we inadvertently introduced something but I just don’t see it at this time. To be safe, let’s keep this topic open for the time being in case we, you or another community member hits on something useful that might help.
Thanks!
March 25, 2017 at 12:18 pm #1260079Thomas ClaffyParticipantJust a visual on what is happening.
April 4, 2017 at 4:45 pm #1264499BarryMemberHi Thomas,
Apologies for the further delay: many of us were unavailable last week due to our annual team trip.
Thanks for the visual. Can you clarify though if this is an ongoing problem that is too big to resolve manually, or that is proving impossible to resolve manually?
Thanks!
April 4, 2017 at 8:47 pm #1264601Thomas ClaffyParticipantNo, as you can see I resolved it manually but the next guy might be so quick
on the draw. Seems like a minor but that should be fixed is all.April 5, 2017 at 4:15 pm #1265473BarryMemberDefinitely, if we could confirm this as a bug it would be great to fix it. As before, however, have been unable to replicate this (nor have we seen comparable reports from other users). We’ll definitely keep and eye out, though.
Thanks again for reporting this: since in your case the problem is resolved I’ll go ahead and close this topic – but if we can assist with anything else please do let us know and one of the team will be only too happy to assist 🙂
April 27, 2017 at 9:35 am #1275277Support DroidKeymasterHey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.
Thanks so much!
The Events Calendar Support Team -
AuthorPosts
- The topic ‘Custom links defaulting to http:// on SSL’ is closed to new replies.