Saurabh

Hi @hollosch,

Could you mention the url to your site, so we can register and see what’s happening for ourselves?

Regards.

Hi,

Although the code is not complete, it is translation ready. The 1% translation that existed was just us experimenting with GlotPress.

@nobodyridesforfree, You’d have to register on https://rtcamp.com, after which you’d need to go to https://rtcamp.com/translate and maybe, re-login with your new username and password. You can start contributing to the translation, straightaway. The Italian set is here: https://rtcamp.com/translate/projects/buddypress-media/it/default

Although the code works, there’s still a bit of refactoring left before we release 2.4, so you could add your transalations and we could include it in the release.

Regards.

Hi,

Apologies for the delay, but we are refactoring all the code we’ve written over months and are a little short of resources, as Rahul as mentioned above.

However, tasks are being completed and work is progressing fine, even though its not as fast as we’d have wanted. You can see the progress here: https://github.com/rtCamp/buddypress-media/commits/master

As you’d notice, almost all our strings have been made translatable and we have started implementing GlotPress here: https://rtcamp.com/translate

We’re into the final stages of the refactoring. Once we’re through with the strings and before the testing and release, we’ll open the translation project, where we’d like to invite you to contribute.

Now, we are new to GlotPress, so not sure if we can start the translations, right away, or we would have.

It’s just a matter of days!

Regards.

Hi Quentin,

Thanks for the frank review and the appreciation.

The facebook count displays shares and not likes because of the restrictions put by facebook on customising the like button. Luckily for us, this has changed and soon we will be able to have the like functionality. If we used the like button like other plugins, we’d have to load facebook’s js and other markup, which’d have defeated the core value of the plugin.

As for the manual placement vs placing the links via options, we left it like that for the time being, so one could customise it whichever way they feel right. However, the demand for such setting has stepped up recently and we’ll definitely add it soon.

Now, as soon as we do these and more as seen here: https://github.com/rtCamp/rtsocial/issues?state=open, I’m sure we can lure you back to the plugin and get the 5 stars! ??

Thanks again for the feedback.

Hi,

We managed to fix this finally. Could you update to 2.1.9 and confirm?

Regards.

Hi,

We’ve just fixed this with the 2.1.8 version. Kindly confirm if it works for you.

Regards.

Hi,

I looked around and found this thread: https://www.ads-software.com/support/topic/buddypress-22?replies=3

That led me to: https://somdefabrica.com.br/members/cesar/

And finally, look at this screenshot. The other plugin breaks royally with BuddyPress, as you can see in the highlighted are (slight red tint).

This is not an issue with BuddyPress Media. You’d have to ask the plugin author to make it compatible with BuddyPress or hire someone for custom development.

Regards

Hi,

The linkedin share button uses a page summary (which is essentially, the page excerpt) within the query that goes to linked in. Normally, rtsocial filters this and strips out all html. In this case, for some reason, it’s unable to.

One of our developers is looking into whether we can get rid of the summary, altogether, without breaking the linked in share. If yes, we’ll remove it. It has been a cause of headaches, quite frequently. Otherwise, we might have to resort to an optional js load that can strip the html that escapes our plugin’s php.

This might take a while.

Regards.

Thank you for the appreciation!

Hi,

Could you post a link of where this is happening? This could be due to any of many reasons. It’s not possible to speculate why that’s happening without looking at the error live. (Although, most likely, this could be due to js conflicts.)

Regards.

Hi,

Facebook from the very beginning has maintained that likes and shares are going to be same thing. In fact, according to Facebook, the share functionality that we use currently in rtsocial, has been discontinued(?) long ago!

Recently, there have been a lot of minor changes in Facebook’s API. One of which says that the current like button will be discontinued (it already has been, apparently in November). This new like functionality will require an app registration but will allow people to build custom like buttons. This means we’ll be able to have a ‘proper’ like button as soon as there is absolute clarity on this.

Other buttons are in the roadmap and the code is being rewritten. However, like I mentioned before, the work’s paused for a while, in favour of some other, more demanding tasks we have at hand. You might want to contribute to the development with your suggestions. In fact, I’d like to invite you to add the 0’s issue in the issue list here: https://github.com/rtCamp/rtsocial/issues. This helps us track and fix issues better.

Finally, thanks for your support and encouragement.

Regards.

Hi,

I don’t know how this happened. I reverted the code to the earlier one, without the fix for the 0’s and everything works as fine. No 0s getting added any more.

Could you confirm this?

I swear, even I got the 0’s on a couple of test sites, earlier.

Regards

And just like that. We fixed it. Kindly upgrade to 3.1.5 and let us know, if you still get the error.

Regards.

Hi,

This is actually a little more complicated than we assumed. For some reason, whenever wordpress shows up the post excerpt, it also takes rtsocial that had been added to the post content for display and strips all the html, leaving just the counts and adds them to the excerpt. And after this, rtsocial is added to excerpts, as it should.

Ideally, rtsocial should not be called ‘before’ creating the excerpt. However, this is happening now. Not sure if it is a bug in wordpress or a deliberate change. This will take a little time. Kindly bear with us.

Regards.

Hi,

It seems rtsocial adds 0’s to the end of the content when js is disabled (like in feeds).

This is definitely a bug in our code. Sorry for that and thanks for reporting it. Unfortunately, today we’re closed for business. We’ll check the code and if a quick fix is possible, we’ll update it promptly. If not, we’ll definitely fix this in a day or two.

Sorry for the inconvenience. Thanks for the help.

Regards.