Support Forum
Support Forum
Offline
This time - I hope 😉 - just a small problem with an easy answer.
I freshly installed the plugin "Blog Post Linking".
Whenever I try to save a Blog Post with the Option set to create a forum link, I receive the following error:
Any idea that points me in the direction of the cause?
Obviously it is some conflict on the post header, but why? BTW the plugin wpSEO ist offline now and no other SEO plugin active.
Thanks Michael
------
Warning: Invalid error type specified in /...../wordpress/wp-content/sp-resources/forum-plugins/blog-linking/library/sp-linking-blog.php on line 153
Warning: Cannot modify header information - headers already sent by (output started at /...../wordpress/wp-content/sp-resources/forum-plugins/blog-linking/library/sp-linking-blog.php:153) in /...../wordpress/wp-admin/post.php on line 242
Warning: Cannot modify header information - headers already sent by (output started at /...../wordpress/wp-content/sp-resources/forum-plugins/blog-linking/library/sp-linking-blog.php:153) in /...../wordpress/wp-includes/pluggable.php on line 1207
Offline
It's a curious one. Seems there is some confusion out there in the past over this and in this case it appears to come down to the fact that my own, personal, php documentation is incorrect. Perhaps that has been the reason for other chatter I see on the internet on the subject.
At the location specified by the error there are three calls to the php trigger_error() function which pass an incorrect constant value. The even more curious thing is that up to date documentation suggests it should just return a false whereas in your case it has echoed out the message which has then caused the http headers error condition.
So the first task is to correct the constant used. It would most useful if you could make the small edit so you can then use the plugin to find out what triggered your error in the first place. More on that below. First, if you are willing to make the change the file is in the forum plugins folder:
/blog-linking/library/sp-linking-blog.php
There are 3 calls to the function trigger_error() at lines 150, 153 and 156. In all cases they pass - as the second argument - the constant E_WARNING.
This constant should be - E_USER_WARNING
This will, of course, be corrected immediately for the next update due - if all goes to plan - some time next week. The extra problem this correction is giving me is that the errors triggered do not appear to be showing up in the log as they used to. That, I am afraid, is going to be a little longer and harder to diagnose.
Perhaps a more interesting question is why this error condition was thrown. In your case is appears to have been triggered during the data validation tests. The main (but not all) reasons for this are:
No topic name has been entered and post cannot be saved (that would be the blog title)
No topic post has been entered and post cannot be saved (that would be the blog post content)
Maximum number of allowed links exceeded
You are not allowed to put links in post content
Maximum number of allowed smileys exceeded
Duplicate post refused
So could any of these reasons be the trigger?
 |
