Strange package version errors when submitting
Permalink 1 user found helpful
I get some strange fails in the automatic tests when submitting:
Handle matches controller.php
Minimum version matches controller.php
Expected concrete5 Version: 5.6.0.2. Controller concrete5 version: .
Version in listing matches controller.php
Expected package Version: 0.9.5. Controller package version: .
- the package structure seems correct (one directory, my_addon, containing controller.php)
- controller.php is using the correct name convention (MyAddonPackage)
- pkgHandle, pkgVersion and appVersionRequired is set in the controller class.
The only thing I'm doing differently is that I'm setting the above properties in __construct, not directly on the class. Will that mess up the tests? (It should find the package class name anyway, right?) And there are no blocks in the package, just in case that would affect something.
Handle matches controller.php
Minimum version matches controller.php
Expected concrete5 Version: 5.6.0.2. Controller concrete5 version: .
Version in listing matches controller.php
Expected package Version: 0.9.5. Controller package version: .
- the package structure seems correct (one directory, my_addon, containing controller.php)
- controller.php is using the correct name convention (MyAddonPackage)
- pkgHandle, pkgVersion and appVersionRequired is set in the controller class.
The only thing I'm doing differently is that I'm setting the above properties in __construct, not directly on the class. Will that mess up the tests? (It should find the package class name anyway, right?) And there are no blocks in the package, just in case that would affect something.
If you define the values as usual, then overwrite them in the constructor, it will pass the auto tests. Then you just need to justify it to the PRB.
Thanks for the idea, but I solved it with preprocessing to keep things simple. Now the new add-ons are finally passing the tests!
When doing preprocessing, that is a bit of a nuisance. Hope it helps anyone.