Posted by subcomandante on May 12, 2009 at 9:20am
Jump to:
| Project: | Project issue tracking |
| Version: | 6.x-1.x-dev |
| Component: | Issues |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi,
I have Internationalization module on my site and it works, but when I use project_issue I get this error on every issue pages:
* warning: preg_match() expects parameter 2 to be string, array given in /home/xxx/www/includes/bootstrap.inc on line 771.
* warning: preg_match() expects parameter 2 to be string, array given in /home/xxx/www/includes/bootstrap.inc on line 771.
* warning: preg_match() expects parameter 2 to be string, array given in /home/xxx/www/includes/bootstrap.inc on line 771.if I disable the Interationalization module project_issue works.
Comments
#1
Maybe more info would be needed on this:
The module I'm using is i18n http://drupal.org/project/i18n
The modules activated are:
Block translation
Internationalization
Menu translation
String translation
The version I'm using is 6.x-1.0 2009-Jan-25 (but today I upgraded to 6.x-1.x-dev 2009-Apr-28 but the problem still persist, but as I stated previously the module is working on the whole site so it doesn't seems a i18n issue)
The project_issue module I'm using is Project issue tracking 6.x-1.x-dev (2009-May-10) but the issue was already in previous versions.
The problem seems to happens at issue creation, because just after submitting an issue I see the newly created issue w/o Project association and others not setted. Infact if I later go to content management and click on edit besides an issue I see an error message saying "Invalid project selected."
Hope this helps
#2
I posted this on i18n module bugtracker too #488518: project_issue incompatibility.
Nobody else has this problem?
#3
Hi,
I encountered exactly the same problem using the project_issue module into a Drupal 6 installation (migrated from a Drupal 5 one). I had the ''preg_match()'' error on each project issue node page. I managed to remove these warning by completely un-install and remove the commentrss module.
I hope it will help to locate how to fix this issue.
NiNiX
#4
ty NiNiX, after your post I wondered if something went wrong and I tried to do a fresh project_issue install on a fresh site and it worked.
I used several dev snapshots upgrading the database everytime, but seems something was wrong updating database on a dev version I cannot find.
With a fresh install, i18n and project_issue seems work together, anyway I need to check it deeply to confirm.
#5
After a lot of testing I can say it works now, so it seems really something went wrong after several upgrades.
#6
Automatically closed -- issue fixed for 2 weeks with no activity.