Comments for Sourcefusion

Comment on Drupal’s menu system - take two by donquixote

donquixote — Tue, 18 May 2010 21:57:05 +0000

drupal menu system does always store the internal path, that is “node/123″. It will only use the alias when the link is rendered.

Comment on Drupal’s menu system - take two by helma

helma — Mon, 03 May 2010 17:58:11 +0000

I haven’t had the time to check the menu editor out, but being able to search for a node by strings inside the node, would certainly be a big improvement, even more so if the result is added to the menu as ‘node/’ rather than the (auto-)alias of the path.
Over time I have developed the following strategy (based on recommendations in several Drupal docs/books/websites): references to nodes are always done to the node id. I’ve added the autopath module to automatically create aliases. This way my links are fine if I change the title of the node, e.g. every year I update a Page node with the upcoming convention info, changing the year in the title. I know this is debatable, but for me it works fine and I have the added benefit of links that stay current.

Hmm, this would also be great for a ‘link editor’, where you have a search box to find existing nodes and when selecting the one you want, the node id is added for use with the path filter module. I once saw something like this in Joomla, although I never got it to work properly (one more reason for the switch to Drupal) and in Daisy the search feature used for the menu editor, is also used for the link editor.

Comment on Drupal’s menu system - take two by donquixote

donquixote — Mon, 03 May 2010 13:14:33 +0000

Well, with menu editor you have two things to solve these problems:
1. autocomplete for the link path, to find existing nodes.
2. if you store or for the path, the menu item will send you to a page where you can create a node that will be linked to the menu item.

But yes, the autocomplete does not find strings inside of nodes, it only finds node titles. Do you think a search would be a huge improvement?

Comment on Drupal’s menu system - take two by helma

helma — Mon, 26 Apr 2010 08:54:50 +0000

Sorry for the delay in replying. Looking at the menu_editor it certainly improves the speed in which a menu can be created or edited. What I still miss is Daisy’s functionality of quickly looking up documents (related to Drupal’s nodes) right from the menu.
Example: if I want to add a Drupal node to a menu, along with it’s translated counterpart, I have to jot down or memorize both node IDs and add them subsequently to new menu items. In Daisy I would click the search button and find all documents containing the string I enter. Then I select the required document and Daisy adds the ID.
BTW same goes for adding links to other Daisy documents. Something I sorely miss in Drupal.

Comment on Drupal’s menu system - take two by donquixote

donquixote — Thu, 01 Apr 2010 02:42:11 +0000

If you are still interested in this: I used to have the same problem, and here is the solution:
http://drupal.org/project/menu_editor
happy?

I have not seen the daisy menu editor - is there anything that would make sense to adapt?

Comment on Adobe’s Help Center by Alex

Alex — Sun, 28 Mar 2010 22:42:30 +0000

I ended up deleting both xml files AND the prefs file before I got AHC visible. Thanks for your article!

Comment on Moving Drupal and Gallery2 by Shai Efrati

Shai Efrati — Sat, 27 Jun 2009 16:39:27 +0000

Thanks! you just saved my website!

Shai.

Comment on Drupal Clean URLs on OS X Leopard by iddaa

iddaa — Sat, 04 Apr 2009 18:06:07 +0000

very nice article. thanks

Comment on Update to Wordpress 2.7 by Margot

Margot — Thu, 26 Feb 2009 11:29:43 +0000

I, too, are often faced with the problem and still do not know how to solve it. Perhaps you like to respond to it?

Comment on Update to Wordpress 2.7 by Carolyn

Carolyn — Thu, 05 Feb 2009 09:27:51 +0000

I also had a lot of difficulties with the update to Wordpress 2.7, but now it all is over and I am very happy.