Hello Rob,

what plugin are you using? This support forum is for FV Simpler SEO which has no field for custom SEO title for categories.

Thanks,
Martin

Hello Linda,

I guess you are using some special template which shows all the custom post meta values. We didn’t counted on this, but we can fix this in the next release.

Our custom meta value is not showing in the “Custom Fields” editing box when you edit a post, because it’s an Array, so at least that part works ok.

Thanks,
Martin

Hi Mr Duong,

if that worked it was just a side effect. I was not our goal with this plugin.

WordPress 3.3 includes some changes in how the rewrite rules are generated for categories and pages, so putting in support for /subcategory URLs would be tricky, as it would have to check for the pages on the same URL.

If you use hierarchical categories and then you want all the URLs on the same level, I would suggest that you make all the categories master categories and then organize them into structure in the WordPress menu. You can build any structure there and not worry about the actual structure of your categories.

Thanks,
Martin

Hello Teresa,

if you are using Mac computer and you don’t have the right mouse button, you need to hold the Control or “ctrl” key and click the image to see the available options (same as any other contextual menu on Mac).

Then pick the desired image size with just the mouse click – don’t hold the Control key.

Thanks,
Martin

Hello Rob,

are you still having these issues? When I open your site I can see “Web Designers (1)” with one link in it.

Thanks,
Martin

Hello jagdynamics,

Foliopress WYSIWYG works only for posts, pages and derived custom post types.

Sorry, it does not work for comment fields.

What exactly do you mean by topic description? Sounds like you expect our plugin to be compatible with some other plugin you are using.

We are currently providing no general hook for our editor which would allow it to work on any text input field of any plugin. The main plugin object has fv_wysiwyg_load() function which replaces the post editing textarea with id ‘content’, so that part would have to be rewritten. If you know a bit of programming, you can probably figure it out – we will be happy to include your improvements.

If this functionality is very important for your work and you are able to make a donation as either individual or group, we could be persuaded to accelerate the development for this feature.

We prefer our comment and other forms plain text.

Thanks,
Martin

Hello David,

Can you try to go into Settings -> Permalinks and hit “Save Changes”? That should reset the WordPress rewrite rules. Let us know if that helps please.

Otherwise you can remove the plugin and install previous version 1.1.3 from a zip file here:
http://wordpress.org/extend/plugins/fv-top-level-cats/download/

However the previous version won’t work in WordPress 3.3.

Thanks,
Martin

Hello Jonathan,

we will have a look into this in our own WP Multisite and let you know if it’s just you, or there is some issue between our plugin and WP Multisite.

Thanks,
Martin

Also, if you try to open a link like ‘http://blog.com/child-category’ and the correct link is ‘http://blog.com/parent-category/child-category’ – then the WordPress will try to redirect you to some post or page I think which has similar slug. So that would be the reason to the weird redirection issue you are seeing.

Thanks,
Martin

Hello Ken,

thank you for your report, highly appreciated!

The new version of the plugin should be released tomorrow.

Martin

Hello Matt,

we are not using your test environment anymore. We only used it when we were fixing the issues you reported.

Thank you for your contribution and cooperation.

Martin

Hello Aisak,

you should look at 3 random articles you wrote and check the <meta name=”description”> tags in their source code. It should contain the correct meta description as entered with FV Simpler SEO.

If it does not, then it could be a problem with your theme or a conflict with some other plugin.

Thanks,
Martin

Hello walt,

could you please try our development version?

It’s here:
http://foliovision.com/downloads/fv-top-level-cats-dev.zip

Please let us know if that solved your issue. Think of it as of a contribution to open source development – we didn’t had time to fully test it yet, so any help is welcome.

Thanks,
Martin

Hi Bryan,

just one more thing – if you want to use normal WordPress Media Library, you can – just turn on Settings -> Foliopress WYSIWYG -> Enable WordPress uploader buttons.

Thanks,
Martin

Hello hittheroadjack,

the main plugin object has fv_wysiwyg_load() function which basically does what you want. However it’s fixed to textarea with id ‘content’.

Then it would also require the main editor JS to be loaded, just like in FckLoadAdminHead().

So if you know a bit of programming, you can probably figure it out – we will be happy to include your improvements.

If this functionality is very important for your work and you are able to make a donation as either individual or group, we could be persuaded to accelerate the development for this feature.

We prefer our contact forms plain text.

Thanks,
Martin

Hello Randy,

I did a quick test with WP Security Scan, but I haven’t noticed any issues.

However, I cleared up the warnings which show up when WP debug is ON, so maybe that will help you.

The new version was released just now.

Thanks,
Martin

Hello CJ,

