nzde

Hi Bradvin. I’d love to test the latest beta version please. I’ve sent you an email at your gmail account.

Many thanks
Richard

Awesome. Thank you.

Hi Bradvin – Hope you don’t mind me asking, but how are things going with the new release? Just wondering as I’d prefer to wait for your add-on for a site I’m building; will be preferable to throwing a heap of hacks into functions.php

Many thanks
Richard

Excellent news. Thanks Bradvin. I think 1 and 2 are the best. At this point, I’ll take whatever I can get, with gratitude a plenty.

If you need a beta tester, please let me know.

Thanks
Richard

Hi Bradvin

With GF 1.6 just round the corner, I was wondering whether you’re still planning on building in support for user defined taxonomies? If so, it’ll be the best thing since sliced bread.

Thanks so much for this plugin. It takes GF an extra mile.

Cheers
Richard

I’m keen to be able to use a custom field to denote a boilerplate item’s source. DO you think this would be simple to add?

Many thanks
Richard

Hi – The plugin works but your site, to which apparently users can go to for help with security risks, is down/has been compromised…

The only plugin I’m aware of right now with which one can do this well is the Wishlist Member plugin. You can set up various types of membership levels, given them access to a posting form thanks to the Gravity Forms plugin, and then downgrade their access to the posting form after a defined period using the sequential upgrade (downgrade in this case) feature in the Wishlist Member plugin.

R.

Great, thanks Scribu.

As to (2), I don’t achieve it with the regular WordPress editor. This is for a set-up that uses Gravity Forms to create posts from the front-end. The answers to the form questions then determine what will be sent to the post body and that is determined by a filter in the functions.php file. So, the complex numbering etc is brought into the post directly from the functions.php file using the Gravity Forms hooks.

Do you think a tweek to the FEE visual editor could accommodate what I’m after in my question (2) above?

The beauty of using Gravity Forms in conjunction with your Front End Editor is that it can allow full posting (GF) and editing of posts (FEE) from the front end, the advantages of which are probably obvious. The only sticking point I’m facing is the FEE visual editor stripping out the para and break tags. I appreciate that the WordPress editor does the same but hope we can come up with a workaround for the FEE visual editor.

Thanks again.
Richard

Ah, many thanks Scribu. Sorry for the slowness on my part; I hadn’t fully grasped those hook changes.

Hi again Scribu

Can I just check please if the code above, which allows one to limit the FEE to selected categories, is still working in the latest release of FEE? I ask because I’m using it but without success.

The code I’m using is this:

<?php

add_filter('front_ed_allow_post', 'restrict_to_category', 10, 2);
function restrict_to_category($allow, $post_id) {
	$allowed_cats = array('Templates', 'Website terms of use');
	return $allow && in_category($allowed_cats, $post_id);
}

?>

The theme I’m using is quite complex and has a functions.php file which pulls in a number of functions files from a functions library. The calling code I’m using in the main functions.php file, which follows the same model as for other functions it’s pulling in, is as follows:

// Load Front End Editor functions
require_once(WEBTREATS_FUNCTIONS . '/front-page-editor-functions.php');

Do you have any idea please why the code you’ve provided might not be working?

Any help much appreciated.

Richard

The best plugin to do that is Gravity Forms.

Hi Scribu

I’m wondering whether you’d be interested in developing the FEE for me please, for a fee of course.

If possible, I’m after two things please:

(1) I’d love to have the ability to select, from the admin backend, for which categories the FEE will work (in other words, I want it to be available for some categories, but not others).

(2) I’d also love it if the visual editor could be configured, perhaps by an option in the backend, not to strip out paragraph and break tags, even if (dare I say it) they appear nested within list tags. I know I might be suggesting heresy on this one, but my use would really benefit from this, because the posts I’d like to be editable contain complex autonumbering, with a series of nested ordered lists, where the only solution I can find to make it all work visually is to use <p> and <br /> tags within list items.

If you’d prefer to touch base directly with me about this, my email address is [email protected]

Many thanks Scribu
Richard

Hi again Scribu. Further to my two posts above, I see from my trusty HTML bible that <br /> can be used within other elements such as list items. That being so, if I replace all my para tags with the appropriate number of <br /> tags, and use your latest dev version of FEE, all should be working perfectly. That being so, I’d be really grateful if you could consider what seems to be a bug with the dev version please. In the meantime, I’ve gone back to the latest stable release, which is still stripping out the <br /> tags when saving.

Cheers
Richard

Hi Scribu – I’ve tried the dev version on www.ads-software.com but now I’m afraid the highlighted and seemingly editable post areas are not editable, i.e., when I double click on the area the edit screen does not come up. Any help much appreciated.