[rbc]

Originally Posted by Dave

I'm pretty sure this project/plugin is dead and no longer developed/supported.

Dave

That's how it looks

best regards

[Paul M]

Originally Posted by Dave

I'm pretty sure this project/plugin is dead and no longer developed/supported.

Actually, i noticed Yves did some work in svn the other day.

[In Omnibus]

Originally Posted by rbc

Tried to install this version of Project Tools on vBulletin 4.2.5.
Installation not possible - no way.

Attachment 156442

No error message ....... just the progressbar for ever

Someone an idea?

I have this up and running on a 4.2.5 installation. There must be some other issue.

[rbc]

Originally Posted by In Omnibus

I have this up and running on a 4.2.5 installation. There must be some other issue.

@In Omnibus

i have a fresh (clean) install of vB 4.2.5 (testboard)
When i try to install PT v. 2.2.2 nothing happens. Just progress bar as pointed above.

my live board works very well with vB4.2.4 and PT 2.2.2 and i am sure i can
update my board to vB4.2.5 and it would still work.

hope you know what i mean. (english -> not my language)

best regards

[In Omnibus]

Originally Posted by rbc

@In Omnibus

i have a fresh (clean) install of vB 4.2.5 (testboard)
When i try to install PT v. 2.2.2 nothing happens. Just progress bar as pointed above.

my live board works very well with vB4.2.4 and PT 2.2.2 and i am sure i can
update my board to vB4.2.5 and it would still work.

hope you know what i mean. (english -> not my language)

best regards

Without much information I suspect it may be a PHP issue.

Which PHP version is your 4.2.5 installation using?

[rbc]

Originally Posted by In Omnibus

Without much information I suspect it may be a PHP issue.
Which PHP version is your 4.2.5 installation using?

@In Omnibus

I use PHP Version 5.6.24-pl0-gentoo, exactly the same as on my live board.
-----

What i did today ! :
I did a fresh installation of vBulletin 4.2.4
Then the installation of vB Project Tools v. 2.2.2 works just fine.

Then i did an upgrade to vBulletin 4.2.5 - PT still there and visible.

try to add a new issue, results in a white page.

i did a new import of the product PT xml.

still the same -> white page.

(Its no problem to me, because this is only on a test site)
PT 2-2-2 works just fine on my live Board with vBulletin 4.2.4!

best regards

[In Omnibus]

Originally Posted by rbc

@In Omnibus

I use PHP Version 5.6.24-pl0-gentoo, exactly the same as on my live board.
-----

What i did today ! :
I did a fresh installation of vBulletin 4.2.4
Then the installation of vB Project Tools v. 2.2.2 works just fine.

Then i did an upgrade to vBulletin 4.2.5 - PT still there and visible.

try to add a new issue, results in a white page.

i did a new import of the product PT xml.

still the same -> white page.

(Its no problem to me, because this is only on a test site)
PT 2-2-2 works just fine on my live Board with vBulletin 4.2.4!

best regards

Odd. That's the same PHP version I'm using on my test site. I'm trying to think of what else might be causing the issue but my knowledge of the changes between 4.2.4 and 4.2.5 as it relates to project tools specifically is limited to say the least. If I get some free time later I'll test this in debug mode on a clean installation.

[Dave]

Are there any errors in the error logs of Apache/PHP?

[rbc]

Originally Posted by Dave

Are there any errors in the error logs of Apache/PHP?

@Dave

[04-Jun-2017 00:33:57 Europe/Zurich] PHP Fatal error: Call to undefined method vB_DataManager::vB_DataManager() in /home/xxxx/xxxx/vbtest/includes/class_dm_pt_project.php on line 89

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

[04-Jun-2017 00:42:37 Europe/Zurich] PHP Fatal error: Call to undefined method vB_DataManager::vB_DataManager() in /home/xxxx/xxxx/vbtest/includes/class_dm_pt_projectgroup.php on line 77

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

best regards

[Dave]

Yea, it seems that it will not work properly with the latest vBulletin version that supports PHP 7.
It should work if you change all instances of

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

to

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

