Module works perfect for me, but I've just one rather simple problem:
Storage for the 'paths' field seems to be limited to about 250 chars for all input lines. If I try to input more chars, they're truncated.
Unfortunately, my longest path definition is very long. So on my site this limit is exceeded by about 20 chars, and the last breadcrumb generated for this specific node type is therefore invalid.
I would appreciate for this being enhanced / made user definable in the next version. Not urgent for me.

Comments

MGN’s picture

MGN commented

The storage length for titles and paths is set when the database tables are created. The titles and paths fields are both set as 'type' => 'varchar', 'length' => 255, in the custom_breadcrumb.install file (and the same in the submodules). If you need to increase the storage, the length can be increased. I don't see how this could be made user definable, aside from the user editing the install file before installing.

I don't think there is a performance penalty for increasing the size of varchar beyond 255. I am just not sure how useful it would be for most people who use the module. Still, I will look into increasing the length.

Transhumanist’s picture

Transhumanist commented
Category: feature » bug

This problem becomes mildly catastrophic if one needs to use complex PHP code to return different titles/paths depending on properties of the $node object - which is the situation I'm faced with (CCK field values, in this case). Because the field contents are truncated, the code gets broken, fails to return an array and produces breadcrumbs formed from mangled PHP...! :(

MGN’s picture

MGN commented
Category: bug » feature

@Transhumanist, this has been discussed at #654766: text size limit breaks php code.. The advanced php in titles and paths option was never intended for complex code. But you can easily make it work by defining a custom function (or token) (elsewhere, in an include file, for example) that you call from a brief php snippet in the titles or paths fields. There is no bug here. It functions as intended.

MGN’s picture

MGN commented
Status: Active » Closed (fixed)

Closing because the question was answered and the feature request is part of a related issue, which I will as postponed for now.