Cannot assign/edit/change submitted proposal

[charlener]

Admittedly, I have been editing files to add additional fields to the proposal/abstract submission, plus have added an additional presentation format, but this seems totally unrelated. When I try to do anything related to changing a submitted proposal (editing metadata, assigning a reviewer, submitting a director decision on the proposal, etc.), I get the following errors:

Notice: Only variable references should be returned by reference in /home/XXXX/public_html/ocs/classes/schedConf/SchedConfSettingsDAO.inc.php on line 58

Warning: Cannot modify header information - headers already sent by (output started at /home/XXXX/public_html/ocs/classes/schedConf/SchedConfSettingsDAO.inc.php:58) in /home/XXXX/public_html/ocs/classes/core/Request.inc.php on line 40

...and things don't work right (data not saved). Any ideas, other than reverting all my code?

UPDATE: I have installed a fresh copy of OCS with a new db, loaded data into it, and still get the above errors. It seems to happen with various login/role combinations as well as different abstracts. The weird thing is that it seemed to save the metadata once properly, but hasn't since. So maybe it isn't my mods...

[asmecher]

Hi charlener,

The error message is harmless (and has been corrected in CVS), but should be sent to a log file rather than displayed to the browser or it may interfere with browser redirects. See the display_errors directive in your php.ini.

Could you describe the process that you're using that's not saving metadata as you expect?

Regards,
Alec Smecher
Public Knowledge Project Team

[charlener]

Hi Alec,

Thanks for the prompt followup.

Concerning metadata saving: I must have been careless in the last test - sorry. It does seem to save the data, albeit at an abrupt halt with that error message, which occurs with most actions, it seems.

I'm on a hosted provider, so I don't have easy access to changing php.ini file settings...is there a way for me to update only the particular files affected to prevent the error? I suspect that while I am content with hitting the action buttons then going back or refreshing, many of the reviewer types will become horribly confused...

--Charlene

[asmecher]

Hi Charlene,

Try adding the following to OCS's index.php near the top (but outside of any comment blocks):

Code: Select all

ini_set('display_errors', 0);

If your host allows it, this will suppress PHP errors from being displayed to the browser.

Regards,
Alec Smecher
Public Knowledge Project Team

[charlener]

It worked just fine - awesome. Thanks for the code