April 2005 - Development - lists.drupal.org

[drupal-devel] Release critical bugs for April 14, 2005
by drupal-devel＠drupal.org 14 Apr '05

14 Apr '05

Bbcode / bug reports email spam filtering does not "see" email addresses when they are NOT preceded by a word age: 12 weeks 4 days url: http://drupal.org/node/15654 Chatbox / support requests Cron run kills Chat? age: 18 weeks 1 day url: http://drupal.org/node/14032 Drupal / bug reports database table "term_node" not updated when removing a term from a node under editing and submitting age: 2 days 9 hours url: http://drupal.org/node/20315 Attached files can not be deleted age: 2 days 12 hours url: http://drupal.org/node/20307 Reassigning a node to a different term does not work properly age: 3 days 4 hours url: http://drupal.org/node/20278 4.6 aggregator showing/not interpreting HTML tags age: 1 week 4 days url: http://drupal.org/node/19874 Search ranking broken on pgsql age: 2 weeks 1 day url: http://drupal.org/node/19629 New submit error, non-admin user, postgresql database age: 5 weeks 1 day url: http://drupal.org/node/18552 When I delete a user, any forum in which s/he has commented also disappears. assigned: Jill6q age: 8 weeks 6 hours url: http://drupal.org/node/17428 Published poll doesnt show up in poll block if in submission queue age: 9 weeks 6 days url: http://drupal.org/node/16671 Change to sesssion.inc violates UID database constraint age: 12 weeks 3 days url: http://drupal.org/node/15666 forum.module problem with postgresql v7.4.1 age: 13 weeks 2 days url: http://drupal.org/node/15411 PHP 5 gives error when session table has no session assigned: adschar age: 13 weeks 2 days url: http://drupal.org/node/15399 postgresql error age: 14 weeks 1 hour url: http://drupal.org/node/15175 Entering an empty title broke drupal age: 21 weeks 2 days url: http://drupal.org/node/12974 Argument NOT must be type boolean age: 21 weeks 2 days url: http://drupal.org/node/12950 Comments in approval queue still show up in tracker age: 25 weeks 4 days url: http://drupal.org/node/11647 Twin problems with comments assigned: Junyor age: 26 weeks 6 days url: http://drupal.org/node/11366 Drupal / feature requests Add a footer that is specific to a particular book, shown only on certain pages age: 1 week 6 days url: http://drupal.org/node/19757 moving pages en masse age: 1 week 6 days url: http://drupal.org/node/19754 Taxonomy module should use nodeapi 'load' age: 5 weeks 6 hours url: http://drupal.org/node/18631 Auto PHP memory maximisation age: 7 weeks 2 days url: http://drupal.org/node/17663 Don't reset existing password on request, prevent DoS password reset abuse age: 9 weeks 2 days url: http://drupal.org/node/16909 User info exposed to anonymous user age: 19 weeks 5 days url: http://drupal.org/node/13545 Allow named anchors to work without specifying full path to node age: 1 year 20 weeks url: http://drupal.org/node/4213 Drupal / support requests Fatal error: Unknown column 'headers' in 'field list' query assigned: Eagle-i age: 4 weeks 1 day url: http://drupal.org/node/18928 Strange session behavior age: 4 weeks 3 days url: http://drupal.org/node/18821 user redirected to homepage when logging in age: 5 weeks 5 days url: http://drupal.org/node/18381 Problem with Forums age: 13 weeks 4 days url: http://drupal.org/node/15299 Drupal / tasks atom.module working version to 4.5.0 assigned: hugoromano age: 23 weeks 9 hours url: http://drupal.org/node/12496 Consistency assigned: stefan nagtegaal age: 28 weeks 5 days url: http://drupal.org/node/11045 Drupal.org maintenance / bug reports www.drupal.org - Too many connections error. age: 1 day 11 hours url: http://drupal.org/node/20370 Website search broken with some terms age: 1 week 2 days url: http://drupal.org/node/19956 drupaldocs.org and large fonts age: 5 weeks 5 days url: http://drupal.org/node/18367 Drupal.org print preview crashes Mozilla age: 6 weeks 11 hours url: http://drupal.org/node/18248 Konqueror problem age: 9 weeks 2 days url: http://drupal.org/node/16913 screenshots : page not found age: 9 weeks 5 days url: http://drupal.org/node/16752 Large Fonts problems age: 9 weeks 6 days url: http://drupal.org/node/16664 Drupal.org maintenance / feature requests Plain text posting age: 8 weeks 2 days url: http://drupal.org/node/17335 Drupal.org maintenance / tasks Prune the viewCVS display of Contrib repository age: 1 year 46 weeks url: http://drupal.org/node/1734 Event / bug reports Events show in wrong month age: 1 day 8 hours url: http://drupal.org/node/20378 Timezone improperly applied to new events age: 4 days 2 hours url: http://drupal.org/node/20239 Date formatting issues age: 4 days 3 hours url: http://drupal.org/node/20236 Convert node type on upgrade age: 4 days 3 hours url: http://drupal.org/node/20234 Events for March 31, 2005 not showing up in calendar view age: 4 weeks 2 days url: http://drupal.org/node/18885 Doesn't work with i18n hack/module age: 6 weeks 1 day url: http://drupal.org/node/18145 search over fields.inc fields conceptual error age: 23 weeks 6 days url: http://drupal.org/node/12259 fields.inc screws up with multible multiselect fields age: 23 weeks 6 days url: http://drupal.org/node/12257 Still GMT/TZ issues with CVS age: 24 weeks 6 days url: http://drupal.org/node/11870 Time entry is GMT even when site default is not age: 25 weeks 4 days url: http://drupal.org/node/11630 Start Time of Event is NOT Preserved age: 42 weeks 6 days url: http://drupal.org/node/8565 Feature / bug reports Menu item not showing age: 27 weeks 5 days url: http://drupal.org/node/11210 File / bug reports segmentation fault related to filestore age: 1 year 28 weeks url: http://drupal.org/node/3001 Filestore / support requests File store module - Overwriting Filename....Help needed assigned: harishkm age: 1 year 1 week url: http://drupal.org/node/6827 Unserialize error at line 104 age: 1 year 8 weeks url: http://drupal.org/node/5857 Filestore module- sql errors rectified assigned: harishkm age: 1 year 9 weeks url: http://drupal.org/node/5619 Filestore Module Problems unaddressed assigned: harishkm age: 1 year 11 weeks url: http://drupal.org/node/5365 Gallery / bug reports no images displayed in drupal 4.6-RC but they are displayed by gallery2 age: 2 weeks 5 days url: http://drupal.org/node/19467 Fatal Error: variable_get() age: 3 weeks 3 days url: http://drupal.org/node/19189 No Gallery Image Block age: 3 weeks 6 days url: http://drupal.org/node/19045 Mini applet can't find gallery at url / age: 4 weeks 4 days url: http://drupal.org/node/18785 "Cannot modify header information" age: 5 weeks 3 days url: http://drupal.org/node/18457 Fatal error: Undefined class name 'galleryembed' age: 7 weeks 1 day url: http://drupal.org/node/17746 Gallery / support requests Can't Embed Gallery into Drupal age: 6 weeks 3 days url: http://drupal.org/node/18029 Groups / bug reports Drupal-4.4-rc breaks registration setups and groups.module age: 1 year 4 weeks url: http://drupal.org/node/6392 Image / bug reports Cannot upload .jpgs age: 6 weeks 3 days url: http://drupal.org/node/18076 Wrongly formed html in image gallery age: 7 weeks 6 days url: http://drupal.org/node/17462 Image.Module does not know the correct filename age: 21 weeks 1 day url: http://drupal.org/node/13032 SAFE MODE Restriction in effect... age: 24 weeks 6 days url: http://drupal.org/node/11843 Uploading jpeg makes Imagemagick do high compression age: 26 weeks 3 days url: http://drupal.org/node/11445 Image module failing on Preview because of a blank node id age: 28 weeks 4 days url: http://drupal.org/node/11069 Similar problem with Directory Upload Slow age: 28 weeks 4 days url: http://drupal.org/node/11064 Node (key)words / bug reports Fatal error on logout - only when "cache" enabled age: 5 days 14 hours url: http://drupal.org/node/20174 Node Aggregator / bug reports Please update Node_Aggregator age: 3 weeks 5 days url: http://drupal.org/node/19096 Import doesn't like XML/RSS feeds with no Title element age: 45 weeks 4 days url: http://drupal.org/node/8128 Node Aggregator / feature requests RSS items overwriting edited items age: 43 weeks 5 days url: http://drupal.org/node/8455 Notify / feature requests Notify.module ignores the true submission queue age: 1 year 24 weeks url: http://drupal.org/node/3765 Online / support requests Need Help age: 7 weeks 6 days url: http://drupal.org/node/17475 Pdfview / feature requests Internationalization support for PDF assigned: TheLibrarian age: 1 year 2 weeks url: http://drupal.org/node/6795 Project / bug reports Invalid link to release files age: 7 weeks 3 days url: http://drupal.org/node/17625 blank page after install age: 10 weeks 1 day url: http://drupal.org/node/16575 "Page Not Found" when trying to view issues or add new release age: 18 weeks 6 days url: http://drupal.org/node/13815 Project pages display only title and description age: 21 weeks 4 hours url: http://drupal.org/node/13082 Fatal error: Cannot use string offset as an array in includes/tablesort.inc on line 113 assigned: publian age: 27 weeks 6 days url: http://drupal.org/node/11187 Can't create new project with issue tracker age: 34 weeks 18 hours url: http://drupal.org/node/10148 Project / support requests Help with everything - nothing seems to work in the latest build age: 20 weeks 2 days url: http://drupal.org/node/13310 Recipe / bug reports Recipe trimmed/teaser text does not show up on main page. age: 20 hours 36 min url: http://drupal.org/node/20407 Taxonomy dhtml / bug reports MySQL Error age: 2 weeks 5 days url: http://drupal.org/node/19413 javascrip downloads square.gif for every category age: 8 weeks 1 day url: http://drupal.org/node/17366 TrackBack / bug reports Sends trackbacks for unpublished nodes age: 11 weeks 5 hours url: http://drupal.org/node/16239 Overly aggressive age: 18 weeks 5 days url: http://drupal.org/node/13865 trackback borks google and every other search engine age: 23 weeks 2 days url: http://drupal.org/node/12388 User experience / bug reports user interface problem http://drupal.org/forum/1?from=25 age: 6 weeks 16 hours url: http://drupal.org/node/18237 User experience / tasks WorkFlow and Action Module age: 7 weeks 5 days url: http://drupal.org/node/17517

