silent88uk

I was suggested this solution:

If you would like to always append a follow button at the end of an embedded profile timeline widget then the after_widget parameter should be a good place to add follow button HTML.

You can call do_shortcode on a twitter_follow shortcode to return the HTML to prepend in the after_widget argument.

Only not quite sure how exactly this should be executed? Can anyone help me out with this? where can I find the HTML code in question? I’m not a dev/coder but can do bits n bobs with proper instructions..

Hey (just2)Ronald

Yes, I’ve seen the said link and displaying the Follow button itself is not an issue, can either use existing WP widgets/plugins for that or just the available code. I specifically wanted to have them 2 as a “single item” hence I was after some existing free plug-in already offering it. It’s OK to combine as you suggest and have tried it, but sometimes it can look skewed and “separated” (and “misplaced”, rather than “connected” as one item), depending on the timeline lengths/browser/page layout etc. I’m not that much of a coder (but can edit/update the code if someone points me to the right direction)

• This reply was modified 7 years, 11 months ago by silent88uk.

Turns out, this is NOT being handled by the Polylang as such, it can be fixed by updating respective .po (and .mo !) language files located in wp-content/language folder.

You can get the complete and updated .po files for your respective language from
https://translate.www.ads-software.com/

What’s important though, if doing this manually, updated .po must be then converted to .mo and re-uploaded.

I used https://po2mo.net/ for the conversion in question

The issue of customised translation (to our liking) is now FIXED.

Turns out, this is NOT being handled by the Polylang as such, it can be fixed by updating respective .po (and .mo !) language files located in wp-content/language folder.

You can get the complete and updated .po files for your respective language from
https://translate.www.ads-software.com/

What’s important though, if doing this manually, updated .po must be then converted to .mo and re-uploaded.

I used https://po2mo.net/ for the conversion in question

The issue of customised translation (to our liking) is now FIXED.

Hey there

I suspect it’s the issue I was having recently.
https://www.ads-software.com/support/topic/how-to-hide-comments-are-disabled/

I also see that your blog post in question is almost a year (=365 days) old as it’s from Mar 12, 2016, so it might, indeed, be the same case/issue

Check your Comments settings (from WP-Admin) for this entry:

Automatically close comments on articles older than: 365 days

Untick it.

• This reply was modified 7 years, 12 months ago by silent88uk.

Hi Niall,

Perfect. It (i.e. “no footer” + after_widget) does sound like an option we should consider. Thanks a lot

Hi Niall,

Thanks a lot for your reply – much appreciated.

Yes, I realise that these are 2 widget areas – I was just wondering if there was a way of actually displaying the follow button so that it replaces the “embed” as shown in the mock-up below?

https://i1044.photobucket.com/albums/b444/silent88uk/PastedGraphic-1-1_zpslhwenj1q.png

It’s both for aesthetic and practical reasons, i.e. blog readers don’t really benefit from the “embed” hyperlink and the code made available to them, we wanted to turn into a follow button instead

Perhaps there is a way to tweaking the underlying code in order to do that?
If not, then I guess we’ll just have use both widgets, Profile Timeline and Follow Buttons.

thanks in advance for your reply

• This reply was modified 7 years, 12 months ago by silent88uk.

Hey systemsbox

Thanks for your reply. We seem to have meanwhile found the root cause for it, it was down to Comments settings:

Automatically close comments on articles older than: 365 days

So, for the posts older than 365 days we were seeing the said message. We have disabled this particular settings and got rid of the said message being displayed.

Hi Steve..
Thanks a lot for your prompt reply. I’ll look into your solution proposal. With regards to being on the old WP version – I was told it’s to do with the hosting company charging for the backup, so she’s been putting it off, and therefore hasn’t updated WP yet, so with “other than to update” I was just looking for some temp fix until we do update…