Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Pre-Release Channel Feedback: Front End Event Submission | Event Espresso - Staging Server

Support

Home Forums Pre-Releases Pre-Release Channel Feedback: Front End Event Submission

Pre-Release Channel Feedback: Front End Event Submission

Posted: December 25, 2013 at 3:42 am

Viewing 10 reply threads


Tim

December 25, 2013 at 3:42 am

I, like many users, are very interested in the ability to submit events from the Front-End. I am testing the P/R of the Front-End Plugin which blends well and is very useful.

Not sure where to write feedback so I’m putting it here.

I’d hoped that the Front-End plugin would have an option that would NOT require users to login to create an event. That the ability to add recaptcha or another spam test would prevent false submissions – and/or – only post the events once admin approved ie. email to adminstrators a new event is submitted – approve/disapprove.

My rationale being that I don’t open my website to registration for one. Second, my website is read by alot of elderly people, and their limited knowledge of registration, makes their requirement to submit events very challenging.

Please consider it for a future release, the ability to submit front-end events WITHOUT registration becuase no doubt I could convince others to buy the EE suite for their events if they could submit their own events.

Thanks for reading
Tim
http://www.nmracanada.ca / http://www.medicshelp.org


Josh

December 26, 2013 at 10:30 am

Hi Tim,

Thanks for taking the time to leave this valuable feedback. I’ve registered your suggestions that you gave here and we will keep them in mind for future features and updates!


Tim

January 2, 2014 at 3:05 pm

Josh,

Will EE consider dropping the front end EVENT SUBMITER user level from ADMINISTRATOR to CONTRIBUTOR/AUTHOUR/EDITOR?

We’ve already ran into one or two roadblocks with this addon. It doesn’t make any logical sense that we can consider having anything higher than CONTRIBUTOR, since most of our Front-End users are basic level members who will submit the odd event here or there.

Thanks
Tim


Anonymous

January 3, 2014 at 6:13 am

Hi Tim,

Currently the Front End Manager just checks if a user is logged in or not, UNLESS you are using the Role & Permissions Pro Add-on which allows you to set the user level required.

I’ve just ran through creating multiple events using a Subscriber account on a test site and found no issues.

Are you having issues with other accounts?


Tim

January 3, 2014 at 7:06 am

Pardon me, you are appear correct. My mistake. I’m not sure why I had such an issue, perhaps my browser cookies.

(bug) The REGISTRATION LIMIT box is painfully large and doesn’t size the entry window.

Will it be possible to have additional boxes where the user submit other information such as ticket price/url/location/etc or is part of another plugin?

Sorry for asking for so much upfront, but my intent is to sell the idea of the whole EE suite to a bunch of old fogies for their model railroading events since none of them are computer literate.


Anonymous

January 6, 2014 at 12:46 am

(bug) The REGISTRATION LIMIT box is painfully large and doesn’t size the entry window.

I can’t see an issue with the registration limit box on my test site, could you link us to a page in which we can see it or if not possibly a screenshot?

Will it be possible to have additional boxes where the user submit other information such as ticket price/url/location/etc or is part of another plugin?

If you go to Event Espresso -> Template Settings. In there you’ll now find ‘Front-end Event Manager’ settings (http://d.pr/i/W1Zl).

Those are currently the only options available for FEM. Adding extra fields is likely possible but would require some custom development.


Tim

January 6, 2014 at 12:08 pm

Have a look at this link for the registration size box.
http://nmracanada.ca/wp-content/uploads/2014/01/front-end-registration-limit-box-size.jpg

Even with the calendar on a full sized template, it is ill-sized.


Tim

January 6, 2014 at 12:12 pm

Thank you, changing those settings are idea.
Sorry I dont’ know notice them before.


Anonymous

January 7, 2014 at 2:29 am

No need to apologize :)

Re. Registration limit field.
This is likely just some CSS styling. Unfortunately I do not have the same issue so without viewing the code it will be hard to fix.

Can you link to a page with FEM active so I can see the code please?


Tim

January 7, 2014 at 10:03 am

Not sure what you are asking but built a temp login
http://nmracanada.ca/event-calendar/


Anonymous

January 7, 2014 at 10:22 am

Sorry, my fault for using abbreviations.

FEM = Front End Manager.

Do you have a page setup with FEM already in use that I can view?

I’ve removed the log in details from the forum, although we can still view them currently.


Tim

January 7, 2014 at 10:29 am

Hi Tony:
Thanks – yes FEM is at the bottom of that page. http://nmracanada.ca/event-calendar/
But since there is no recaptcha option to block the spam that was being received, you’ll need those credentials to login.


Anonymous

January 7, 2014 at 10:50 am

Sorry, I see now.

The issue is caused by the sites theme. Within the themes .css file is this rule:

#content-container input[type="text"] {
margin: 0 10px 10px 0;
width: 300px;
}

which sets the width of all text inputs within #content-container to 300px.

You have a few options. You can either remove that rule from the .css file. Although it may be there for another reason (this would be preferred but depends on the use case).

Make the rule more specific for its use case by adding more specific selectors.

Override that rule for FEM using:

#ee_fem_form input[type="text"] {
width: auto;
}

with a plugin such as My Custom CSS


Tim

January 10, 2014 at 9:10 pm

Thanks Tony. Sorry for the delay. That CSS did resolve it.
#ee_fem_form input[type=”text”] {width: auto;}

Viewing 10 reply threads

The support post ‘Pre-Release Channel Feedback: Front End Event Submission’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server