1 0

[drupal-devel] [bug] Postgres fixes for 4.6 release
by adrian 14 Apr '05

14 Apr '05

Issue status update for http://drupal.org/node/20440 Project: Drupal Version: 4.5.2 Component: postgresql database Category: bug reports Priority: critical Assigned to: adrian Reported by: adrian Updated by: adrian Status: patch Attachment: http://drupal.org/files/issues/postgres_0.patch (6.74 KB) Attached are a bunch of postgres fixes. Caveat: Search index has to be rebuilt after this patch, and there is a postgres specific updates.inc entry. adrian

2 3

[drupal-devel] [feature] View blocks by roles
by tostinni 14 Apr '05

14 Apr '05

Issue status update for http://drupal.org/node/12988 Project: Drupal Version: cvs Component: block.module Category: feature requests Priority: normal Assigned to: tostinni Reported by: tostinni Updated by: tostinni -Status: active +Status: patch Attachment: http://drupal.org/files/issues/block_visibility_0.patch (9.95 KB) Ok here is the new version including these changes : - based on latest CVS version - I created a new function _block_roles_save to handle saving roles - when a new custom block is created, it automatically selects all availables roles (user can change it) and save it - it also handles drupal sequence system for boxes table to allow insertion of the roles next to the custom block creation Still pending : make a _block_roles_rehash. Well I'm not very sure about this one, because it would generate a lot of queries : number of rows in blocks table x num in role _block_rehash works this way, but is it reasonnable ? If _block_rehash is needed not to display blocks that doesn't exists anymore, _block_roles_rehash is only here to clean the block_visibility table, but there won't be any problem with new or missing roles, block would just respect current roles. What should I do ? tostinni Previous comments: ------------------------------------------------------------------------ November 15, 2004 - 16:35 : tostinni Attachment: http://drupal.org/files/issues/block_0_0.patch (5.45 KB) After the release of drumm's work about new block.module in CVS : Make block configuration understandable [1] and another comment : Set blocks to be hidden from anonymous users. [2], I decided to create a little patch to allow use of 'roles' for 'blocks'. So my patch provide a set of checkboxes in block configure (the new field drumm has setting up) that allow roles to see a block. Way it works : 1. If no roles set, block is visible by everybody. If some roles are set, only users with at least one of the roles can see the block. 2. Database : As I'm not sure this block will be included in core because a team is working on it (see Drupal 4.6 roadmap [3] - I will post a comment on civiclabs site), I just set up a new field 'roles' in blocks table. So when you modify the roles of a block, it just update this field with a concatenation of roles_id separated by comma. I'm conscient it's quite ugly, but if this patch find his public, I was thinking in creating a new table block_roles (as done for user_roles). Also update.inc isn't updated for the reasons mentioned above. Well I hope your comments. [1] http://drupal.org/node/11875 [2] http://drupal.org/node/12168 [3] http://drupal.org/node/12202 ------------------------------------------------------------------------ November 15, 2004 - 18:55 : drumm You use user_roles(1) which, if I understand that function correctly, removes the anonymous user role from the list. I think that this should be included. Use case: you want information for non-logged in users which is useless to those who are logged in. Watch your editor's use of tabs instead of spaces. It can and should be included. I haven't started work on this, and it saves me a lot of time if I have patches such as this to review. Why not have all the boxes checked by default to indicate visible to everyone instead of none checked? I would even support adding a validate step to make sure at least one is checked (probably belongs in another patch). I think another table is the way to go. Then you could even write the test for visibility by role to that query in block_list() instead of a loop in php. ------------------------------------------------------------------------ November 15, 2004 - 19:49 : tostinni Hi, Thanks for your feedback. Well a few mistakes (tabs, my editor is now configured, and user_roles(0)) I will correct in next patch. A little comment : for the moment I choosed NULL value for everybody if not, we face a few problems : - if the admin add a new role, it won't be asigned the right to view blocks with the "everybody" grant. - also if people import their blocks or if they apply this patch with a site containing blocks settings, they would be invisble unless explicitly allowed. That's why I considered this option, but if you prefer, I can select all checkboxes. For the validate step, I was thinking of it, but for the moment and the design, It was useless. Regarding of the table, the only issue I was contempling, was the lack of a block_id in blocks table, so I would have to create one. Are you ok with that ? ------------------------------------------------------------------------ March 13, 2005 - 14:37 : killes(a)www.drop.org New patch needed nased on drumm's feedback. ------------------------------------------------------------------------ April 11, 2005 - 18:02 : tostinni Attachment: http://drupal.org/files/issues/block_visibility.patch (8.09 KB) Hi, Sorry for the delay, here is the new patch based on current CVS. *Observations :* - I created a new table : block_visibility that store the visibility for each role / block When you update db scheme it would make visible blocks for all your availables roles, i.e. it changes nothing ;), just set up correctly permissions. - When you configure blocks, you will see a set of checkboxes to allow block to be visible regarding of the user's roles. If no role checked, nobody will see it. *Know bugs (by design ?) :* - When a custom block is created it receives no permissions, it means that it would be invisible unless you configure role in "configure" screen. I'm aware of this problem, but I still don't now how to deal with it. The major issue is that I can't predict which id will be inserted in 'boxes' table as it works with auto_increment / SERIAL columns instead of Drupal own sequence table. We can work around it, but I'm not sure it's a good solution to change this, it would cause a lot of troubles... Maybe look for a db_insert_id function ? Any ideas ? For the moment, the user have to grant permissions to role to be able to see custom block. *To do :* - Add visibility rehash in _block_rehash function. - Change help messages ? - Does my queries look nice ? (It works for sure, but is it a good way to write a join : FROM blocks b LEFT JOIN role r ON 1 = 1 ? ) - Others suggestions ? ------------------------------------------------------------------------ April 12, 2005 - 12:59 : drumm "When a custom block is created it receives no permissions, it means that it would be invisible unless you configure role in "configure" screen. " It should probably display the checkboxes for permissions on the block creation screen. All checkboxes check by default. "The major issue is that I can't predict which id will be inserted in 'boxes' table as it works with auto_increment / SERIAL columns instead of Drupal own sequence table. " It really should use Drupal's sequesnces table. You can safely ignore any auto increment or SERIAL. Just use db_next_id as usual. "- Does my queries look nice ? (It works for sure, but is it a good way to write a join : FROM blocks b LEFT JOIN role r ON 1 = 1 ? ) " I've never seen the INSERT ... SELECT syntax elsewhere in Drupal. This may mean that it is not Postgres-compatible or it is avaided for other reasons. A real join condition should be used, such as r.rid = v.rid. ------------------------------------------------------------------------ April 12, 2005 - 17:51 : tostinni "It should probably display the checkboxes for permissions on the block creation screen. All checkboxes check by default. " I was thinking of this issue, it's just that I didn't find out how to display it without redundancy between form's groups from block_box_form and from block_block, it's done now. "It really should use Drupal's sequesnces table. You can safely ignore any auto increment or SERIAL. Just use db_next_id as usual. " Ok, I will make the changes. "I've never seen the INSERT ... SELECT syntax elsewhere in Drupal. This may mean that it is not Postgres-compatible or it is avaided for other reasons. " Well INSERT ... SELECT syntax is part of SQL ANSI 92 and fully implemented in Postgre. I couldn't find since when, but at least since 6.4 version [4] of Postgre. So I think it's good enough. And maybe if no drupal developer ever used it, it's maybe they never needed it ;) Btw, if there's any limitation not to use it, who can tell me ? "A real join condition should be used, such as r.rid = v.rid. " I've done this on purpose : - If I'm modifying the block options and a new role has been added posterior to the block. Now I got a sort of inconsistance in my block_visibility table, because I miss this new role_id for the (module, delta) tuple. So when I'm reviewing/modifying my block configuration, I need to detect this inconsistence to be able to add this new (module, delta, rid) tuple in block_visibility. This is made doing a JOIN between role and blocks with this strange condition : 1=1 because they don't have a commun column. The other reason I've done it this way is because my MySQL documentation told me to prefer LEFT JOIN to RIGHT JOIN for compatibility. What do you think about it ? Should I use RIGHT JOIN without fear ? It would gives us : SELECT r.rid, v.visible FROM blocks b LEFT JOIN block_visibility v ON v.module = b.module AND v.delta = b.delta RIGHT OUTER JOIN role r ON r.rid = v.rid WHERE b.module = '%s' AND b.delta = '%s' and works the same way. Tomorrow I'll post my changes. [4] http://www.postgresql.org/docs/6.4/static/sql-insert.htm

