Charlie, Appreciate your comment.
But how on earth I am not able to convey a simple fact that the theme does not allow migration of your recipes from any given recipe plugin in the market. And where is the author saying that they support the plugin I have I mean you seem have read it completely wrong?
My grievance is not that the author does not forewarn me about the incompatibility of my plugin. I have problems when the theme does not support migration of recipes from any recipe plugin, it is a major thing to inform the customer, which they kept hidden.
I am sure you understand the food blogs and food blogs do not exist without using a recipe plugin. A theme maker, when making a new recipe theme, was already aware of the fact that every food blog would be using a recipe plugin. When they will buy a new theme, they will need to migrate their existing recipes in the new theme. It was the theme developer duty to let the customer know that they do not support this activity. Period.
Maybe it’s important to know here is that there is two type of recipe themes.
- The theme that does not have a built-in recipe section.
- The theme that has inbuilt recipe section.
In the first type of theme, the user is free to use a recipe plugin of their choice and use with the theme, for example, NEWSPAPER Theme or Studio Press Themes. The theme developer suggests the best compatible plugin, and then leave the rest to the user to decide which plugin they want to use.
In the other type of theme, the theme author should mention if their theme is capable of migrating the existing recipes to the new theme or not, which FoodBook did not do. And when I found this (just on the very same day), I requested a step by step solution.
Just because they failed to initially inform me about the drawback, and secondly, that I am a non-tech person, does not mean that they will offer me another expensive alternative method to migrate my recipes. In this case, I demanded the refund. What wrong did I do?