Jan Koester

You can create your own layout if you like. Unfortunately I didn’t find the time to document this feature.
Create a subfolder rpr_layouts in your themes directory and copy one of the layout folders from rpr to there. You can adjust the layout to your needs. It should then appear as a local layout in the appearance section of the settings page.

If you like you can also submit your layout to be included in future releases.

Fixed in release 0.7.10

Just wrote a little howto on that: http://tech.cbjck.de/wp-plugins/rpr/documentation/users-documentation/use-nutritional-information-on-your-recipes/

Please note that in the current version 0.7.9 nutritional information will only be displayed if all fields are given. Release 0.7.10 will change this. I plan to release it this week.

Don’t worry. I know your situation just too well. I’ve just had two weeks holidays and some time to work a little on the plugin. The next weeks will again be very busy with work.

You could try adding the function add_taxonomy to the file rpr_migration.php. I guess I’ve moved it to rpr_taxonomies at some time.
However, I don’t have an old database so I can’t test it. If you provide your database file by email to admin@cbjck.de I’ll be happy to test the migration procedure.

Kind regards
Jan

public function add_taxonomy($name, $singular, $slug, $hierarchical, $edit_tag_name) {
			$editing = false;

			if( strlen($edit_tag_name) > 0 ) {
				$editing = true;
			}

			if( !$editing && taxonomy_exists( strtolower($singular) ) ) {
				die( 'This taxonomy already exists.' );
			}

			if( strlen($name) > 1 && strlen($singular) > 1 ) {

				$taxonomies = get_option('rpr_taxonomies', array());

				$name_lower = strtolower($name);
				$singular_lower = strtolower($singular);

				$tag_name = $singular_lower;

				if( $editing ) {
					$tag_name = $edit_tag_name;
				}

				$taxonomies[$tag_name] =
				array(
						'labels' => array(
								'name'                       => $name,
								'singular_name'              => $singular,
								'search_items'               => sprintf( __( 'Search %s', $this->pluginName ), $name ),
								'popular_items'              => sprintf( __( 'Popular %s', $this->pluginName ), $name ),
								'all_items'                  => sprintf( __( 'All %s', $this->pluginName ), $name ),
								'edit_item'                  => sprintf( __( 'Edit %s', $this->pluginName ), $singular ),
								'update_item'                => sprintf( __( 'Update %s', $this->pluginName ), $singular ),
								'add_new_item'               => sprintf( __( 'Add New %s', $this->pluginName ), $singular ),
								'new_item_name'              => sprintf( __( 'New %s Name', $this->pluginName ), $singular ),
								'separate_items_with_commas' => sprintf( __( 'Separate %s with commas', $this->pluginName ), $name_lower ),
								'add_or_remove_items'        => sprintf( __( 'Add or remove %s', $this->pluginName ), $name_lower ),
								'choose_from_most_used'      => sprintf( __( 'Choose from the most used %s', $this->pluginName ), $name_lower ),
								'not_found'                  => sprintf( __( 'No %s found.', $this->pluginName ), $name_lower ),
								'menu_name'                  => $name
						),
						'show_ui' => true,
						'show_tagcloud' => true,
						'query_var' => true,
						'hierarchical' => $hierarchical,
						'rewrite' => array(
								'slug' => $slug,
								'hierarchical' => $hierarchical
						)
				);
				update_option('rpr_taxonomies', $taxonomies);
                $this->taxonomies=$taxonomies;
				return true;
			}
		}

I was a bit surprised to see that allinkl indeed does not offer any error log at all. However its is possible to create a logfile within your webspace as described ie here: http://blog.joergboesche.de/serverphp-config-php-error-handling-via-htaccess

Without an error message I won’t be able to sort out the problem.

The problem sound a bit weird to me. I’ve never seen such a problem and not even heard of it.

Your .htaccess seems to be alright.

The options page should be at [Your URL]/wp-admin/edit.php?post_type=rpr_recipe&page=_options so the link seems to be fine. In the frontend I have the same link like you but it works for me.

I have no idea why this does not work for you.