Hello stwc,

I revised the code and tested activation on WordPress 3.0.4 multisite on localhost and one of our Cpanel hosts.

Please download the zipfile again and let us know if it works this time.

Thanks,
Martin

Hello Brett,

sorry for not responding earlier.

Yes, we want to improve this plugin to work with titles and so on.

The function to copy the WordPress title into the SEO Title field could go into our FV All in One SEO Pack plugin.

Thanks,
Martin

Hello stwc,

we are glad that you like our plugin.

I’ll look into the issues you outlined.

Thanks,
Martin

Hello Ivan,

you need to put ‘foliopress-next’ into your custom toolbar. I guess you added ‘PageBreak’, but that’s not the correct command.

Thank you for reporting this, I’ll remove PageBreak from the installation guide and add the correct command.

Let us know how it goes, it works perfectly on our site.

Martin

Hi Oliver,

My default (empty) gravatars are all loaded from gravatar.com and your plugin creates files for them. Then your plugin checks for a 404, but the file exists (13 byte).

I’m sending you a tweaked main PHP file of the plugin. Can you test it to see if it solves the problem?

I basically added another check for the 404. But I’m not sure if it will solve your problem. Can you provide the email address of some comment which has this bad 404 13B gravatar so I can see it? Or send me one of these 13B files?

I have tried it on two different servers now and on one it works properly so it won’t actually create empty gravatar files for people without gravatars. On the other it creates a gravatar (empty 13 bytes file) for all comments for some reason.

I suppose it’s because I disabled fopen on one server and it checks via fopen if it’s a default avatar (compare line 437) Since fopen is a major security risk I would have to rewrite this check.

That’s a different part of code and has nothing to do with the default gravatars. But if you disabled the fopen function, that might be the reason why none of the gravatars are cached properly. The files are probably containing only some warning instead of the content. Can you check it out?

Anyway, fopen is a standard function and is required to write the cached gravatar files. The more dangerous function is the remote fopen, but we are not using that. Have you any suggestion what we should be using instead of fopen and fwrite to write the cached files?

Can you check if there are any warnings on plugin settings page? It should be wp-admin/options-general.php?page=fv-gravatar-cache on your site. It checks if the directory is writable. If you disabled just the writing permissions, it should display a warning.

If you just disabled the fopen and fwrite functions, the plugin just can’t work, unless there is any other safer function which you think is better and we could use it.

Thanks, Martin

Hello Balthazar,

that’s because it’s JavaScript. Firefox seems to cache JavaScript a lot, so when you do changes to some files, it needs to be cleared.

Thanks,
Martin

Hello Laura,

looks like there is something wrong with your wp-config.php file – a whitespace character on line 155.

Here’s a guide how to solve this: http://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F

Please let us know how it went.

Thanks,
Martin

Hello Andy,

actually our plugin is cloning the dashboard settings too. I added a FAQ section with list of what’s cloned.

If you are missing some widgets on dashboard as a contributor, I would guess that the appear only to higher level users.

Thanks,
Martin

Hello JJ,

we just released a new version of the plugin which allows authors to manage comment bellow their own articles. You can simply upgrade the plugin in wp-admin menus.

It uses the same checking mechanism as WordPress – current_user_can(‘edit_post’, $post->ID) (which by the way doesn’t sound so good, but that’s how is WordPress checking the permissions for comment moderation in wp-admin section).

Thanks,
M.

Hello Luca,

what you want to do is to create some classes with different font faces (if you know a bit of CSS you won’t have any problem with this) and then add it into the Custom Dropdown. More on this topic in Installation guide

Thanks,
Martin

Hello Bodhi,

You should be setting up the CSS in the back end and in the front end so that your users neither need nor want to mess around with double carriage returns.

If you want to have more white space between paragraphs you should put something like this into your CSS:
#entry p { padding-bottom: 10px; }

If your webpage shows correctly and the problem is just in the editor, make sure you have WYSIWYG mode properly configured using this guide. If there’s some problem with the display even in the WYSIWYG mode, you can enter the above CSS into Custom WYSIWYG CSS in plugin options.

Of course you might want to play with the exact padding value and you must enter the right CSS selector, #entry should work with most templates.

If you really can’t live without extra carriage return, you can use Shift + Enter at the end of paragraph.

If you really need these empty paragraphs, you can just replace line 39 in foliopress-wysiwyg/fckeditor/editor/plugins/foliopress-clean/fckplugin.js with this:

//strChange = strChange.replace (“<p> </p>”,””); // disabled to allow empty paragraphs

But you have to be careful to do the fix again after each plugin upgrade then.

We really recommend you to go the clean CSS way.

Thanks,
M.

Hello Teros,

we don’t like using font and font colors as it puts a ugly inline CSS. Instead we added a customizable drop-down menu to the latest version which you can download here.

We recommend you adding some classes for different fonts and fontsizes in your CSS and then just to add it to the dropdown.

If you are not ok with that, you can still just customize the toolbar and add all the default buttons to it.

All of that can be done within the plugin options page & CSS customization, all the info you need is here: http://foliovision.com/seo-tools/wordpress/plugins/wysiwyg/installation

Thanks,
M.

Hi Simon,

I checked on the Mailpress issue and it’s really not working. However we want to make it compatible in one of the next versions.

We tested the Insert media button extensively and it’s working. Are you seeing any JavaScript errors in your Firefox? Can you create a test editor account on your site for me to see the problem?

Thanks,
M.