Autoposting 0 - Error: 0 on New Blog Post or Save
By Stu on Thursday, 06 February 2014
Posted in Technical Issues
Replies 5
Likes 0
Views 626
Votes 0
Hello

Since upgrading to 3.9.15218 I get an Error: 0 when I try to save either a new or edited blog post and have autoposting/share options selected. This happens in both the front and back end.

New articles are still saved and live in the blog but no social sharing is happening.

If I deselect the autoposting options the articles are saved correctly.

Can you please advise as to how I can investigate this error? What information do you need?

Thanks in advance.
Hello Stu,

That's strange, is it possible provide us with the following information:
1) Joomla backend access
2) FTP access
3) Facebook access/ twitter access/ Linkedin access
Arlex Wong
·
Thursday, 06 February 2014 22:46
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks Alex, the business owner is not keen for me to allow access so I will have to exhaust other avenues first.

I switched error reporting on and got the following messages:


Notice: Array to string conversion in /home/account/public_html/components/com_sh404sef/shSec.php on line 108

Notice: Array to string conversion in /home/account/public_html/components/com_sh404sef/shSec.php on line 111

Notice: Array to string conversion in /home/account/public_html/components/com_sh404sef/shSec.php on line 114

Notice: Array to string conversion in /home/account/public_html/components/com_sh404sef/shSec.php on line 117

Looks like it is to do with the SEF URL, any thoughts?
Stu
·
Thursday, 06 February 2014 23:43
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Stu,

Hmm, we hard to tell you what is that exactly error coming from if we didn't have the access, hope you understand.
As for confidentiality, the username and password you've provide to us will not be reveals to anyone else other than the support team of Stackideas:)
You can put the information in the optional information field below. Don't worry about privacy. Only Support team can view the information.
Arlex Wong
·
Friday, 07 February 2014 00:29
·
0 Likes
·
0 Votes
·
0 Comments
·
Just to update this, I narrowed it down to a FaceBook error and it was to do with the token having expired.

I renewed the token and it started working again.

Perhaps you should consider having an alert built in to notify people when the token is due to expire.

Thanks for your help.
Stu
·
Monday, 10 February 2014 21:36
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Stu,

Sorry for late reply to this,
You're welcome, glad to heard your issues resolved.
Yes, thanks for suggestion, I will sent this suggestion in the EasyBlog request feature list and see how it goes
Arlex Wong
·
Monday, 10 February 2014 22:29
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post