khermberg

Thanks for your help. I agree that the theme and framework need to be re-visited, but that isn’t an option in the short term. Your help with the CSS code is very much appreciated as a temporary solution.

The theme is quite nice and I truly appreciate your help in resolving the issue for use with my clunky old theme.

Thanks!

Thanks for the quick reply. Unfortunately, it is not much help because I had tried that before posting on this forum. If nothing is selected, the share buttons (as expected) show up nowhere.

If ONLY “display at bottom of posts” is selected, the buttons do not show up on the pages (or their sidebars). They DO show up on posts (and the sidebars when the posts are displayed).

If ONLY “display at bottom of posts” is selected, the buttons show up on pages, as expected, AND in sidebar widgets when the pages are displayed. They do not, however, show up on posts or the sidebars when the posts are displayed.

The other alternatives behave similarly.

The issue is with widgets that were built that have html (one site has several of these). On one site https://aaptstudies.org, I removed all but the most necessary widgets so there are only two things in the sidebar (a widget with a logo, it has html in it) and a custom menu. For now, that is a possibility, but it is a very short-term thing. I have the settings currently set to show at the bottom of posts and the bottom of pages (all other boxes have been deselected). The same client has another site with several widgets in both sidebars for which this is an issue and for which using fewer things in the sidebars is not an option.

I do not need to use your “follow me” widget, so I am hoping I can append code (either in the css in settings or in the appropriate php file) that will not allow the buttons to populate anywhere in any sidebar or widget. Any suggestions?

Your help in resolving this issue will be greatly appreciated.

Thanks for the speedy reply, @fishang. Hopefully the plugin author can respond with a speedy fix.

Any movement on this issue?

reCaptcha shows up in the back-end preview but not on the front end. I have tried deactivating other plugins, etc.

fishang, did you get it working?

Help in resolving this issue will be greatly appreciated.

I am having the same problem, with ReCaptcha being there on the adminsitration preview but not on the front end. I see this has been marked as “resolved.” What is/was the resolution?

Any help with this issue will be greatly appreciated. This plugin has some features not available in the other free form plugins and has been precisely what we needed. Love it! But this recaptcha issue is a big one in our application.

Nice plugin. A few features would make it MUCH more useful for me:

Formatting within text box, preferably via WP’s visual editor, but otherwise at least simple markup, much like in this reply box on this support forum, so they can bold, italicize, insert line breaks.

Ability to include some text in the form that is not associated with a field (so one can include instructions or explanations).

Include option to the post include links to the files uploaded with/via the form when form submission creates a post.

Any success-progress with this issue?
I want to place the uploaded file into a different directory (not within the wp uploads directory) and am having trouble getting the uploads directed properly and the links in post and email generated by the form to point to the uploaded file.

When submitting the form, I get an error message having to do with wordpress-form-manager/types/file.php line 102. That line is related to the url, but it does not appear to be what establishes what the url should actually be.

Some help here will be greatly appreciated. The plugin does exactly what we need, if I can resolve this uploading issue.

Very nice. That seems to have done the trick. Kicking myself for not thinking of the “else.”

Thanks for your help and your quick replies.

Thank you for your reply.

I have not fully tested your suggestion, but I have made those changes and at first glance they appear to have done the trick. Thank you!

One unexpected and unwanted result is that the ‘read more’ tag now appears even if the post is shorter than the specified excerpt length. Before the change, if the post was that short, the tag did not appear. The ideal would be for the tag to only appear if the post is longer than the excerpt, but if the choice is between the original behavior and the behavior after the fix you suggested, for my purposes, the fix is better.

Do you think you will include that change in your next update? That (combined with the read more tag only showing when the post is longer than the excerpt length) would have the excerpts yielded by the plugin behaving in a manner that is typical of blog excerpts.

Nice plugin. Thanks.

Thanks. This is helpful. The code addition you suggested works well on an initial test and only using it will reveal if there are unintended consequences.

Having to change the file each time the plugin is updated is not ideal, but it is manageable. Would you be wiling to incorporate this into your next update so that the code is then there through future updates? It is a feature some folks will find useful and that will not likely cause trouble for folks who do not want it.

Thanks for your help and your plugin.

Does anyone have an answer to this, or an alternative method for accomplishing it?

Anyone? I found it on a different form plugin but the other features of this one are better.

Thanks. I decided to put a conditional into the template to replace the get_sidebar command … it now gets one for page XXX and the other for the rest of the site. Then, your comment about looking more carefully at the brackets and negation got me to this for excluding some of those widgets from the four categories and their posts. I had successfully included a widget in those same places I wanted to exclude others, so I used that code inside !().

Here is what I used in widget logic for the excluding:
!(is_category(array (6,7,8,9)) || (is_single() && in_category(array (6,7,8,9))))

It appears to be working. Thanks for the pointer.