1

Hello Stephanie,

this was added in Foliopress WYSIWYG 0.9.19. Some people reported issues with it, so we’ve put this into advanced options, turned off by default (Settings -> Foliopress WYSIWYG -> Advanced -> Use WordPress Linking Dialog).

Thanks,
Martin

Hello Rachelle,

can you at least let us know what WordPress version and permalink structure are you using?

You can give our beta version a try here: http://foliovision.com/downloads/fv-top-level-cats-1.1.4beta.zip

Let us know if it helps. We are planing to do a major rewrite to not have issues like this anymore.

Thanks,
Martin

Hello Paul,

there might be a conflict with your template CSS or HTML. It works well on all the sites we build, we work with a lot of different templates.

Try following the “Testing” guidelines in our FV Antispam Installation and Testing guide.

Thanks,
Martin

Hello Stephanie,

you need to delete the plugin and install it again. All the configuration will be stored.

Perhaps this is the problem you had – WordPress has issues with FTP on certain hosts: http://foliovision.com/seo-tools/wordpress/plugins/wysiwyg/install-upgrade-failed

We are looking into decreasing the size of our plugin.

Thanks,
Martin

Thank you for that, it’s a nice addition into our FAQ!

Martin

It could also be due to CSS. Maybe one of the lines in your template CSS is forcing display for the textareas.

I added your question into FAQ section.

Thanks,
Martin

Hello Poli,

my guess be that your template is using some different HTML for the comment form (it should do it with a WordPress function) and that’s why the special CSS is not working and two textareas appear instead of one.

If you are using any publicly available WordPress template, we can check it out and see what could be wrong.

Also, try clearing any WP cache you are using and browser cache.

Thanks,
Martin

Hello Heather,

sorry about the issues, there has been a mistake in the update. Thank you for letting us know.

It’s fixed now, please delete the plugin and reinstall.

Martin

Hello Greg,

it looks like your web server configuration only allows data files being served from wp-content directory. It might be a good idea to block requesting any of the PHP files in that directory and subdirectories, but there is no reason to disallow HTML files.

With your setup, it’s not possible to call any of the PHP plugin code directly, but the PHP includes work.

You will have to disable these restrictions. Make sure that none of these directories is 777 and only restrict the file types in your 777 directories. Actually, chmod-ing plugin directory to 777 might be the reason why PHP and HTML is stopped. Are you sure you put 777 only on the images directory (it shouldn’t be needed on modern hosts anyway).

Thanks,
Martin

Hello eak1111,

we tested this plugin in WordPress 3.1 and it works. Can you provide any details about your issue? Does it happen on another blog with other set of plugin? It might be a conflict with some other plugin.

WordPress 3.1 has also better default Screen Options. Is that somehow interfering on your site?

Thanks,
Martin

Hello Dave,

yes, you can insert videos using the WordPress Media Uploader, after you hit the Insert FV WP Flowplayer icon in either Foliopress WYSIWYG or the standard WordPress editor.

The Media Library works with the WordPress Media Library directory (which uses wp-content/uploads/ as a default).

WordPress supports only one directory for all the uploads, so it won’t go into /videos, unless you change that directory in Settings -> Media. But that would affect other uploads too. We are trying to figure our a way of changing this path for the videos without user intervention and without breaking older uploads.

Thanks,
Martin

Hello Jeff,

check out the updated FV Antispam Installation page for some suggestions on how to test this plugin.

Thanks,
Martin

Hello Carmen and Douglas,

I tested your isses thoroughly.

1. Installed latest WP with users admin, editor1, editor2
2. Configured admin’s screen options
3. Installed FV Clone Screen Options plugin
4. Logged in with editor1 to see that he has the default screen options
4. Cloned admin’s screen options all around
5. editor1′s and editor2′s screen options are now the same as admin’s

6. Registered new account – editor3
7. Checked that editor3 has the new default screen options forced by FV Clone Screen Options

Carmen’s issue –
8. I changed something in Screen Options for admin – this setting was preserved, it wasn’t destroyed after page refresh
9. Changed some Screen Options for editor2 – working fine
10. Changed some Screen Options for editor3 – working fine
11. Cloned admin’s Screen Options with FV Clone Screen Options – works ok

So the plugin is not breaking changes to Screen Options.

Douglas’ issue –
12. I deactivated the plugin and was able to freely change Screen Options for editor2, editor3 and admin, so it works.
13. I registered new user called editor4. He had all the default WordPress Screen Options.

The plugin is not altering your WP Screen Options when turned off. There must be something else, maybe some other plugin is having problems. Typically when there is some broken JavaScript in the edit screen, the Screen Options editing for that screen might not work anymore. This plugin uses no JavaScript.

Carmen, I’m not sure what do you mean by “the clone was a permanent state with no role back”. The cloned Screen Options will remain in wp_usermeta after the plugin is deactivated, but they can be freely altered usign all the default WordPress Screen Options controls. We also hate when plugin leaves some irreversible changes. But the purpose of this plugin is

