• Home
  • Get help
  • Ask a question
Last post 11 hours 18 min ago
Posts last week 94
Average response time last week 34 min
All time posts 67837
All time tickets 10483
All time avg. posts per day 20

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.

#2575 – Article Published with EasyBlog > Redirection Error Since Linkedin

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, 04 August 2016 15:18 UTC
didier.auss
Hello
We use EasyBlog to manage the blog of a website. You can automatically publish a blog post on LinkedIn account through an API.

We encounter a bug if this automation is done in the back office. We lose re-written link and image. So, it is the Joomla crude link is recovered (screen capture A2 and C). By clicking on the article link in LinkedIn, the article appears on the website but on the home page (screen capture A1), rather than appear in the section of the website (screenshot and B1 B2).

We contacted the support EasyBlog with this answer:
"Actually that was known issue in Sh404sef extension, if you published new post from backend, that post URL will not show SEF URL e.g. http://xxxx.eu/index.php?option=com_easyblog&view=entry&id=32 , is because SH404sef do not render the SEF URL from backend, it only render on frontend.





In other word, if you publish your new post from frontend, that post URL which post to your Linkedin account, it will show correctly the post URL and the image also show correctly.


"


When do you think? I changed the settings of sh404SEF, but that does not change (screenshot config-sh404SEF) ...

There is no problem if we created and published the article from the blog front office

Thank you for the help you could bring me
Thursday, 04 August 2016 16:11 UTC
wb_weeblr
Hi

"Actually that was known issue in Sh404sef extension, if you published new post from backend, that post URL will not show SEF URL e.g. http://xxxx.eu/index.php?option=com_easyblog&view=entry&id=32 , is because SH404sef do not render the SEF URL from backend, it only render on frontend.
This is not correct, or rather misleading. No extension renders full SEF links from the backend, this is not part of Joomla API.
Good extensions such as AcyMailing handle that nicely, but it seems EasyBlog has not work enough on this. We actually have an API for 3rd party such as Easyblog to still get the SEF URLs from the backend.

The general use is:
Sh404sefHelperGeneral::getSefFromNonSef($nonSefUrl, $fullyQualified = true, $xhtml = false, $ssl = null)


This is what they should be using when sh404SEF is installed.

Hope this helps

Rgds
 
Friday, 05 August 2016 09:15 UTC
didier.auss
Hello,

Thanks for your feedback. I did follow the info EasyBlog ...

Is what I can do something, waiting for a patch of EasyBlog? Is it possible to disable "temporarily" SH404SEF for blog posts?

Bests regards
Didier A.
Friday, 05 August 2016 09:23 UTC
wb_weeblr
Hi

Yes, the problem must be fixed in EasyBlog. You can can currently set EasyBlog to "Leave as non-sef" under the "By components" tab of config, but I wouldn't recommend that, this would change all links, just for the sake of this sharing feature. Don't they have an option to just leave links as non-sef when in the backend?
That way, you can enable "301 redirect from non-sef to SEF" in sh404SEF, and those non-sef will be redirected to their SEF equivalent automatically. That would certainly be the most robust solution.

Rgds
 
Friday, 05 August 2016 12:13 UTC
didier.auss
Thank you for your comeback,

I tried several types of configurations and it changes nothing ... the URL rewritten is lost if publishing from the back office to LinkedIn (though the rewritten URL is present at the blog).

By against the url rewritten is present on LinkedIn and on the blog if publishing since frontoffice ...

I await the return of EasyBlog media ... it's a shame because the rest of this component is very well ...

Thank you for your help, I leave the post open days, if new information came
Friday, 05 August 2016 12:21 UTC
wb_weeblr
Hi


I tried several types of configurations and it changes nothing ... the URL rewritten is lost if publishing from the back office to LinkedIn (though the rewritten URL is present at the blog).

That's what I said. This can only be fixed in EasyBlog and nothing in sh404SEF can help.

Rgds
 
Saturday, 20 August 2016 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.