Forum Replies Created

Viewing 15 replies - 196 through 210 (of 230 total)
  • P.S. Did not do the magpie rss upgrade feedwordpress requests, but does not require.

    Just did a clean WP install with feedwordpress. Worked fine.

    Added Twitter Tools. Would post to Twitter directly, but would not post to twitter when new posts were added. Same as above.

    Uninstalled Twitter Tools and tried (( WP Twitter ))

    Success! It works! 88 miles per hour!

    feedwordpress + (( WP Twitter )) = Easy autoblogging, rss aggregating, joy.

    Line 740 in twitter-tools.php says:

    738 function aktt_notify_twitter($post_id) {
    739 global $aktt;
    740 $aktt->do_blog_post_tweet($post_id);
    741 }
    742 add_action(‘publish_post’, ‘aktt_notify_twitter’, 99);

    When I try to (re-)activate feedwordpress with twitter tools activated, I get the following error:

    Fatal error: Call to a member function do_blog_post_tweet() on a non-object in […]/wp-content/plugins/twitter-tools.php on line 740

    Anyone have better experiences with another RSS feed + wordpress plugin?

    I tried feed.informer.com, which has handy filtering qualities (e.g., remove same titles/URL posts), but it displays via javascript so there’s no SEO impact. Which is a big reason for posting RSS feeds from other sites on your own site in the first place…

    Here’s what my homepage displays (twilightnewssite.com), occasionally, though on reload it displays the page fine(?!).

    Warning: Illegal offset type in
    […]/wp-includes/rss.php on line 1459

    Warning: Cannot modify header information – headers already sent by
    (output started at
    […]/wp-includes/rss.php:1459) in
    […]/wp-includes/pluggable.php on line
    865

    Note this is with Twitter Tools (and similar) plugins deactivated.

    Deactivating FeedWordpress now. Hope we get some feedback here on how this can be fixed.

    Thanks Alex. There does seem to be some sort of problem; either one works well alone on my sites, but both do not seem to work together. Here’s the latest error (top of homepage on a reload).

    Warning: Illegal offset type in […]/wp-includes/rss.php on line 1459

    Alex King, I am having Twitter Tools vs. FeedWordPress problems also.

    Is there any way to get them to play nice? Are they mutually exclusive?

    Error messages point to various parts of rss-related WordPress files: “Fatal error: Call to a member function do_blog_post_tweet() on a non-object in […]/wp-content/plugins/twitter-tools.php on line 740.”

    This is a shame because being able to aggregate content via FeedWordPress and in turn, send that out to Twitter (automagically) is a stellar concept.

    Note: some posts here attribute the problems to (FeedWordPress’ install of) MagpieRSS, however, even after replacing all WP RSS files with the originals, still no joy.

    Help us Alex-Wan Kenobi, you’re our only hope! 🙂

    Thread Starter websta

    (@websta)

    I humbly accept your chastisement.

    Removing the absolute breaks the site, but setting z-index to 0 sets things right.

    Thanks whooami, and I will try that approach in the future.

    Thread Starter websta

    (@websta)

    I know it doesn’t validate, but it doesn’t appear that any of the errors should impact whether the links work or not…

    Thread Starter websta

    (@websta)

    Thank you drmanry! It works! It works! 88 miles per hour!

    For afandi2, and anyone else who needs it, here is what I have to display a list of posts from another category, which varies according to what category the user is in (e.g., it changes the list of posts in the sidebar depending on what category the current post/page is in).

    This may be useful if, like me, you have child sub-categories but you need a list of posts from them to appear on posts/pages located in the parent directory. Paste the code below into a template page, just change the 14 and 22 below to your relevant categories:

    <?php
    if  (in_category(14)) {
            echo "<li id='recent'><ul class='recent'><li>";
            echo('<ul>');
            query_posts('cat=22');
            if (have_posts()) : while (have_posts()) : the_post();
            echo('<a href="');
            the_permalink();
            echo('">');
            the_title();
            echo('</a>');
            endwhile; endif;
            echo('</ul>');
            echo "</li></ul></li>";
    
    // start of a place that can be repeated for each category,
    // just replace 35 and 28 below
    // i.e., if we are in category id 35, then show
    // a linked list of posts from category 28
    
    } elseif (in_category(35)) {
            echo "<li id='recent'><ul class='recent'><li>";
            echo('<ul>');
            query_posts('cat=28');
            if (have_posts()) : while (have_posts()) : the_post();
            echo('<a href="');
            the_permalink();
            echo('">');
            the_title();
            echo('</a>');
            endwhile; endif;
            echo('</ul>');
            echo "</li></ul></li>";
    
    // end of the repeating part
    
    // below is the end - which is helpful to see if problems arise
    // you can change the text between quotation marks to anything
    // you want - including php or html
    // if you want to show nothing, you can change it to: echo "";
    // or delete the line entirely
    
    } else {
            // catch-all for everything else (searches, 404s, etc)
            echo "<p>Pedro offers you his protection.</p>";
    }
    ?>

    Head’s up: Neil, the “give this code a try” link returns an error:

    “Unknown post id, it may have expired or been deleted”

    Use your ftp software to upload the theme (in its own directory) to your server inside wp-content/themes/ . So your new theme will be in (root)wp-content/themes/(new-theme-here)/.

    Then, in your WP admin area, go to Presentation > Themes and select your new theme.

    (Gratitude to all who helped make installing new themes so incredibly straightforward. Thank you!)

    Wanted to add my $0.02 worth on this issue.

    Could not upload image files, and no wordpress files had been changed during the time from before, when it worked properly, and after, when it would no longer upload, so there was no extra spaces issue as suggested (with enormous surety) in the FAQ. Yet, still I got the “uploaded file could not be moved to… Warning: Cannot modify header information – headers already sent by (output…” error.

    The permission settings were indeed set for 777 within wordpress, via FTP, and via the cpanel interface.

    However, something on the web host caused the directories to act as though the permissions were set differently.

    So, before trying anything else, I suggest entering cpanel (or you may have vdeck on your web host, or something similar), and go to the File Manager (or the equivalent on your web host). Set the permissions on the …wp-content/uploads folder to 777 (again).

    That may clear the error on the web host, and the error should disappear. Very frustrating when errors appear through no fault of your own. Also frustrating when dozens and dozens of forum postings are left unanswered or left with misleading information because the the issue “has already been answered” yet nowhere is a conclusive, summing-up statement made.

    I suggest the something similar to the above solution be added to the wordpress troubleshooting FAQ: http://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem .

Viewing 15 replies - 196 through 210 (of 230 total)