Hi Maurizio,

I’m sorry that we haven’t answered this yet. We haven’t noticed any issues with WP Super Cache (we run it on all our own and all our client sites).

Did you ever figure out the issue?

Let me know.

Thanks.

Hi JC,

If someone needs the feature enough, feel free to give us access to troubleshoot it in a live environment. We are not a free testing laboratory.

You want features, you give us a hand.

Glad you are paying JW for their player. It’s also very good and they deserve the money. Sorry we couldn’t subsidise your business more.

Making the web work for you, Alec

What would it cost to have you look after it instead?

Hi Roscoe,

All h.264 video is not created equal. Our plugin supports h.264 MP4 but sometimes there can be issues with the encoding (also depends on platform/browser). If you want to get your video online quickly, re-encode as Martin suggests.

Thanks for trying FV software!

Check the release notes please.

Hi Anadi,

You shouldn’t be putting so many elements on a single piece of text in the first place.

If you have some complex formatting you use often, it should be a CSS style which you pull from the drop down menu.

Not only that but using underlining on the web is extremely bad practice as underlining is assigned to hyperlinks.

We do our best to provide the best possible WYSIWYG editing environment but if you bang your head against the wall hard enough, you are sure to draw blood and/or fade into unconsciousness. No helmet will protect you.

Making the web work for you, Alec

Hello Amanda,

We have no particular desire to make Foliopress WYSIWYG work with live PHP in the posts. Putting live PHP in posts is a huge security risk and defeats the purpose of a templated CMS. Use John Godley’s Sniplets if you must put PHP in your posts.

Thanks for using Foliopress WYSIWYG.

Hi Valerie,

We often think about adding an add your own testimonial form (with picture).

Thanks for the suggestion.

Zdenka, let’s try to add this to at least the pro version sometime soon. We can use the built-in WordPress text parsing for comments and just need an image uploader. Of course the image uploader is a security issue but I think we have one now which is safe (i.e. disallows anything other than images and won’t allow execution of the files until they are vetted: it should also not let the visitor know where the files are going – when approved the image should be moved to a different directory).

Hi Nick,

You should be able to change those levels quite easily in the PHP code. If there is a lot of demand for this feature, we could make it a selectionable option.

Thanks.

Hi Heliogabal,

We’re not keen to see two large javacript containers on the same page ourselves. So we are not rushing to add two instance support.

If two WYSIWYG containers are very important to your work and you are able to make a substantial donation as either individual or group, we could be persuaded to accelerate the development of multiple instances.

Personally, I’d make one container WYSIWYG and the other plain text html.

Thanks for using FV plugins!

Hi Stéphane,

There’s no reason that FV Antispam won’t work for you. FV Antispam is a much better solution for your server than WP Spam Free (which we used but actually got a couple of clients booted off shared hosting for server load).

You’ll want an active Akismet key for FV Antispam to be most effective. FV Antispam takes care of all the machine spam but to handle human spam we rely on Akismet (horses for courses).

Let us know how you get on.

Paid hands on support is available for all our plugins if you find you’d like a hand with your install or tweaking performance.

Hi Jonathan,

You should upgrade your Authors to Editors if you’d like them to be able to edit comments on other posts. Otherwise get in touch with us and we can make a custom mod to enable this for you at a special rate.

For part two, you will have to dig into the source code and program that yourself. You are firmly in the arena of custom development there.

Thanks for stopping by.

Very glad you like Thoughtful Comments. To my mind, Thoughtful Comments may be the most important WordPress plugin out there, at least on the sites we maintain.

Hi Zdenka,

I’d like to enable this feature. It should be relatively straightforward for people with commercial licenses.

Thanks.

Hi Oliver,

You’re welcome.

A donation would be much appreciated.

Thanks for taking the time to write to us about this issue and look into it with us.

Making the web work for you, Alec

Thanks for isolating that issue Oliver.

With what would you suggest we replace fopen for our gravatar checks?

Hi Tracey,

That looks like a good solution. Let us know how it goes. Markdown on Save may work out of the box without any changes.

Hi Tracey,

With editors, you have to make a choice. Either WYISWYG/html or Markdown or Textile.

The issue is with your Markdown plugin. You have to make your Markdown plugin read html and convert it back to Markdown. When Markdown saves a post it needs to convert it to html.

I.e. to use Markdown or Textile, the alternative language has to include a reliable two-way converter. That way the posts are always saved in a single language (html) which is easily converted back and forth.

Let me know if you have any luck with this. I’d like to have html/textile markup compatibility myself.

