Let me first say that I like Drupal very much and it is currently definately my choice of CMS!
I am relatively new to Drupal and I just found out that unpublished nodes are visible in the menu for non editors or admins!
Opening the page will then lead to an 'access denied' message which is of course correct. However, the menu items should not be visible for non editors in the first place!
First, I thought I must have made a mistake somewhere because this behaviour is not to be expected from a CMS!
After trying for a while I just could not figure what I did wrong, so I did some searches on drupal.org:
The results:
This HUGE bug was already reported in 4.6!
Here is another thing:
There is a content type which has default published unchecked and create automatic revisions.
A non admin editor creates a node that will of course not be published.
The admin publishes the node.
Now the editor decides that he wants to make some changes to the published node.
I am interested in creating a javascript application and I am thinking to have drupal engine in the back-end and maybe GWT (Google web toolkit) or prototype as the front-end. So does anybody have any suggestions on how to start? I am fine with GWT on it's own but how do I integrate it with Drupal (CMS php scripts in general)?
So I installed and have Drupal running, no problems. I've used other CMS before, and am used to a front end / back end concept. I've found the back end at http://myserver/drupal, but where is the front end?
I think I may have completely missed something important here, but when I try to make changes to the front end I end up losing my back end stuff and replacing it.
So how can I see what's being published, or if I am completely off track can someone re-orient my head please?
Hello.
We're creating a website at gamelanx.com (a crazy hybrid gamelan band) and we want to have a really easy way for folks to sign up for our email list - like just type your email address in the box and push a button (and then a confirmation email is sent to the subscriber). Also, we'd like the ability to easily add addresses manually - like after a show, from our email sign-up clipboard.
Any help in finding the right module would be much appreciated.
Thanks!
Eric
In the few months that I have used Drupal, the most frustrating aspect of the experience has been the lack of documentation to support contributed modules. I had indeed abandoned several modules days along the way, because there was really no guidance on how to make them work. This underlines the general problem that techies face when presenting solutions meant for the real world .In our own experience we feel enlightened to have been able to present useful tools - whereas the consumer feels nothing other than obfuscation , because they have no idea how to use these tools.
When I'm setting up a test/development site, I'm frequently enabling/disabling modules.
1) No specific solution, but is there a better way to decide which fieldsets on the module page should be expanded vs contracted? That could save a decent amount of searching/scrolling around.
2) Likewise, is there a reason to keep the Core - required fieldset and its contents?
DDEV is the official local development tool of Drupal. And like Drupal, DDEV depends on the support of the open source community.
