2014

[VERSION] =E2==80=98should=E2=80=99 do that


Regards

Stuart Tremain
IDFK Web Developments
AUSTRALIA
webdna@idfk.com.au




> On 20 Dec 2014, at 9:31 am, Kenneth Grome <ken@webdnasolutions.com> wrote:
>
> I specified "Server" twice, once in the subject and again in= the
> body.=C2=A0 But I could not specify the version number (thus the
> question marks in both the subject and body), here's why:
>
> Chris sent me the first version/build that was supposed to run on
> Ubuntu 14.04.=C2=A0 I discovered a couple bugs after installing and> running it for the first time so I reported these issues.=C2=A0 It
> didn't take him long to fix them both and send me a new build.
>
> However ...
>
> The new build did not come with a version number or a build number
> that I am aware of, so I have no idea how to refer to it -- other
> than to say that it is the first bug-fixed version built and sent
> to me after I first used the new Ubuntu 14.04 installer.
>
> Maybe the take-away here is that WSC can probably do a better job
> of clearly and uniquely numbering every build they produce.=C2=A0 Then=
> we can specify the build number when we have issues to report.
>
> There's another benefit to uniquely numbering each build too:
>
> We will never have to specify "Server" or "FastCGI"=; or platform
> any more because WSC will immediately know which one we are having
> problems with simply by looking at the unique build number we give
> them.
>
> So now I have a question:
>
> Isn't it possible to bury a unique build number inside the
> executable itself, and then run a command that returns that build
> number?
>
> It seems to me that Chris gave me instructions for doing this in
> an earlier version, but as far as I know it is not common
> knowledge.=C2=A0 In fact I have no idea if it would even work on the> latest builds -- but if it does we should all learn how to do it
> -- so we can use a simple command to look up the exact build we
> are having trouble with.
>
> Regards,
> Kenneth Grome
> WebDNA Solutions
> http://ww=w.webdnasolutions.com
> Web Database Systems and Linux Server Management
>
>
> On 12/19/2014 04:03 PM, Donovan Brooke wrote:
>> This was fixed way back in the beta FastCGI, then I believe it
>> was fixed in the Server platform as well (off the top of my
>> head).
>>
>> However, it=E2=80=99s not impossible that a certain build missed t=he
>> fix. That=E2=80=99s why when reporting bugs that you should always=
>> list Server/FastCGI [platform] [version], etc..
>>
>> Donovan
>>
>>
>>
>> On Dec 19, 2014, at 3:54 PM, iPhonzie@G <iphonzie@gmail.com>
>> wrote:
>>
>>> [createdate] hasn=E2=80=99t worked since WebCatalog was ported= to
>>> *nix=E2=80=A6 it has always returned the =E2=80=9Clast opened =date=E2=80=9D rather
>>> than the file creation date. I=E2=80=99m pretty sure I reporte=d this
>>> to Smith Micro a decade ago. I=E2=80=99m running WebDNA 6, so =I
>>> don=E2=80=99t know if it was ever fixed in a more recent build=.
>>>
>>> -- Brian Fries Sent with Airmail
>>>
>>> On December 19, 2014 at 1:40:51 PM, Donovan Brooke
>>> (dbrooke@euca.us) wrote=:
>>>
>>>> Would this be Server or FastCGI?
>>>>
>>>> Donovan
>>>>
>>>>
>>>>
>>>> On Dec 19, 2014, at 1:49 PM, Kenneth Grome
>>>> <ken@webdnas=olutions.com> wrote:
>>>>
>>>>> I'm using a bug-fixed version of WebDNA (Server 8.=?) on
>>>>> Ubuntu 14.04 and I just discovered that [createdate]>>>>> displays today's date on all files inside a [listf=iles]
>>>>> context ... but the [moddate] tag seems to work okay.<=br>>>>>>
>>>>> Regards, Kenneth Grome WebDNA Solutions
>>>>> http://www.webdnasolutions.com Web Database Systems and
>>>>> Linux Server Management
> ---------------------------------------------------------
> This message is sent to you because you are subscribed to
> the mailing list <talk@webdna.us<=/a>>.
> To unsubscribe, E-mail to: <talk-leave@webdna.us>
> archives: http://mail.webdna.us/list/talk@webdna.us
> Bug Reporting: support@webdna.us<=/a>

---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g=t;.
To unsubscribe, E-mail to: <talk=-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us