Stand-alone entry forms are great for allowing members to enter and edit entries from the front-end of your site.  however, they can also be used for collecting information from site visitors, such as feedback, suggestions, enquiries etc. 

unfortunately, the stand-alone entry form tag in the weblog module requires that the user is a logged in member, otherwise the form is not shown and cannot be submitted.  i have seen people use the freeforms module as a work-around, and although this is a reasonable solution, i was determined to do it with weblogs.

so i developed a plugin that allows you to automatically log a site visitor in from any template without having to collect details from them.  the idea is you set up a guest user account and assign it to any member group that has weblog posting priveleges to the weblog you want to submit the SAEF to.  in the template where your SAEF is, you just check if the user is logged in.  if not then you log them in automatically as the guest user.

you can find the plugin and more info here

Simple, effective… brilliant!

Cheers ben!

Hi Ben,

Sounds like simplicity itself!!
I needed this on a site I was building or at least I thought I did. In the end I went with having people register as I did want them to have to do so first although I can think of quite a few places where this will come in handy in the future. Fantastic addition.

Will try it out as soon as possible.

Best wishes,

Mark

This could be very handy…Thanks Ben

if anyone is wondering why the conditional if statement in the following code does not work, it is because plugins are processed before conditional statements in templates.

this means that the visitor is logged in as priveleged_guest even if they are already logged in.

i may add a parameter in the plugin to handle this problem, will let you know.

Hi Ben, the 1 day expiry set in the plugin doesn’t seem to be respected, it looks like once you are logged in it stays that way. exp_last_activity and exp_last_visit are being set 6 months in advance.

I’m just saying what I see, I don’t understand it :(

I’m using logmein to login a user called disclaimer who is in the members group. I also have a template with access restricted to another group called projects.

Problem is the disclaimer user (in the members group) can strangely access the the template that’s restricted to the projects group.

Hi there,

I don’t think that this has anything to do with the plugin here though unless you have the plugin code on the template that shouldn’t be accessible?

The fact that you have a user called disclaimer means nothing to this plugin. Instead the plugin is used to allow non-logged-in members (guests) to be able to post items but all get logged into the same member group set in the plugin variable username=“privileged-guest” so it will seem as though one person posted all the entries.

What code do you have on the template that is not supposed to be viewable by the disclaimer user?

Also this thread (depending on your answer) may need splitting off because if it isn’t the plugin that is causing this then this won’t be relevant here but we can get one of the admin to do that if that is so.

Best wishes,

Mark

Hi Mark, thanks for taking the time to reply, it’s much appreciated. The disclaimer user is in the members group and the plugin automatically logs this user in when they hit the page with the plugin code on - so the I think the user does mean something to the plugin. But your reply did help me understand my problem. I know it’s the wrong place, but could you give me any advice on how to setup a disclaimer from which people have to accept before getting access to content.

Thanks
Lee

Lee perhaps you could post this question into a new forum thread so that we don’t detract from the original one?

I will find that thread once you have posted and pop in there. Please re-explain the whole matter in the new thread though in case other people come across it too.

Thanks.

Mark

Hey!

I’m trying to use this plugin with the Simple Commerce plugin but can’t get the email templates to work after a purchase anyway. I added a user called “shop” in the Guests member group and gave that group access to the Simple Commerce plugin under “Module Access Privileges” as Ben wrote in the comments on his page.

I’m thinking that I might have to edit the mod.simple_commerce.php file to send the customer email to the address supplied by PayPal instead of getting it from the EE member database?

Anyone that have gotten LogMeIn to work with the Simple Commerce email templates?
Thanks!

Regards,
Christofer

Wonderful plugin, ben c! But how to defend from spammers? Any ideas about Captcha using?, but in standart SAEF captcha is absent.

Hey Ben,

Excellent plugin by the way, I am super glad you put this together as it has solved a major, and common issue with stand alone entry forms. That being said, we are having one issue. I am using the logmein plugin along with a stand alone entry form (obviously) and your image editor plugin to allow users to upload images along with a form. The issue I am seeing is if I log someone in automatically as a guest or member user group account they cannot upload images. I am positive the file upload preferences are correct, and all the information they enter in the form gets enter into the database, but the file does not get uploaded. Any Ideas?

I have been able to get it to work if I automatically sign the user in as a super admin, probably not most advisable, but it makes me think it is a permissions issue I am missing somewhere.

Thanks,

—Chris

Ben,

I’m wondering if this issue has been resolved? I’m anxious to use the plugin but if it logs every member in as a ‘guest’ then it can’t really work for me. Is there any way I could fix this myself with my minor understanding of php?

Thanks!

ben c - 23 November 2007 03:35 AM

if anyone is wondering why the conditional if statement in the following code does not work, it is because plugins are processed before conditional statements in templates.

{if member_id == "0"}
  {exp:logmein:now username="priveleged_guest"}
{/if}

this means that the visitor is logged in as priveleged_guest even if they are already logged in.

i may add a parameter in the plugin to handle this problem, will let you know.

Would an embedded template help?

then in the embedded template -