Hi,
Drupal is brand new for me for publishing
What I am planning to do is if an editor Approves a content or Dis approves a content then he should fill a form.
Eg. If my publishing workflow is like
Content Writers Write the content
Language Administrator checks the language used and approves or dis approves
Editor checks all the content created and approved by Content Writer and Language Administrator
Now if any stage a content is dis approved then the person who disapproves it should be able to fill a form
Like if Language administrator dis approves he should be asked for
- line number
- content which he feels is wrong
- suggested language
in a form
If Editor dis approves it
A form should ask
- Reason
Also,
Is there any way we can get consolidated view of count of content at each stage of workflow
I will be grateful to get any help
Regards,
Saurabh
Comments
is this module alive.
is this module alive.
I applied a workflow to one
I applied a workflow to one of the content type and now those content do not show up in home page. is this normal? and what if i want to show them on homepage.
hi all i have found out a
hi all i have found out a solution to one of my problem i stated.
"I applied a workflow to one of the content type and now those content do not show up in home page. is this normal? and what if i want to show them on homepage."
Ans: This is normal as if we apply workflow other then what drupal gives to content, then drupal dont know what is published and what is not.
if you want to publish your content when it reaches end state, then use a trigger and action to publish that content.
Sorry, I really didnt read readme.txt for my question about putting form. I will read it once and see if the author has mentioned there.
thanks all,
saurabh
*_*
Well, every module on d.o has a file called 'README.txt'. The file mentions everything from installation to configuration. I'd suggest you to study the file accompanying respective module.
Regards.
BeautifulMind
!
Whoah, hang on a minute beautifulmind; the OP took the time to write a very reasonable question, and I can't see a single reason to justify the addition of a comment which I can only describe as rude.
Not cool.
For the record, and to try to add some value to this discussion, not all modules include a readme file, and the quality and clarity of those that do varies wildly.
I very rarely find anything of use in the readme which isn't better covered on the module download or support pages.
Al
*_*
Well, It wasn't rude if you felt like that way. At most of the time, I can configure modules by reading the project details on the project page and then reading the README.txt. But hey, this is not to justify my reply. I wrote what I do and what I feel. if you don't like it, just ignore it.
Regards.
BeautifulMind
True enough!
True enough alexharries! The readme.txt files with most module downloads are a VERY poor excuse for documentation. Not only is it a vague place to keep information but it's also not clear where else to look for information. In the grand scheme of things Drupal suffers the most in the documentation department. There's certainly efforts to rectify this issue but there's still a long ways to go. Sadly the most reliable source is to trace through/read/look at the module code. Not really a great solution especially for those new to Drupal.
Remember Google is your friend. If you can come up with the right key words often someone has posted an article suggesting solutions.