But even as a inveterate textile writer, I have no problems using Foliopress WYSIWYG as all the core textile functions (numbered and unnumbered lists) are right there in the menu bar as buttons. Much easier for a textile or markdown user to use the WYSIWYG than for the non-technical writers to try to write in special markup.

Those are the kind of usability sacrifices the technical writers have to make on shared sites. Comes with the territory.

Hi Jurgen,

What would you suggest we should change for the new Google images?

Cheers, Alec

Hi Andy,

We aren’t cloning the dashboard at this point. We’ll keep these changes in mind for a future update. Thanks for the suggestion.

If you’d like to accelerate development of these features, feel free to contribute to the project.

Hi Red,

White sizing handles are a very big mistake. When you resize in the post it means your image is being resized by the browser.

That means longer download times (sizing an image down) or distorted ugly images (upsizing an image).

With Foliopress WYSIWYG you right click and choose the right size for your needs in that particular post. At that point Foliopress WYSIWYG creates a smaller version exactly that size. Presto: good looking images and fast downloads.

Hi Brian,

Much as we would like our Foliopress WYSIWYG editor and our SEO Images file manager to work on the iPad, it’s not likely to happen on the current version as they are both very javascript dependent and the version of Safari running on the iPad is not fully compatible with normal Safari.

We suggest using a dedicated WordPress posting app on an iPad and then coming back to add the images later from a desktop computer. Manipulating images on an iPad is a pain in the neck anyway.

Due to content production issues on the iPad, I’ve chosen to go with a powerful netbook instead (11″ screen, Core 2 Duo 1.2 GHz processors).

We don’t have a recommended WordPress posting app for the iPad yet. If you could look around and let us know which one we should recommend that would be great.

Foliopress WYSIWYG should be fully compatible with a posting app as we include the full html in our code. We are also working to automatically convert entries posted with the outmoded and cumbersome WP AutoP missing paragraph tags.

Hi Jim,

Thanks for the tips about our listing in the WordPress plugin database.

We do have an issue with captions as our solution is predicated on being compatible with all CMS not just WordPress. After you’ve published a photo with Foliopress WYSIWYG, you just have When you’ve added images with our plugin you can switch to another CMS with no loss, unlike WordPress’s built-in solution with it’s custom short tags.

Perhaps we can add a converter when opening posts but it will not be two way, it will be one way.

WordPress’s whole way of handling images is very database intensive, clunky and not portable (every included image or attachment is eleven database calls). Our way of handling images means that there are no database calls, even if you add twenty images to a single post. Plus our handling of SEO is much more complete (just name your image properly before you upload it).

BTW, I’d recommend going forward your client use our image management. It’s much stronger for SEO and is far more resilient if s/he ever decided to change platforms. But we should still have legacy compatibility.

Hi Alan,

NextGen Gallery is awful. In SEO terms, NGG is a disaster. The code inside is a real mess as well. No better way to slow down a WordPress install. You can build much more attractive galleries inside Foliopress WYSIWYG which work with Lightbox and virtually no server overhead (flat files served with the lightbox javascript executed locally on the visitor’s computer).

You could have saved a lot of your valuable time by sending us the $30 to fix your site and supported Open Source software while you were at it. We send OSS companies and programmers money all the time to make fixes in their software or just because we like the software. Sent $300 to the creator of WP Super Cache this month. Sent $10 yesterday to the guy who writes SiteSucker and we don’t even use SiteSucker much. If we start to use it some more, we’ll donate again.

In any case, thanks for the report on HostEurope.

Hi Alan,

Actually it would cost you $30, as we’d fix one of your sites and let you know what the issue is and you could repair your installs on the other two sites yourself.

Foliopress WYSIWYG is the best SEO friendly WYSIWYG on any platform and it’s free. Sorry that’s not enough for you.

If your time doesn’t have any value, that’s your problem. Ours does.

In any case, if you’re using NextGen gallery, there’s not much we can do to help you as your WordPress site will always be broken as long as NextGen gallery is running.

Hi Joseph,

The way I solve this issue (huge image uploads), is to put selects (up to 20) inside WordPress with Foliopress WYSIWYG/SEO Images and then link out to a Smugmug gallery for 100 images (in the case I need it).

Smugmug is set up for all the heavy lifting including selling images and it keeps WordPress lean.

It’s very rare that one would have more than 10 must see photos of any given event.

Just be more selective. Your readers will thank you.

PS. If you decide to sign up for Smugmug you can save $5 with this code: mIQp9QbUmqWu6