1 0

[drupal-devel] [feature] Change default $db_url to something unique and informative
by danielc 13 Apr '05

13 Apr '05

Issue status update for http://drupal.org/node/19800 Project: Drupal Version: cvs Component: base system Category: feature requests Priority: normal Assigned to: Anonymous Reported by: danielc Updated by: danielc Status: patch Attachment: http://drupal.org/files/issues/settings.dburl.diff (581 bytes) Currently, the default $db_url in /drupal/sites/default/settings.php is "mysql://drupal:drupal@localhost/drupal". It would be helpful for end users if its contents were more descriptive, such as "mysql://user:password@localhost/databasename". A side benefit of this change is helping automated installation scripts determine if the settings in the /drupal/sites/default/ are meant to be used or not. This is because the existing db_url could possibly be used in real life while the proposed text is very unlikely to be used. danielc

3 10

[drupal-devel] [bug] db_set_active acting strangely/not working
by chx 13 Apr '05

13 Apr '05

Issue status update for http://drupal.org/node/20235 Project: Drupal Version: cvs Component: database system Category: bug reports Priority: critical Assigned to: chx Reported by: jakeg Updated by: chx Status: patch "If a second call is made to mysql_connect() with the same arguments, no new link will be established, but instead, the link identifier of the already opened link will be returned. The new_link parameter modifies this behavior and makes mysql_connect() always open a new link, even if mysql_connect() was called before with the same parameters. " So, two calls to the same server had only resource ID instead of two. This is corrected. chx Previous comments: ------------------------------------------------------------------------ April 9, 2005 - 21:50 : jakeg As per my forum posting at http://drupal.org/node/20211 , db_set_active isn't working, and is in fact acting extremely strangely. I've never used it before, so maybe I'm using it wrong, but I've looked at the contributed drupal docs and I believe I have the correct usage. See http://drupal.org/node/20211 for details. Jake. ------------------------------------------------------------------------ April 9, 2005 - 22:09 : jakeg This problem persists and hence is not related to my other problem I had concurrently (http://drupal.org/node/20233) which has now been resolved for me. ------------------------------------------------------------------------ April 10, 2005 - 08:57 : jakeg [GRRRRR... I just posted a long explanation of this problem only to get /Terminated request because of suspicious input data./, and when I pressed the back button my response was gone. Damn it!!! That took about half an hour to write and I don't have time to write it all again now] ------------------------------------------------------------------------ April 11, 2005 - 09:14 : jakeg some more detail: settings.php: ... $db_url['default'] = 'mysql://[snip]@localhost/local_aspodrupal'; $db_url['depletion'] = 'mysql://[snip]@localhost/local_aspo'; ... mymodule.module: ... // Switch to the depletion database to perform some queries db_set_active('depletion'); // [run a query on my custom db, or even do nothing and i still have the problem] // switch back to the default drupal database db_set_active('anything-but-default'); ... ... the code above works, but the last line should be, as far as I can understand, db_set_active('default'), but that causes errors. If I ue anything-but-default then it works. Jake ------------------------------------------------------------------------ April 13, 2005 - 17:39 : chx Yes. Working on this. ------------------------------------------------------------------------ April 13, 2005 - 19:44 : chx Attachment: http://drupal.org/files/issues/db_set_active.patch (760 bytes) ------------------------------------------------------------------------ April 13, 2005 - 19:46 : jakeg legend

