Awesome! RC1 Download file name is called 'full beta' - Is that right?

What's the install technique going from the latest 1.4 version... I went to back-end Joomla installer and did 'Install' from 'choose file' - It uploaded the file (or at least I saw the upload climb to 100%) but then nothing.

Hey Andy,

Awesome! RC1 Download file name is called 'full beta' - Is that right?

That is correct.

What's the install technique going from the latest 1.4 version... I went to back-end Joomla installer and did 'Install' from 'choose file' - It uploaded the file (or at least I saw the upload climb to 100%) but then nothing.

I believe it hitting php script time up issue, try increase following php value into your server and see how it goes.

// More than that also okay

max_execution_time 500

post_max_size 64M

upload_max_filesize 64M

If still can't, you can use another install from directory method, upload installer from this file location -> JoomlaFolder/tmp/createNewFolderHere , then put that installer file inside this new folder and extract it.
After that go to Joomla backend > extension > install > click on install from folder > set the path link to your new folder > click install.

If the issue still persists, I would suggest you post in our issue page, so our developer will help you on this.
https://stackideas.com/issues/easysocial

That worked (I did the upload of the file to the tmp folder and install from there)... Thanks!

You're welcome Andy

Is this safe to install on a live site, or should I continue to wait? What does the RC1 stand for?

Is this safe to install on a live site, or should I continue to wait? What does the RC1 stand for?

Hello,

I would suggest that you at least try this on a staging site first to prepare for any unwanted issues like missing customization etc.

..and RC stands for 'Release Candidate' - It's standard development language used in the development cycle.. typically things start with an alpha release, then move to beta release, and then Release Candidate versions are the final ones before the stable release arrives... so RC are usually very stable.

Thank you Mark and Andy. I'm excited about the release. When will Easysocial 2.0 be released for live sites?

Hello Bombshell,

Recently most of the issues posted on our issue tracker are almost 99% related to "teething design issues" or some usability issues. We have not had any report of fatal errors which is a good sign of a stable release

We'll monitor the issue tracker for a week or two before deciding the final dates!

Cheers buddy!

Hey there,

are there any news related to the mobile app? I understand the massive amount of work behind the things but being hyped makes patience soo hard.

Hey Sabih,

Yes, our developers already developed a mobile app in Easysocial 2.0 but this mobile app is not standalone mobile app, you can discover this app from backend > Easysocial 2.0 > application .

Regarding this build-in mobile app have it own top bar and footer bar without template design.

Even disable this mobile app from the application page, it will still show responsive but it will included your current template design, you can refer on my attached screenshot below or you can test it from our demo site here.

Hi Arlex,

thank you for your reply. I could see it on your demo site but when I install ES 2.0 RC1 there is no mobile app. If I go to "discover" nothing is found.

You're welcome Sabih, I already consult with our developer regarding this, the mobile layout already implemented in RC1 but the Easysocial mobile build-in app will be implemented in RC2 and we will release RC2 very soon.

Posted by mistake - ignore me!

Hi guys

I've installed all the latest versions of blog, discuss and social on a staging site, and the (paid) discuss for groups integration app. http://ezb3ta.cloudaccess.host/index.php/community/

Topics posted in groups as discussions look absolutely horrible in the feed, and doesn't seem to play nice with the new group layout either. It's not a question really - I just assume an update will follow to this app soon?

Hey Steve,

I am really sorry for the delay of this reply as it is a weekend for us here.

Regarding the Discuss group app, it will not come with the latest Easydiscuss/Easysocial RC2 installer, have to manually download latest app from the app store.

But the current Discuss group app installer only compatible with Easysocial 1.4. I will report this to our developer regarding this on week start and we will update this app when we release Easysocial stable version.

When testing the new EasySocial 2.0 RC1, the Community Polls app for easySocial causes the stream page to fail with following error:

Call to a member function addDescription() on NULL

Switching off the app stops the error but then the Community Polls don't show correctly in the Easysocial stream.

I asked Corejoomla about this issue and they replied as follows:

I can't verify any such backward compatibility issues as their documentation is available only to the subscribers. Could you please ask this question to EasySocial team and as they can tell better what to do to fix such integration issue?

How do we resolve this problem?
Im sure that you are going to get a lot of support queries of this nature when EasySocial 2.0 is released to the public


We are using Joomla 3.6.4 with PHP 7

What is the exact error that you are getting on the stream? Is it possible for you to enclose the entire error message here?

The screenshot is attached.

From what I can tell, its coming from this line in the Corejoomla app Poll file:

$item->opengraph->addDescription( $item->content )

The Corejoomla app works fine with Easysocial 1.4.12 but breaks with Easysocial 2.0 RC1

Hello Marc,

When we normally develop 3rd party apps, we have almost no access to the extension's documentation or either access to these extensions. We have to makeshift with what we already have and try to figure this out ourselves.

This is why we are developers and not web masters / system integrators. The developer of the app should be responsible if their app fails and all they need to do is to refer to one of the app that already exists and refer to the codes.

The correct syntax should really just be,

$item->addOgDescription($item->content);

Hi

do you know when we will have EasySocial 2.0 stable release?

It will be out pretty soon

When we normally develop 3rd party apps, we have almost no access to the extension's documentation or either access to these extensions. We have to makeshift with what we already have and try to figure this out ourselves.

This is why we are developers and not web masters / system integrators. The developer of the app should be responsible if their app fails and all they need to do is to refer to one of the app that already exists and refer to the codes.

The correct syntax should really just be,

$item->addOgDescription($item->content);

The above change did indeed fix the problem.

I think we all agree that these sorts of problems should be handled by the app developer, instead of being fobbed off as a "Stackideas" problem.

However, when an product upgrade is done and fails, Stackideas immediately gets the blame and the first support call.
Stackideas then has to do all the troubleshooting to identify the cause. It doesn't really matter that it was the 3rd party app developer who messed it up by not using proper code or following the standards.
What makes it even more frustrating is that some of the app developers I contacted didn't even know about Easysocial 2.0
They developed an Easysocial app/integration and once they got something working, that's the last time they looked at it.

On the plus side, the quality of the Stackideas support is why I have stuck with (and still paid for) all of your products, even when shiny new challengers appear on the block.


Viva Stackideas, Viva!

Hello Marc,

Thanks for your input on this and I appreciate this very much! We have actually sent to over 100 different e-mails which we collected as developers that developed apps on the app store and guess what, only 30% of them opened the e-mail.

We are still finding ways to get in touch with app developers as contacting all of them via Skype is no longer viable