I am just trying out Storm and have gotten 3 warning messages when I try to save a new project. Here are the steps that I took prior to getting the messages:

1. Created 2 Organizations; one for the provider and one for the customer.
2. Created people so that I would have users to add to the team.
3. Created a team with 3 members
4. I began creating a project which is where I ran into the issue.

First when I created the project, I filled out the begin/end dates, category, status, priority, Organization, Project Manager and assigned to. I gave it a title and then tried to save it. What I got were these 3 warning messages and nothing else on the page:

Warning: function_exists() expects parameter 1 to be string, array given in C:\xampp\htdocs\t2\includes\form.inc on line 726

Warning: function_exists() expects parameter 1 to be string, array given in C:\xampp\htdocs\t2\includes\form.inc on line 726

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\t2\includes\form.inc:726) in C:\xampp\htdocs\t2\includes\common.inc on line 335

So, I tried two more times, making sure that all fields were filled in but it made no difference. When I clicked on projects from the main Storm page, I noticed that all three projects I created where there. I tried editing one of them and got the same 3 warnings.

Is there something I am doing incorrectly or is this a bug? If it is something I am doing wrong, is there a tutorial somewhere on how to use Storm correctly or some user documentation that will give me some better guidance?

Thanks in advance
John

CommentFileSizeAuthor
#17 010810.patchresults.JPG40.54 KBdbt102
#13 partial_storm.task_screenshot.JPG27.08 KBdbt102
#11 storm.module.patch1.11 KBMagnity

Comments

Magnity’s picture

Magnity commented
Priority: Minor » Normal

Hi John - any other modules installed?

Has anybody else had this issue?

jsmoorejr’s picture

jsmoorejr commented

Yes, I have several other modules installed, here is the list that I installed aside from the core:

ACL
Advanced Forum
Author Pane
CCK
Devel
Dynamic Persistent Menu
Forum Access
Nice Menus
Node as Block
Private Message
Quotes
Subscriptions
User Longin Bar
Views
Zenophile
and of course Storm.

I am also going through the Modules tutorial so I have a small example mod from the tutorial called "onthisdate" installed.

I looked around and didn't see anyone with this same issue.

John

Magnity’s picture

Magnity commented
Title: I get warnning messages when I try to save a project » I get warning messages when I try to save a project

The message about headers being modified sounds like something is at least being amplified by the devel backtrace functionality. (Btw - does a backtrace appear with devel for this error?).

Do the errors change without devel?

Anything in the logs? I'm guessing it might just be a copy of the php warnings that you've already posted.

jsmoorejr’s picture

jsmoorejr commented

The only thing that appeared on this error page was the 3 warnings that I posted, the rest was just white space. Theme, other page widgets all of it was missing.

When I uninstalled Devel and tried saving the project, I get the same first two errors, but the third goes away. The difference is that I actually have content on my page without Devel. It takes me back to the projects page with the list of projects. Changes I make are being saved, but in a red block right under the page Title (under the banner) is the warning block with these two errors:

    * warning: function_exists() expects parameter 1 to be string, array given in C:\xampp\htdocs\t2\includes\form.inc on line 726.
    * warning: function_exists() expects parameter 1 to be string, array given in C:\xampp\htdocs\t2\includes\form.inc on line 726.

At least now I have a menu. :)

I probably won't be reinstalling Devel.

Magnity’s picture

Magnity commented

Glad you've got the site works at least now then. Lets hope we can fix those other warnings too.

Which version of PHP are you on?

Are there any circumstances you've come across when this doesn't happen, or other situations where it does happen?

I've had a cursory look at this section of the code, but haven't found an issue of yet!

jsmoorejr’s picture

jsmoorejr commented

PHP Version: 5.3.0

I do not recall seeing this error before. Although in my first attempt to install drupal, I installed the Admin menu module and I saw warning messages like these. I don't know if they said the same thing or not, but regardless, I am not working on the same install as I had then.

I appreciate the help, now that my page is at least showing when I save a project, I can continue to set it up and get it working.

jsmoorejr’s picture

jsmoorejr commented

I rolled back to PHP version 5.2.8 and the warning messages went away. Not sure why, but seems that there is something that PHP 5.3.0 doesn't like. Thanks again for the help.

Magnity’s picture

Magnity commented

That's interesting to know. In fact, I think I may have heard about issues with 5.3.x before, but can't remember when.

Sounds like it still will need solving at somepoint though - especially with more and more people moving to PHP 5 and higher versions of that.

Magnity’s picture

Magnity commented
Title: I get warning messages when I try to save a project » PHP warning messages saving project with PHP 5.3.0

Changing title to better describe for the future...

Magnity’s picture

Magnity commented
Category: support » bug

Reclassifying as probable bug.

Magnity’s picture

Magnity commented
Status: Active » Needs review
StatusFileSize
new storm.module.patch1.11 KB

I think the attached patch might fix these warning messages, but am going to need someone to test as I don't have a PHP 5.3 environment up and running.

Magnity’s picture

Magnity commented

Note on this issue that Drupal core also has some compatibility issues with PHP 5.3.

