Forum Replies Created

Viewing 15 replies - 16 through 30 (of 202 total)
  • Thread Starter Modifiedcontent

    (@modifiedcontent)

    Thanks for your reponses spacegrrl and bcworkz!

    I am running out of time again. I will test these sometime in the next month and report back…

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    Thank you for your response. I had come across another (?) paid plugin with an, as far as I can tell, similar approach:

    http://rudrastyh.com/wordpress/search-across-wp-multisite.html

    Also solving another issue:

    http://rudrastyh.com/plugins/get-posts-from-all-blogs-in-multisite-network

    These are priced fairly. I am thinking about getting them, but wonder if this type of indexing solution is already “out there” as open source and these plugins are just repackaging.

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    No, because it is not every time and it also often happens in the admin area users list.

    I am hoping that someone recognizes the issue, knows what can cause a jpg to get displayed at text.

    Where it happens is probably less relevant.

    Modifiedcontent

    (@modifiedcontent)

    @jwertin, where did you change that code? Is that in a core file somewhere? Can we come up with a fix to put in functions.php?

    I don’t understand how/where RSS feeds are generated in WP. Have had this problem for years. Is this a genuine WP bug?

    In my case, this function in feedwordpress.php seems to be the source of the problem:

    /**
     * syndication_comments_feed_link: Escape XML special characters in comments
     * feed links
     *
     * @param string $link
     * @return string
     *
     * @uses is_syndicated()
     * @uses FeedWordPress::munge_permalinks()
     */
    function syndication_comments_feed_link ($link) {
    	global $feedwordpress_the_original_permalink, $id;
    
    	if (is_syndicated() and FeedWordPress::munge_permalinks()) :
    		// If the source post provided a comment feed URL using
    		// wfw:commentRss or atom:link/@rel="replies" we can make use of
    		// that value here.
    		$source = get_syndication_feed_object();
    		$replacement = NULL;
    
    		if ($source->setting('munge comments feed links', 'munge_comments_feed_links', 'no') != 'no') :
    			$commentFeeds = get_post_custom_values('wfw:commentRSS');
    			if (
    				is_array($commentFeeds)
    				and (count($commentFeeds) > 0)
    				and (strlen($commentFeeds[0]) > 0)
    			) :
    				$replacement = $commentFeeds[0];
    
    				// This is a foreign link; WordPress can't vouch for its not
    				// having any entities that need to be &-escaped. So we'll do it
    				// here.
    				$replacement = esc_html($replacement);
    			endif;
    		endif;
    
    		if (is_null($replacement)) :
    			// Q: How can we get the proper feed format, since the
    			// format is, stupidly, not passed to the filter?
    			// A: Kludge kludge kludge kludge!
    			$fancy_permalinks = ('' != get_option('permalink_structure'));
    			if ($fancy_permalinks) :
    				preg_match('|/feed(/([^/]+))?/?$|', $link, $ref);
    
    				$format = (isset($ref[2]) ? $ref[2] : '');
    				if (strlen($format) == 0) : $format = get_default_feed(); endif;
    
    				$replacement = trailingslashit($feedwordpress_the_original_permalink) . 'feed';
    				if ($format != get_default_feed()) :
    					$replacement .= '/'.$format;
    				endif;
    				$replacement = user_trailingslashit($replacement, 'single_feed');
    			else :
    				// No fancy permalinks = no problem
    				// WordPress doesn't call get_permalink() to
    				// generate the comment feed URL, so the
    				// comments feed link is never munged by FWP.
    			endif;
    		endif;
    
    		if (!is_null($replacement)) : $link = $replacement; endif;
    	endif;
    	return $link;
    } /* function syndication_comments_feed_link() */

    This function is hacking around some WordPress issue – ‘Q: How can we get the proper feed format, since the format is, stupidly, not passed to the filter?’

    A PHP Fatal error is caused by the line if ($source->setting('munge comments feed links ... -> Call to a member function setting() on a non-object

    Modifiedcontent

    (@modifiedcontent)

    As far as I call the issues below were the main reason for the 4.1.2 upgrade – and main cause of all the problems:

    Fixing add_query_arg() and remove_query_arg() usage

    XSS Vulnerability Affecting Multiple WordPress Plugins

    So if you have add_query_arg() or remove_query_arg() anywhere in old plugins or custom theme code, you have to escape them with esc_url() or somehow replace them.

    You will have to do that manually and puzzle clues on how together from all over the WordPress world – note that ‘_smartik_’ in that first thread gets arg and var mixed up for example.

    Replacing/cleaning up .htaccess also fixed issues in my sites, but I had just moved to VPS when the automatic updates happened, so I have no idea what is causing what.

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    Here are more clues:

    Fixing add_query_arg() and remove_query_arg() usage

    XSS Vulnerability Affecting Multiple WordPress Plugins

    > Where did you find the “dodgy queries” that you removed/fixed?

    Stuff in my custom themes, developed over years.

    These automatic upgrades coincided with a migration to a VPS server, so it is just a big hairy mess. I have no idea what causes what.

    Please don’t force me to use another plugin to get rid of those 3rd or 4th empty columns wasting space in my admin!

    Why does WordPress/Automattic have so little common sense? Why do you keep doing these idiotic things?

    I “fixed” it for now by adding the following code from a link earlier in this thread to my functions.php, under my growing ‘f*** you Matt Mullenweg’ code section:

    function wpse126301_dashboard_columns() {
        add_screen_option(
            'layout_columns',
            array(
                'max'     => 2,
                'default' => 1
            )
        );
    }
    add_action( 'admin_head-index.php', 'wpse126301_dashboard_columns' );
    
    add_action( 'admin_head-index.php', function()
    {
        ?>
    <style>
    .postbox-container {
        min-width: 100% !important;
    }
    .meta-box-sortables.ui-sortable.empty-container {
        display: none;
    }
    </style>
        <?php
    });

    @wpyogi, these RSS feed errors seem to be all variations of the same problem. I have posted several threads about it that went nowhere and have seen others do the same.

    Usually these threads end with the standard ‘uninstall all plugins one by one’ advice, but there is never a real solution.

    I have also tried the solutions in this thread without success. This looked like another dying ‘broken RSS feed’ thread, so I posted to try to keep it alive.

    This is a recurring problem for me that makes WordPress RSS feeds pretty much useless. Uninstalling plugins one by one or searching for whitespaces in files really isn’t a solution.

    Please WordPress/Automattic, fix this.

    BTW, I tried this RSS feed repair plugin and it killed the feed entirely. All these fixes – dodgy plugins, editing core files, etc. – are only creating more problems.

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    And it is broken again. Error message this time:

    The following tags were not closed: rss, channel, item, wfw:commentRss.
    Line: 0 Character: 0

    What does that mean? How to fix it?

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    There is more background about this problem here.

    Very clear explanation here:

    Unfortunately, with WordPress it seems all too easy for a plugin, a theme, or for your configuration file to contain a blank line.

    Removing the last ?> from functions.php fixed my problem for now – I did not know that last php closing tag was optional.

    Fixing the feed by looking for “blank spaces” in wp-config.php, functions.php, etc. + all the plugin files is really cumbersome. I am not even really sure what counts as a “blank space” and what doesn’t.

    Is there no way to filter these “blank spaces” out with some code?

    Someone worked on the same problem here, but he has a command line solution for locally installed code – I have no idea how to get that working.

    This thread seemed to be moving toward a solution until it was derailed by esmi’s catch-all ‘disable all plugins and revert everything to standard WordPress’ solution.

    Modifiedcontent

    (@modifiedcontent)

    Updated with no problems now. Thanks radgeek!

    Modifiedcontent

    (@modifiedcontent)

    @miamitom, I have several multisite installations that depend heavily on FeedWordpress, including custom code that leverages FeedWordpress.

    It is very much in my interest that the plugin is solid and that any issues it may have are solved. But I haven’t noticed any structural issues with FeedWordpress.

    I have had lots of problems with WordPress RSS feeds recently. Could your FeedWordpress issues have to do with something else?

    The plugin sees new posts but does nothing to import them.

    Are those posts perhaps still in your trash folder, from an earlier test? I have made that mistake in the past. Whatever your problem is, it sounds more like configuration issues.

    The cause of this upgrade problem is very obvious. Lets fix this first, by adding that missing ‘externals’ folder, and then fix whatever other issues there are in separate threads.

    Keep it simple. One thing at a time.

    Modifiedcontent

    (@modifiedcontent)

    I was able to “fix” my sites by simply reverting to the old version, uploading it with FTP over the new version.

    The problem with this upgrade is pretty straightforward; it is supposed to have a folder called ‘externals’ with a myphp.class.php file and it doesn’t.

    I haven’t been able to find that folder+file anywhere else online, so I’ll just wait for dev radgeek to add it.

    FeedWordPress is normally one of the more sophisticated, solid plugins in the WordPress universe, so don’t get too distracted by side issues.

    Modifiedcontent

    (@modifiedcontent)

    Looks like the dev radgeek forgot to include the externals folder in the new version? Is that folder available anywhere? Is myphp.class.php a generic file?

Viewing 15 replies - 16 through 30 (of 202 total)