1 0

[drupal-devel] [bug] db_set_active acting strangely/not working
by jakeg 13 Apr '05

13 Apr '05

Issue status update for http://drupal.org/node/20235 Project: Drupal Version: cvs Component: database system Category: bug reports Priority: critical Assigned to: chx Reported by: jakeg Updated by: jakeg Status: patch legend jakeg Previous comments: ------------------------------------------------------------------------ April 9, 2005 - 20:50 : jakeg As per my forum posting at http://drupal.org/node/20211 , db_set_active isn't working, and is in fact acting extremely strangely. I've never used it before, so maybe I'm using it wrong, but I've looked at the contributed drupal docs and I believe I have the correct usage. See http://drupal.org/node/20211 for details. Jake. ------------------------------------------------------------------------ April 9, 2005 - 21:09 : jakeg This problem persists and hence is not related to my other problem I had concurrently (http://drupal.org/node/20233) which has now been resolved for me. ------------------------------------------------------------------------ April 10, 2005 - 07:57 : jakeg [GRRRRR... I just posted a long explanation of this problem only to get /Terminated request because of suspicious input data./, and when I pressed the back button my response was gone. Damn it!!! That took about half an hour to write and I don't have time to write it all again now] ------------------------------------------------------------------------ April 11, 2005 - 08:14 : jakeg some more detail: settings.php: ... $db_url['default'] = 'mysql://[snip]@localhost/local_aspodrupal'; $db_url['depletion'] = 'mysql://[snip]@localhost/local_aspo'; ... mymodule.module: ... // Switch to the depletion database to perform some queries db_set_active('depletion'); // [run a query on my custom db, or even do nothing and i still have the problem] // switch back to the default drupal database db_set_active('anything-but-default'); ... ... the code above works, but the last line should be, as far as I can understand, db_set_active('default'), but that causes errors. If I ue anything-but-default then it works. Jake ------------------------------------------------------------------------ April 13, 2005 - 16:39 : chx Yes. Working on this. ------------------------------------------------------------------------ April 13, 2005 - 18:44 : chx Attachment: http://drupal.org/files/issues/db_set_active.patch (760 bytes)