See:

#360605: PHP 5.3 Compatibility

So the real need for this issue to be fixed will be once core is fixed and people start using Drupal in that environment.

dbt102’s picture

dbt102 commented
StatusFileSize
new partial_storm.task_screenshot.JPG27.08 KB

Reviewed this as per request (#3 @ http://drupal.org/node/678994)

I dooo get the following error when using PHP 5.3.0

""warning: function_exists() expects parameter 1 to be string, array given in C:\wamp\www\drupal\includes\form.inc on line 727. ""

However, when I revert back to PHP5.2.11 this error does not happen (but the prior issue from node/678994 does).

I tested for this error at ...storm/projects , ...storm/tasks , ...storm/tickets & ...storm/timetrackings , in all cases the error occurs only after I change the "Filter by Organization" to something different.

I also notice that in the Category and Priority columns of ...storm/tasks view , only the default error icons come through (see attached image). But, with the ..storm/tickets view all the Status and Priority icons display as they should. Looks really nice...

Magnity’s picture

Magnity commented

Thanks. Does the patch in #11 do anything to solve it?

I don't have an available 5.3 environment, so much your help on this is much appreciated.

dbt102’s picture

dbt102 commented

OK, after working with drupal off and on for a year and a half, I think I'm ready to plunge a bit deeper... I've never applied a patch before... what is the easiest way to do this? ...from a storm perspective...

Magnity’s picture

Magnity commented

There is a pretty good guide at http://drupal.org/patch/apply

One thing to check though is where a patch is rooted from. Most of the time for storm, it will be from the storm directory, in which case that is where to put the patch before applying. Sometimes it may be from the modules directory or a storm subdirectory.

For this patch it is rooted in the storm directory.

dbt102’s picture

dbt102 commented
StatusFileSize
new 010810.patchresults.JPG40.54 KB

OK Thanks ... I took some time to install cygwin and play with patching ... pretty cool ...

In short... with PHP v5.3.0 ... the patch didn't work. Since this is my first attempt at patching I've attached a screenshot of cygwin output. It looks like the patch successfully installed. But after update.php ...it did some pretty ugly stuff and ... after testing ... didn't seem to reverse as I would have expected. Following is a sampling of some of the testing errors...

@ ...site1/storm/projects

Fatal error: Call to undefined function storm_icon_add_node() in C:\wamp\www\drupal\sites\all\modules\storm\stormproject\stormproject.admin.inc on line 44

@ ...site1/storm/tasks

Fatal error: Call to undefined function storm_icon_add_node() in C:\wamp\www\drupal\sites\all\modules\storm\stormtask\stormtask.admin.inc on line 463

@ ...site1/storm/tickets

Fatal error: Call to undefined function storm_icon_add_node() in C:\wamp\www\drupal\sites\all\modules\storm\stormticket\stormticket.admin.inc on line 74

@ ...site1/storm/timetrackings

Fatal error: Call to undefined function storm_icon_l() in C:\wamp\www\drupal\sites\all\modules\storm\stormtimetracking\stormtimetracking.admin.inc on line 85

Note: Since cygwin didn't throw an error when I reversed the patch (as per http://drupal.org/patch/reverse), and after running ./update.php again, storm (and admin menu) was still misbehaving as noted above, I just wiped the folder and reinstalled latest .dev

and all is well...

Magnity’s picture

Magnity commented
Status: Needs review » Needs work

Yes, looks like the patch applied successfully, but very odd results.

Back to the drawing board on this one then. Thanks.

snake00jap’s picture

snake00jap commented
Version: 6.x-1.26 » 6.x-1.33

hi there i have the same issue in a fresh instal of drupal 6.17 (on ubuntu 10.04 "Lucid Lynx", LAMP, PHP Version 5.3.2-1ubuntu4.2)

juliangb’s picture

juliangb commented

These bugs are harder to get because of the few people currently running 5.3. If you'd be willing to put some time into solving these, it would be much appreciated!

beejaysea’s picture

beejaysea commented

The changes in #11 worked for me. Ubuntu 10.04, PHP 5.3.2-1ubuntu4.2, Fresh install of Drupal 6.17, Storm 1.33.

I didn't apply the patch directly, but made the two requisite changes by removing "=> array()" on the two lines that set up #element_validate

So far, so good.

tchurch’s picture

tchurch commented

Does this link to issue #684016: Fix E_NOTICE notifications ?

I'm trying to fix some of these errors so that the test bot can work again. From what I read it has something to do with the PHP version.
Maybe the PHP version on the test clients has been upgraded?

I still don't have a resolution for this error in the other issue yet.

Any thoughts?

tchurch’s picture

tchurch commented

I've manually added this patch into #684016: Fix E_NOTICE notifications and it seems to resolve my issues too.

juliangb’s picture

juliangb commented
Status: Needs work » Closed (duplicate)

Marking this as a duplicate of #684016: Fix E_NOTICE notifications, which has now been committed, I believe fixing this issue.

If any more notices are found, we should create tests which expose these so that we have a systematic way of knowing that we´ve fixed them.