[rbc]

Originally Posted by Phillip

Yes, still the same result.

I would rename all the old files of the PT on the server.
Upload the complete package again - Be sure it is the latest version 2.3.1

Try again the installation / update

[Phillip]

Finally got it to work after imported it on my server instead of the "EITHER upload the XML file from your computer".

[rbc]

Originally Posted by Phillip

Finally got it to work after imported it on my server instead of the "EITHER upload the XML file from your computer".

Thats Great !!

Best regards!

[barnsi]

Hello friends!
We have ProjectTools2.3.1 running well on vB4.5 with PHP7.1.9 and MariaDB10.1.26 installed.

But there are two fatal problems:

1. when trying to import a thread (Example: projectpost.php?do=importcontent&p=12392&type=post) an error occurs:

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

2. when clicking on a projecttype (Example: issuelist.php?projectid=1&issuetypeid=SFMInfo) an error occurs:

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

I have seen that it works very well here: https://www.vb-os.com/project/2-Project-Tools with vB4.5Beta3.
Is there a way to fix this?

[PitchouneN64ngc]

Those errors are related to PHP 7, vb-os.com is still running on PHP 5.6.

Fixes will come quickly

[PitchouneN64ngc]

As another note, Im not sure why 2.3.1 was defined in development code, reverted to 2.3.0. You can edit the installed product file to change it from 2.3.1 to 2.3.0 or updating it won't execute added code for 2.3.0 & 2.3.1 in the future.

[PitchouneN64ngc]

After further research, those errors are not related to PHP 7. They are fixed locally, will commit them

[WindVoice]

Can't find the latest version 2.3.1 at https://www.vb-os.com/content/123-Download

Where to get it from?

Thanks!

[PitchouneN64ngc]

1/ It's not 2.3.1 but 2.3.0, there were an error versioning.
2/ Follow instructions on the page, it's on development.

[barnsi]

Hey!
...yes, installed it from SVN (29.09.2017 at Revision #904)

[barnsi]

...and today again (at #Rev908) and 2.3.0 is back!
YES!!! importing a thread works perfekt now without an Error. Thank you very much

issuelist.php?projectid=1&issuetypeid=SFMInfo still causes this fatal error

[boarddocTOR]

I have v 2.3.0 installed and it works fine except for 2 issues I'm trying to resolve. I'm using vBulletin v 4.2.5.

1) There is no option for me to set up how attachments are saved. I'm concerned I'm going to eventually have a corrupted database since there's no way of knowing where my attachments are going to be saved. This image shows my control panel on this matter.



2) Issue Type Manager - No matter how I try to configure this I can't get the color styles applied to my issues. The attached images show what I have set up in Issue Manager. The dark styles are different than the light styles, which, according to the instructions they must be. So I don't think that's the problem.



I've also set up the status color ID's in vBulletin options. This doesn't seem to work either. Have I entered the IDs correctly? I don't have any documentation on what the ID actually is.



I also changed the Issue color to "Severity Color" and that didn't work either.



If anyone can help me out, it would be mucho appreciated!

[dunc07]

In the "status color options" screen, the list of "Dark Styles" and "Light Styles" does not refer to some color IDs, but to the actual "vbulletin style IDs" that are available on your forum.

You can check the available styles by using the vBulletin admin panel, then look for the "Styles & Templates -> Style Manager" page.

Here, you will have a list of all styles, by default these are only "vB4 Default Style" and "Default Mobile Style". Unfortunately, that list does NOT show the actual ID of each style.

In order to find the IDs, either simply do a mouseover on the style names and check the URL, e.g. <foobar>/forum/forum.php?styleid=5, or select "Edit Style Options -> Edit Settings" from the drop-down boxes on the right and hit the "GO" button. On the new page, the title bar of the options screen will now show the name and ID of the style you've selected, e.g. "Style: vB4 Default Style (id: 5)".

These ID number are what you have to use in the "Project Tools: Status Color Options" screens you've posted.

[barnsi]

http://svn.vbulletin.org/svn/project_tools

Is this path still working? Can´t connect

[Dave]

Works fine to me, check the source code of the page. It doesn't display anything visible.