1 0

[drupal-devel] [bug] db_set_active acting strangely/not working
by chx 13 Apr '05

13 Apr '05

Issue status update for http://drupal.org/node/20235 Project: Drupal Version: cvs Component: database system Category: bug reports Priority: critical Assigned to: chx Reported by: jakeg Updated by: chx -Status: active +Status: patch Attachment: http://drupal.org/files/issues/db_set_active.patch (760 bytes) chx Previous comments: ------------------------------------------------------------------------ April 9, 2005 - 21:50 : jakeg As per my forum posting at http://drupal.org/node/20211 , db_set_active isn't working, and is in fact acting extremely strangely. I've never used it before, so maybe I'm using it wrong, but I've looked at the contributed drupal docs and I believe I have the correct usage. See http://drupal.org/node/20211 for details. Jake. ------------------------------------------------------------------------ April 9, 2005 - 22:09 : jakeg This problem persists and hence is not related to my other problem I had concurrently (http://drupal.org/node/20233) which has now been resolved for me. ------------------------------------------------------------------------ April 10, 2005 - 08:57 : jakeg [GRRRRR... I just posted a long explanation of this problem only to get /Terminated request because of suspicious input data./, and when I pressed the back button my response was gone. Damn it!!! That took about half an hour to write and I don't have time to write it all again now] ------------------------------------------------------------------------ April 11, 2005 - 09:14 : jakeg some more detail: settings.php: ... $db_url['default'] = 'mysql://[snip]@localhost/local_aspodrupal'; $db_url['depletion'] = 'mysql://[snip]@localhost/local_aspo'; ... mymodule.module: ... // Switch to the depletion database to perform some queries db_set_active('depletion'); // [run a query on my custom db, or even do nothing and i still have the problem] // switch back to the default drupal database db_set_active('anything-but-default'); ... ... the code above works, but the last line should be, as far as I can understand, db_set_active('default'), but that causes errors. If I ue anything-but-default then it works. Jake ------------------------------------------------------------------------ April 13, 2005 - 17:39 : chx Yes. Working on this.

