Hello Bob
Apparently the number 174 is not an id number but the quantity of permissions listed in the policy.
The process I went through on this most recent test site, which is MODX 2.5.7 and has had never had newspublisher 2 or NewsPublisher 3 installed before....
- Install newspublisher 2.1.0
- As no upgrade was available I installed NewsPublisher 3.0.3
It is interesting to note that although version 3 was not available as an upgrade, when it was installed version 3.0.3, version 2.1.0 disappeared from my list of available packages.
Today, in order to see if I can recreate the original error message I did the following
- Uninstalled and Force Removed NewsPublisher 3.0.3 (when I did this newspublisher 2.1.0 reappeared in my list of packages)
- Uninstalled and Force Removed NewsPublisher 2.1.0 - this caused the NewsPublisher Editor policy to be removed
- Downloaded and installed NewsPublisher 3.0.3 - this generated the installation log shown below
Console running...
Attempting to install package with signature: newspublisher-3.0.3-pl
Package found...now preparing to install.
Grabbing package workspace...
Workspace environment initiated, now installing package...
[Resource Resolver] Could not find parent: NewsPublisher
[Resource Resolver] Could not find parent: NewsPublisher
xPDOVehicle resolver failed: type php (/www/core/packages/newspublisher-3.0.3-pl/modCategory/aec67926ebe9745cd5629d938476708d.accesspolicy.resolver.resolver)
Cannot get the NewsPublisherPolicyTemplate
xPDOVehicle resolver failed: type php (/www/core/packages/newspublisher-3.0.3-pl/modCategory/aec67926ebe9745cd5629d938476708d.accesspolicytemplate.resolver.resolver)
Could not set np_login_id System Settings; Set it manually to the ID of the Login page
Successfully installed package newspublisher-3.0.3-pl
I have been able to recreate this error on a few sites, with MODX version 2.2.5, 2.5.5 and 2.5.7.
Bob, I have resolved the problem on the site that I need to user NewsPublisher on by creating my own policy, so don't pursue this if it is just to help me. But if you want to get the bottom of the problem I am very happy to continue with experiments.
It occurs to me that if you are unable to recreate the problem, and I am able to recreate it on every installation across a range of different versions of MODX, then perhaps it is a problem caused by the configuration of my hosting? Having said that I haven't had a problem with package installation previously. If you think this is a possibility I am happy to set up a test site and provide you with admin/ftp access to it if you would like me to.
