Hey Dayo,

Based on your screen shot, it seems as though the errors are being generated from within Joocial. As I am unsure as to what Joocial is actually trying to do with these forms, perhaps it would be ideal that you try to create a ticket with them.

We would be more than happy to collaborate with Joocial in getting this solved but to be honest, we don't really know how Joocial works and what scripts are involved.

Cheers Mike,

It is indeed from Joocial and I do have a ticket with them. Can only hear crickets chirping there though.

Took a look at things and is seems the error is because they assume the EB composer form is called "publishing" but a look at the source shows it is called "composer".

Changing their files accordingly solves the issues. Will update them accordingly.

Hey Dayo,

Thanks for updating us on this and glad that you managed to figure this out. I would strongly suggest that you push this patch to them and get them to apply this fix in their codes in their next release as it would cause less issues in the future for them

Thanks again Dayo!

Update on this and the other post at https://stackideas.com/forums/self-explanatory-question-is-why.

The reason for the confusion in the response given by Extly (stating that the Joocial social publish was broken by you guys with the EB 5 release is that they were talking about the default EB Composer.

It turns out that the Joocial Social Publish Button appears if using TinyMCE as editor but it does not appear if using the default EB Composer.

So, the fix I found only applies if using TinyMCE. If using the default EB Composer, the integration is broken as stated by the Extly Team.

Apparently something fundamental was changed in the default EB Composer with the EB 5 release and none of their JS is loaded with the default EB Composer meaning that no integration is possible in this case as things stand.

If using TinyMCE as default editor however, all their JS is load and the fix I posted makes it work as intended.

Extly will push out a release with this incorporated at some point. Looks like they can't see a way to make it work with the default EB Composer as things stand.

Something the two teams can get together to resolve?

Hey Dayo,

Hm, not really sure what they are trying to do here but I am all in to get this resolved. I will try to get in touch with Anibal on this matter. Do you have a thread identifier from Joocial or should I just mention Dayo in the e-mail?

Hi Mark,

The ticket ID on Extly is #5494.

Summary of the Issue is:
1. With the Inbuilt EB Composer, the Joocial "Social Publish" does not appear at all. See https://www.screencast.com/t/iTbLM2J8FJW
2. With TinyMCE, it does appear but does not work. See https://www.screencast.com/t/4BkDu2IwIjMN

With TinyMCE, while the Joocial options are shown when the button is clicked and users can select various options, these are not saved anywhere and have no effect without my fix in place. Extly is looking at updating Joocial to include the fix after they do their due diligence.

So basically, there is a way forward with TinyMCE. What you could work with them to resolve is coming up with something for the Inbuilt EB Composer (if possible) for those that use this.

Hey Dayo,

Hm, strange, how does this work before EasyBlog 5.1 update? EasyBlog does not render any editor buttons in Joomla when using it's built in composer and there was no way for Joocial to inject those buttons in the composer even in version 5.0

Was just wondering how it was done prior to the update eh?

Mike,

Extly said "StackIdeas broke the Social Publish Button Integration when EB 5 was released". I took that to mean EB 5.0.

I have only started really leveraging Joocial in the last couple of months and as I never could get my head around the inbuilt Composer and switched my default editor much earlier that, I can't really tell. I suppose it never worked with the inbuilt composer since EB 5 as Extly says.

Works with CodeMirror as well btw (With the Fix): https://www.screencast.com/t/7SJb6ZN7xB

Yeah, that's correct because EasyBlog's built in editor is different than the rest of the editors. Our intention of developing the built in editor is primarily to cater for users who aims for simplicity and to not have the user see all these galore of buttons on a WYSIWYG editor. Most of them wouldn't be used anyway.

Let me discuss this with Anibal and see if there is any way for them to inject a link on the page and allowing them to configure this.

True that the buttons can get a bit OTT.

I actually now go for this after missing the social button earlier in the mess of button: https://www.screencast.com/t/T3SGYkHBNB

Shows the Joocial and AlterUserPoints buttons.

I can see that trying to inject the Social Publish would create new issues. How about others? Alter, etc etc etc?
Probably best to stick with your design decision and leave them out altogether. Those that want them should use other editors.

Hm what does that button do actually? Do you have a screen shot of that functionality?

For Joocial:
https://www.screencast.com/t/edMOdmFsQ
https://www.screencast.com/t/osGvEtcoREJ
https://www.screencast.com/t/pyQRmGzVj
https://www.screencast.com/t/C0oRX9gcKDM
https://www.screencast.com/t/knIlTwGjm
https://www.screencast.com/t/aWIwphQPRGi6

.. and for AlterUSerPoints:
https://www.screencast.com/t/dPZZUgBABj

Assume there are other extensions that inject buttons into the editor. I only have these two that do so.

Thanks for the input on this Dayo. What happens when you hit submit ? Does it automatically push the contents? Or does it just add some contents into the post?

Not 100% sure but I believe what they do is:

1. Add a hidden form input element (autotweet_advanced_attrs) to the EB Editor form
2. Add their Joocial form mapped to the Social Publish button for users to input data
3. When a user clicks submit on the Joocial form, json encode the data and update the autotweet_advanced_attrs element in the EB Editor form
4. Listen for EB article creation/save events and retrieve data from the autotweet_advanced_attrs element when event is triggered
5. Save the data into Joocial database tables along with the EB Post ID

They are now free to do their thing separately and can pull blog titles etc from the EB post database table later as needed.

Again not 100% sure but roughly what seems to happen.

Hm, I see. Then it is going to be really tricky to implement this in EasyBlog's built in editor because of the way their plugin works

Either way, let me write an e-mail to Anibal and see if there is anything that we can assist on our end to make this work.