We're excited that we are finally able to release Project Tools Open Source version 2.2.2.
Here's all you need to do to have Project Tools running on your site.
1. Download the files
2. Unzip the files locally
3. Upload the contents of the files located inside the /upload/ directory to your existing vBulletin directory.
4. Log in to your forum's control panel. Go to Plugins & Products > Manage Products > Add/Import Product
5. In the Import the XML file from your server field, enter: ./includes/xml/product-vbprojecttools.xml Change Allow Overwrite to yes if you are updating a previous installation.
6. Click Import
Comments, Questions, Support and Concerns will be addressed here and here only.
Further documentation can be found in the docs and here. Beta documentation is located within the /do_not_upload/ directory within the download.
For this release, the Italian language is not updated to Project Tools 2.2.2, and the Romanian language is added and noted for 2.2.1.
I checked the SVN and see that there has been updates as late as July 2019 by yrigaud. Not sure if the SVN was compromised or if the changes are valid. Anyone shed some light on the ID or want to run a DIFF on the updated files? The trunk where the updates are shows as v2.3.0 and not 2.3.1
Seems legit. /includes/class_pt_issuelist.php was updated to fix a XSS security issue.
If you use a tool such as TortoiseSVN, you can easily see the commit history.
I checked the SVN and see that there has been updates as late as July 2019 by yrigaud. Not sure if the SVN was compromised or if the changes are valid. Anyone shed some light on the ID or want to run a DIFF on the updated files? The trunk where the updates are shows as v2.3.0 and not 2.3.1
Yves Rigaud used to work for vBulletin (he might still, I'm not certain) and probably uses this himself so it would be a legitimate update.
Unable to install it with vB4.2.5. Tried with PHP 5.6, 7.0, 7.1. The only difference is that with PHP 7.0 & 7.1 I'm getting error:
Code:
Call to undefined method vB_DataManager::vB_DataManager() on line 89 in /home/christer/public_html/includes/class_dm_pt_project.php
#0 /home/christer/public_html/includes/functions.php(196): vB_DataManager_Pt_Project->vB_DataManager_Pt_Project(Object(vB_Registry), 3)
#1 /home/christer/public_html/includes/adminfunctions_plugin.php(1201) : eval()'d code(568): datamanager_init('pt_project', Object(vB_Registry), 3)
#2 /home/christer/public_html/includes/adminfunctions_plugin.php(1201): eval()
#3 /home/christer/public_html/admincp/plugin.php(1755): install_product(' #4 {main}
while with PHP 5.6 I'm not getting any error but system frozes at "Importing Product". I tried with both version available here (minified and not), but again nothing. Also tried a trick that I read somewhere here to import it from server instead from computer. Again nothing.
Any idea where I can find a direct link to download the latest 2.3.0 (or 2.3.1)? Some links that I found simple does not work.
Thank you
Im getting the exact same error on a clean VB installation. Im guessing this mod is dead for new vbulletin versions?
It's a PHP incompatibility error and not related to vBulletin. The call to vB_DataManager::vB_DataManager should be replaced with vB_DataManager::__construct
Yves Rigaud used to work for vBulletin (he might still, I'm not certain) and probably uses this himself so it would be a legitimate update.
Yup, it's me
I know there isn't a lot of updates but all the stuff is still working. The latest fix in the repo is i got someone who tried to do an xss issue with the pagenumber value in the url.
I will try to finish officially that 2.3.0 (2.3.1? It's not even in the milestones ) to be able to release at least all php 7.0/7.1 compatibilities (as vB4 is not php 7.2 compatible, nothing will be done for this php version and higher). I have currently health issues which will need a surgery in less than a week
Interesting as my PT install says 2.3.1 and I know it was nothing that I did. I have attached a copy for of the XML for reference. Anyways were on PHP 7.4.9 and running smoothly...
Still would love to see some sort of update/final release.