Sorry if this post duplicates a previous posts question. I've searched and did not find any question that matches mine.
I am working up a site for my community. I have created menus and am using the nice_menu module to display them. Some of the menuitems I created from scratch appear to anonymous (not logged in) users and my admin menuitem appear to non-admin users (even though when they click on it, it doesn't show them anything)
Can some let me know how I can hide this items to underprivileged users?
I love the event module. I just don't like how big the event block is. I have a quite and somewhat obvious fix to that problem. So obvious I feel silly posting this. So forgive me if this duplicates an older post.
Simply add this line to the top of your event.css file:
.block-event{font-size: 7pt}
Since the font sizes are percentage based, all further font declarations become percentages of your initial font-size declaration. Therefore the block still keeps its proportional differences in font size.
Now I create different content for product, documentation, downloads, I switched on taxonomy_menu.
If I click now on Product1 I will see all the entries in documentation and downloads.
I would like to see the documentation-entries only if i click on documentation not before!
So, as administer I have organized a book by weight, so the chapters are in the correct order and everything. Now, when a user edits a page, it apparently resets the weight to 0 and means that every time a page is edited, I have to go back and re-organize it!
This is a little annoying, and I'm wondering if there is a way to keep the previous weight after a page edit.
I have just started exploring Drupal, and I am a little concerned that it does not seem to be able to do incremental backups. MySql allows for incremental backups using binary logs, but my ISP, and I suspect many ISPs, do not provide for this with a typical account. Has anyone considered this problem at all?
When I searched for information about backups, they are all about full backups (and even about a module that does a full backup by emailing large chunks! This should be avoidable most of the time if incremental backups were possible).
I saw this addressed here http://drupal.org/node/44257, but have yet to find a solution to this. I still have this problem and I cannot create new vocabularies, although I do get the message saying it was created. It was not, I checked the database tables. I am certain it is an upgrade problem, from 4.6.3 to 4.7.0 beta. However, everything else runs very well...no problems. Is it possible for me to just run the update/commit that deals with the 'tags' ?