See the Mailing lists or Drupal Issue queue. There are also various working groups on groups.drupal.org

LEGAL or SPAM? Cache table and External Sites

Hello, I've noticed that several URL links are referenced via my statistics software that concern me. Particularly, since they're all external to my website, I'm curious why my web server is referencing them as local hits.

In particular, I'm worried because the links are all banner ads or similar, which have no business being on my website. I think maybe it's SPAM in my system somehow?

In any case, the two URLs of concern are:

Speedup the bootstrab with cached pages

In bootstrab.inc it says:

// Call all init() and exit() hooks without including all modules.
// Only use those hooks for critical operations.
  foreach (bootstrap_hooks() as $hook) {
    module_invoke_all($hook);
  }

then in module.inc

Menu Trouble 4.5: Unable to "add Menu"/"add Menu Item"

Menu Trouble: Unable to "add Menu"/"add Menu Item" w/ or w/o taxonomy_menu active though states successful.

In attempting to "add Menu" or "add Menu Item" under .../?q=admin/menu, it will always state it's OK with "Updated menu item..." etc after trying to add new menu items. But nothing shows remotely even new - almost like the entry never happened AND no log errors.

Have tried to enable Taxonomy_Menu or disable Taxonomy_Menu to see if this will make a difference.

List of pages and titles query required

Hi, guys
If you please to help to a newbie...
I need to write query to get all the site pages URLs and their titles

Thanks a lot,
Jacob.

Node locking to prevent simultaneous updates - is this in core?

I have come across this discussion about the problems caused when two people want to update the same node at the same time. However it is not clear to me what the status of this is in Drupal 4.5.0. Did any of the patches make it into core?

More generally, I'm inclined to think that this discussion misses the main point. The proposed patches may stop people overwriting each other's updates - however, this only fits the use case where two people doing simultaneous updates on the same content is something exceptional.

If you are really running a site where multiple people may potentially be editing the same content, then IMHO what you require is a "check-out/check-in" solution. In other words:
- Alice presses the edit button for a node
- Drupal immediately updates the node to show that it is in the process of being edited by Alice
- Bob presses the edit button for the same node: an error message informs him that he cannot edit it, because it is "checked out" by Alice
- Alice finishes editing: on Alice's edit form, there is a checkbox which allows her to choose
---- either to submit the node and check it back in (ie it becomes available for others to edit)
---- or to submit the node while leaving it checked out (ie it remains locked for editing as far as other users are concerned - only Alice can come back and edit the node again).

If Alice leaves the node checked out, then it might be an idea to make the "log message" an obligatory field (if available) and display this to other users trying to edit, so that they know what Alice is doing.

Give me information about PHP

Please Give me PHP releted information

Pages

Subscribe with RSS Subscribe to RSS - Deprecated - Drupal core