By Phivos on Monday, 26 December 2016
Replies 27
Likes 0
Views 800
Votes 0
Dear support,

We tried to update EasySocial to the version 2.0.7 as we had a pre 2.x.x version, but we faced errors as you can see in the photos below.

Now we restored the site to the state it was just before the installation as we took a backup for that purpose.

Any ideas what might went wrong?

If you want to test something we include the details of our developing site as well.

Regards,
Hi Phivos, sorry for hijacking your post but...

Seams to be browser cache related, did you try deleting your browser cache?

Also had this once and after deleting my browser cache everything worked fine.

Other forum post with similar issue
·
Monday, 26 December 2016 08:17
·
0 Likes
·
0 Votes
·
0 Comments
·
Dear Jean-Marc,

We are going to give it a try but if this is a browser cache related issue, what happens with the browser cache of our users?

Regards,
·
Monday, 26 December 2016 14:54
·
0 Likes
·
0 Votes
·
0 Comments
·
On the back end, it is definitely caused by your browser cache. Clearing your browser's cache should address this. Since your users never login to the back end, I think this wouldn't be an issue at all.

As for the front end, do you have any customizations made on the site or template overrides?
·
Monday, 26 December 2016 15:33
·
0 Likes
·
0 Votes
·
0 Comments
·
Dear Mark,

It was a browser cache issue but in this case, what happens with the browser cache of our users with regards to the front end conflicts?

In addition, we had to restore the site once again from the backup because this time the links to the profile pages of the users have changed and so the users would not be able to access any profile page. We noticed that the link to a profile page under version 2 is like this format:
/community/471-andreas

but before it was like that:
/community/Προφίλ/471-andreas

Even if we type the URL (/community/Προφίλ/471-andreas) on the browser, that link does not exist. This will create more conflicts as we have a lot of extensions that navigate the user to the EasySocial profile page of each user. Therefore, we need to have the same URL path to the profile page as before.

As we restored the site to the state before the update and in order to avoid the hussle, we replicated the problematic site with EasySocial version 2 to our developing site. So please check our developing site to check the issues. We include the credentials in our first post above.

With regards to your last question, yes we have many customizations and template overrides.

Regards,
·
Monday, 26 December 2016 15:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Phivos,

I've checked in your development site, it seems like it always load the script file from your live site even i load your development page, you can check my attached screenshot below. Can you consult with your webhosting provider and see is it not configure correctly from your development server?

Regarding with your main issue, we already removed that 'profile' alias in Easysocial 2, so the user link will be /community/userAlias .

And i also believe other extension user permalink will intelligent enough to load the same link with Easysocial user profile link because it will load our Easysocial user library as well.

And I did noticed from your live site actually have 2 different user permalink :
For example :
https://yourLivedomain.com/vironakos
https://yourLivedomain.com/community/Προφίλ/730-vironakos

Once your hosting fix the first issue I described, I will continuous check your user permalink issue.
·
Tuesday, 27 December 2016 11:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Dear Arlex,

Ok we will contact cloudaccess.net support and come back to you.

Regards,
·
Tuesday, 27 December 2016 14:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Alright, keep us update then.
·
Tuesday, 27 December 2016 16:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Dear Arlex,

This is their reply:

"I checked and I cannot find any setting in the EasySocial extension that would cause it to call to the live site. As for the sites themselves, they are totally independent of each other, so far that they even reside on separate servers. Perhaps the extension itself is storing domain name information somewhere - if so, they might have not become overwritten during the replication process and need to be rewritten manually."

Regards,
·
Tuesday, 27 December 2016 19:11
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Phivos,

I've re-checked again, I noticed this following script URL which pointing to another domain, do you familiar with this?


<script src="https://penaltara1-penaltara.netdna-ssl.com/media/com_easysocial/scripts/admin-2.0.7.min.js"></script>


If I manually access this domain on browser, it will redirect to your live site.

Because of these all the Easysocial script is not load so everything can't function now.

Keep us update if you know something about this.
·
Tuesday, 27 December 2016 19:58
·
0 Likes
·
0 Votes
·
0 Comments
·
Dear Arlex,

The URL that you showed is the CDN URL. Because we have set a CDN (using maxcdn.com) for the live set. For the developing site we have disabled the CDN plugin form the backend since the beginning. We do not understand how this kicks in right now. Any ideas?

Regards,
·
Tuesday, 27 December 2016 20:13
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for pointed to the correct at the first place, I already removed your CDN URL which configured into your development site, you can check my attached screenshot below.

I will continuous check your main issue tonight.
·
Tuesday, 27 December 2016 20:28
·
0 Likes
·
0 Votes
·
0 Comments
·
Dear Arlex,

Ok thanks for the update. Please note that we cannot restore the developing site to the live site, therefore, you have to transfer ONLY your changes once done. Please let us know before you do this.

Regards,
·
Tuesday, 27 December 2016 21:40
·
0 Likes
·
0 Votes
·
0 Comments
·
It seems like this 3rd party poll app is not compatible with Easysocial 2.x , I already applied some fix in this file -> /httpdocs/media/com_easysocial/apps/user/poll/poll.php , it should work fine now, can you give it a check again?
·
Tuesday, 27 December 2016 23:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Dear Arlex,

Thanks for the valuable input. We have run some tests and these are issues faced right now.

1. There is some confilct with EasyBlog. Does this has something to do with the EasySocial update? Please check the below links:
a) Please click on any article in the below link. The article page does not function
http://dev.penaltara.com/blog

