Forum Replies Created
-
Berardo,
Unzip the contents of the ZIP file for the new version, overwrite the existing files via FTP and you’re done :). There’s no true upgrade process involved.
in reply to: New Update Available – v1.0.83Hey Ahmed,
I’m actually trying to get it to where there’s a drop-down on the front-end submission form, so the post meta is what I need. I’m not trying to set this for a profile field :).
Basically, I need to allow publishers to choose the condition of what they are selling on our site and only select one from a drop-down menu.
– Brand New
– Used – Good Condition
– Used – Slight Wear / Tear
– etcSo how would I go about that? Right now, the drop-down menu doesn’t work.
in reply to: New Update Available – v1.0.83Andy,
Nope, it doesn’t look like it. I’m still waiting on the ability to allow publishers the ability to choose only one category and the ability to allow us to choose which categories they have the option of selecting. Right now, all categories are open, so if we have a news & updates category that only us admins post to, publishers can choose that and if auto-publish is set, it’ll get sent through.
Right now, the only option I have is to create a form for each category, which is kind of a pain :).
in reply to: New Update Available – v1.0.83Andy,
You’ll need to add “category” into the display order definition. Since you’re able to choose and re-order the display, using that short-code option effectively only displays what you tell the short-code to and in that order. If category isn’t in the definition, it won’t show up.
in reply to: New Update Available – v1.0.83Ahmed,
Thanks so much for the added functionality!!!!
I did run into one issue though. I added a new field as a drop-down using the “Add New Field” option. There’s 4 options, one on each line, no spaces before or after each option as would be standard. However, when I go to pull the field using the shortcode, it doesn’t display a dropdown menu as would be expected. Instead, it’s a blank text field.
in reply to: New Update Available – v1.0.83Hey Ahmed,
So with the next release we’ll be able to add custom fields to the front-end publisher and custom forms, or just custom forms? Just wanted to clarify :). I’d still like to see the ability to add custom fields and the ability to mark them as required or not – something many of us would find useful :).
As for the editing, sounds good and I’m looking forward to it!
in reply to: v1.0.83: Development – Frontend PublisherSounds great Ahmed! Do you have a time-frame for release?
in reply to: v1.0.83: Development – Frontend PublisherAwesome work Ahmed! When do you think the ability for users to edit their posts will make its way into the front-end publisher? That’s one thing we’re dying for right now!
in reply to: v1.0.83: Development – Frontend PublisherJust added a few of my suggestions as well (to andy999’s thread listed above).
in reply to: Frontend submission flexibilityLooks like Andy beat me to the submit button in the midst of writing up my thread, so I’ll post here :).
Merged
in reply to: Front end publisher requests for AhmedAhmed,
I’ll volunteer. I’ll post a new thread with the list summary from this thread.
in reply to: Frontend submission flexibility9). The ability to allow users to edit their post submissions. Right now if a member makes a mistake or otherwise forgets to include something, we have to go in and edit it. If members could edit their own posts, that would be a MAJOR plus.
in reply to: Frontend submission flexibility8). Currently when a post is submitted using the front-end form, a small pop up pops up telling them that their post will soon be approved but it leaves the form in place instead of redirecting them to another page. This leaves things open for the member to repeatedly submit them same post over and over, thus filling up the review queue for admins. It’d be super-helpful to see the option of being able to redirect to another [customizable] page that gives them this information so we can avoid duplicate entries.
in reply to: Frontend submission flexibilityI’ll add one more to the list 🙂
7). E-Mail the author of the post once their post is live. So if they submit a post and it goes into pending, when it’s approved and goes live, send them an e-mail letting them know with a link included. If their post goes live instantly, send them the same e-mail. This ensures they know the post has indeed been published.
in reply to: Frontend submission flexibilityI would love to see extended functionality available as well. Specifically:
1). The ability to create multiple front-end submission forms and manage them from the back-end.
2). The ability to specify custom fields for each individual form. For the site I’m working on now, I need to add another 5-8 fields to the submission form. While I could request members simply specify this in the post, it’d be much easier if custom fields existed and I could make them required, thus forcing the member to fill them out.
3). The ability to easily customize how the fields appear on the post once a submission is made (i.e. custom ordering of the fields, placement of the fields etc).
4). Same as #4 above – the ability to specify which roles can post and instantly be moved from pending to live post.
5). Ability to upload not just a featured image, but also X additional images, which will be formatted using the WordPress gallery core functionality.
6). The ability to “Report a Post” should a member feel that something is wrong with the post. The report would be logged and a notification would be sent to an administrator. We could them remove the post, hide the post etc. It’d simply make things easier, but this option would have to be global and apply to all posts, not just those made from the front-end plugin, so I can understand if this one doesn’t make the cut :-).
in reply to: Frontend submission flexibility