sharpenedpixels
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] Purge cache doesn’t seem to be working after latest updateSeems the CSS and JS files did clear out after a short period of time. However, the little dialogue that used to pop up in the dashboard to say the purge was complete is no longer displaying. Was this an intended change? It threw me out a bit because that wasn’t showing as normal and the files didn’t clear out immediately, which made me think it wasn’t working.
Any chance you can add the dialogue back in to show a purge has been completed?
Forum: Plugins
In reply to: [All-in-One WP Migration and Backup] Serious problems uploadingThanks for your reply. I find it hard to believe this is an issue with my hosting environment when this plugin worked perfectly well for several years on the same hosting and now is having issues all of a sudden after a major WordPress update. Nothing has changed on my hosting from before when this always worked flawlessly. Unless the plugin has changed and requires more resources or uses a different method to apply an import now which could mean it could require more modifications to the hosting, but I am in charge of all of that and haven’t changed anything. However, I will check the logs to see if it pinpoints anything, but I have got a feeling it won’t be much help as I have literally tried and checked everything a few times before when this happened.
If I get any joy, I will reply to this thread.
- This reply was modified 3 years, 3 months ago by sharpenedpixels.
- This reply was modified 3 years, 3 months ago by sharpenedpixels.
Forum: Plugins
In reply to: [Contact Form 7] Displaying field values in form before submitting@enet2020 thanks for the suggestion, but this plugin is no good for what I need. I’m building a multistep/conditional logic form on one page. That plugin only works by having separate forms on different pages. I did find a solution for this anyway, using conditional logic.
Thanks for taking the time to reply.
Hi @ironikus,
Thank you for letting me know. I have just updated the plugin to the latest. I’ll let you know if I find any other bugs.
Thanks very much for all your help.
Yeah, you are right, there would be several variations of phone number formats, which might make it hard to cover every single one. It just would be awesome if this was possible.
Of course, happy to help out with beta testing. Just let me know when you have something ready to test.
No problem at all @ironikus =)
Hi @ironikus,
Apologies, I have retested the button. Previously, it looked like it wasn’t being encoded as when I inspected the element via Chrome, I could still see the email as normal. After your response, I ran the test again and checked the source code. From this, I can see the email in the button is working fine and encoded.
Thanks for clarifying this.
Hi @ironikus,
Thanks for investigating this further.
I downloaded the new zip and installed it to test and it seems to be working as expected.
I created 4 pages and all are encoding the emails in some way and converting them to mailto links. Also, any email displayed in the meta title and/or description are being encoded as well, which is perfect.
See the 4 pages below:
https://plugintest.sharpenedpixels.co.uk/
https://plugintest.sharpenedpixels.co.uk/test-page-without-divi/
https://plugintest.sharpenedpixels.co.uk/test-page-without-divi-no-email-in-title/
https://plugintest.sharpenedpixels.co.uk/test-page-with-divi/
Thanks very much.
Hi @ironikus,
Thanks for looking at this. I have now run some further tests my end and have got the phone number encoding in the areas I previously tested, including the ACF wsywyg editor, using:
<a href="tel:[eeb_protect_content method='encode']+441234567890[/eeb_protect_content]">[eeb_protect_content method="encode"]01234 567 890[/eeb_protect_content]</a>
Thanks for your help.
P.S. Are you still planning to implement a way to auto encode phone numbers too? I really hope you are, and also the ability to convert plain phone numbers to links. That would be awesome if these could be added at some point soon.
Hi Ironikus,
I have just tested this issue as I too run Divi theme, but there is an issue with the email being used on a button.
Unfortunately, your answer doesn’t help resolve the issue.
You are right that mailto: needs to replace https:// but when I added mailto: to the link field of the button module, it did nothing at all. The email was not protected by the chosen method in the settings.
To clarify, I used this as the link – mailto:[email protected]
Kind regards,
Kevin
- This reply was modified 4 years, 1 month ago by sharpenedpixels.
Hi @ironikus
Thanks for your response. I really appreciate you taking the time to try and help sort out the issue.
I have just tested the code provided, but it caused the javascript to display again. I changed it to this to fix it:
<a href="tel:[eeb_protect_content method="encode"]+441234567890[/eeb_protect_content]">[eeb_protect_content method="encode"]01234 567 890[/eeb_protect_content]</a>
This sorted the issue where the html was being displayed on the page, however, it seems to strip out the tel link altogether in the source code. So, in the source code it now outputs like this:
<a>01234 567 890</a>
I also tried:
<a href="tel:[eeb_protect_content]+441234567890[/eeb_protect_content]">[eeb_protect_content method="encode"]01234 567 890[/eeb_protect_content]</a>
But this caused the link to output with the javascript that was displaying before.
Seems like it may need a bit of tweaking in the original plugin code to get it working correctly.
I appreciate you taking the time to respond to all my queries and that you are willing to include some of my suggestions in a future release.
I don’t suppose you have a roadmap of what is being worked on and what is on the list of suggested updates for future releases? I’m very keen to include the plugin in all my website projects, but need to make sure it is working as expected. I appreciate it is a free plugin, and development of the plugin may not be a priority right now, but if you could give me some sort of timescale of when you might include the tel links being automatically added to plain phone numbers like the email links, I’d be very grateful.
Hi @ironikus
Ok great, thanks for letting me know. Only thing that still isn’t working after implementing your fix, is that it isn’t applying making the number a link like in the other ACF fields. It seems to be ignoring the html code and displaying the whole code on the website, see the page again for the example of what I mean: https://plugintest.sharpenedpixels.co.uk/test-page-with-divi/
And just regarding the country code, I feel it will be valuable to most people, as websites are global and can be accessed from any part of the World. If someone from another country were to try and click on the phone number to call, I don’t think it will work. This was the reason I suggested adding some way of the users being able to add their country code in the settings somewhere, so this could replace the beginning part of the phone number in the link only. I imagine this would help decrease bounce rate too, as I expect visitors would leave a website if a clickable phone number didn’t work as expected.
I have just sent a message via your form on https://ironikus.com/contact
Kind regards,
Sharpened PixelsHi @ironikus,
I feel you may have completely misunderstood the problem here, as your answer is confusing and doesn’t seem to answer my problem.
The shortcode
[eeb_protect_content]
is for protecting phone numbers, is it not? So I can’t understand why you have said it doesn’t turn emails into mailto links. This is not the issue.The issue is as explained above that some emails on some of the pages are not being converted into mailto links and some pages are. I have not used any shortcodes to wrap around the emails, just typed in plain text emails like this
[email protected]
in the content areas that I have tested across the website.I was under the impression that if I enabled the ‘convert emails into mailto links’ setting in the advanced settings section, then this would automatically convert all plain text emails across the website without the need to add any shortcode or anything. And, it works flawlessly on most pages, but just not the one page that had the email typed into the main content field.
If it would help, I am happy to do a screenshare with you and call on the computer to explain fully. That way it may be easy to explain the issue, as I feel I may not have explained it well enough previously.
Hi @ironikus,
Thanks for your response and clearing that up. Still I’m unsure why one page hasn’t applied mailto links like the other two. You can see the three examples below with explainations:
https://plugintest.sharpenedpixels.co.uk/
Uses the standard WordPress editor but has no content in the text editor field.
Encoding emails fine and adding mailto links to all email addresses.https://plugintest.sharpenedpixels.co.uk/test-page-without-divi/
Uses the standard WordPress editor and has email and phone number with encode shortcode in the text editor field.
Emails are encoded, but use a different technique to the homepage and the emails are not being converted to mailto links.https://plugintest.sharpenedpixels.co.uk/test-page-with-divi/
Uses the Divi builder to add content.
I have used an array of different solutions including ACF fields populating the sections with the same content throughout.
Emails are encoded fine and also added mailto links.NOTE: I tested adding content to the homepage content field, to see if it was affected. I tried adding the same content from the page https://plugintest.sharpenedpixels.co.uk/test-page-without-divi/, which was this:
[email protected] [eeb_protect_content]<a href="tel:+441234567890">01234 567 890</a>[/eeb_protect_content]
This then caused the page to not convert emails to mailto links, although, like the other page, the emails were encoded. Very odd.
I also tested adding this to the content field:
Again, this caused the same problem.
I also tested adding this to the content field:
[eeb_protect_content]<a href="tel:+441234567890">01234 567 890</a>[/eeb_protect_content]
But it was fine and all emails were encoded and included adding mailto links. So seems there is an issue when an email is added to the content field.
If you need anymore info, please let me know. I can setup more pages with examples if needed. I’d love this to get sorted as this will be a really useful plugin.
I look forward to your response.