Sample zanata.xml and for a project and sample zanata.ini for a user sometimes had different URLs (e.g. http://example.com vs. https://example.com). This was due to the zanata.xml sample using the server configured URL, but the zanata.ini using the current navigation URL.
Zanata clients would not properly associate user configuration from zanata.ini with the server specified in zanata.xml when the defaults from the sample configuration documents were used, leading to errors about missing user configuration information.
The sample zanata.ini was updated to use the server configured URL.
URL is now consistent between zanata.ini and zanata.xml, so clients will properly detect user configuration when default server URLs in sample configuration documents are used.