1 0

[drupal-devel] Drupal.org forums
by Dries Buytaert 13 Apr '05

13 Apr '05

Hello world, I reorganized the drupal.org forums based on the outcome of the Drupal conference in Antwerp: http://drupal.org/node/18270 "We realize that the Drupal community is growing. One of the effects of this is that there is a need for better segmentation of concerns and focus. The suggestion was for the formation of several "working groups", along with tools and assistance to allow members of the groups to interact with each other in a focused manner." Changes: - I created new forums and shuffled the existing forums around. - I added RSS feeds to the forum listings so it is easy to subscribe to your favorite forums using an RSS aggregator. Until we have subscriptions, this might help you track or filter discussions. Next steps: - Discuss the new layout and wording of the forum names/descriptions. Suggestions welcome. - I'd like to invite some of you to recategorize existing forum topics that now have a better home. - The /forum page is getting slow. It is in the top 10 of most popular Drupal.org pages though so any performance improvements to either the taxonomy or forum module are much appreciated. - As soon we settled on a new forum layout and recategorized a bunch of forum topics, we'll announce the changes and their intend on drupal.org. -- Dries Buytaert :: http://www.buytaert.net/

1 1

[drupal-devel] [bug] Some pages in book are missing node links
by moshe weitzman 13 Apr '05

