geoff67

We experienced this while staging a local WordPress installation, as well.

If we var_dump( $cpt_post_types ), we were getting bool( false ) returned.

I still don’t know the solution, but we were able to force it to work (for anyone on a deadline like us).

Important: Copy and save the value from *_options.cpt_custom_post_types in your database. Make a backup of your database as well, if you’re not familiar with MySQL.

After grabbing your data from *_options.cpt_custom_post_types, go to Add Custom Post Type in your wp-admin and add a post type. It doesn’t matter what it is, it will be deleted. Please note that this will remove and replace all data in *_options.cpt_custom_post_types. You will see the new post type on Manage Post Types.

Go back to your database, and replace the value in *_options.cpt_custom_post_types with the values you copied/saved before.

Revisit Manage Post Types in wp-admin, and everything should be restored.

Hopefully this write-up will also assist the plugin author on how to fix this bug.

You need to specify an ID for the first argument. I used the submit buttons as naming conventions until the plugin author corrects it.

//    register_sidebar_widget('Most Favorited Posts', 'wpfp_widget_view');
//    register_widget_control('Most Favorited Posts', 'wpfp_widget_control' );
    wp_register_sidebar_widget('wpfp-widget','Most Favorited Posts', 'wpfp_widget_view');
    wp_register_widget_control('wpfp-widget','Most Favorited Posts', 'wpfp_widget_control' );

and

//    register_sidebar_widget('User\'s Favorites', 'wpfp_users_favorites_widget_view');
//    register_widget_control('User\'s Favorites', 'wpfp_users_favorites_widget_control' );
    wp_register_sidebar_widget('wpfp-uf-widget','User\'s Favorites', 'wpfp_users_favorites_widget_view');
    wp_register_widget_control('wpfp-uf-widget','User\'s Favorites', 'wpfp_users_favorites_widget_control' );

No problem. I’m just glad it was easy to patch.

Getting the same error. Couldn’t find the option in the *_options table.

Turned on debugging and it produced this:

Array
(
    [post_id] =>
    [function] => wp.newPost
    [args] => Array
        (
            [post_title] => Antique Croc Rust
            [post_type] => fabric
            [terms_names] => Array
                (
                    [color] => Array
                        (
                            [0] => Bronze - Brown
                        )

                    [grade] => Array
                        (
                            [0] =>   5
                        )

                    [pattern] => Array
                        (
                            [0] => Leather
                        )

                )

            [terms] =>
            [custom_fields] => Array
                (
                    [0] => Array
                        (
                            [key] => material_content
                            [value] => 100% Leather
                        )

                    [1] => Array
                        (
                            [key] => fab_num
                            [value] => 11877
                        )

                )

            [post_status] => publish
            [post_author] =>
            [post_password] =>
            [post_excerpt] =>
            [post_date] =>
            [post_date_gmt] =>
            [post_thumbnail] =>
            [comment_status] =>
            [ping_status] =>
            [post_format] =>
            [enclosure] =>
        )

)
POST /massoud/wp-content/plugins/supra-csv-parser//xmlrpc/supra_xmlrpc.php HTTP/1.0
Host: localhost
Content-Type: text/xml
User-Agent: The Incutio XML-RPC PHP Library
Content-Length: 2337

<?xml version="1.0"?>
<methodCall>
<methodName>wp.newPost</methodName>
<params>
<param><value><string></string></value></param>
<param><value><string>[username here]</string></value></param>
<param><value><string>[password here]</string></value></param>
<param><value><struct>
  <member><name>post_title</name><value><string>Antique Croc Rust</string></value></member>
  <member><name>post_type</name><value><string>fabric</string></value></member>
  <member><name>terms_names</name><value><struct>
  <member><name>color</name><value><array><data>
  <value><string>Bronze - Brown</string></value>
</data></array></value></member>
  <member><name>grade</name><value><array><data>
  <value><string>  5</string></value>
</data></array></value></member>
  <member><name>pattern</name><value><array><data>
  <value><string>Leather</string></value>
</data></array></value></member>
</struct></value></member>
  <member><name>terms</name><value><string></string></value></member>
  <member><name>custom_fields</name><value><array><data>
  <value><struct>
  <member><name>key</name><value><string>material_content</string></value></member>
  <member><name>value</name><value><string>100% Leather</string></value></member>
</struct></value>
  <value><struct>
  <member><name>key</name><value><string>fab_num</string></value></member>
  <member><name>value</name><value><string>11877</string></value></member>
</struct></value>
</data></array></value></member>
  <member><name>post_status</name><value><string>publish</string></value></member>
  <member><name>post_author</name><value><string></string></value></member>
  <member><name>post_password</name><value><string></string></value></member>
  <member><name>post_excerpt</name><value><string></string></value></member>
  <member><name>post_date</name><value><string></string></value></member>
  <member><name>post_date_gmt</name><value><string></string></value></member>
  <member><name>post_thumbnail</name><value><string></string></value></member>
  <member><name>comment_status</name><value><string></string></value></member>
  <member><name>ping_status</name><value><string></string></value></member>
  <member><name>post_format</name><value><string></string></value></member>
  <member><name>enclosure</name><value><string></string></value></member>
</struct></value></param>
</params></methodCall>
HTTP/1.1 200 OK
Date: Thu, 13 Dec 2012 16:50:16 GMT
Server: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/0.9.8r DAV/2 PHP/5.4.4
X-Powered-By: PHP/5.4.4
Connection: close
Content-Length: 502
Content-Type: text/xml; charset=UTF-8

<?xml version="1.0" encoding="UTF-8"?>
<methodResponse>
  <fault>
    <value>
      <struct>
        <member>
          <name>faultCode</name>
          <value><int>405</int></value>
        </member>
        <member>
          <name>faultString</name>
          <value><string>XML-RPC services are disabled on this site. An admin user can enable them at http://localhost/massoud/wp-admin/options-writing.php</string></value>
        </member>
      </struct>
    </value>
  </fault>
</methodResponse>

Issue successfully reported!XML-RPC services are disabled on this site. An admin user can enable them at http://localhost/massoud/wp-admin/options-writing.phpProblem Ingesting Antique Croc Rust

Héctor,
Go ahead. Love the plugin, so thanks for all of the work so far.

What’s the reasoning behind changing the way post_type usually works in a query (by adding post_type_name as a parameter)?

Would it not be simpler to say:

$args = array(
    'orderby' => 'views',
    'post_type' => array('posts','pages','custom-post-type'),
);
wpp_get_mostpopular($args);

OR
wpp_get_mostpopular('order_by=views&post_type=posts,pages,custom-post-type');

And ditch the pages parameter altogether. If you want to keep backwards compatibility, setting pages to false or true would simply add it into the post_type array.