this is actually in WP Dashboard -> Settings -> Discussion as “Enable threaded (nested) comments”:
http://codex.wordpress.org/Settings_Discussion_Screen

Our plugin is great for moderating larger discussions where you need to see the comments in context, rather than seeing them all sorted by time regardless of to which article they belong. We don’t redo this basic WordPress functionality, we just extend the moderation interface to the front-end.

Thanks,
Martin

Hello Pontus,

Foliopress WYSIWYG 0.9.20 is out. It doesn’t have the IE9 fix yet, but it has the Youtube button, which can be used for pasting of any Embed code and also any HTML code, so it comes handy.

Regarding the IE9 issues – we discovered that when you switch IE9 to IE8 mode, it works with our editor. We suggest this in our compatibility warning message when editing. Hopefully it will work at least for the more advanced users.

Thanks,
Martin

Hello Pontus,

I’m sorry about the delay, we are having a longer debate about this issue (and possible fixes) right at this moment.

Thanks,
Martin

Hello Veaceslav,

first of all, thank you for your interest in our plugin.

I believe this works properly in our plugin. WordPress always picks the category with the lowest ID for the permalink, if you use structure like /%category%/%postname%.html

So if you have parent and child category and you assign post to both, it will end up as /parent/postname.html if you assign only child category, it will be /parent/child/postname.html

If you are aware of this, then the issue must be somewhere else, perhaps some conflict with another plugin. Can you try to disable all the plugins and switch to default template and do the testing again?

There is a new version coming, which is in the final test stages:
http://foliovision.com/support/fv-top-level-categories/bug-reports/category-feed-404-error?replies=9#post-604

Martin

Hello Jelenko,

thank you very much for a nice bug report.

It looks like some of the PHP warnings might be damaging the JavaScript code present in the window. We check our error logs on our sites to make sure our plugins are not filling them with errors, but we haven’t seen these before.

Could you try to save the plugin options in WP Admin -> Settings -> Foliopress WYSIWYG to see if it works afterwards? The options are initialized properly together with the plugin, but there might be a glitch in that.

We will test your issues and see if we can get to the same error. We also prepare some performance tweaks for the new version.

Thank you,
Martin

Hello Rachelle, Randall and Ricardo!

Here’s the new beta version:
http://foliovision.com/downloads/fv-top-level-cats-dev.zip

It will fix your issues.

We preserved all the standard category URLs but (same as the older versions), if there’s a page with same URL as category, we show this page instead of the category.

Please let us know if it works for you. We are putting it on some of our sites too, once we have tested it for a while and once we hear back from you, we can put it on WordPress.org.

Thanks,
Martin

The fix has been included in 0.9.19.7.

Thank you for your contribution and report!

Martin

Hello Ken,

we might give this a try next week if we have any time left in our schedule.

Thanks,
Martin

Hello Daren,

Foliopress WYSIWYG is using your theme CSS if you specify the wrapper ID or class element. We describe the whole configuration process here:
http://foliovision.com/seo-tools/wordpress/plugins/wysiwyg/installation#wysiwyg

You might need to adjust the styling for the tables, just like in step 6.: “If some HTML element (for example headers) are missing the styling”

We also want to add support for the editor CSS which comes with new WordPress templates, so this will be easier in future.

Thanks,
Martin

Hello seoweb!

So your site has a lot of pages with URLs ragiong from http://example.com/page/2 up to http://example.com/page/200 and titles ranging from “Example blog – Part 2” to “Example blog – Part 200”, is that right?

And Google Webmaster tools or similar SEO utility is saying that you have too many similar titles? We suggest that you ignore warnings like this, just changing these titles by inserting some random text as you suggest would remove the warnings, but it makes no sense.

The issue here is that your blog has a lot of URLs which have /page/ in them, so that might lead search engines to assume that “page” is one of your keywords. We try to eliminate these issues on our some of our WP sites which are not really blogs by not providing the paging feature on the homepage and instead featuring the site content in few content boxes on the homepage. Each of these boxes might list one of the main categories and then link to archive for that category.

Thanks,
Martin

Hello slingr,

last time we looked there were only next and previous buttons available for Flowplayer. There appear to be some good options now.

If you would like to implement this code in FV Flowplayer, we would be happy to integrate it in core of our plugin:
http://flash.flowplayer.org/plugins/javascript/playlist.html
http://flash.flowplayer.org/demos/plugins/javascript/playlist/scrollable.html

Thanks,
Martin

Hello Darian!

We did a major rewrite of this plugin for better WordPress integration and compatibility. We fixed the basics first, so we will need to put this functionality back, as it was in the old version. Stay tuned for future version upgrades.

Thanks,
Martin

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