By Sean Carney on Wednesday, 02 November 2016
Posted in General
Likes 0
Views 196
Votes 0
My EasySocial is located at this URL (https://www.drcarney.com/clan) and I just discovered that it is not working. This is a site I am just installing EasySocial on but it was working before.

I totally want to upgrade to EasySocial 2 and am hoping you might be able to look at my site, figure out why there is a JSON error and then upgrade my site to a working version of EasySocial 2 with all the modules installed.

My site details are in my Site Detail link.
I have backed up this site after upgrading EasyBlog and EasyDiscuss to the latest versions. In case you have any problems with the EasySocial installation I will have a good backup that I can recover to.
·
Wednesday, 02 November 2016 10:50
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Sean,

I have fixed the issue and updated your site to Easysocial 2.0. Please give it a try. By the way, the Json issue is actually because of one of your users has invalid json data in his params column.
·
Wednesday, 02 November 2016 13:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you so much Nik,

I am grateful. I do have another question which is whether or not you can help me to know which user has invalid JSON data. I am really not sure what this means but I wonder if I can pinpoint this user and determine if the user is real or an account made by a spammer before I installed EasySocial?

Either way I would love to know what the wrong data is and how I might be able to get rid of it. Also, I wonder if there might be a way to prevent users from putting JSON into their profiles? It is scary to think that a user can put something in their profile which can completely take down the EasySocial pages.

I am very grateful. Now I have to figure out how to nicely style the page at drcarney.com/clan :-)

Do you have an idea why my page at https://www.drcarney.com/clan does not look nice? The page with EasySocial 1 was nice looking and all the pictures in your EasySocial 2 documentation look nice. But, mine looks dreadful. :-)

I figured you might be able to point me in the right direction.

Sean
·
Wednesday, 02 November 2016 21:15
·
0 Likes
·
0 Votes
·
0 Comments
·
I do have another question which is whether or not you can help me to know which user has invalid JSON data.

The user that was having an invalid data is user with ID 899.

Do you have an idea why my page at https://www.drcarney.com/clan does not look nice?

Hm, it looks normal to me. Which part do feel is not right? Maybe we can start from there.
·
Thursday, 03 November 2016 10:33
·
0 Likes
·
0 Votes
·
0 Comments
·

The user that was having an invalid data is user with ID 899.


That is VERY interesting. That is a user that is automatically created by my host CloudAccess.net through their control panel which they can use to provide us support and we can use to automatically login from their control panel

Can you please help me to be able to share with them why they broke EasySocial? I know that they are a great company and believe that they will try to resolve the issue quickly.

Do you have an idea why my page at https://www.drcarney.com/clan does not look nice?

Hm, it looks normal to me. Which part do feel is not right? Maybe we can start from there.
The page now looks like it was never formatted to be looked at with a nice design. Previously, before the upgrade, there was a control bar across the top and the page was not a bunch of items aligned to the left of the page and sitting on top of each other and having some overlapping.
I am hoping to be able to get this page to look nice like at my page at https://www.starch-smart.com/social which is the site I am trying to move to this new installation at https://www.drcarney.com/clan
·
Thursday, 03 November 2016 13:30
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

Can you please help me to be able to share with them why they broke EasySocial? I know that they are a great company and believe that they will try to resolve the issue quickly.


There is a JSON issue with the params column in #__users table for this user. I can't remember the JSON content but it is not a valid JSON format since there is some extra 'i' (if I'm not mistaken) that breaks the JSON format.

http://take.ms/liZhd This screenshot I took to compare both sites' Easysocials and the obvious different I can see is the toolbar. Is this what you mean? If so, you might want to change your Easysocial theme to Frosty
·
Thursday, 03 November 2016 13:45
·
0 Likes
·
0 Votes
·
0 Comments
·
Ah. interesting. The url I showed you is different from the url you showed me. I suspect the url you are showing me is only available after logging in? It does look nicely formatted and so I like it. The url I am showing you is https://www.drcarney.com/blog and I believe the url you are showing me is https://www.drcarney.com/blog/dashboard (only after logging in?)

However, I am showing you the url https://www.drcarney.com/clan which is how it appears before logging in.

My pages for EasyBlog and EasyDiscuss both look nice BEFORE logging in. You can see them at https://www.drcarney.com/blog and at https://www.drcarney.com/talk

BTW, I am also using wireframe for my site at https://www.starch-smart.com/social
·
Thursday, 03 November 2016 14:08
·
0 Likes
·
0 Votes
·
0 Comments
·
BTW, I tried Frosty as you suggested and it looks nice although it is very different from the EasyBlog and EasyDiscuss pages!
·
Thursday, 03 November 2016 14:20
·
0 Likes
·
0 Votes
·
0 Comments
·
Ah. interesting. The url I showed you is different from the url you showed me. I suspect the url you are showing me is only available after logging in? It does look nicely formatted and so I like it. The url I am showing you is https://www.drcarney.com/clan and I believe the url you are showing me is https://www.drcarney.com/clan/dashboard (only after logging in?)

However, I am showing you the url https://www.drcarney.com/clan which is how it appears before logging in.

My pages for EasyBlog and EasyDiscuss both look nice BEFORE logging in. You can see them at https://www.drcarney.com/blog and at https://www.drcarney.com/talk

BTW, I am also using wireframe for my site at https://www.starch-smart.com/social
·
Thursday, 03 November 2016 21:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Sorry but I am a little confused here. Is the issue resolved for you now Sean?
·
Thursday, 03 November 2016 23:31
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Mark,

I can live with it the way it is (using Frosty as the theme). Although I do think it very odd that the wireframe theme looked so terrible in my EasySocial installation (V2) here at https://www.drcarney.com/club (I just changed the url) while it looks really great at http://www.starch-smart.com/social (V1.4)

What I am looking forward to eventually is the time when I can have the pages at EasySocial, EasyDiscuss and EasyBlog all look pretty much the same at the top. I kinow you are heading in that direction.

On another note: For my DrCarney.com site I am hoping to get rid of K2 to only use StackIdeas software and use your Migrator tool, so I added a suggestion in voices. I was hoping you might look at it for me to see if it is something you would consider doing. Also, It is something that I might again be willing to contribute to because the idea will be a win for you and for me. :-) I opened a ticket but it was closed already and I am not sure you saw it. :-)
·
Friday, 04 November 2016 00:32
·
0 Likes
·
0 Votes
·
0 Comments
·
The page at https://www.drcarney.com/club is on frosty theme and not wireframe.
·
Friday, 04 November 2016 00:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes Mark, That is correct. I had changed to Frosty because the Wireframe looked terrible. But, I believe as you pointed out to me in a couple other tickets, that the problem was caused by my cache. I cleared the browser cache and Wireframe looks good.

Sean
·
Friday, 04 November 2016 02:59
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Sean,

Can I assume your issue has resolved?
·
Friday, 04 November 2016 15:22
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes, the issue that was the reason for this ticket is resolved. It was really just that I did not realize I needed to clear my browser cache.
·
Friday, 04 November 2016 19:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating Sean, glad that your issues are resolved now
·
Friday, 04 November 2016 22:49
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post