By Brent Critchfield on Friday, 26 August 2016
Posted in Technical Issues
Replies 13
Likes 0
Views 396
Votes 0
We installed EasyBlog on a development site for a domain that we were upgrading from J 2.5 to 3.x. No problems - it worked perfectly and we were able to create/edit posts. However after changing the URL from our development domain to the live domain, we can no longer save posts in the composer. The popup appears and says "Saving your post, please wait." The progress bar moves about 70% across, then stops.

I've tried changing editors, browsers, uninstalled/reinstalled EasyBlog - no change. None of the files or permissions have moved between the development site and live version, all we did was update the domain name in cPanel.

Any ideas?
Hi Brent Critchfield,

It seems like you are requesting support for http://allabouxxxxx.com but your licensed domain is http://brentwxxxxxx.com . Please understand that Pro versions only entitles you to support for 1 domain only. You can request us for changing the support domain as you did not make any ticket support for the registered domain yet.

If you require support for additional domains, please consider purchase an additional subscription for this site.

Thanks for understanding
·
Friday, 26 August 2016 12:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes, please change the support domain as noted above.
·
Tuesday, 30 August 2016 01:34
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Brent Critchfield,

My colleague has changed the domain as you prefer. I'll checking this issue now.

Thanks for understanding.
·
Tuesday, 30 August 2016 11:53
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,

Seems like you're using Rokbox, can you apply this fix according to our documentation here:
Conflicts With Rokbox
and see how it goes?
If this issue still persist, can you provide us with your FTP login credential so we can troubleshoot further on this? You can simply add the information needed by edit your first post in the site details or you can just include your site's access once at http://stackideas.com/dashboard/site rather than needing to keep adding them in your replies
·
Tuesday, 30 August 2016 12:15
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks Muhammad,
I tried the RokBox fix which didn't help, and just to be sure I've uninstalled RokBox completely. You'll notice various odd behaviors with the composer: you can't change a post's author, the Fields, SEO and History tabs are missing from the sidebar, etc.

I updated the original post with FTP credentials for you. Thanks for your help.
·
Wednesday, 31 August 2016 07:12
·
0 Likes
·
0 Votes
·
0 Comments
·
hey Brent,

Currently we still investigate on this issue.

May i know the existing post is it created from 3.9version?

Can you provide us with your PHPMYADMIN access as well? because I would like to check the post data from database.

You can update on this page http://stackideas.com/dashboard/site
·
Wednesday, 31 August 2016 11:56
·
0 Likes
·
0 Votes
·
0 Comments
·
I've updated the account with login details as requested.

This was a J2.5 site running an older version of EasyBlog. We copied the site to a temporary domain, migrated to 3.x and updated EasyBlog. During this time we also added several new blog posts and did other work with EasyBlog, and it worked fine. When it was time for launch we deleted the cPanel account for the old J2.5 site and updated the domain name to make our dev site live. No files were moved, no permissions changed, etc. When we made it live, we suddenly ended up with the behavior we've got now.
·
Thursday, 01 September 2016 02:41
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Brent,

I am sorry for the delay of this reply,

After troubleshoot long hour ago, but i still cannot figure out why the composer block JSON string will show "Unexpected token \ in JSON" error form the browser console then break the whole Javascript when load the composer on the site.

I suspect is your server added the extra double quote " or remove some of the string in JSON string when the value return back from your server.

I have do some testing from your site, when I try to echo the string which convert to json string, it will striped some of the text.

Added some of the php code in this following file.
JoomlaFolder/components/com_easyblog/easyblog.php
To see the result you can run this following URL on your site.
http://replace.your.domain.name/index.php?option=com_easyblog&clear=1


$jsontext = '{"data":"Jesper","block":"<div class="ebd-block-sort-handle"> testtest </div>"}';

echo json_encode($jsontext);exit;


Result from your site :
"{\"data\":\"Jesper\",\"block\":\"testtest <\ div="">\"}"


And this is my local result :
"{\"data\":\"Jesper\",\"block\":\"<div class=\"ebd-block-sort-handle\"> testtest <\/div>\"}"


Is it possible consult with your webhosting provider regarding this and see is it got encounter this issue before?

Also consult with your webhosting provider is it have enable this `magic_quotes_gpc` from your php server?

If yes, is it can temporary disable it? Make sure disable that php `magic_quotes_gpc` from the frontend and backend.

By the way, may i know your development domain site is it still can accessible now?

Keep us update once your webhosting provider response you.
·
Thursday, 01 September 2016 19:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for your work on this, Ariex. I can confirm that magic_quotes are off:
grep "magic_quotes_gpc" /usr/local/lib/php.ini
magic_quotes_gpc = Off


I've sent the info from your post above to my host and am waiting for their response. The dev site is no longer available as we simply changed the URL in WHM from dev.sitename.com to sitename.com. However I do have a few other sites on the server (using the same PHP config) which are working fine. I'll see if I can update the secure portion of the first post with a login for one of those sites which you can use.
·
Saturday, 03 September 2016 04:04
·
0 Likes
·
0 Votes
·
0 Comments
·
I asked my hosting company to look into this and sent them a copy of your post above. I also mentioned to them that the component is working properly on sierravetclinic.com. Here is their response:

I've been looking into the differences between the server settings on sierravetclinic.com and allaboutnumbers.com, and have not been able to find any. Your developer had requested that we disable magic_quotes_gpc, and it looks like it had already been disabled. I have not been able to find any local file on allaboutnumbers.com that would turn that setting on. Unfortunately, I'm not sure what is causing the issue with the code on one site and not the others, as the server settings are consistent amongst all of the domains.


Let me know what else I can do to help.
·
Saturday, 03 September 2016 11:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Brent,

Apologies for the delay as I had to spend the entire day trying to troubleshoot this and managed to find a solution for your site and it seems like the composer is behaving itself now.

Would you mind letting me know which PHP version do you have on your other site? The one that you are using is 5.5.38 and I am not too sure if there's some issues with the json parsers.

Anyhow, I have applied some temporary fixes for you on the site by replacing the block of codes below in the file /components/com_easyblog/themes/wireframe/composer/blocks/menu.php


<textarea data-eb-composer-block-meta data-type="<?php echo $block->type; ?>"><?php echo json_encode($block->meta()); ?></textarea>


With,


<textarea data-eb-composer-block-meta data-type="<?php echo $block->type; ?>"><?php echo json_encode($block->meta(), JSON_HEX_QUOT | JSON_HEX_TAG); ?></textarea>


And the file /administrator/components/com_easyblog/includes/blocks/blocks.php and replacing line 352,


$out = '<textarea data-block>' . json_encode($block->data) . '</textarea>';


With,


$out = '<textarea data-block>' . json_encode($block->data, JSON_HEX_QUOT | JSON_HEX_TAG) . '</textarea>';


This seems to do the trick but I am still very puzzled as to why this only happens on one site and only your site. Not sure if we should be including these into the core but please let me know about the PHP version on your other site before we can decide to include it into our core.
·
Saturday, 03 September 2016 14:21
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks guys for all of your work on this. It does seem like you've gotten it fixed.

The PHP version is 5.5.38 on both sites - in fact they're loading the same php.ini file. I included a login for the second site in the Additional Details section of the first post in this thread if you want to take a look.
·
Monday, 05 September 2016 12:58
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Brent Critchfield,

Thanks for the heads up, this fix has been applied in our repository and it will included in our next released

Have a nice day ahead
·
Monday, 05 September 2016 13:21
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post