I was running version 0.91 on Windows 10 PC. I could not find any option to check for upgrade.
I downloaded the Windows Installer and ran it. It went smoothly. I have started the trial and the program is rebuilding the library (it might take a few days)
BTW I still cannot not see what has changed to lose access from the LAN & WAN computers!
Another thing I noticed, and I’m not sure if this is intended behavior or the nature of going from Alpha to Beta, but now that PhotoStructure is opening, I noticed I was signed off and moved back to Lite.
I logged in, entered verification code, and I’m still on Lite status.
That’s actually by design: people running the “stable” build won’t upgrade to alpha and beta builds (even if they check for updates). You’ll only upgrade to a new alpha or beta build if you’re already running an alpha or beta.
Have you followed these steps? (maybe that’s not what you’re asking, though?)
Yes I have set PS_EXPOSE_NETWORK_WITHOUT_AUTH to 1. Everything had worked for a few weeks but something has not changed!! Maybe it’s something I have done.
When I subscribed to the Plus plan, I could not see anywhere to add a coupon. Every when paying no obvoius place to add a coupon. I cancelled the plan and tried again. I still couldn’t see to where to add a coupon.
I’ll add a screenshot tomorrow morning pointing out where Stripe put their coupon entry field. (Stripe is PhotoStructure’s payment processor, and they host the billing form).
If you set up a subscription, I can apply the coupon for you retroactively. As long as the coupon is applied before the trial period elapses, the coupon will be respected.
(I actually helped a couple other people with this as well).
$ ./photostructure --version
1.0.0-beta.1
$ node --version
v14.16.0
$ ./start.sh
Please install Node.js v14.16.0 or later
Please refer to <https://photostructure.com/server/photostructure-for-node/>.
You can also visit <https://forum.photostructure.com> for help.
PhotoStructure uses it instead of the default package manager, npm, for a litany of reasons, including speed, repeatability, and because npm install provides no way to silence a bunch of compilation warnings in dependencies and a bunch of other console spam.