Jump to:
| Project: | Vocabulary Index |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Xano |
| Status: | closed (fixed) |
Issue Summary
Location http://www.example.com/cms/admin/build/vocabindex/blocks
Referrer http://www.example.com/cms/admin/build/vocabindex/pages
Message preg_match() expects parameter 2 to be string, array given in /home/*****/public_html/cms/includes/bootstrap.inc on line 777.
Severity error
Location http://www.example.com/cms/admin/build/vocabindex/blocks
Referrer http://www.example.com/cms/admin/build/vocabindex/pages
Message Missing argument 2 for theme_table() in /home/*****/public_html/cms/includes/theme.inc on line 1297.
Severity error
Drupal 6.14
VI 6.x-2.x-dev
Installed latest 6.x-2.x-dev version and ran upgrade.php and the configuration settings pages "Pages' and "Blocks" are unusable. No form just collapsed text.
Changed theme back to default theme but same problem.
Un-installed and re-installed but still the same problem and the above error messages in my logs.
Dropped back to version 6.x-2.2 though this has the alphabetical index bug.
Comments
#1
Not sure if this isn't a duplicate of:
http://drupal.org/node/596986#comment-2119322
#2
Have the same error messages displayed at /admin/build/vocabindex:
* warning: Missing argument 2 for phptemplate_table() in /XYZ/sites/all/themes/commpress/template.php on line 67.
* warning: preg_match() expects parameter 2 to be string, array given in /opt/drupal6/includes/bootstrap.inc on line 777.
* warning: preg_match() expects parameter 2 to be string, array given in /opt/drupal6/includes/bootstrap.inc on line 777.
* warning: preg_match() expects parameter 2 to be string, array given in /opt/drupal6/includes/bootstrap.inc on line 777.
Regard,
Ralf
#3
I concur, same error here 2
#4
Could you provide step by step instructions how to reproduce the problem using a fresh installation of Drupal and Vocabulary Index dev?
#5
I can confirm the 6.x-2.x-dev release dated 2009-Nov-07 has fixed the problem for me.
Thanks Xano, much appreciated.
#6
It appears this was a bug that somehow slipped it during 7.x-2.x-dev development. Fixed and committed.
#7
#8
Automatically closed -- issue fixed for 2 weeks with no activity.