Error on installation

At this stage, the “Error retrieving Subscription data” can be ignored, this is a fallout affect of a prior error.

“Warning: SimpleXMLElement::__construct(): Entity: line 1: parser error : Start tag expected, ‘<‘ not found in /xxxx/wp-content/plugins/ozpost-multiquote/wc-shipping-ozpost.php” can also be ignored for the same reason.

“Warning: SimpleXMLElement::__construct(): Forbidden in /xxxx/wp-content/plugins/ozpost-multiquote/wc-shipping-ozpost.php on line 451”

Now we are onto something – This is a file or folder permissions error – and is the crux of the problem. Solve this and all should be fine.

Although it is the ozpost module that is reporting the error, the actual cause will invariably be traced back to the SimpleXMLElement PHP class.

Sadly, that is about all I can tell you. Although it is going to be impossible for me to fix the problem via the ozpost code, I think I will need to add a check/trap to ensure that SimpleXMLElement class is installed and functional before attempting to use it. This won’t fix the actual problem, but it will allow me create a simpler more user friendly error message.

All of the other errors are a result/fallout of the SimpleXMLElement permissions problem.

“I have also tried to login into the vcsweb server to check the expiration for one of ur clients and requested a lost password but I get nothing so can you check that as well please”.

It is possible the the customer/client doesn’t have an account on the vcsweb server – This is quite common if the subscription(s) were paid for via the PayPal Express checkout.
Furthermore even if they did have an account here and you could log in, you won’t find the information that you are seeking. The VCS servers only handles the accounts (if created) and the subscription payments. The actual subscription details (expiry) are only stored on the srvX.ozpost.net servers – These servers don’t have logins, in fact they don’t even have web=pages. They are ‘back end’ servers only.

There are only two ways you can check the subscription status of any given store – The 1st being what is reported in the admin/settings area of the store. The second is by ‘hand crafting’ a request to the server(s) that will produce an output of the raw xml data that will contain the number of days until expiration. It is the exact same output that you would see if things were working and the DEBUG output enabled.

The ozpost servers will never (intentionally) block access to the server requests regardless of the subscription status – Such access is essential otherwise they can’t tell if a subscription is valid or not.

The ‘hand crafted’ URL will needs to be in the format of
http://svrX.ozpost.net/postage.php?host=My%20Store&storecode=1234

Where “X” can be 0, 1 or 2 (The ozpost system utilises 3 independent servers for redundancy purposes)
The ‘host’ needs to be the name of the store (URL encoded, so spaces become %20 as in the example given), and the final parameter is the postcode defined for the store (This is to differentiate between two stores of the same name in different suburbs).

For Woo, the hostname is the one that is defined as the ‘Site Title’ under the Settings->generalSettings area.

If you enter a host name and/or postcode that doesn’t exist on the ozpost servers a *new* account is automatically created and assigned a 60 day subscription (depending on timezone and server used, this may show as 59 days rather than 60). Please be aware of this if/when trying to check the subscriptions via this method else the 59/60 days could be misleading.

“Did more testing and it seams that I can run the script locally but not on the server. Both locally and on server I am running WP 4.3.1 and php 5.4
The only difference is that I am using xampp on windows as the local server”.

You may need to contact your hosting provider to see what is going amiss with the SimpleXML class. Although it is possible they don’t have it installed I feel this is unlikely as it has been a default install with all PHP versions after V5.1.2. For whatever reason though your site doesn’t have sufficient permissions to use it.

Hopefully this has given you enough info to get things working.

Cheers
Rod.
ps. Our little secret (in a public forum <g>) – but currently the ozpost module for Woo is actually more advanced and supports a courier (Hunter Express) that I’ve not made available to ozpost for the other stores – including ZenCart, which has, until now, always been the 1st with any updates.