1. you build a new site, you want your users to see some nice pre-configured Screen Options right after logging in.
2. you want to adjust Screen Options for all of your existing users, because you know what you are doing, as that will remove their own custom Screen Options if they had any. If you want to apply your settings only for new users, there’s “Save for new users only” option when cloning.

Let us know what’s your opinion, as I think we aim for the same thing here – plugin which is simple to use, works with no extra installation steps and handles your WordPress without breaking any of the core processes or leaving some garbage.

Thanks,
Martin

Hello Jose,

check “Custom WYSIWYG CSS” text area in plugin Settings screen. We put a width 600px as a default, as that’s the common width of the content column. Adjust it for your liking, or remove it.

Read our Foliopress WYSIWYG Installation Guide for more information.

That will most likely be the cause to your issues.

Thanks,
Martin

Hello Will,

I checked the Ajax Comment Preview plugin and there’s nothing we can do about it, as the comment input textarea code is hardcoded in the plugin.

However, there are some other comment preview plugins that work with FV Antispam:

Live Comment Preview works, but you have to change the textarea ID in the live-comment-preview.php file on line 124. You can find out that the ID is by looking into the source code of the page with comment form on it. It will be an unique string of seemingly random numbers and letters like “a7391152e”, so use that.

jQuery Comment Preview is not so lightweight as the Live Comment Preview, but you can set the ID in options, so you don’t have to edit files.

Thanks,
Martin

Hello stwc,

I found the issue and worked on getting this fixed. The bugfix will be a part of next release of this plugin, version 0.3.

In the meantime, you can install our latest beta version: http://foliovision.com/downloads/thoughtful-comments-0.2.9.beta.zip

It has some other improvements, which might need a bit of fine tuning, so we will love to hear any suggestions.

Thank you again for reporting this!

Martin

Hi fusse,

big thanks you reporting this, the wp-content directory location can be changed using a constant: http://codex.wordpress.org/Editing_wp-config.php#Moving_wp-content

We will fix it in one of the next releases.

Martin

Hello Oliver,

thank you for the bug report, now the new version is released on WordPress.org.

Regards,
Martin

Hello Tracey,

I spoke to Alec a bit more about your issue.

We think that the Markdown plugin should be disabled by default and functional only if the post is marked as a Markdown post.

We can add a nice interface for this function, if you can provide a good tested piece of code which will disable the Markdown plugin when editing the post and also a piece of code which will disable it when displaying the post (so the Markdown won’t touch the normal HTML posts).

That way, your advanced users would be able to click a checkbox saying “this is a Markdown post” and our editor would not interfere with it.

Thanks,
Martin

Hello Balthazar,

it should work fine with the latest version which is 0.9.16. Have you cleared your browser cache after the update of XML? I guess that’s what I forgot to add into FAQ.

Thanks,
Martin

Hello Steve,

you need to check out open_basedir in your php.ini. More information here:

http://www.php.net/manual/en/ini.core.php#ini.open-basedir

Your host should be able to give you a hand with this. Generally, if you are not running some complicated website, you should not have this issue with Foliopress WYSIWYG.

Thanks,
Martin

Hello Jim,

the setting to convert caption shortcodes into HTML was added into Settings -> Foliopress WYSIWYG -> Advanced -> Compatibility Convert [caption] shortcodes before editing. It’s turned on by default.

Thanks,
Martin

Hello JJ,

no, it’s not like that. Users with author user role are not able to delete comments on any blog post via the front end with our plugin.

On the other hand, they are not able to do so even on their own posts, so that could be considered as a missing feature.

What other plugins are you using if you experienced the problem you describe?

Thank you for your input.
M.

Hello Jon,

you should be able to hook our editor somewhere the same way as FCK Editor. However it’s relying on WP options, so you will have to take care of that – I think playing with custom-config directory will get you the idea. Maybe it’s enough just to remove it from the fckeditor/ config files. For image management tool, which is based on KFM, you will have to configure your db in configuration.php somehow and maybe also remove some of the WP options.

Thanks,
M.

Hello Andy,

we found out that Dreamhost is escaping quotes (” “) in HTTP POST and that is destroying JSON in our Image Management Tool (even though magic quotes are off). Here’s a patch for current plugin version until we fix it in new version of plugin:

kaejax.php.txt

Just rename it to kaejax.php and copy it over the original file in wp-content/plugins/foliopress-wysiwyg/fckeditor/editor/plugins/kfm/includes/

Hello Sam,

a) & b) please read WYSIWYG installation guide here. I’m sure it will help you a lot. We want to make it easier, so we are open to suggestions.

b) You need to customize the dropdown manually. If you have and idea how to add all the styling automatically, we will love to hear about it. It would not be a problem to add it all there, but that’s not what you/we want. There’s a lot of styling in the style.css which isn’t applying to the actual text/html elements.

Thanks,
M.

Hello Cees,

the only change to the plugin is in the mailing library used, so it will work right after you upgrade the plugin.

Thanks,
M.