That's to be expected. The Open Graph plugin gets the article information and then has to determine if the category that it is set to exist in is within the object category or sub-categories that you selected. So, we have to 'test' every article to see if the object you created should apply to it.curiously when I change the object category setting to another category it still messes with "womens" products
I just did some quick investigation on a test site. The catid field in the database that we read from is setup by Joomla as an integer, as would be expected, since it should only store one value. From the MySQL error you show, it seems like the value "25,32" is being stored there, which is most definitely not an integer. My guess is that the other extension is actually altering Joomla's core tables to perform its function. That can have profound effects on functionality (as seen here), performance (integers are much easier to search and sort on) and various other effects. Definitely not a Joomla solution.I agree it really isn't a standard Joomla solution
I'm not sure what you're actual goal is. I was focused on the SQL error and it's cause. All I did was narrow down the cause. I didn't add any tags to the article itself.Can I clarify, when you say there were no errors did you also insert the plugin code into the article or this unnecessary?
Have you created an Open Graph Action in the JFBConnect area? If so, you need to use the id of that action (an integer as well) where the 'X' is above, like {JFBCAction action_id=1 ...}I also tried it on an article that is only assiged to one category and had no DB errors but when I tried to insert the plugin syntax: {JFBCAction action_id=X action text= button text} I got this result: JFBCAction ID not found!
Join our newsletter to get alerts for Joomla releases, tips and tricks and extension updates.