• Home
  • Get help
  • Ask a question
Last post 2 hours 11 min ago
Posts last week 89
Average response time last week 30 min
All time posts 67693
All time tickets 10463
All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#3491 – Social Buttons plugin tags get converted in frontend editor

Posted in ‘sh404SEF’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Thursday, 06 April 2017 10:07 UTC
TheSDHotel
Hey there man,
I noticed an issue. The plugin tags of the Social Buttons {sh404sef_social_buttons}
get converted even when inside the front-end editor. This is a problem because now the plugin tags are no longer there and are replaced by the direct facebook/twitter/social html code (which on top of everything can also sometimes be broken based on html filters of the editor etc.), so when you save the article, you now save it with that code.

If possible, the plugin tags shouldn't be converted inside the frontend editor. This problem doesn't happen in the backend editor of course.


EDIT: HAHA Look they just got converted here too! Look at the buttons and look at the source text of my post. :)

I actually wrote
{ sh404sef_social_buttons }
(without spaces)
but now that tag is no longer there and it got replaced by the buttons
Thursday, 06 April 2017 10:22 UTC
wb_weeblr
Hi

Thanks for the report. That doesn't seem like a big issue as nobody ever complained, but I can think of a way to mitigate that, at least in some specific situations.

It cannot be solved in general (like for all extensions that uses an editor) but if talking about com_content only, I can identify that page and block the replacement. It's been added to the feature tracker.

Rgds
 
Thursday, 06 April 2017 10:30 UTC
TheSDHotel
That's true, there are also more extension that can use an editor in the frontend.
But yeah, the main one is com_content only really. The only other one (native ) that I can think about is modules, as also modules could be edited in the frontend, but I really think the use of the plugin tags in modules would be almost none (and also, who edits modules from the frontend really?), or anyway pale in comparison to the com_content use, which is definitely more likely to be used.
Thanks!
Friday, 07 April 2017 07:15 UTC
wb_weeblr
Hi

(and also, who edits modules from the frontend really?
About just as few who edit articles on the front end. In my experience, this is extremely rare.

Rgds
 
Saturday, 22 April 2017 05:34 UTC
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.