<div dir="ltr">I've created the empty folders and indeed the error messages no longer appear. Thanks for the comprehensive explanation and simple solution.<br><br>Did I tell you how much I loved WPKG?</div><br><div class="gmail_quote">On Thu Feb 26 2015 at 9:52:38 PM Rainer Meier <<a href="mailto:r.meier@wpkg.org">r.meier@wpkg.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Peter,<br>
<br>
On 26.02.2015 11:58, Peter Gough wrote:<br>
> Firstly can I say 'thank you' for all of the work you've put into this project.<br>
> You have saved me and I imagine others countless hours of<br>
<br>
Thanks. Good to hear and you're very welcome. Although I didn't have as much<br>
time recently to invest in new features and enhancements as I would like to. But<br>
WPKG is still not dead.<br>
<br>
<br>
> I've never previously made any changes to config.xml. The version on my WPKG<br>
> server is from 2009 and I've checked and I didn't make any changes to the one I<br>
> downloaded at that time. I have just copied a more recent version to my dev<br>
> server but I get the same errors. I was under the impression that if wpkg.js,<br>
> hosts.xml, packages.xml and profiles.xml were all in the same folder then all<br>
> would be well.<br>
<br>
This is entirely Ok, even in latest version.<br>
<br>
<br>
> I've always maintained a separate folder for my packages, unsurprisingly called<br>
> 'Packages', which contains individual .xml files for each package but my hosts<br>
> are in the hosts.xml file in the root directory and in the same directory I use<br>
> profiles.xml file to keep info about my profiles.<br>
><br>
> Did something change that means I now need to edit config.xml or other files?<br>
<br>
No. You don't need to.<br>
Let me explain what happened:<br>
In WPKG versions previously WPKG releases the paths to the packages, hosts and<br>
profiles were hard-coded. WPKG was looking up the following locations:<br>
- packages.xml<br>
- packages/*.xml<br>
- hosts.xml<br>
- hosts./*.xml<br>
- profiles.xml<br>
- profiles/*.xml<br>
<br>
WPKG did silently ignore if one of the files/directories did not exist. Now in<br>
one of the latest packages I have introduced the ability to add as many paths to<br>
the search path (XML files or directories) as you would like to. Allowing you to<br>
specify completely different locations (on file system or HTTP servers) as you like.<br>
<br>
In order to keep compatibility the defaults were set to the following values:<br>
<param name='packages_path' value='packages.xml|packages' /><br>
<param name='profiles_path' value='profiles.xml|profiles' /><br>
<param name='hosts_path' value='hosts.xml|hosts' /><br>
<br>
As a result WPKG behavior is exactly the same as in previous versions. Except in<br>
a very small detail. If one of the paths specified within packages_path,<br>
profiles_path or hosts_path does not exist, then WPKG knows that this is an<br>
error since the user on purpose specified a folder/file which does not exist.<br>
While previous versions would also simply have continued without even a warning<br>
if for example the packages/ folder had gone missing. Now WPKG knows that a<br>
missing packages/ folder is an error since you explicitly specified it to read<br>
the packages from there. Though as you noticed the error is logged but does not<br>
cause WPKG to stop.<br>
<br>
Moreover the default distribution package of WPKG comes with empty packages/<br>
profiles/ and hosts/ folders inside the distribution ZIP. Hence there is no<br>
error at all. Though if somebody of course removes one of the folders (as there<br>
are no files within) then of course WPKG prints an error about inconsistent<br>
configuration and folders.<br>
<br>
There are two solutions to this:<br>
- Create missing folders (even emtpy)<br>
- Change configuration to tell WPKG not so use the folders<br>
<br>
The second solution can be achieved by altering config.xml (e.g. for profiles<br>
and hosts):<br>
<param name='packages_path' value='packages.xml|packages' /><br>
<param name='profiles_path' value='profiles.xml' /><br>
<param name='hosts_path' value='hosts.xml' /><br>
<br>
<br>
If you don't want to alter config.xml try just creating hosts/ and profiles/ sub<br>
folders and the error will go away.<br>
<br>
br,<br>
Rainer<br>
</blockquote></div>