stitchkingdom

it probably will. any plug-in that automatically adds things to the body of the post (even before or after the actual content) will be affected by it.

glad to hear it. hopefully the fact that at least 2 of us would at least like the option to avoid putting the messages through the filters will be reflected in a future update.

I’m not sure why, but after I added the line of code, I got a weird error when attempting to post (refresh made the post go through), so do try it, but be prepared to remove it if the error pops up. It’s such a simple line, not sure why it causes problems, but when I took a brief look at it, the resulting error was just complicated.

for the record, this is the exact change I made, replacing the FULLTEXT line itself:

if (preg_match('%FULLTEXT%', $msg)) { $postContent = $post->post_content; $msg = str_ireplace("%FULLTEXT%", $postContent, $msg);}

this works without error and avoids putting the post through the_content to allow other plugins to affect it.

I haven’t tried this out to be honest, but it should work. If you look around line 431 in NextScripts_SNAP.php and look for the line that begins:

if (preg_match('%SITENAME%', $msg))

and add the following above it:
if (preg_match('%RAWTEXT%', $msg)) { $postContent = $post->post_content; $msg = str_ireplace("%RAWTEXT%", $postContent, $msg);}

and save it, then go into your preferences for SNAP and change references from %FULLTEXT% to %RAWTEXT%, it should go ahead and post messages without processing them, so you can see the difference.

Of course this will break if you later update the plug-in, so you’d have to re-edit with the new changes or hopefully they’ve added it in by then.

The problem with Tumblrize of course is that it no longer works. And IMHO, SNAP is better with Tumblr except for no option for default tags (which I resolve by manual code edit) and the edit aspect, which isn’t that important to me frankly, but isn’t unreasonable.

But just wanted to point out that he already explained why %FULLTEXT% is doing what it is, which Tumblrize didn’t do because it didn’t do it. It’s because before posting, SNAP runs the post through the_content filter, so plug-ins that automatically add/change stuff before posting can manipulate the post. I have this issue myself with an auto-more plug-in, so I again have to edit the SNAP code to not call the_content.

What would be a good compromise is if SNAP introduced something like %RAWTEXT% which would show the fulltext without running it through the_content filter. Should be very easy for them to do.

Thank you for the NextScripts SNAP suggestion. I did find a bug in it but once I squished it, it’s been amazing. I even paid for for the additional functionality for G+ and Pinterest which I also appreciate because it looks like they let you tap into their code outside of WP as well.

Only other issue I had was that I had another plug-in that was hooking in to the the_content filter and was modifying the result to something different than I expected, but I kludged it and all is well again.

fixing the code above did the trick, so I’m going to mark this as resolved myself, but please make a note it is a legitimate bug in the existing code.

As for #3, I found the problem to be that you are using the_content filter which is fine, but I have a plug-in called Post Teaser so I don’t have to manually deal with more tags and it hooks into the filter, so it was basically truncating the text. I’m experimenting by adding a global boolean variable that I turn on when your posting function begins and turns it off when it ends.

there must be a simpler, easier way, but I’m just tweaking at the moment.

I also hardcoded tags I want added to every entry like I was able to specify with tumblrize. Would be nice if that were part of the config, but not worth it for me to do for just myself.

Quick followup. I looked at some of the code and I feel weird that I’m the only one seemingly having this issue (maybe because I’m not doing cron), but I believe the code in line 312 of the main script is in error. where it says:

} else { $fname = 'ns_doPublishTo'.$avNt['code']; $fname($postID, $optMt); }

it should say

} else { $fname = 'nxs_doPublishTo'.$avNt['code']; $fname($postID, $optMt); }

as I checked the TR as well as some of the other scripts and there are no functions beginning with ns, they’re all nsx. So we’ll see how that works out when I post again.

well, for what it’s worth, I found out that paginating the post works.

gizmomol’s solution works. note the /* */ around the function in the code above.

okay, my bad. I was getting that error because notepad kept adding those extra characters at the beginning that I couldn’t detect. had to ssh into server and VI the php to remove them. functionality is restored. about to test a postie now.

just tested and appears to work great. thanks for the suggestion of commenting out that function.

this appeared to have worked. until the preview button stopped working for me when composing a new post. saving a draft also results in the error:

Warning: Cannot modify header information – headers already sent by (output started at …/wp-content/plugins/postie/postie-functions.php:1) in …/wp-includes/pluggable.php on line 866

this is unfortunate. I rely on postie.

And I don’t mean to bump this, but I don’t see an edit and I realized there was one fundamental thing I didn’t try either, which is changing themes.

So what I did was take the domain which does work and give it the theme of the domain that’s not working and its feed still works.

UPDATE: Solved it. I had Advanced Permalinks plugin active since I had changed my permalink structure recently and it’s been a trusty way to handle it, but I decided I no longer wanted it so I went to deactivate it and couldn’t find it in my plugins list, so I deleted the folder and that seemed to do the trick.

cancel that, sorry, not sure how I missed it, but I just realized that you can re-import an existing gallery and it will pick up only the additional images.