YELLOW
SWORDFISH
|
Offline
Actually- the errors being triggered do appear to get sent to the error log. The error I tried to replicate was bogus but I have since retested.
|
YELLOW
SWORDFISH
|
Offline
Yellow Swordfish,
I identified the file, found the three lines and changed as you described.
Then I confirmed, that the changes are truely on the server. They are.
I tried again by saving a blog post with linking. This is the (new) result:
Warning: Linking - Validation: No topic post has been entered and post cannot be saved in /...../wordpress/wp-content/sp-resources/forum-plugins/blog-linking/library/sp-linking-blog.php on line 153
Warning: Cannot modify header information - headers already sent by (output started at /...../wordpress/wp-content/sp-resources/forum-plugins/blog-linking/library/sp-linking-blog.php:153) in /...../wordpress/wp-admin/post.php on line 242
Warning: Cannot modify header information - headers already sent by (output started at /homepages/8/d491105546/htdocs/wordpress/wp-content/sp-resources/forum-plugins/blog-linking/library/sp-linking-blog.php:153) in /...../wordpress/wp-includes/pluggable.php on line 1207
As per your question, this raises another problem I was not aware of.
Yes, it might be possible, that a blog post has far more smileys or links than are allowed for a forum post.
The reason is simple, blog posts are much longer and I write them, where a forum post anyone can write.
So the "Blog Post Linking" Plugin is only of use to me, if I can stay with strict restrictions in the forum but still go beyond that in a blog post.
I understand, that this would be impossible and a logical catch22, if the content is copied to the forum thread in full. Because this *is* a forum post then.
But this is not what I am looking for. I am looking for a simple link - without copying content - between the blog post and a forum thread.
Reason is, that I want the associated forum thread to be the "comment section" for any blog post, the comment function of wordpress itself, is disabled.
So what I am looking for, is to generate a two way link between blog post and forum.
In the blog post a line that more or less says "Discuss this article here in the forum" with link to the topic. And in the forum a new topic consisting just of the link to the blog article plus the headline.
This "should" be able to do, without violating any strict smiley or link restriction in the forum, as only one link (to the blog post) is part of the new topic.
But does it really work this way? I am a bit confused now.
Offline
Does Blog Linking work that way?
Yes - that is exactly how it works. Check our 'Latest News and Developments' forum to see examples.
Maximum Links and Smileys
If the author is also a Simple:Press Admin user then these limits are not applied
Cannot modify header information – headers already sent
This suggests you are seeing these notices, warnings and errors on the screen? Is this the case? If so this is a most unwise course and is seriously not recommended on any live production system. This should be turned off.
No topic post has been entered and post cannot be saved
So the a actual cause of the validation error was this as you no doubt saw. Was this the case? and if not - is there something unusual or non-standard about your blog post editing?
|
YELLOW
SWORDFISH
|
Offline
If the author is also a Simple:Press Admin user then these limits are not applied
I am the autor and I am Admin everywhere, so these limits should not apply.
This suggests you are seeing these notices, warnings and errors on the screen? Is this the case? If so this is a most unwise course and is seriously not recommended on any live production system. This should be turned off.
I see these errors on a white screen after trying to save the post. This white sceen has no reference to the blog. Just white and URL is: http://www.xxx.de/wp-admin/post.php
This is the first time I see something like this. I am not in Debug Mode so I have no idea what you are trying to say
So the a actual cause of the validation error was this as you no doubt saw. Was this the case? and if not – is there something unusual or non-standard about your blog post editing?
No it isnt. The post surely has a title (topic).
Is there something "unsual"? Depends on what "unsual" is. I would say No.
I use the standard Wordpress Editor in Text Mode (not wysiwyg) and the plugins I use you know from the other problem thread.
I never ever had such a "White Sceen" Error Message after saving a Post yet in 4 years.
The only thing worth mentioning is, that this article is protected via S2 Members as most of my articles. I cant see anything "unsual" beside that.
Offline
I see these errors on a white screen after trying to save the post
As I said - you are allowing message to be sent to the screen. This is bad practice and not recommended by anyone except for, perhaps, debugging when building a site. If you are using no overrides then this is a setting in the servers php.ini file and I would recommend you ask your host to correct the error reporting settings.
I never ever had such a “White Sceen” Error Message after saving a Post yet in 4 years.
This is because of the above. And it will only happen when an error occurs before the page has started to be assembled by php on the server. hence the message that the headers have already been sent and can not be sent again. Errors that occur after the headers have been sent will not trigger this and, depending on where they happen, may even be in the html source sent to the browser without being displayed.
No it isn't. The post surely has a title (topic).
The error message stated there was no post - nothing to do with the title. So - was there post content?
Is there something “unsual”? Depends on what “unsual” is. I would say No.
Assuming there was content then there would have to be something unusual for it not to be sent to the forum. The Blog Linking plugin uses the standard WordPress API Action hooks to process the data. So if there was content then something is not allowing the action hooks to function correctly. And no - i have no idea what that might be but some plugins do do some odd things.
I use the standard Wordpress Editor in Text Mode (not wysiwyg) and the plugins I use you know from the other problem thread.
Well - there are thousands and thousands of plugins for WP and most of those on your list were completely unknown to me I am afraid.
The only thing worth mentioning is, that this article is protected via S2 Members as most of my articles
Would S2 Member stop the code from being able to read the blog post data from the database? Might that be possible?
|
YELLOW
SWORDFISH
|
Offline
I see. Another "not simple" problem with possible plugin incompatibilty. lol 😉
Btw yes, this was a long and full blog post with almost anything in. Definitly nothing was missing.
Does S2 Members stop the code? I dont have more of an idea as you - I guess less. 😉
So basically this means, I will stay away from this plugin, until I have more time to investigate. I dont have the time at the moment for another 2 days of incompatibility search and this is not a showstopper type problem like the performance issue, but just a small fraction of functionality I cant use. I can live without for some time.
So I might come back to you during the coming weeks, after I found some time for further investigation.
Thanks.
Offline
okay, happy to dig in further if needed...
Visit Cruise Talk Central and Mr Papa's World
All RSS1 Guest(s)