And the function which contains that call should be changed to __construct since a class can not have a function that has the same name as the class. (For example change function vB_DataManager_Pt_Project to function __construct

I took a quick look and it seems that a bunch of files do this so you might have to apply these changes to multiple files.

[rbc]

Originally Posted by Dave

Yea, it seems that it will not work properly with the latest vBulletin version that supports PHP 7.
It should work if you change all instances of

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

to

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

And the function which contains that call should be changed to __construct since a class can not have a function that has the same name as the class. (For example change function vB_DataManager_Pt_Project to function __construct

I took a quick look and it seems that a bunch of files do this so you might have to apply these changes to multiple files.

@Dave

Thank you for pointing this out.
I will try to change these functions - and then try a new installation.

I took a look too and compared some new files from vB 4-2-5 with 4-2-4 and it`s
exactly how you wrote.

best regards

[rbc]

Some good and some bad news ...........

After updating this files :

class_dm_attachment.php (Z. 82)
class_dm_pt_issue.php (Z. 138)
class_dm_pt_issueassign.php (Z. 77)
class_dm_pt_issuechange.php (Z. 83)
class_dm_pt_issuenote.php (Z. 91/708/824/911)
class_dm_pt_issuepetition.php (Z. 79)
class_dm_pt_issuereport.php (Z. 85)
class_dm_pt_issuestatus.php (Z. 84)
class_dm_pt_issuesubscribe.php (Z. 75)
class_dm_pt_issuetype.php (Z. 104)
class_dm_pt_issuevote.php (Z. 78)
class_dm_pt_magicselect.php (Z. 71/232)
class_dm_pt_milestone.php (Z. 94)
class_dm_pt_project.php (Z. 87)
class_dm_pt_projectgroup.php (Z. 75/820)

the install script works perfect

All database entries, the sample project group and an example project Is created.
Everything is as good as it should be ..... but

If you want to make a new issue click on submit, a white page appears. You go back to project main page and the just created issue is listed in timeline and wherever. When you click on them -> white page.

Php.log:
[04-Jun-2017 15:14:16 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/includes/adminfunctions_projecttools.php on line 428
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1403
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1409
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Declaration of vB_DataManager_Pt_IssueNote::verify_ipaddress() should be compatible with vB_DataManager::verify_ipaddress($ipaddress) in /home/xxxx/vbtest/includes/class_dm_pt_issuenote.php on line 0
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1572
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 506
[04-Jun-2017 15:15:07 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 507
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1403
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1409
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Declaration of vB_DataManager_Pt_IssueNote::verify_ipaddress() should be compatible with vB_DataManager::verify_ipaddress($ipaddress) in /home/xxxx/vbtest/includes/class_dm_pt_issuenote.php on line 0
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/projectpost.php on line 1572
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 506
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 507
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue:re_delete() should be compatible with vB_Attachment_Dm:re_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue:re_delete() should be compatible with vB_Attachment_Dm:re_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 15:15:13 Europe/Zurich] PHP Fatal error: Unhandled BB Code Call : vB_BbCodeParser in /home/xxxx/vbtest/includes/class_bbcode.php on line 221

A coder will quickly recognize where the problem lies. I'm not a coder

best regards ...

[Dave]

Every

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

has to be changed to

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

in all files.

--

In /includes/class_dm_pt_issuenote.php

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

Remove the ampersand.

--

In /packages/vbproejcttools/attach/issue.php

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

to

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

--

I'm not sure about the fatal error though, it's not clear to me where it's called from.

[rbc]

Thank you @Dave

I will check and fix this - I come back with feedback!

best regards

[rbc]

@ Dave

I changed the files:
/vbhome/
projectajax.php (c 100/202/363/374)
projectpost.php (c 406/704/757/1407/1414/1578/2697/2714/3103/3296/3353/3438/3973/4554)
projectsearch.php (c 791/928/961/)
/vbhome/includes/
adminfunctions_projecttools.php (c 428/459/
class_dm_pt_issue.php (c 570/587/645/670/680/907/995/1408)
class_dm_pt_issueassign.php (c 139/183/)
class_dm_pt_issuechange.php (c 167/247)
class_dm_pt_issuenote.php (c 389/403/503/517/568/582/619/696)
class_dm_pt_issuepetition.php (c 158/187)
class_dm_pt_issuemagicselect.php (c 299)
--
/vbhome/includes/class_dm_pt_issuenote.php (117)
/vbhome/packages/vbprojecttools/attach/issue.php (520)
--

I uninstalled vb PT. AdminCP remove plugins.
Installed it new - > no problems.
install script
create issue -> white page.

Of course i uploaded all the altered files ....

php.log:

[04-Jun-2017 18:16:25 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue:re_delete() should be compatible with vB_Attachment_Dm:re_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 18:16:45 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue:re_delete() should be compatible with vB_Attachment_Dm:re_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 18:38:44 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue:re_delete() should be compatible with vB_Attachment_Dm:re_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 18:39:01 Europe/Zurich] PHP Strict Standards: Declaration of vB_Attachment_Dm_vBProjectTools_Issue:re_delete() should be compatible with vB_Attachment_Dm:re_delete($list, $checkperms = true) in /home/xxxx/vbtest/packages/vbprojecttools/attach/issue.php on line 0
[04-Jun-2017 18:52:45 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/admincp/projectcounters.php on line 153
[04-Jun-2017 18:53:04 Europe/Zurich] PHP Strict Standards: mktime(): You should be using the time() function instead in /home_p2/c/o/compusoft.li/htdocs/includes/class_core.php(4735) : eval()'d code on line 2
[04-Jun-2017 18:53:15 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 506
[04-Jun-2017 18:53:15 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 507

[04-Jun-2017 19:14:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/includes/adminfunctions_plugin.php(1201) : eval()'d code on line 568

[04-Jun-2017 19:14:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/includes/adminfunctions_plugin.php(1201) : eval()'d code on line 633
[04-Jun-2017 19:14:13 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/includes/adminfunctions_plugin.php(1201) : eval()'d code on line 683

[04-Jun-2017 19:14:30 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/admincp/project.php on line 957
[04-Jun-2017 19:14:52 Europe/Zurich] PHP Strict Standards: Only variables should be assigned by reference in /home/xxxx/vbtest/admincp/project.php on line 647
[04-Jun-2017 19:17:08 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 506
[04-Jun-2017 19:17:08 Europe/Zurich] PHP Strict Standards: Only variables should be passed by reference in /home/xxxx/vbtest/includes/class_dm_pt_issue.php on line 507

@Dave
feel free to abort your kind advice at any time ...

best regards