Hello,
Is it possible to hide a textarea field or the whole form on a category blog page, if a user is currently adding an article to that same category?
The reason is that the blog is a chronological "Story". Each user can add(auto publish/submit an article) to the story(category). Therefore, if a user is currently adding an article, I do not want any other user to be able to submit an article until the first user clicks submit.
Thank you
Jeff
Hi Jeff,
No, this functionality does not currently exist in SEBLOD - to be able to lock and hide the submission of a content type if someone is already submitting an item of content of that type.
Cheers,
James
James,
Ok, thank you for the answer.
Do you have any recommendations on how to do it? Other extensions? Custom coding?
Regards,
Jeff
James,
Do you know if this can be done with a custom plugin-in that I can have developed for SEBLOD?
Thanks,
Jeff
I'm sure some sort of restriction plugin like this might be possible. You can ask Octopoos for a quote to develop it - but with everyone super busy working on the release of SEBLOD 3.6, I'm not sure how quickly someone's going to be able to get back to you.
You may want to try and get in touch with someone like Klas who may have the skills to develop this for you. I don't have his email address though.
Cheers,
James
James,
How much would you charge to set up your suggestions?
In SEBLOD, a soultion to your original problem (but does not address Randy's concerns) could be to:
- Create an independent table in the database called “lock_table”, fields can be id_contenttype, lock, date, user_id…
- When the first user clicks on “new", make the "lock" field value="1" (this can be done with code plugin from the SEBLOD marketplace)
- When another user user tries to access the form and if the form is locked, make a redirection to a page that displays a message.
I'm still learning SEBLOD, so I could learn faster from your custom work then for me to hack around like a bull in a china shop.
Thanks
Jeff
Basically when an article is being created/edited, then its category gets checked_out.
I can see that when a category is being edited by a user in the backend then their user ID gets inputted into that category's "checked_out" field in the DB.
See screenshot: https://www.dropbox.com/s/zq4y7qqgalhtosv/Screenshot%202015-05-06%2010.47.01.png?dl=0
So instead of creating "an independent table in the database called “lock_table”, fields can be id_contenttype, lock, date, user_id…" and then "When the first user clicks on “new", make the" category "checked_out" field value the user ID. Is this possible?
I crude but possibly effective idea could be to use a GROUP X field within the category. User's actually have to edit the category in order to submit a new item using the Group X. You would have to make all past entries from the Group X read-only and non-deletable. Then the user editing the category can add a new Group X node and write their entry. When they click save, the Category becomes checked out again... it's a possibility.
Hi there,
I'm not in a position to give you a quote for this. Please contact Octopoos directly: http://www.seblod.com/contact
Cheers,
James
