Page 2 of 3

Re: Update 4.7a

Posted: Wed Jan 19, 2011 6:37 pm
by jachen
Hi folks

Every update is at risk. Therefore always keep the last good firmware copy stored at /data/transfer/ folder. This enables to go back easily in case the new update turns out to be crap.
It's a matter of about 15 minutes and the old system runs as before.

cheers
jachen

Re: Update 4.7a

Posted: Wed Jan 19, 2011 7:05 pm
by EmjayNet
Yes, I already do that!

But this time when I rolled back, the problem is still there. I assume that once the smbpasswd database has had the user removed thats it, it is removed even if you roll back.

This can only be fixed by Boris, so were stuck with it!!!

Re: Update 4.7a

Posted: Wed Jan 19, 2011 8:53 pm
by Rheintalwetter
how could I do "keep old version" in this directory?

why is it not done automatically by system when upgrading? maybe this could be a suggestion for developer to do this automatically in future versions... :wink:

Re: Update 4.7a

Posted: Wed Jan 19, 2011 9:06 pm
by jachen
I wonder that update 4.7a is still offered for download on the server after all mentioned trouble.
Boris might disable it occasionally.

jachen

Re: Update 4.7a

Posted: Wed Jan 19, 2011 11:50 pm
by admin
just released 4.7b should have this fixed.

Re: Update 4.7a

Posted: Thu Jan 20, 2011 12:05 am
by Rheintalwetter
Thanks a lot!! I'm happy to report it's running again :lol:

Re: Update 4.7a

Posted: Thu Jan 20, 2011 12:08 am
by atlantique44
OK it works thank you for your quick boris :wink:

Re: Update 4.7a

Posted: Thu Jan 20, 2011 11:17 am
by Friese111
4,7 b solved the problem :wink:

Re: Update 4.7a

Posted: Thu Jan 20, 2011 11:49 am
by EmjayNet
Sorted :D :lol: :D

Re: Update 4.7a

Posted: Thu Jan 20, 2011 2:16 pm
by jachen
Since 4.6u no solar data import into WD 10.37Q build 22.
4.6t was the last update where solar import worked.

Don't know where to ask for support on this issue.
Any suggestions?

cheers
jachen

Re: Update 4.7a

Posted: Fri Jan 21, 2011 5:58 pm
by skyewright
jachen wrote:Since 4.6u no solar data import into WD 10.37Q build 22.
4.6t was the last update where solar import worked.
I think I have found the cause.

see: viewtopic.php?f=8&t=8302&p=9412#p9412

A fix for what I have found would need Boris.

Re: Update 4.7a

Posted: Fri Jan 21, 2011 7:05 pm
by jachen
Thank you very much for posting the result of your research.
I "think" Boris is aware of this problem but didn't put it on priority since one can stay with 4.6t until remedy comes.
What I am missing is an acknowledgment of problems and a list of items planed to be fixed in future updates.
Maybe it's somewhere that I just don't know.

cheers
jachen

Re: Update 4.7a

Posted: Fri Jan 21, 2011 7:51 pm
by skyewright
jachen wrote:Thank you very much for posting the result of your research.
I "think" Boris is aware of this problem but didn't put it on priority since one can stay with 4.6t until remedy comes.
I didn't have a solar sensor when the original probelm with the quotes in 4.6u was discovered. The solar only arrived at Christmas, and since then I hadn't had cause to use the test system, otherwise I might have spotted the problem earlier... :(

The "live" system is usually only updated if there is a specific reason such as a feature or fix that I want (same with WD; last time I updated WD on the live system I'd skipped around 2 years of updates!).

Re: Update 4.7a

Posted: Fri Jan 21, 2011 8:46 pm
by jachen
Good advise and makes sense.
I am tuned to update Operating Systems and Appplication Software for reasons of viral and other malware attacks.
Weather sensor logging and weatherstation application software represents a different world. Have to change my
way of thinking.
Have a nice evening.

Re: Update 4.7a

Posted: Fri Jan 21, 2011 8:58 pm
by admin
The missing data on WD import will be fixed with next update. Reason is that meteolog.cgi did not produce syntactically not correct XML code in the past. Triggered by some users having trouble to parse this I changed to correctly formed XML. Unfortunately, WD now doesn't recognize the XML in total (when values are quoted) or in parts (when some brackets are terminated by "/>").

Next update wil produce wrong formatted XML output (but one that WD can import) unless you specify "quotes=1" as parameter, which will result in correctly shaped and quoted XML.

All this trouble has been started by me not using the correct XML specs from the beginning on. sorry... :(