View Issue Details

IDProjectCategoryView StatusLast Update
0023081mantisbtcustom fieldspublic2017-08-01 15:31
Reporteraguileraisabelm36M Assigned Toatrol  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionno change required 
Product Version2.5.0 
Summary0023081: Error diferent pages
Description

Hi!
Last week, perform a migration from mantis 1.1.0 to mantis 2.5.0
Everything went very well but I have a problem that I do not know how to solve.
Some users, can not see if view, nor show issues.
You can not manage your columns from your page either.

Any idea?

TagsNo tags attached.
Attached Files
error.png (32,447 bytes)   
error.png (32,447 bytes)   

Relationships

duplicate of 0023028 closedatrol 'Argument 1 passed to columns_remove_invalid() must be of the type array, null given, called in /var/www/html/mantislast/core/cu 

Activities

aguileraisabelm36M

aguileraisabelm36M

2017-07-05 06:34

reporter   ~0057173

Thanks you!

But my problem isn't resolved.

This problem only happens with three or four users, for the rest everything works perfect.

For those three or four users, the pages:

my_view_page.php
view_all_bug_page.php
account_manage_columns_page.php

Show the error attached in first image.

In the second image is all information the my mantisBT.

Thanks you very much!!

error1.png (34,730 bytes)   
error1.png (34,730 bytes)   
atrol

atrol

2017-07-05 07:30

developer   ~0057174

MantisBT 2.x does not support PHP 5.4.16, at least PHP 5.5.x is required.
https://www.mantisbt.org/docs/master/en-US/Admin_Guide/html-single/#admin.install.requirements.software.versions

Feel free to reopen the issue if the problem can still be reproduced after upgrading PHP.

aguileraisabelm36M

aguileraisabelm36M

2017-07-05 08:10

reporter   ~0057175

Thanks you!

But my problem isn't resolved.

It's already updated php 5.5.38

Thanks you very much!!

error2.png (38,769 bytes)   
error2.png (38,769 bytes)   
atrol

atrol

2017-07-05 08:27

developer   ~0057176

Do you think that 0023028 is the same issue?
If so, please stop reopening the current issue and provide feedback in 0023028.

Did you read 0023028:0057172 and if so, did you check if any of the hints provided in 0020872 solves the issue?

atrol

atrol

2017-07-21 06:51

developer   ~0057281

aguileraisabelm36M,

You did not provide any further feedback.
So I assume that 0023028 is the same issue or one of thee hints provided in 0020872 solved the issue.

I am therefore resolving this issue as "no change required".