In my efforts to make my drupal forum behave like an actual forum that people are used to, I'm trying to get rid of the original post from appearing in every single page in that thread. It is very confusing to users to see the same past at the top of each page when they are navigating through comments.
So far I haven't found an answer. I created a new field in profiles using the profile module and stored a value in it. But the value doesn't show up in the mysql table "profile_values". And yet, if I revisit the user profile, the value is there. It's being stored somewhere, but where?
Does Drupal store field updates in a cache? If so, how does one force a "flush" to the table?
I would like users to go to the last page of the forum topic rather than the first page, so when they reply can see their reply without having to hit "last page" every time they make a post. This is a fairly standard action for forums that should be part of the drupal forum module IMHO. In fact, some forums give the user the option after they post to go to their post (last page) or to go back to the topics list page. That would work too.
Hi all, this is a big question. I'm using the category module, and I would love to have the feature to view, update, and delete a category restricted in a fasion the same as cac_lite performs for just view. Does anyone have a patch/hack/sheep that could help? I've looked everywhere and came up relatively empty. Thanks.
What I want to do is to publish news about specific topics, without having to TAG every news item that gets into my site.
So I got this idea that I could create some static search query and insert that query into a block, so that the block would automatically nodes that would respond to that query normally!!
For example on a page about football I would create a block that searched only for news feeds and for the term football... The results of that query would then show on the block...
I finally got my website set up, and then all the suddenly my hosting company decided they wanted to upgrade their MySQL server. Now I get this on my website when I try to log in with any of the user names I set up:
* warning: Cannot modify header information - headers already sent by (output started at /{path}/database.mysql.inc:120) in /{path}/common.inc on line 139.
* user warning: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' query: SELECT * FROM users WHERE status = 1 AND name = LOWER('john') in /{path}/includes/database.mysql.inc on line 120.
* user warning: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' query: SELECT * FROM users WHERE status = 0 AND name = LOWER('john') in /{path}/includes/database.mysql.inc on line 120.
* user warning: Illegal mix of collations (utf8_general_ci,COERCIBLE) and (latin1_swedish_ci,IMPLICIT) for operation 'like' query: SELECT * FROM access WHERE status = 1 AND type = 'user' AND LOWER('john') LIKE LOWER(mask) in /{path}/includes/database.mysql.inc on line 120.
* user warning: Illegal mix of collations (utf8_general_ci,COERCIBLE) and (latin1_swedish_ci,IMPLICIT) for operation 'like' query: SELECT * FROM access WHERE status = 0 AND type = 'user' AND LOWER('john') LIKE LOWER(mask) in /{path}/includes/database.mysql.inc on line 120.