Jan Koester

This is a major misconfiguration of your webserver. PHP warnings or notices are nothing to worry about in general. So this is not actually a bug in RPR, more an issue of not really nice coding.
However you should NEVER expose these information to any visitor of your site. The warnings might expose paths to executables and make it easy to exploit security vulnerabilities.

Please fix your webserver’s settings!

Hi,

yes I’m still alive and doing pretty well. Though I don’t find the time to work on RPR any more.
I guess the problem with your theme is, it’s altering the query so recipes (which are a custom post type) can’t appear. Just a quick guess.

Regards
Jan

To me this looks like get_term_meta( $term->term_id, ‘cost’, true ) returns false which is equal to 0.

Front end submission is not possible and also not on the roadmap for the future.

Feel free to fork the plugin on GitHub, implement the required feature and then create a pull request to have the feature included in a future release.

No, this is currently not possible.

This is a feature and not a bug.

The ‘excerpt field’ in the editor is not the same as ‘the excerpt’.
The excerpt as displayed on the front page is a composition of several data (including categories, tags and other meta data) as defined by the layout files of RecipePress.
As some themes do not make use of the the_excerpt() function provided by wordpress but rather take the value aof the excerpt field directly from tha database, the plauginsaves the description into the excerpt field to provide at least some data in this case.

The austosave message seems to be a quite annoying yet harmless bug, as the saving of data still works.

Alright, that was my mistake.

Quick fix: Add the following line at public/class-rpr-public.php in line 231:

return $content;

The complete block of code then should look like this:

/* Only render specifically if we have a recipe */
        if ( get_post_type() == 'rpr_recipe' ) {
            remove_filter('get_the_excerpt', array( $this, 'get_recipe_excerpt' ), 10);
            $recipe_post = get_post();

            $content = $this->render_recipe_excerpt( $recipe_post );
            return $content;
            add_filter('get_the_excerpt', array( $this, 'get_recipe_excerpt' ), 10);
        } else {
            return $content;
        }

I will add this fix to the next release, but this might take some time.

Quite obvioulsy most themes (including the default theme TwentySeventeen, …) do not seem to be affected by this bug.

I will have a deeper look into this as soon as possible.
From the code of the theme it should be working. Please have a little patience.

Please read the documentation. It’s of no help if you do things without understanding what is happening.

Just a little hint: You need to copy the file you want to change /overwrite to your child theme and edit it there.

Has this issue been resolved by the suggested solution?

As I thought: this feature of jetpack (https://jetpack.com/support/featured-content/) is not implemented in a way at dyad2 to show anything else than normal posts.
In inc/jetpack.php line 17 the function to pull posts for featured content is defined like this:

//Featured content
add_theme_support( 'featured-content' , array(
    'featured_content_filter' => 'dyad_2_get_banner_posts',
    'max_posts' => 6,
    'post_types' => array( 'post' ),
) );

according to jetpack’s feature page this should include recipes as well

add_theme_support( 'featured-content', array(
    'featured_content_filter' => 'dyad_2_get_banner_posts',
    'max_posts'  => 20,
    'post_types' => array( 'post', 'rpr_recipe' ),
) );

Manually editing the file might not be the best idea, as each update of the theme will break it. Maybe ask the developers of the theme to add an option to include other posts types as well. Or think about creating a child theme.

Finally: This is not a issue of RecipePress reloaded!

Most probably the theme is only looking for posts of type post and nor for rpr_recipe. So this problem affects all plugins creating a new post type.

I’ll have a deeper look into the code of the theme as soon as possible.

As explained here: https://www.ads-software.com/support/topic/jetpack-update-has-broken-another-plugin/#post-9408387

I’ll close this issue now.

Please ask the support there for the location of the log files. I don’t that either.

After scrolling through jetpacks’s support page I’m pretty sure this a problem of jetpack. There are several reports of similar issues with other plugins.

Please report the error over there.

EDIT: Just seen there is a quick fix already: https://www.ads-software.com/support/topic/jetpack-update-has-broken-another-plugin/#post-9408387

• This reply was modified 7 years, 3 months ago by Jan Koester.

I see the facts. But it’s also fact that using the same versions of wordpress, the plugin, the theme and jetpack I do not get the error. So probably some functions of jetpack are interfering with RPR. I can’t test this on my dev system as I run wordpress locally and therefore can’t connect to jetpack.
Very difficult to debug now.
Could you please have a look at the PHP error log of your hosts if there is anything related to RPR. Maybe there is a clue.
It might also be related to this: https://www.ads-software.com/support/topic/jetpack-plugin-conflicts-with-wordpress-visual-mode/ and several similar reports affecting quite a lot of plugins using custom post types

If the PHP error log is of no help, please report this issue also to Jetpack

• This reply was modified 7 years, 3 months ago by Jan Koester.
• This reply was modified 7 years, 3 months ago by Jan Koester.