Backwards compatibility?
-
I am supporting a client on 4.2.2 using RecipePress 2.2 and we are running into performance issues. This looks like a great plugin, but I can’t find info on backwards compatibility and would like to know before spinning up a test environment.
Can anyone speak from their experience moving from RecipePress by grandslambert to one of the new versions of this plugin? Please include WP version, grandslambert plugin version and the reloaded version you installed.
Thanks!
-
I can’t promise backwards compatibility is still there. I didn’t test migrating since release 0.5 and some things have changed.
If you hit any bugs on your test environment I’ll e happy to fix them.Thanks for the response. I’m testing on a clone of the host and receiving this error:
[Tue May 19 09:36:51 2015] [error] [client 127.0.0.1] PHP Fatal error: Call to undefined method RPR_Migration::add_taxonomy() in /var/www/html/stage.madejustright.com/wp-content/plugins/recipepress-reloaded/php/class/rpr_migration.php on line 347, referer: https://mjr.earthbalancenatural.com/wp-admin/plugins.php?plugin_status=all&paged=1&s
I’ve tried versions 0.5.0 – 0.7.9 and all have the same error.
$ php --version PHP 5.3.3 (cli) (built: Oct 30 2014 20:12:53) Copyright (c) 1997-2010 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies $ wp core version 4.2.2
Thanks for reporting. I will look into this as soon as possible. However I probably won’t be able to do so before the weekend.
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 [email protected] I’ll be happy to test the migration procedure.Kind regards
Janpublic 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; } }
Was this issue resolved? I’m supporting a client who is using Recipe Press 2.2 and we are migrating her site to a new domain with a new theme. I’ve installed Recipe Press Reloaded onto her new domain (have yet to migrate over her database from the old site), but it says “The Recipe Press Reloaded database needs to upgraded. Make sure you have a backup before you proceed. | Proceed”
When I click proceed, I get the following error.
“Fatal error: Call to a member function set() on a non-object in /home/content/73/7424773/html/abraskitchen/wp-content/plugins/recipepress-reloaded/php/class/rpr_migration.php on line 73”
To me this seems to be a different issue.
Please check:
– which version of RecipePress reloaded are you using?
– did you install the Redux framework? It shoul be working without, but thats the only ‘set’ method aroundAs RecipePress reloaded is a free time project I mainly do to run my own web page I can’t guarantee that compatibility to RecipePress is still there. In case it’s broken I might or might not be able to fix this in the next release if you can give me access to the RecipePress data (eg a wordpress export)
I think you’re right. I sent that message before I did a whole lot more digging into this client’s site. She currently has RecipePress 2.2 on her old site. I downloaded RecipePress reloaded 0.7.12 and Redux framework on the new site just to see if I could import her recipes into it. When I activate the new plugin and click the button to upgrade the database, with Redux framework also activated, now I get these errors:
Warning: preg_replace() [function.preg-replace]: No ending delimiter ‘_’ found in /home/content/73/7424773/html/abraskitchen/wp-content/plugins/recipepress-reloaded/php/class/rpr_taxonomies.php on line 456
Warning: preg_replace() [function.preg-replace]: No ending delimiter ‘_’ found in /home/content/73/7424773/html/abraskitchen/wp-content/plugins/recipepress-reloaded/php/class/rpr_taxonomies.php on line 456
Warning: Cannot modify header information – headers already sent by (output started at /home/content/73/7424773/html/abraskitchen/wp-content/plugins/recipepress-reloaded/php/class/rpr_taxonomies.php:456) in /home/content/73/7424773/html/abraskitchen/wp-includes/pluggable.php on line 1171
I super appreciate your help with this! I’ve spent so many hours trying to find a workaround so she doesn’t have to retype out all of her recipes into the posts. I’d be happy to send you the RecipePress data from her wordpress export – what’s your e-mail?
Thank you!!
Despite the warnings, do the recipes get imported?
Please send the data to [email protected], but I can’t promise I’ll be able to look into this before August.
- The topic ‘Backwards compatibility?’ is closed to new replies.