Deprecated - Usability feedback

How do you set the font color using WiKiText?

I can successfully use the 'Full HTML' Input Format in a Story Body to specify font color. For example, the following line correctly shows a green 'string':
string

However, this doesn't work with the 'WikiText' Input Format. The above line shows the original 'string'.

I'm trying a make a handbook that reviews the 300-400 Drupal modules on www.drupalecommerce.com using 4.7. When I go to submit a book page, every existing book page is on the pulldown menu. If you try it on drupal.org (not 4.7 yet) you'll see that the pulldown list seems to have hundreds of lines. I read nodes 11283 and 12927 which has been discussing fixing this from 2004 to present. Am I correct in thinking that this problem still is not fixed in 4.7?

Hi All,

No doubt the devs are aware of this and are looking to correct it in the future, but I just thought I'd post it anyway just so they know it is a "real" problem for those using drupal and worthy of their time. The only siginifcant problem I've come across with Drupal is that deleting content and/or users is like trying to navigate a minefield while riding a pogo stick. One false move and you can end up with orphaned content that is impossible to remove via the Drupal admin control panel, and which then requires you to go and manually remove this data from the database. As Jeff Eaton pointed out for me (see link below), you *can* delete content sucessfully if you remember to delete a modules content prioir to removing the module. However, this could be very cumbersome if the module you are removing has several hundred nodes published under it, plus I think phonetically this process is destined to bring a lot of Drupal newcomers totally unstuck.

What to do with orphaned content and their comments/votes:
http://drupal.org/node/21923

Deleting users it seems is less like navigating a minefield on a pogo stick, but rather using an actual mine as your pogo stick (i.e. total suicide mission). From what I've been able to gather there is no way to sort/group content by author name to be able to delete or change the author of content by a user en masse. The result this has is when you delete a user, then all the content they've created is replaced with an "N/A" error message. From here the only way to delete/modify the author of all content by that user is to write yourself an SQL query to execute directly against your database. I know the site maintainer's guide (see below) strongly recommends blocking users rather than deleting them, but my question is that as deleting a user in Drupal is so destructive why is the option there in the first place? If the delete user option absolutely must be there, then shouldn't the warning screen at least make the user aware of what will happen if they proceed rather than just saying the action can't be reversed?

Is there a way to sort or reorder search results in terms of things like

Poster or Last post or somting like that.

Like you can with the threads themselves

The current model mixes 2003 posts which may be outdated with new 2006.

I noticed a new post in this thread but rather than continue in that thread I decided to start a new one here.

First, I really do need this image embedding functionality and I am not a coder with the ability to be able to code this sort of stuff.

I have followed many discussions and made numerous comments (many other users have done likewise on similar threads). So without any workable results I revisited the image module and installed it again on my test site.

To my surprise....I found that it seems to now work as I would like it it work for about 70% of the functionality which I require.

It is indeed possible to simply choose an image from your local file system and reasonably seemlessly have it produce a node with the image displayed at the site admins choice of sizing with a link to the original image included on the page. The node teaser also includes a clickable thumbnail to the preview page. Great!

My earlier experiences with this module were less than workable and I dismissed it as next to useless and went on to test all the other options with similar results in all cases.

Is it at all possible that the image.module could be slightly extended to enable extra images to be added to the same node in the same seemless was as the initial image is added?

I have looked around in the forum and in the specific issues, bugs and features pages for i18 but I didn't really find a solution to my problem: how can I grant translation rights to some specific roles? Can anyone give a suggestion?
Thanks,
Jan