Invalid symbol

Hmmm. Never heard of that one before. When you're using the loadposition tag, is it loading any modules that are from JFBConnect (like our JFBCLike or JFBCFan modules), or is it loading something completely independent of it? From trunk's post, it seems independent, but just checking.

We'll have to do some testing to figure out where the conflict between these two things are. The best suggestion I can give for now is to try re-ordering the Load Position and JFBCContent plugins. Try swapping the ordering number (which changes the order they execute in) and see if that helps. You may also want to simply disabling the JFBCContent plugin (temporarily) to see if that changes the behavior. If so, please let us know what you find.

Thanks,
Alex

We'll be investigating this tomorrow and hopefully be able to recreate it. If not, we'll let you know. At that point, we may need administrator credentials to understand your site configuration.

Finally, did you ever try making the JFBCContent plugin first? Just curious if that changed the behavior in any way.

Thanks,
Alex

Trunk,
Thanks for the extra info through PM. We were in the process of investigating this as you sent it

We have been able to recreate the issue that you both describe. The problem is due to the setting in the Social Configuration - Open Graph tab for "Use beginning text in article for default". Basically, it's picking up the {loadposition xxx} tag and using it for the description. It's not using the ending } in the description and instead leaving that in the article text.

Both things are obviously incorrect -- that's a terrible description if someone Like's the page and posts it to Facebook and the extra } is annoying.

For now, we can only recommend disabling the "Use beginning text.." setting. I've added a ticket to our bug tracker for this item, but honestly am not sure the best way to fix this immediately. Likely, we should be ignoring any {blah} tags, but that could cause other issues for users that actually want to put a { in their intro text.

Hope the above at least works as a temporary solution, and we'll try to get a better solution into an upcoming release.

Thanks,
Alex

Definitely a creative solution

This is a lower priority issue, but one that will likely be looked into over the next few weeks, and definitely for the 4.2 release (due in April). Thanks for your patience, and let us know if you have any other problems.

Thanks,
Alex