13 Apr '05

Issue status update for http://drupal.org/node/20451 Project: Drupal Version: cvs Component: book.module Category: bug reports Priority: normal Assigned to: moshe weitzman Reported by: moshe weitzman Updated by: moshe weitzman Status: patch Attachment: http://drupal.org/files/issues/book_link.patch (608 bytes) Some ancient code was assuming that all apges in a book are of type=book. 1 line patch attached. the existence $node->parent is currently the best way to know that a node is in a book. ideally that element should be renamed book_parent for better namespacing but thats for another patch. moshe weitzman

1 0

[drupal-devel] [bug] Post title written twice when posting using BloggerAPI
by david 13 Apr '05

13 Apr '05

Issue status update for http://drupal.org/node/19406 Project: Drupal Version: cvs Component: blogapi.module Category: bug reports Priority: normal Assigned to: Anonymous Reported by: david(a)puntbarra.com Updated by: david(a)puntbarra.com Status: patch Attachment: http://drupal.org/files/issues/blogapi.blogger.duptitle.patch (362 bytes) Wrong variable name causes post title not to be removed from the content and posted twice (in title and body). It only affects BloggerAPI posts, not metaWeblogAPI nor mtAPI. This bug affects all Drupal versions AFAIK. david(a)puntbarra.com

3 2