You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Announcements" custom post type and user submission
"Events" post type, powered by The Events Calendar
forms by Gravity Forms
Display page
Display sidebar area
Pieces that don't:
"Events" user submission, by logged-out users
-- specifically, events submitted by logged-out users do not save the Organizer, Venue or the categories assigned to the event. (All these things work fine if you're logged in.)
-- If I'm reading the Gravity Forms logs correctly, all the information is being sent as expected regardless of your login status. So the dropping of the infos is happening from the Events Calendar plugin side.
Possible solutions:
1 - fix user submission for Events (time: unknown given struggles so far)
Is there a possible solution that I haven't found yet? Things I have tried:
-- giving tribe_venue and tribe_organizer different post type settings for capability_type and public, to match other posts and tribe_event where logged-out submissions did seem to work. This did not seem to solve the problem, though.
-- setting the post_author as an administrator in the PHP code so that all submitted events list Project Largo as the author, not whoever was or wasn't logged in.
Events Calendar offers a "Community Events" add-on to its plugin, but apparently it's bad -- City Limits tried it and discarded, and have heard bad reviews from at least one WordPress dev in my asking around for solutions. But maybe there's code there that we can pull apart and use to fix the logged-out problems.
2 - find a new calendar option (time: 6-8h)
Not sure what the state of the art is for Wordpress calendars. The main thing would need to be allowing anyone to submit events.
Alternatively, can we add minimal calendar functionality to the other custom post type we created, and lump everything together?
3 - make submitting users log in to the City Limits site (time: 4-6h)
as far as I can tell, City Limits doesn't currently use user functionality for readers at all. Is that something they want to start managing?
Do we need to worry about permissions, still? e.g. will "Subscribers" have closer capabilities to my admin account or to logged-out users?
How do we enforce logged-in status? We don't want to restrict that entire CommunityWire page to logged-in users because the forms and the actual content all live on the same page.
The text was updated successfully, but these errors were encountered:
Pieces of CommunityWire that work:
Pieces that don't:
-- specifically, events submitted by logged-out users do not save the Organizer, Venue or the categories assigned to the event. (All these things work fine if you're logged in.)
-- If I'm reading the Gravity Forms logs correctly, all the information is being sent as expected regardless of your login status. So the dropping of the infos is happening from the Events Calendar plugin side.
Possible solutions:
1 - fix user submission for Events (time: unknown given struggles so far)
Is there a possible solution that I haven't found yet? Things I have tried:
-- giving
tribe_venue
andtribe_organizer
different post type settings for capability_type and public, to match other posts andtribe_event
where logged-out submissions did seem to work. This did not seem to solve the problem, though.-- setting the
post_author
as an administrator in the PHP code so that all submitted events list Project Largo as the author, not whoever was or wasn't logged in.Events Calendar offers a "Community Events" add-on to its plugin, but apparently it's bad -- City Limits tried it and discarded, and have heard bad reviews from at least one WordPress dev in my asking around for solutions. But maybe there's code there that we can pull apart and use to fix the logged-out problems.
2 - find a new calendar option (time: 6-8h)
3 - make submitting users log in to the City Limits site (time: 4-6h)
The text was updated successfully, but these errors were encountered: