i have not provided footer options like -
- Recommended modules
- Other modules
- Credits
that maintainers may decide to attach.
vinaysamant → created an issue.
where should i write the documentation? Can i write it here in my next comment?
Also i have a small feature request, if you can spare some time and help.. plz where should i post it?
Just commented
https://www.drupal.org/project/publishcontent/issues/3368259#comment-158...
📌
Users without publish access should not be allowed to create published content
Active
Is this helpful in anyway?
dear rodrigoaguilera,
1st of all thanks a lot for great module. i wish this should be in Drupal Core.
Look at my following comment https://www.drupal.org/project/publishcontent/issues/3368259#comment-158... 📌 Users without publish access should not be allowed to create published content Active on this module. I dont know how much you understand English as your preferred lang is Spanish. But if you allow me, i can write a good documentation about this module and it's correct usage. Let me know.
I am going to build a crowdsource website dedicated for "Responsible Parenting". I m going to use your module heavily. Thanks.
i was struggling a lot to get this module configured as my expectations that were close to your's.
I wonder why is this not inbuilt in Drupal even after 10. They have some monster like Content Moderation & Workflows but not something very basic like "publish content". anyways..
In this, i think major issue is with documentation of module : "After enabling it, you first need to choose the content types this will work with. Goto Structure -> Content Types then edit each that should work with this module. Tick the "Enable publish content" tickbox under the publishing options and save.". This is totally missing.
Module has independent setting under Workflows menu "Publish Content" submenu. There is an option "Publish and unpublish via checkbox" which is uncheck by default. But if you enable this then it sorts everything. Additional option to set "status" appear on content creation form. In Content Type setting's keep option of "Published" unchecked. So by default content is unpublished. For every user. But when user has "Publish Content" permission, "status" can be set. Otherwise this option is visible but disabled. This is really useful, mainly w/o using any patch or making any programming changed. Unfortunately it's not properly documented.
vinaysamant → created an issue.
vinaysamant → created an issue.
@raveen_thakur51
i made one more install on fresh site for this and faced same issue and i have to make same changes. So the core module isn't yet updated? can i do something in this regard? plz guide n advice
I m facing same problem like @jrochate for "user" form modes. Any update as this is 3 years old thread?
i dont understand this issue Q etc and formalities here.
i hope u will get this done in the module.
There is one more thing though. The email login functionality is not working. It gives some HTML/URL error when enabled and tried login with email. IF possible look into it as well. I disabled it as my site is not dependent on that. But it's good n required functionality. And your module is doing good job. Thanks for your help and work.
After reading some online articles and checking backtrace of exceptions i realised that having "$query->accessCheck();" call before "$query->execute()" is compulsory. Otherwise it will keep throwing exceptions.
FBL module at /modules/contrib/fbl/fbl.module has "$query->execute()" at line 85 & 114. If u place "$query->accessCheck();" just before these 2 calls then this error is gone and everything runs smoothly.
This is not final solution. Module needs to be upgraded for this change. Developers plz look into this.
vinaysamant → created an issue.
vinaysamant → created an issue.
vinaysamant → created an issue.
The problem still exists when i try to create subtheme. Looks like patch not committed properly
i think the issue is with "libraries/dompurify/dist/purify.min.js" which is external JS a module uses for RSS feeds. If this library is unavailable then aggregator fails. But then can this be listed under aggregator module? Actually if some file is missing, then aggregator should ignore and still continue with other JS files isn't it?
vinaysamant → created an issue.