Forum Replies Created
-
-
Hi Mike,
Those are very good suggestions. Thank you very much.
I can certainly see how time entry fits in (right now we are using time entry in Freshbooks but we might switch over ourselves as we’ve just moved to an unlimited Freshbooks account which means we can integrate Basecamp and Freshbooks better: our team might work better if they don’t have to go into Freshbooks to manage their time). So we will definitely add the time entry option (probably a global preference so it’s not there for teams who don’t use Basecamp time tracking, with default to on).
Could you elaborate on how you’d like the Milestones features to work?
What would be different about an OS X desktop widget and just using a Fluid browser (what I do now)? What should the Desktop widget do different than the browser version?
Making the web work for you, Alec
Hi Sid,
That’s why no one in his or her right mind should use Yoast’s Plugin as you are making your site dependent on a plugin. Plugins should retire gracefully and use core WordPress tables as much as possible.
Turning FV Simpler SEO on and off will not damage your site, unlike most of the other WordPress SEO plugins out there.
—-
Hi Henry,
That sounds like a Pro Support Incident. Let us know if you’d like our help sorting out your site.
Making the web work for you, Alec
Hi Ralf,
We are currently working on multiple Basecamp accounts within AscentList (individual accounts) and then plan to move on to the Highrise integration.
We might reverse that order as middle sized and larger companies such as us basically have a Suite with integrated Highrise and Basecamp. Hence multiple Basecamp accounts are less important to us than integrating our single main Highrise account.
Thanks for your feedback!
Hi Matt,
The underlying code is FCK editor. If you look for information about custom buttons for FCK editor you should be able to find some documentation out there. Let us know if you find something really good.
Also be sure to read all you can in our documentation: http://foliovision.com/seo-tools/wordpress/plugins/wysiwyg/faq
Making the web work for you, Alec
Hi Matt,
The underlying code is FCK editor. If you look for information about custom buttons for FCK editor you should be able to find some documentation out there. Let us know if you find something really good.
Also be sure to read all you can in our documentation: http://foliovision.com/seo-tools/wordpress/plugins/wysiwyg/faq
Making the web work for you, Alec
HI Mohamed,
FV Simple SEO is entirely cross-compatible with all in one SEO. FV Simple SEO is simply more robust, less dangerous (code has been security checked by Mark Jacquith and does not have potential XSS exploits in it like all in one) and doesn’t include branding inside your source code.
Plus FV Simpler SEO looks better, is easier to use and has SERP preview.
Thanks.
Hi Matt,
We would be able to make buttons which interact with that GUI. For simpler short codes, we could also make a single button which offers multiple short codes.
Keep us posted.
Making the web work for you, Alec
Hi Matt,
Sorry I didn’t realise you had already donated. Thank you. We have to find some way to mark those who have donated here in our forum. Now that you remind me, I remember. We appreciate your support.
Let us know how you get on with creating new buttons yourself or if you require our help. If you do create some useful buttons (with matching icons please), please pass them on so we can add them to core for you.
Thanks.
Making the web work for you, Alec
PS. Martin are we still using this hosting for testing?
Hi Matt,
It’s pretty easy to create your own buttons. We have a YouTube button now which will allow you to insert shortcodes as well (you’d have to memorize them). You could also copy the YouTube button and create buttons of your own.
If you are using it enough to make a donation, we can create a couple of buttons for you ourselves.
Thanks for being part of Foliovision!
Making the web work for you, Alec
Hi Matt,
I’m sorry but it’s unlikely these buttons will work as TinyMCE is an entirely different codebase. We don’t like TinyMCE at all which is why we developed Foliopress WYSIWYG.
If you’d like us to look at a particular case, feel free to post a couple.
Thanks.
Making the web work for you, Alec
Hi TeckniX,
Thanks for stopping by and for sharing your concerns.
Could you give me an example of the kind of info you’d like to see?
I agree that there is an element of good faith involved. Foliovision is five years old (officially and another five years before that as a small web design agency). We are specialists in the real estate and insurance areas (i.e. finance) so we handle private data every day for clients even those who are in direct competition with one another. We take great care to protect their data and we take great care to protect your data.
Only the two programmers specifically working on AscentList have access to the server where we maintain AscentList. One of them has been with Foliovision for over four years and the other has been with Foliovision for more than two years. Peter is completing a Master’s degree in Higher Mathematics and previously did database work for the European Union. Zdenka has a PhD in video processing and also has impeccable references.
Here are what our clients say about us: http://foliovision.com/about/testimonials
We have a large office in the building next to the British Embassy in Bratislava.
Here’s what we look like: http://foliovision.com/about/bios
We do not look at the client accounts ever. If we have to test on an account, we have our own Basecamp account inside the same server.
Does any of the above help?
Making the web work for you, Alec
Hi Mohamed,
For keywords in our FV Simpler SEO, we simply use Tags. So any WordPress tag editor will solve your issues.
We’d like to add Tags though to FV Descriptions.
Good point.
Making the web work for you, Alec
Hi Aisak,
Sorry the code didn’t work for you. The issue is not with FV Simpler SEO but with your template.
If you’d like us to troubleshoot your template for you, please make a pro support request: http://foliovision.com/seo-tools/wordpress/pro-install
Thanks!
Hi Aisak,
There is probably something missing in your header template. Please open up /wp-content/themes/yourtheme and have a look in header.php
There should be something like:
// Add the blog description for the home/front page.
$site_description = get_bloginfo( 'description', 'display' );
if ( $site_description && ( is_home() || is_front_page() ) )
echo " | $site_description";If there isn’t it, try adding it. You could also try enabling the TwentyTen theme which has proper meta description support built-in, to test.
Making the web work for you, Alec
Hi Chris,
Thanks for letting us know Chris. We will fix this next week.
Let us know if you have any questions once you are on the other side.
Thanks!
Making the web work for you, Alec
Hi Chris!
Thanks for the detailed report. We will sort this on Monday at the latest.
Making the web work for you, Alec
Hi Chris,
When you sign up, we just need the address: ‘https://evergent.basecamphq.com/’
Let me know if that works for you.
Thanks for letting us know about your issue. We’ll add some URL stripping logic to the signup.
Making the web work for you, Alec
Hi Gant,
I’m very sorry but this is not happening unless you would like to us to code it custom for you (paid).
Thanks for using FV plugins.
Hi Linda,
That’s a great tip. Thanks for reporting it. We’ll look at trying to eliminate this bug.
We are always looking for ways to lighten the footprint of our software so that installing or removing it does not cause issues.
Please let us know if there is anything else you find which could be tweaked.
Making the web work for you, Alec
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.
JC, thanks for your post.
If no one can be bothered to give us a ready live environment in which to test for password protected videos on S3 nor to fund that development, we are not interested.
Foliovision does not exist to code for your company for free. We support our paying clients. We are kind enough to share the code we develop with the world as we believe in giving back to the open source world and not just taking.
You might consider that principle in your own relationship to open source.
PS. We also make substantial financial contributions every month to open source software projects we use.
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
Hi Zdenka,
I’d actually like to be able to incorporate the Flowplayer plugins.
Bruce, would you be able to donate something to FV Flowplayer if we add this code?
Making the web work for you, Alec
What would it cost to have you look after it instead?
Hi Michelle,
You don’t really need individual fields. You can add a class to title, the company and the name.
We’re considering adding additional fields but at the same time, we’re trying to keep FV Testimonials easy to use straight out of the box.
What the pro will do for you is give you multiple images and give you categories so you can show testimonials for individual services and products.
Making the web work for you, Alec
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!
We do NOT recommend using IE9 with Foliopress WYSIWYG at this point. There are serious enough issues that we’ve removed support for the browser until FCKeditor and CKeditor work properly in Microsoft’s browser.
Until that point, we cannot troubleshoot any issues with IE9.
Thanks everyone.
Making the web work for you, Alec
Check the release notes please.
Hi Doaadi,
Foliopress WYSIWYG is a business text editor designed to simplify and speed up posting for both prolific content sites and photographic sites, while maintaining best SEO practices.
It will be difficult to resolve the nesting tags issues as they are part of the core FCKeditor (they might be better in CKeditor and we are preparing the move to CKedtitor now, but probably not).
I have a lot of sympathy for those programming CKeditor on this issue. These editors are javascript so there are real limitations to what you can do. They do a great job in pushing those limits so far that we think we are working in a desktop application. But we aren’t.
The best thing you can do is create complex classes which you can use as pull downs.
Thanks for sharing your find.
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
Hi Sid,
We wouldn’t recommend using excerpts as metadescription as excerpts don’t exist for pages since about WordPress 2.2.
I’d recommend you use our FV Simpler SEO instead. You are a lot less likely to get into trouble than with Yoast’s everything but the kitchen sink SEO Plugin.
That said, FV Descriptions should work with Yoast’s plugin too.
Let us know how it works out.
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.
We should be compatible with Typepad Antispam. Antispam Bee and FV Antispam are mainly duplicate functionality.
We prefer FV Antispam of course but there’s lots to like about Antispam Bee.
I’d love to hear about your success with Typepad Antispam together with FV Antispam. Please let us know how it goes.
I agree that the license fees for Akismet are pretty stiff for those who decide to pay. We paid $800 this year and that’s too much for a single year.
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 Christine,
Glad we could help you.
It’s not really free. It costs me a ton of money every month.
If you have found FV Flowplayer and our help useful, there is a nice donation button right here: http://foliovision.com/seo-tools/wordpress/plugins/fv-wordpress-flowplayer
Making the web work for you, Alec
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,
That’s an interesting notion having a better visual selection when one clicks on an image. For the moment the focus is on the WYSIWYG part rather than on visual edit signals. But there’s no reason we couldn’t do that.
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 Jeff,
FV Anti Spam is a great plugin. We won’t run a website without it. Zero server load and complete protection.
And like all FV plugins, FV Antispam is set to intelligent defaults out of the box. No need to configure anything. It just works.
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 stwc,
We’d be happy to troubleshoot your install with you. I’ve sent you an email.
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 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 Will,
If the Ajax Comment Preview author Michael Adams (aka mdawaffe aka MDA) would like to work with us on making the two plugins compatible we would be happy to collaborate to make FV Antispam work with Ajax Comment Preview.
Hi Zdenka,
I’d like to enable this feature. It should be relatively straightforward for people with commercial licenses.
Thanks.
Hi Andrew,
Thanks for the tip about shortcodes. We should put something defensive in there. We’ll try to throw a visible error message if wp_head is not properly setup.
On the other hand, we will continue to anticipate wp_head and a footer file and the rest of the accoutrements of a properly configured theme file. Once one decides to support every possible mutilation of WordPress good coding practices, it’s a steep slope downhill to code spaghetti and total incompatibility for all of us between all plugins. I.e. welcome to Linux distribution fracturing.
Making the web work for you, Alec
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 the feedback Oliver. We use FV Gravatar Cache on a lot of our busy sites, so we’d like to keep it running smoothly. FV Gravatar Cache does speed load times considerably.
If you find the issue tomorrow, let us know and we’ll update the code right away.
Thanks for isolating that issue Oliver.
With what would you suggest we replace fopen for our gravatar checks?
Hello Tracey,
I disagree that a grammar checker is what Foliopress WYSIWYG needs. Machine grammar checkers do a less than stellar job. That’s what school if for (avoidance) and editors (cleanup).
Someone who really needs serious grammar checking should be using a dedicated writing application and just pasting into their web publishing platform.
We do not want to slow page loads or worsen performance. If anything we’d like to trim Foliopress WYSIWYG down further.
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 Zdenka,
Could we make this a little more automatic (on entering of a license key). Is there any particular reason that people need the absolute latest version?
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 Zdenka,
Thanks for letting Dave know. Adjusting play button size is not a priority feature. The current size works with most videos.
Hi Jurgen,
What would you suggest we should change for the new Google images?
Cheers, Alec
Pages and posts editing environment were our concern with this plugin.
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,
The reason the button doesn’t work in Firefox is that Mozilla does not allow javascript control of the clipboard. It’s a browser limitation. IE and Safari both allow this. I’m not sure about Opera offhand.
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 Joe,
The focus of Screen Options is not to take choice away from the end user but to give him/her a good default configuration.
We might add a preference to disable Screen Options for non-Admin users (we put clients at Editor level as a general rule).
Would you be able to donate to help us make this feature possible?
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 your kind words.
We are working on a one way converter of WordPress images into Foliopress WYSIWYG images on post open (it will be an option in preferences). We will set some intelligent defaults for converting Caption and the other attributes into static format. Once converted images will be straight html and easily managed. It should make people’s posts load more quickly with a lower server load as well (advanced aching can help even the current WordPress system though).
Let us know if you run into any other issues.
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).
Hi Stephanie,
You are facing an issue of colour profiles. I think you are on a Mac and what you are finding is that you are saving images out with their colour profiles. Foliopress WYSIWYG seems to be deleting the colour profiles.
Historically correct web behaviour was to strip out colour profiles (as most browsers don’t respect them).
We might try to add colour profiles to a future version of Foliopress WYSIWYG. In the meantime, make sure you are exporting to web WITHOUT colour profiles. Let me know how you get on.
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 Chris,
We designed Foliopress WYSIWYG to work only with the real html image links. Most of our Typepad to WordPress clients come over with the images already inside the html (we clean it up on the way to be better styled with our default lightbox styling, with some very fancy regex).
Our main commercial clients are usually starting not from WordPress.
But I see the issue. We’ll try and do something about the parsing to pick up the WordPress default images.
Thanks for bringing this to our attention. And thank you for the clear and detailed bug report.
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 Andy,
We have a Dreamhost account (mass storage, would never dream of using Dreamhost for a production site, nor Bluehost or any of the budget oversold hosts). We’ll give the latest Foliopress WYSIWYG a test again later this week (it’s worked on Dreamhost in the past).
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 Andy,
For the moment Foliopress WYSIWYG image management works with Firefox 2+, IE 6+, Camino 2+. The image management is not working with Safari or Chrome yet (we’re working on it). However the text editing features are working with both those browsers.
If you are still having trouble with your install, we’d be happy to troubleshoot your install. Having us do it for you is just $30 and we’ll have the work done within a day.
Thanks for stopping by.
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
Hi Eric,
Thanks for writing.
NextGen Gallery is one of the worst WordPress plugins around. We were called in to rescue a WordPress site falling apart under NGG. Our resuscitation attempt was successful but gave us a lifelong distaste for this convoluted and processor hungry code.
You can emulate most of the functionality with our SEO Images/Foliopress WYSIWYG just by putting the thumbnails in a single post (works conveniently up to about 20). You’ll get a lightbox slideshow. This gallery type post was created with Foliopress WYSIWYG: http://uncoy.com/2009/05/choreolab-09.html
We have no plans to support NextGen Gallery. If I were you, I’d avoid NGG altogether. Your site will run faster, smoother with less compatibility issues. It will also be far more future proof.
