WordPress.org

1. rovers
   Member
   Posted 3 years ago #

   Had version plugin 1.7 running on domain (wp2.6.3 in subdirectory) with php4.4.8 with myql5.0.67
   had one project with one dataset record in it.
   Used automatic upgrade on 7 feb. Said was successful but accessing front end website produced

   Warning: Missing argument 1 for projectmanager() in ****/wp-content/plugins/projectmanager/lib/core.php on line 102

   Warning: Cannot modify header information - headers already sent by (output started at ****wp-content/plugins/projectmanager/lib/core.php:102) in ****/wp-content/plugins/wp-postratings/wp-postratings.php on line 691

   Went back to admin and found that plugin update still required - this time downloaded 1.8.1, uploaded and when accessing project said database updarte due - agin completed and said successful but same error. Have deactivated awaiting feedback

2. MichaelH
   Volunteer
   Posted 3 years ago #

   Using 2.7, I downloaded the zip file, used the Plugins->Add New->Install a plugin in zip format, and successfully installed and activated the plugin.

   Then changed version from 1.8.1 to 1.8.0 and did the automatic upgrade, again, successfully.

   Might delete the plugin folder, download the zip, do Plugins->Add New->Install a plugin in zip format, to see if you have success.

3. rovers
   Member
   Posted 3 years ago #

   Thanks for your reply. I am using 2.6.3. The back end upgrade to 1.8.1 had previously said firstly plugin upgrade successful and database upgrade successful.

   I have tried deactivating wp-postratings plugin to see if that was the cause of the problem but front end above error message still occurs (core.php line 102 - missing argument 1)

   Reactivated wp-postratings.

   As my project wasn't originally assigned to a category, assigned to "Unassigned" to see if that was a possible cause of the conflict.

   Still same error. No obvious white space after end close of php which sometimes causes "Cannot modify header information - headers already sent" error.

   I've gone back to version 1.6.2 until 1.8.1 is confirmed as compatible with earlier versions than wp 2.7

4. lgedeon
   Member
   Posted 2 years ago #

   I am getting the same error in WordPress 2.7.1 with ProjectManager 1.9 so this seems to be a problem across version numbers.

5. lgedeon
   Member
   Posted 2 years ago #

   Ok, I just got rid of the problem by upgrading to PHP 5.

   I work on several different systems. I have upgraded most to PHP 5 but had missed this one.

6. Kolja
   Member
   Posted 2 years ago #

   @rovers try the following. Change in lib/core.php:

   function ProjectManager( $project_id )

   into

   function ProjectManager( $project_id = false )

   Maybe that helps.

Topic Closed

This topic has been closed to new replies.