Jon Hardison

Not at all TLW. We’ve been trying to figure this thing out but it’s really weird. Not entirely sure what the heck the cause is. We’ll get it, or go another way. I’m just really trying to avoid you having to reenter all of those products.

You’re very, very welcome. Glad it worked out for you, and glad everyone else that sees this wont edit their plugins. ??

My cure-all for almost every problem folks are having with this plug-in is to be sure your FB app has ‘Remove offline_access permission’ disabled in advanced settings. Once I changed that everything, including thumbnails started working. Hope it helps.

??? I’m not sure I understand. When you set everything up it will show you a list of all page you’re an Admin on, but will require that you select only one. This plug-in only posts to one page her site.

If that’s not what you’re looking for, please clarify a little. ??

Make sure your facebook app isn’t is sandbox mode. Also check in advanced settings for your facebook app and be sure Remove offline_access permission is disabled. Give that a try.

Just a note: You really shouldn’t have to edit the plug-in to get it working. Part of the issue (IMHO) is that Facebook keeps changing stuff so quickly it’s almost impossible for most to keep up.

To fix this issue without having to edit the plugin, simply admin your Facebook App and go to Advanced. Turn off the ‘Remove offline_access permission’ and that should do it.

Yeah… Just loaded it up on a few other Headway 2X sites and found that it doesn’t work. I’ll do some more digging, but I’m not going to waste too much time on it as Headway is basically not supporting that version of their framework anymore. Such a pain considering 3.X basically doesn’t work right yet.

Well thanx for that Badluck13. That should be quite useful for a lot of people. Unfortunately, my theme does used comment_form(), so this won’t help me. I’ve passed this issue on to the guys at Headway but I don’t think they’re going to look into as as I’m using the previous gen of the framework. I also haven’t taken a moment to test it on other sites, so I’m going to do that to be sure it’s not something specific to that site.

This is a strange problem. Hope to have the issue figured out soon.
Jon-

Sorry it took a while for me to get back to you. Thanx for the update on the API for Google Maps and the information on the language issue!

The xiliGroup Plug-in Xili-Language actually uses WordPress Standards, which was part of the issue for me. Turns out my theme (HeadwayTheme v2.x) did NOT. I worked with Michel at XiliGroup to rewrite xili-extended to add support for Headway so that’s all working now.

I’m going to grab the new copy of your plug-in and give it another go. It’s entirely possible that it’s working properly already.

Thanx again for turning this around so quickly. If I still find issues, I’ll jump on your forum link and let you know what I find.

Jon-

… and thank you for that help Michel. =)

Please disregard. Thank you.

Actually, it just struck me that this might also be an issue with xiligroup’s Language plug-in, so if you can’t think of anything obvious, don’t worry about it at all.

Uggg… This site is for a Canadian client and most things have to be in French and English, which is turning into a real pain.

Anyways, thanx again for your help.
Jon-

Thanx a bunch for that! I didn’t think that would work. Will try it now. Do I need to v2 or v3 API for your plugin?

Last question: I went ahead and activated the plug-in again and it seems to be working so far. I added a test property and saved it.

It seems the plug-in creates a listings page automatically. I looked at the page and it contains [fsrep-listings], but when I try to visit the page I get a 404. Can’t think of why, and I haven’t looked too deeply into the matter (as I was waiting for word back from you), but I thought I’d ask considering I had your ear. ??

I’ll obviously continue to try to figure out what I did wrong, but if you can think of anything, please do let me know.

We’re running HeadwayThemes 2.X and WP’s latest release. Our permalinks are /%category%/%postname%/.

Thanx again for your quick response to the question. Really appreciate it.

Jon-

Hi there, and thank you for the speedy reply. I found it and started to dig around, allocating more space with no change. Can you think of anything that might cause this, or any other files I should be looking at to attempt to resolve this?

Thank you again for your help.
Jon-