neononcon

They’re assuming that any call to the_content filter is going to be output as visible information on the page. That is an incorrect assumption. So because of their incorrect assumption, SFC calling the_content in order to actually get the content (which is the purpose of the_content in the first place) is actually getting that contact form. But it doesn’t display it. And then in the *next* call to the_content, this time by the actual page itself, the contact form code doesn’t work properly and it doesn’t return the contact form again.

This is exactly what appears to happen, because when you have STC and simplepress active together, when you click the STC button to comment, it replaces the comments form and displays a frame of the entire forum.

I am just curious can you please explain why STC (specically “comments”) was incompatible with simplepress but SFC was working fine, and now since the update SFC is not working with it.

Will you be doing the same thing with STC (moving the code that generates the metadata into the base plugin)?

What causes the conflict exactly? That two plugins are looking for separate metadata at the same time?

I understand what you’re saying, but the other plugins were not updated recently at all, but SFC was. This means that something in the new SFC was changed and is now causing conflicts, right? Wouldn’t it make sense to try to figure out what was changed in SFC to cause these issues with other plugins? A lot of sites use SFC and they might not even know that after the update their other stuff is bonkers.

Since the upgrade, this plugin is also causing conflicts with simplePress Forum… now it is doing exactly what STC was doing before.

You do great work, and the community should be grateful, but every time there is a conflict between FTC/STC you simply say it’s the other side’s fault.

This is definitely related to the recent update. And now it’s impossible to go back because the previous version wants the API Key which now is the same as the App ID. And Facebook doesn’t display the old API Key anymore (even though it was still working fine for now).

*frustrated*

Can you please explain how exactly to reduce this width?

Speaking of buttons and css… is there a way to change the comments button from Medium to Large? Playing around with CSS will do it but then of course the css is hosted by fb. Any advice?

How can the Connect With Facebook button be modified? Anything?

yikes! is this normal activity?

This is exactly what I was just about to post here. How to have this on the homepage?

Thanks for the update, this is an outstanding plugin. Any chance of adding the feature above in the next update? I just think it would add another level of interactivity. Even if you can let people use gravatars, even better! There is so much possibility!

@cartpauj hi thanks for answering in this thread. It is understandable that the media tab should be visible when the option for allowing registered subscribers to upload files is checked on. But when that option is unchecked and off, it should no longer be visible. How can this be fixed? This is conflicting with the purpose of using WP Hide Dashboard.

@kpdesign Thanks I found that it was being caused by uCan Post plugin.

In the admin there is an option for:

Allow uploads on sumbission:
NOTE: For security reasons, only registered members can upload files

It was activated just to test and ever since turning that option on, the media tab exists in the dashboard even when unchecked.

I know this is nothing to do with WP Hide Dashboard at least now. Thanks for the great plugin and service.

What happened?

Speaking of buttons and css… is there a way to change the comments button from Medium to Large? Playing around with CSS will do it but then of course the css is hosted by fb. Any advice?

All css then?

Thank you for the reply.