b) Please go to search for bloggers. The link does not function
http://dev.penaltara.com/blog/blogger


2. If you search for a user in the Community there is no result. Please login with a user and perform a search
http://dev.penaltara.com/community


3. There are a lot of new language strings. Before a year that we translated EasySocial we faced problems because the FRONT END language strings were included in three files located in:
httpdocs/language/el-GR,
httpdocs/language/en-GR and
httpdocs/administrator/language/en-GB
Now that we have to do it almost from the beginning we are going to set the new language strings in override files like below, is that correct?
templates/your_template/language/el-GR/el-GR.com_yourcomponent.ini
templates/your_template/language/en-GB/en-GB.com_yourcomponent.ini

But what happens with the FRONT END language strings located in the administrator path "httpdocs/administrator/language/en-GB"? Shall we create an override like that?
templates/your_template/administrator/language/el-GR/el-GR.com_yourcomponent.ini



Please note that any corrections that you will do with regards to point 1. and 2. above cannot be transferred to the live site, so please let us know which file is affected by the correction.

Regards,
·
Wednesday, 28 December 2016 21:45
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Phivos,

a) Please click on any article in the below link. The article page does not function
http://dev.penaltara.com/blog

b) Please go to search for bloggers. The link does not function
http://dev.penaltara.com/blog/blogger

It seems like you still using very older version of Easyblog which not compatible with Easysocial 2.x , I already help you update your Easyblog to latest version in your development site, it should work fine now.

2. If you search for a user in the Community there is no result. Please login with a user and perform a search
http://dev.penaltara.com/community

Regarding this, it seems like your development site that smart search data do not have existing any of your current user data, I already help you reindex again, it should work fine now.

Regarding this, It still indexing, you can refer on my screenshot here : http://take.ms/stgz6
Once it indexed finish, you can able to search the user data from your Easysocial.


3. There are a lot of new language strings. Before a year that we translated EasySocial we faced problems because the FRONT END language strings were included in three files located in:
httpdocs/language/el-GR,
httpdocs/language/en-GR and
httpdocs/administrator/language/en-GB
Now that we have to do it almost from the beginning we are going to set the new language strings in override files like below, is that correct?
templates/your_template/language/el-GR/el-GR.com_yourcomponent.ini
templates/your_template/language/en-GB/en-GB.com_yourcomponent.ini

But what happens with the FRONT END language strings located in the administrator path "httpdocs/administrator/language/en-GB"? Shall we create an override like that?
templates/your_template/administrator/language/el-GR/el-GR.com_yourcomponent.ini

Nope, if I recall correctly, you can't override these language ini file into your template.

You have to do it this way, copy all inside the language translation string move into following file location. (you have to manually create these Joomla language override file)

JoomlaFolder/language/overrides/el-GR.override.ini
JoomlaFolder/language/overrides/en-GB.override.ini
JoomlaFolder/administrator/language/overrides/el-GR.override.ini


Hope this will help.
·
Thursday, 29 December 2016 18:23
·
0 Likes
·
0 Votes
·
0 Comments
·
Dear Arlex,

We appreciate your effort to offer your valuable support to us.

With the update of EasyBlog we face one more issue unfortunately. The pop-up component to create a new blog is not loading. Please check, try to write a blog:
http://dev.penaltara.com/blog/dashboard/write

Regards,
·
Thursday, 29 December 2016 20:14
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Phivos,

The composer is actually loading up fine but jQuery Easy is causing a lot of delays when rendering the composer layout. I believe jQuery Easy is trying to compress the scripts and it is taking very long to do it.

You can try this by turning off jQuery Easy.
·
Friday, 30 December 2016 11:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Dear Mark,

Thank you for the valuable input. We understand that you are on holidays. We post the reply here for next week i.e. Tuesday onwards. Happy new year to the Stackideas team.

We performed the updates on the live site as well and the issues we face right now are:

1. With regards to the jquery we had it long time enabled on the site as it was needed for other extensions. This is the first update of EasyBlog that brings a conflict with it. Is there a way to disable jquery for the whole EasyBlog functionality? We managed to disable jquery for the specific URL.

2. Please have a look at the attached photos. In the development site the buttons are green but in the live site these do not exist at all.
https://penaltara.com/community/%CE%A0%CF%81%CE%BF%CF%86%CE%AF%CE%BB/%CE%B5%CF%80%CE%B5%CE%BE%CE%B5%CF%81%CE%B3%CE%B1%CF%83%CE%AF%CE%B1%20%CE%B5%CE%B9%CE%B4%CE%BF%CF%80%CE%BF%CE%B9%CE%AE%CF%83%CE%B5%CF%89%CE%BD

http://dev.penaltara.com/community/%CE%A0%CF%81%CE%BF%CF%86%CE%AF%CE%BB/%CE%B5%CF%80%CE%B5%CE%BE%CE%B5%CF%81%CE%B3%CE%B1%CF%83%CE%AF%CE%B1%20%CE%B5%CE%B9%CE%B4%CE%BF%CF%80%CE%BF%CE%B9%CE%AE%CF%83%CE%B5%CF%89%CE%BD

Regards,
·
Friday, 30 December 2016 23:41
·
0 Likes
·
0 Votes
·
0 Comments
·
Can you please create a separate ticket for your issue rather than bombarding them all under a single post here? It's really very difficult for us to go through your entire issues on a single thread.

As for the jQuery easy issue. I would suggest that you add an exclusion when the url contains tmpl=component . Since EasyBlog's composer renders tmpl=component
·
Saturday, 31 December 2016 01:20
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post