From brauer at nordakademie.de Wed Jun 1 09:50:09 2016 From: brauer at nordakademie.de (Johannes Brauer) Date: Wed Jun 1 09:50:14 2016 Subject: [Seaside] administrator/password in (Pharo4, Seaside 3.1) Message-ID: Hi, in Seaside 3.0 I could use the following expression for setting the administrator login: (WADispatcher default entryPointAt: 'config?) preferenceAt: #login put: 'new id'. (WADispatcher default entryPointAt: 'config') preferenceAt: #passwordHash put: (GRPlatform current secureHashFor: 'new id'). I cannot figure out how to do equivalent tasks in Seaside 3.1. Hints are welcome. Johannes -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160601/7c12a16e/attachment-0001.htm From david at tibbe.info Wed Jun 1 17:43:20 2016 From: david at tibbe.info (David Tibbe) Date: Wed Jun 1 17:43:30 2016 Subject: [Seaside] administrator/password in (Pharo4, Seaside 3.1) In-Reply-To: References: Message-ID: <65b3969c-7530-daf0-8a6a-c379d14bd2a8@tibbe.info> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 834 bytes Desc: OpenPGP digital signature Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160601/6cb21eac/signature.pgp From brauer at nordakademie.de Fri Jun 3 17:21:31 2016 From: brauer at nordakademie.de (Johannes Brauer) Date: Fri Jun 3 17:21:35 2016 Subject: [Seaside] administrator/password in (Pharo4, Seaside 3.1)j In-Reply-To: <65b3969c-7530-daf0-8a6a-c379d14bd2a8@tibbe.info> References: <65b3969c-7530-daf0-8a6a-c379d14bd2a8@tibbe.info> Message-ID: Thanks David, that works. But I have another problem. The Seaside dispatcher itself is password protected, but I lost it. How can I reset it? Johannes Am 01.06.2016 um 19:43 schrieb David Tibbe >: Hi Johannes, (WADispatcher default entryPointAt: 'config') preferenceAt: #passwordHash put: (GRPlatform current secureHashFor: 'new id?). I cannot figure out how to do equivalent tasks in Seaside 3.1. It's #handlerAt: instead of #entryPointAt: in Seaside 3.1. (WADispatcher default handlerAt: 'config') preferenceAt: #passwordHash put: (GRPlatform current secureHashFor: 'new id'). BR, David _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160603/92a08b0c/attachment.htm From david at tibbe.info Fri Jun 3 17:43:52 2016 From: david at tibbe.info (David Tibbe) Date: Fri Jun 3 17:44:03 2016 Subject: [Seaside] administrator/password in (Pharo4, Seaside 3.1)j In-Reply-To: References: <65b3969c-7530-daf0-8a6a-c379d14bd2a8@tibbe.info> Message-ID: <1dc030ef-3f1c-3c06-cb5c-03cfd8b85709@tibbe.info> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 834 bytes Desc: OpenPGP digital signature Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160603/169c18ee/signature.pgp From brauer at nordakademie.de Fri Jun 3 18:09:35 2016 From: brauer at nordakademie.de (Johannes Brauer) Date: Fri Jun 3 18:09:39 2016 Subject: [Seaside] administrator/password in (Pharo4, Seaside 3.1)j In-Reply-To: <1dc030ef-3f1c-3c06-cb5c-03cfd8b85709@tibbe.info> References: <65b3969c-7530-daf0-8a6a-c379d14bd2a8@tibbe.info> <1dc030ef-3f1c-3c06-cb5c-03cfd8b85709@tibbe.info> Message-ID: <869F7FE8-942E-4220-9769-5F3A38AA7BB1@nordakademie.de> if I try this I get a WAAttributeNotFound exception for the symbol #passwordHash, also for the symbol #login Joh, > Am 03.06.2016 um 19:43 schrieb David Tibbe : > > Hi Johannes, > > for the default dispatcher (i.e. "/") it's > > WADispatcher default preferenceAt: #passwordHash put: (GRPlatform > current secureHashFor:'new id'). > > only. > > BR, > David > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside From stephan at stack.nl Sat Jun 18 10:06:57 2016 From: stephan at stack.nl (Stephan Eggermont) Date: Sat Jun 18 10:07:05 2016 Subject: [Seaside] Re: Initialisation of componentClass In-Reply-To: <57399C43.7050808@reahl.org> References: <57399C43.7050808@reahl.org> Message-ID: On 16-05-16 12:09, Iwan Vosloo wrote: > Hi there, > > We have an issue related to magritte-seaside. > > When you set the Component to be used on a MADescription, eg: > > descriptionThings > ^ MAToManyRelationDescription new > ... > componentClass: MyFancyTableComponent; > yourself > > .. then there is no way (that I am aware of) to initialize the created > MyFancyTableComponent in a customised way. > There are several ways to do this, and Magritte provides the building blocks to choose the one reducing duplication most. In QCMagritte, we chain the visitors building the form to do e.g. translations and access control. In Magritte 'style' you'd want to prefer a declarative style with properties over coupling the description strongly to the component. Important for your choice in how to do this is also the question of reuse. If you need it once, your first solution, or just a subclass is fine. In a UI that adapts to screen size, you might want to avoid direct numbers and use properties like large, wide, small to direct the layout Stephan From mike at sharedlogic.ca Mon Jun 20 20:02:34 2016 From: mike at sharedlogic.ca (Michael J. Forster) Date: Mon Jun 20 20:42:32 2016 Subject: [Seaside] jQueryMobile for Seaside 3.2.0? Message-ID: <1466452954347-4901968.post@n4.nabble.com> I see the last mention of jQueryMobile on this list was Esteban A. M.'s inquiry in late 2013. Has anyone tried it with Seaside 3.2.0? I ask because I'm interested in using it, but I find installation of the existing version pulls in an older Seaside and dependencies. I would be happy to collaborate or assist with an update to support Seaside 3.2.0 if anyone is interested. Best, Mike -- View this message in context: http://forum.world.st/jQueryMobile-for-Seaside-3-2-0-tp4901968.html Sent from the Seaside General mailing list archive at Nabble.com. From hilaire at drgeo.eu Tue Jun 21 14:46:05 2016 From: hilaire at drgeo.eu (Hilaire) Date: Tue Jun 21 14:46:44 2016 Subject: [Seaside] GRInvalidUtf8Error: Invalid UTF-8 input Message-ID: Hi, I have this pdf file (joined here) which always produce this error when I try to upload it in Seaside. It seems to be true whenever the filename comes with non ascii characters. All in all, it looks likes GRPharoUtf8Codec is wrong in decoding filename with non ascii characters. It happens with Seaside3.1, Pharo4, newest Grease-Pharo30-Core package When using the Seaside Functional Test Suite / Upload test, the same problem occurs. What did I miss? Thanks Hilaire -- Dr. Geo http://drgeo.eu -------------- next part -------------- A non-text attachment was scrubbed... Name: Identit?s certifi?es.pdf Type: application/pdf Size: 7196 bytes Desc: not available Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160621/c260fc75/Identitscertifies-0001.pdf From philippe.marschall at gmail.com Tue Jun 21 17:01:13 2016 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Tue Jun 21 17:01:17 2016 Subject: [Seaside] GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: Message-ID: On Tue, Jun 21, 2016 at 4:46 PM, Hilaire wrote: > Hi, > > I have this pdf file (joined here) which always produce this error when > I try to upload it in Seaside. > > It seems to be true whenever the filename comes with non ascii characters. > > All in all, it looks likes GRPharoUtf8Codec is wrong in decoding > filename with non ascii characters. > > It happens with Seaside3.1, Pharo4, newest Grease-Pharo30-Core package > > When using the Seaside Functional Test Suite / Upload test, the same > problem occurs. > > What did I miss? A stack trace would be helpful so that we know where error happens. Also some other information: - is the web site utf-8? - what adapter do you use? - what's the encoding on the adapter? - what operating system and browser do you use? - I assume the strange language in the file name is french. Super helpful would be a tcpdump of the http session but we can do without. Cheers Philippe From sven at stfx.eu Tue Jun 21 17:15:13 2016 From: sven at stfx.eu (Sven Van Caekenberghe) Date: Tue Jun 21 17:15:19 2016 Subject: [Seaside] GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: Message-ID: It works with pure Zn in Pharo: Will test later with Seaside > On 21 Jun 2016, at 19:01, Philippe Marschall wrote: > > On Tue, Jun 21, 2016 at 4:46 PM, Hilaire wrote: >> Hi, >> >> I have this pdf file (joined here) which always produce this error when >> I try to upload it in Seaside. >> >> It seems to be true whenever the filename comes with non ascii characters. >> >> All in all, it looks likes GRPharoUtf8Codec is wrong in decoding >> filename with non ascii characters. >> >> It happens with Seaside3.1, Pharo4, newest Grease-Pharo30-Core package >> >> When using the Seaside Functional Test Suite / Upload test, the same >> problem occurs. >> >> What did I miss? > > A stack trace would be helpful so that we know where error happens. > > Also some other information: > - is the web site utf-8? > - what adapter do you use? > - what's the encoding on the adapter? > - what operating system and browser do you use? > - I assume the strange language in the file name is french. > > Super helpful would be a tcpdump of the http session but we can do without. > > Cheers > Philippe > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -------------- next part -------------- Skipped content of type multipart/related From hilaire at drgeo.eu Tue Jun 21 17:31:39 2016 From: hilaire at drgeo.eu (Hilaire) Date: Tue Jun 21 17:31:44 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: Message-ID: <576979FB.1020101@drgeo.eu> Hi, Le 21/06/2016 19:01, Philippe Marschall a ?crit : > A stack trace would be helpful so that we know where error happens. Sadly there is no trace as the debugger does not popup. Only this error raised, from GRPharoUtf8Codec>>decode: with a call to the invalidUtf8 method: GRPharoUtf8Codec>>invalidUtf8 GRInvalidUtf8Error signal: 'Invalid UTF-8 input' Strangely no debugger pop up, only the error message printed on the browser, although in other seaside situation I have error. So I insert an halt to have the attached trace. > Also some other information: > - is the web site utf-8? Yes > - what adapter do you use? Type: ZnZincServerAdaptor Port: 8080 Encoding: utf-8 zinc on port 8080 [running] > - what's the encoding on the adapter? > - what operating system and browser do you use? Linux for the server. I experienced the issue with Chrome under Windows and Linux As well Firefox on Linux > - I assume the strange language in the file name is french. Indeed :) Thanks > Super helpful would be a tcpdump of the http session but we can do without. I have to learn to do that. -- Dr. Geo http://drgeo.eu -------------- next part -------------- A non-text attachment was scrubbed... Name: PharoDebug.log.zip Type: application/zip Size: 3031 bytes Desc: not available Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160621/6630a466/PharoDebug.log.zip From marianopeck at gmail.com Tue Jun 21 19:05:55 2016 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue Jun 21 19:05:59 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: <576979FB.1020101@drgeo.eu> References: <576979FB.1020101@drgeo.eu> Message-ID: Hilaire, As the reason of why not having a debugger come up... did you set the development error handler in Seaside configuration? app filter configuration at: #'exceptionHandler' put: WAWalkbackErrorHandler You may have another error handler defined,... Cheers, On Tue, Jun 21, 2016 at 2:31 PM, Hilaire wrote: > Hi, > > Le 21/06/2016 19:01, Philippe Marschall a ?crit : > > A stack trace would be helpful so that we know where error happens. > > Sadly there is no trace as the debugger does not popup. Only this error > raised, from GRPharoUtf8Codec>>decode: with a call to the invalidUtf8 > method: > > GRPharoUtf8Codec>>invalidUtf8 > GRInvalidUtf8Error signal: 'Invalid UTF-8 input' > > Strangely no debugger pop up, only the error message printed on the > browser, although in other seaside situation I have error. So I insert > an halt to have the attached trace. > > > > Also some other information: > > - is the web site utf-8? > > Yes > > > - what adapter do you use? > > Type: ZnZincServerAdaptor > Port: 8080 > Encoding: utf-8 > zinc on port 8080 [running] > > > - what's the encoding on the adapter? > > > > > - what operating system and browser do you use? > > Linux for the server. > I experienced the issue with Chrome under Windows and Linux > As well Firefox on Linux > > > - I assume the strange language in the file name is french. > > Indeed :) > > Thanks > > > > Super helpful would be a tcpdump of the http session but we can do > without. > > I have to learn to do that. > > > -- > Dr. Geo > http://drgeo.eu > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > -- Mariano http://marianopeck.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160621/05d41f5b/attachment.htm From pdebruic at gmail.com Tue Jun 21 19:59:13 2016 From: pdebruic at gmail.com (Paul DeBruicker) Date: Tue Jun 21 20:39:18 2016 Subject: [Seaside] Re: jQueryMobile for Seaside 3.2.0? In-Reply-To: <1466452954347-4901968.post@n4.nabble.com> References: <1466452954347-4901968.post@n4.nabble.com> Message-ID: <1466539153816-4902268.post@n4.nabble.com> Where did you load the configuration from? Do you know how to make a version that would only load Seaside 3.2 packages? If not I can help with that. I'd guess it would work with minimal changes if any. Michael J. Forster wrote > I see the last mention of jQueryMobile on this list was Esteban A. M.'s > inquiry in late 2013. Has anyone tried it with Seaside 3.2.0? > > I ask because I'm interested in using it, but I find installation of the > existing version pulls in an older Seaside and dependencies. I would be > happy to collaborate or assist with an update to support Seaside 3.2.0 if > anyone is interested. > > Best, > > Mike -- View this message in context: http://forum.world.st/jQueryMobile-for-Seaside-3-2-0-tp4901968p4902268.html Sent from the Seaside General mailing list archive at Nabble.com. From pdebruic at gmail.com Wed Jun 22 06:32:27 2016 From: pdebruic at gmail.com (Paul DeBruicker) Date: Wed Jun 22 07:12:35 2016 Subject: [Seaside] Re: jQueryMobile for Seaside 3.2.0? In-Reply-To: <1466452954347-4901968.post@n4.nabble.com> References: <1466452954347-4901968.post@n4.nabble.com> Message-ID: <1466577147265-4902342.post@n4.nabble.com> Hi Michael, I took a few minutes and got it "working" in Pharo 5 with Seaside 3.2.0. The flickr example in ConfigurationOfJQueryMobileSamples works with the change described below. The new repo on smalltalkhub here: http://smalltalkhub.com/#!/~Seaside/JQueryMobile In a cleanr Pharo 5 you can load the example with Metacello new repository:'http://smalltalkhub.com/mc/Seaside/JQueryMobile/main'; configuration: 'JQueryMobileSamples'; version: #stable; load. The two main problems to fix now are: 1. the javascript libraries are from 2012, so they need to be updated along with any changes to the APIs 2. for the flickr example to work, with my level of understanding, you have to modify a core part of Seaside. I'm not sure about the internals but the flickr example works if you change WARenderPhaseContinuation>>#processRendering: and add document scriptGenerator: JQMScriptGenerator new. right after the document is created the example works great. It is likely that there is a configuration option for this I just don't know it. Hope this helps Paul Michael J. Forster wrote > I see the last mention of jQueryMobile on this list was Esteban A. M.'s > inquiry in late 2013. Has anyone tried it with Seaside 3.2.0? > > I ask because I'm interested in using it, but I find installation of the > existing version pulls in an older Seaside and dependencies. I would be > happy to collaborate or assist with an update to support Seaside 3.2.0 if > anyone is interested. > > Best, > > Mike -- View this message in context: http://forum.world.st/jQueryMobile-for-Seaside-3-2-0-tp4901968p4902342.html Sent from the Seaside General mailing list archive at Nabble.com. From philippe.marschall at gmail.com Wed Jun 22 07:40:29 2016 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Wed Jun 22 07:40:32 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: <576979FB.1020101@drgeo.eu> References: <576979FB.1020101@drgeo.eu> Message-ID: On Tue, Jun 21, 2016 at 7:31 PM, Hilaire wrote: > Hi, > > Le 21/06/2016 19:01, Philippe Marschall a ?crit : >> A stack trace would be helpful so that we know where error happens. > > Sadly there is no trace as the debugger does not popup. Only this error > raised, from GRPharoUtf8Codec>>decode: with a call to the invalidUtf8 > method: > > GRPharoUtf8Codec>>invalidUtf8 > GRInvalidUtf8Error signal: 'Invalid UTF-8 input' Ok, it's likely in the server adapter before Seaside actually kicks in then. Can you set a break point in GRPharoUtf8Codec >> #invalidUtf8? My suspect would be ZnZincServerAdaptor >> #convertMultipart: If you can send us the string it's trying to convert that would be helpful. Cheers Philippe From hilaire at drgeo.eu Wed Jun 22 11:33:32 2016 From: hilaire at drgeo.eu (Hilaire) Date: Wed Jun 22 11:33:49 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: <576979FB.1020101@drgeo.eu> Message-ID: Le 22/06/2016 09:40, Philippe Marschall a ?crit : > Ok, it's likely in the server adapter before Seaside actually kicks in > then. Can you set a break point in GRPharoUtf8Codec >> #invalidUtf8? > > My suspect would be ZnZincServerAdaptor >> #convertMultipart: > > If you can send us the string it's trying to convert that would be helpful. The string argument of GRPharoUtf8Codec>>decode: is aString ->'Identit?s certifi?es.pdf' printed as this in the Debugger. As we know Pharo does not use UTF8 internally it is suspect to see an utf8 string correctly printed in Pharo, right? Does it looks like a Latin1 ?: aString asByteArray do: [:each| Transcript show: each hex ; space] 16r49 16r64 16r65 16r6E 16r74 16r69 16r74 16rE9 16r73 16r20 16r63 16r65 16r72 16r74 16r69 16r66 16r69 16rE9 16r65 16r73 16r2E 16r70 16r64 16r66 So indeed, GRPharoUtf8Codec>>decode: already received a decoded utf8 string to latin1, then obviously fail. Now looking back in the stack as you suggested, then decoding already took place at: ZnMimePart>>fileName "Pathnames are often silenty encoded using UTF-8, this is a no-op for ASCII, but will fail on Latin-1 and others" ^ (self detectContentDispositionValue: 'filename') ifNotNil: [ :encodedFileName | encodedFileName asByteArray utf8Decoded ] The timecode of this method is 10/10/2014 from Sven The second place where the decode takes place is (Zinc-Seaside package): ZNZincServerAdaptor>>convertMultipartFileField: part | file | (file := WAFile new) fileName: (self codec decode: part fileName); contentType: part contentType printString; contents: part contents asByteArray. ^ file Timecode is 11/14/2014 from Johan, where the decode was added. This two methods use too different decoding methods (duplication?), one from the Grease package, the other from ZN package. My opinion is the Zinc-Seaside package should not try to decode, or preferably use the ZN decode method (utf8Decoded), but it will bring an error on already decoded string. Hilaire -- Dr. Geo http://drgeo.eu From mike at forsterfamily.ca Wed Jun 22 11:49:46 2016 From: mike at forsterfamily.ca (Michael Forster) Date: Wed Jun 22 11:49:49 2016 Subject: [Seaside] Re: jQueryMobile for Seaside 3.2.0? In-Reply-To: <1466577147265-4902342.post@n4.nabble.com> References: <1466452954347-4901968.post@n4.nabble.com> <1466577147265-4902342.post@n4.nabble.com> Message-ID: On Wed, Jun 22, 2016 at 1:32 AM, Paul DeBruicker wrote: > Hi Michael, > > I took a few minutes and got it "working" in Pharo 5 with Seaside 3.2.0. > The flickr example in ConfigurationOfJQueryMobileSamples works with the > change described below. > > > The new repo on smalltalkhub here: > > http://smalltalkhub.com/#!/~Seaside/JQueryMobile > [...] > > The two main problems to fix now are: > [...] > > Hope this helps > > Paul Hi Paul, Wow. Thank you. I haven't spent enough time with Metacello configurations to get started, so, yes, that does help! I will test that package and look at the potential changes required for the latest JS libraries. Thanks again, Mike From hilaire at drgeo.eu Wed Jun 22 11:57:31 2016 From: hilaire at drgeo.eu (Hilaire) Date: Wed Jun 22 11:57:56 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: <576979FB.1020101@drgeo.eu> Message-ID: My suggestion is to remove the decode: part, this change looks safe as part fileName already decodes. Hilaire Le 22/06/2016 13:33, Hilaire a ?crit : > ZNZincServerAdaptor>>convertMultipartFileField: part > | file | > (file := WAFile new) > fileName: (self codec decode: part fileName); > contentType: part contentType printString; > contents: part contents asByteArray. > ^ file > > Timecode is 11/14/2014 from Johan, where the decode was added. -- Dr. Geo http://drgeo.eu From hilaire at drgeo.eu Wed Jun 22 12:01:10 2016 From: hilaire at drgeo.eu (Hilaire) Date: Wed Jun 22 12:05:15 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: <576979FB.1020101@drgeo.eu> Message-ID: My suggestion is to remove the decode: in this method. I am not sure about the whole implication. Hilaire Le 22/06/2016 13:33, Hilaire a ?crit : > ZNZincServerAdaptor>>convertMultipartFileField: part > | file | > (file := WAFile new) > fileName: (self codec decode: part fileName); > contentType: part contentType printString; > contents: part contents asByteArray. > ^ file > > Timecode is 11/14/2014 from Johan, where the decode was added. -- Dr. Geo http://drgeo.eu From sven at stfx.eu Wed Jun 22 13:28:28 2016 From: sven at stfx.eu (Sven Van Caekenberghe) Date: Wed Jun 22 13:28:31 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: <576979FB.1020101@drgeo.eu> Message-ID: <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> > On 22 Jun 2016, at 14:01, Hilaire wrote: > > My suggestion is to remove the decode: in this method. I think that too. > I am not sure about the whole implication. Me neither ;-) In any case, here is an older discussion about the same topic: http://forum.world.st/File-upload-encoding-issue-tt4783446.html Sven > Hilaire > > Le 22/06/2016 13:33, Hilaire a ?crit : >> ZNZincServerAdaptor>>convertMultipartFileField: part >> | file | >> (file := WAFile new) >> fileName: (self codec decode: part fileName); >> contentType: part contentType printString; >> contents: part contents asByteArray. >> ^ file >> >> Timecode is 11/14/2014 from Johan, where the decode was added. > > -- > Dr. Geo > http://drgeo.eu > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside From hilaire at drgeo.eu Wed Jun 22 19:59:26 2016 From: hilaire at drgeo.eu (Hilaire) Date: Wed Jun 22 19:59:49 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> Message-ID: Indeed, but looking at the time code of the two methods I mentioned (both after this October 2014 discussion), it looks like you guys concurrently fixed the problem in two different parts, but resulting in a mural break :) Hopefully easy to get fixed. But I am surprise this problem did not show up till then. Or is it fixed in newer ZN-* packages? Hilaire Le 22/06/2016 15:28, Sven Van Caekenberghe a ?crit : > Me neither ;-) > > In any case, here is an older discussion about the same topic: > > http://forum.world.st/File-upload-encoding-issue-tt4783446.html > > Sven -- Dr. Geo http://drgeo.eu From sven at stfx.eu Wed Jun 22 20:01:41 2016 From: sven at stfx.eu (Sven Van Caekenberghe) Date: Wed Jun 22 20:01:45 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> Message-ID: <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> I don't remember every detail of the discussions, but by the look of it, your solution seems correct: Zn did already decode it, the Zn adaptor should not do it again. > On 22 Jun 2016, at 21:59, Hilaire wrote: > > Indeed, but looking at the time code of the two methods I mentioned > (both after this October 2014 discussion), it looks like you guys > concurrently fixed the problem in two different parts, but resulting in > a mural break :) Hopefully easy to get fixed. > > But I am surprise this problem did not show up till then. Or is it fixed > in newer ZN-* packages? > > Hilaire > > > > Le 22/06/2016 15:28, Sven Van Caekenberghe a ?crit : >> Me neither ;-) >> >> In any case, here is an older discussion about the same topic: >> >> http://forum.world.st/File-upload-encoding-issue-tt4783446.html >> >> Sven > > -- > Dr. Geo > http://drgeo.eu > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside From hilaire at drgeo.eu Fri Jun 24 15:21:44 2016 From: hilaire at drgeo.eu (Hilaire) Date: Fri Jun 24 15:21:57 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> Message-ID: If one grants me write access, I can commit the change. Of course I would like to know the opinion of Johan, I don't want to break anything. Hilaire Le 22/06/2016 22:01, Sven Van Caekenberghe a ?crit : > I don't remember every detail of the discussions, but by the look of it, your solution seems correct: Zn did already decode it, the Zn adaptor should not do it again. -- Dr. Geo http://drgeo.eu From johan at inceptive.be Sat Jun 25 06:37:28 2016 From: johan at inceptive.be (Johan Brichau) Date: Sat Jun 25 06:37:31 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> Message-ID: Hi Hilaire, I am curious which package version of Zinc-Seaside you are using. I vaguely remember something about fixing an issue in that area but when I look at Zinc-Seaside-JohanBrichau.43 (which is the latest version) the send of #decode: is not there. cheers Johan > On 24 Jun 2016, at 17:21, Hilaire wrote: > > If one grants me write access, I can commit the change. > Of course I would like to know the opinion of Johan, I don't want to > break anything. > > Hilaire > > Le 22/06/2016 22:01, Sven Van Caekenberghe a ?crit : >> I don't remember every detail of the discussions, but by the look of it, your solution seems correct: Zn did already decode it, the Zn adaptor should not do it again. > > -- > Dr. Geo > http://drgeo.eu > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside From hilaire at drgeo.eu Sat Jun 25 06:58:35 2016 From: hilaire at drgeo.eu (Hilaire) Date: Sat Jun 25 06:58:50 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> Message-ID: Hi Johan, When I browse directly from Monticello the Zinc-Seaside-JohanBrichau.43 package I can read the #decode: message. Is it possible you fixed it locally without a commit? The repo I have been using is http://mc.stfx.eu/ZincHTTPComponents Hilaire Le 25/06/2016 08:37, Johan Brichau a ?crit : > Hi Hilaire, > > I am curious which package version of Zinc-Seaside you are using. > > I vaguely remember something about fixing an issue in that area but when I look at Zinc-Seaside-JohanBrichau.43 (which is the latest version) the send of #decode: is not there. > > cheers > Johan -- Dr. Geo http://drgeo.eu From johan at inceptive.be Sat Jun 25 07:16:53 2016 From: johan at inceptive.be (Johan Brichau) Date: Sat Jun 25 07:16:56 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> Message-ID: <77F14221-FB6C-4DEC-B04D-197F7453793A@inceptive.be> Are there multiple package versions out there with the same version number? Can you check if the UUID is the same as the one below? Name: Zinc-Seaside-JohanBrichau.43 Author: JohanBrichau Time: 26 December 2014, 4:00:06.580211 pm UUID: 62fd0b62-9e07-498e-aac8-3432614b39fc Ancestors: Zinc-Seaside-pmm.42 Here is a screenshot when I look at Zinc-Seaside-JohanBrichau.43 in http://mc.stfx.eu/ZincHTTPComponents I am looking at the correct method, right? > On 25 Jun 2016, at 08:58, Hilaire wrote: > > Hi Johan, > > When I browse directly from Monticello the Zinc-Seaside-JohanBrichau.43 > package I can read the #decode: message. > > Is it possible you fixed it locally without a commit? > > The repo I have been using is http://mc.stfx.eu/ZincHTTPComponents > > Hilaire > > Le 25/06/2016 08:37, Johan Brichau a ?crit : >> Hi Hilaire, >> >> I am curious which package version of Zinc-Seaside you are using. >> >> I vaguely remember something about fixing an issue in that area but when I look at Zinc-Seaside-JohanBrichau.43 (which is the latest version) the send of #decode: is not there. >> >> cheers >> Johan > > -- > Dr. Geo > http://drgeo.eu > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -------------- next part -------------- Skipped content of type multipart/related From johan at inceptive.be Sat Jun 25 07:24:41 2016 From: johan at inceptive.be (Johan Brichau) Date: Sat Jun 25 07:24:44 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: <77F14221-FB6C-4DEC-B04D-197F7453793A@inceptive.be> References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> <77F14221-FB6C-4DEC-B04D-197F7453793A@inceptive.be> Message-ID: <3D4B142C-D765-417B-98B8-02B9F7F01245@inceptive.be> Hilaire, I threw away my package cache and notice that I had a different version of the same package? Need to figure out what happened. The commit comment refers to https://code.google.com/p/seaside/issues/detail?id=836 Looking into it and trying to refresh my mind :/ Johan > On 25 Jun 2016, at 09:16, Johan Brichau wrote: > > Are there multiple package versions out there with the same version number? > Can you check if the UUID is the same as the one below? > > Name: Zinc-Seaside-JohanBrichau.43 > Author: JohanBrichau > Time: 26 December 2014, 4:00:06.580211 pm > UUID: 62fd0b62-9e07-498e-aac8-3432614b39fc > Ancestors: Zinc-Seaside-pmm.42 > > Here is a screenshot when I look at Zinc-Seaside-JohanBrichau.43 in http://mc.stfx.eu/ZincHTTPComponents > I am looking at the correct method, right? > > > > >> On 25 Jun 2016, at 08:58, Hilaire > wrote: >> >> Hi Johan, >> >> When I browse directly from Monticello the Zinc-Seaside-JohanBrichau.43 >> package I can read the #decode: message. >> >> Is it possible you fixed it locally without a commit? >> >> The repo I have been using is http://mc.stfx.eu/ZincHTTPComponents >> >> Hilaire >> >> Le 25/06/2016 08:37, Johan Brichau a ?crit : >>> Hi Hilaire, >>> >>> I am curious which package version of Zinc-Seaside you are using. >>> >>> I vaguely remember something about fixing an issue in that area but when I look at Zinc-Seaside-JohanBrichau.43 (which is the latest version) the send of #decode: is not there. >>> >>> cheers >>> Johan >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> _______________________________________________ >> seaside mailing list >> seaside@lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160625/c1b68518/attachment.htm From hilaire at drgeo.eu Sat Jun 25 07:30:20 2016 From: hilaire at drgeo.eu (Hilaire) Date: Sat Jun 25 07:30:38 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: <77F14221-FB6C-4DEC-B04D-197F7453793A@inceptive.be> References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> <77F14221-FB6C-4DEC-B04D-197F7453793A@inceptive.be> Message-ID: Le 25/06/2016 09:16, Johan Brichau a ?crit : > Are there multiple package versions out there with the same version number? > Can you check if the UUID is the same as the one below? The description of the package I have looks strange (see the Time): Name: Zinc-Seaside-JohanBrichau.43 Author: JohanBrichau Time: 22 Juin 2016, 8:25:10.061265 pm UUID: d2edc44e-eebb-454f-b309-f6d49d639770 Ancestors: Zinc-Seaside-pmm.42 When I flush the Monticello cache and refresh, it looks like (the Time is shifted to now): Name: Zinc-Seaside-JohanBrichau.43 Author: JohanBrichau Time: 25 Juin 2016, 8:25:10.061265 pm UUID: d2edc44e-eebb-454f-b309-f6d49d639770 Ancestors: Zinc-Seaside-pmm.42 > Here is a screenshot when I look at Zinc-Seaside-JohanBrichau.43 in > http://mc.stfx.eu/ZincHTTPComponents > I am looking at the correct method, right? Yes. -- Dr. Geo http://drgeo.eu From hilaire at drgeo.eu Sat Jun 25 07:35:48 2016 From: hilaire at drgeo.eu (Hilaire) Date: Sat Jun 25 07:35:59 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: <3D4B142C-D765-417B-98B8-02B9F7F01245@inceptive.be> References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> <77F14221-FB6C-4DEC-B04D-197F7453793A@inceptive.be> <3D4B142C-D765-417B-98B8-02B9F7F01245@inceptive.be> Message-ID: When downloading http://mc.stfx.eu/ZincHTTPComponents/Zinc-Seaside-JohanBrichau.43.mcz and viewing the source code in a text editor, the #decode: message is present in the convertMultipartFileField: method. Hilaire Le 25/06/2016 09:24, Johan Brichau a ?crit : > Hilaire, > > I threw away my package cache and notice that I had a different version > of the same package? > > Need to figure out what happened. The commit comment refers > to https://code.google.com/p/seaside/issues/detail?id=836 > > Looking into it and trying to refresh my mind :/ > > Johan -- Dr. Geo http://drgeo.eu From johan at inceptive.be Sat Jun 25 08:00:10 2016 From: johan at inceptive.be (Johan Brichau) Date: Sat Jun 25 08:00:12 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> <77F14221-FB6C-4DEC-B04D-197F7453793A@inceptive.be> <3D4B142C-D765-417B-98B8-02B9F7F01245@inceptive.be> Message-ID: <05A8B113-2778-4EEB-BA0C-3ECFDC01FFCF@inceptive.be> Hilaire, Your observation that Sven and I both fixed it in different places is correct. I did revert the fix on December 26th but I somehow created the package below with the same version number and it never got uploaded correctly (for reasons I cannot really explain). Name: Zinc-Seaside-JohanBrichau.43 Author: JohanBrichau Time: 26 December 2014, 4:00:06.580211 pm UUID: 62fd0b62-9e07-498e-aac8-3432614b39fc Ancestors: Zinc-Seaside-pmm.42 I already created a new package .44 and will email it to Sven but... The ?funny? part right now is that the upload file test does not break in my image when using the published code for Zinc-Seaside! So? I am a bit baffled and would like to understand first what is going in. Johan > On 25 Jun 2016, at 09:35, Hilaire wrote: > > When downloading > > http://mc.stfx.eu/ZincHTTPComponents/Zinc-Seaside-JohanBrichau.43.mcz > > and viewing the source code in a text editor, the #decode: message is > present in the convertMultipartFileField: method. > > Hilaire > > Le 25/06/2016 09:24, Johan Brichau a ?crit : >> Hilaire, >> >> I threw away my package cache and notice that I had a different version >> of the same package? >> >> Need to figure out what happened. The commit comment refers >> to https://code.google.com/p/seaside/issues/detail?id=836 >> >> Looking into it and trying to refresh my mind :/ >> >> Johan > > -- > Dr. Geo > http://drgeo.eu > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside From johan at inceptive.be Sat Jun 25 08:21:24 2016 From: johan at inceptive.be (Johan Brichau) Date: Sat Jun 25 08:21:26 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: <05A8B113-2778-4EEB-BA0C-3ECFDC01FFCF@inceptive.be> References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> <77F14221-FB6C-4DEC-B04D-197F7453793A@inceptive.be> <3D4B142C-D765-417B-98B8-02B9F7F01245@inceptive.be> <05A8B113-2778-4EEB-BA0C-3ECFDC01FFCF@inceptive.be> Message-ID: <5EE0AA82-A849-4C98-9BCE-33BB64DF3148@inceptive.be> > On 25 Jun 2016, at 10:00, Johan Brichau wrote: > > The ?funny? part right now is that the upload file test does not break in my image when using the published code for Zinc-Seaside! > So? I am a bit baffled and would like to understand first what is going in. I got it... it crashes in Safari, not with Chrome. Obviously, the ?old fix? was wrong and I undid it in December 2016 but the package was never correctly committed (only in my package cache? which I also never cleared apparently in my Seaside work folder?) I sent my package .44 to Sven for publication. Just remove the decode: message send in the adaptor, as you mentioned. thanks for reporting and sorry about the mess Johan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160625/cdc9b7d8/attachment-0001.htm From sven at stfx.eu Sat Jun 25 08:59:19 2016 From: sven at stfx.eu (Sven Van Caekenberghe) Date: Sat Jun 25 08:59:22 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: <5EE0AA82-A849-4C98-9BCE-33BB64DF3148@inceptive.be> References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> <77F14221-FB6C-4DEC-B04D-197F7453793A@inceptive.be> <3D4B142C-D765-417B-98B8-02B9F7F01245@inceptive.be> <05A8B113-2778-4EEB-BA0C-3ECFDC01FFCF@inceptive.be> <5EE0AA82-A849-4C98-9BCE-33BB64DF3148@inceptive.be> Message-ID: <18C39BDF-0DAF-4047-986E-6D34E828DC73@stfx.eu> Very strange and annoying, I copied Johan's .44 version into the official Zn repositories. > On 25 Jun 2016, at 10:21, Johan Brichau wrote: > > >> On 25 Jun 2016, at 10:00, Johan Brichau wrote: >> >> The ?funny? part right now is that the upload file test does not break in my image when using the published code for Zinc-Seaside! >> So? I am a bit baffled and would like to understand first what is going in. > > I got it... it crashes in Safari, not with Chrome. > Obviously, the ?old fix? was wrong and I undid it in December 2016 but the package was never correctly committed (only in my package cache? which I also never cleared apparently in my Seaside work folder?) > > I sent my package .44 to Sven for publication. Just remove the decode: message send in the adaptor, as you mentioned. > > thanks for reporting and sorry about the mess > > Johan > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside From francescoagati1975 at gmail.com Sat Jun 25 12:54:46 2016 From: francescoagati1975 at gmail.com (francescoagati) Date: Sat Jun 25 13:35:17 2016 Subject: [Seaside] Pharo 5, seaside 3.2 and magritte 3 Message-ID: <1466859286755-4903247.post@n4.nabble.com> Hi, i have try yo use magritte 3 and seaside 3.2 inside pharo 5. With seaside works all good. But when i try to install magritte 3. Magritte say that need the seaside html5 canvas package. The error is: 'Error name not found: Seaside-HTML5' These are the packages i use: Metacello new configuration: 'Seaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; version: ?3.2.0'; load Gofer it smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo50'; configurationOf: 'Magritte3'; loadVersion: #stable. There is compatibility between magritte3 and seaside 3.2 on pharo 5? Thanks Francesco -- View this message in context: http://forum.world.st/Pharo-5-seaside-3-2-and-magritte-3-tp4903247.html Sent from the Seaside General mailing list archive at Nabble.com. From hilaire at drgeo.eu Sat Jun 25 13:58:02 2016 From: hilaire at drgeo.eu (Hilaire) Date: Sat Jun 25 13:58:12 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: <18C39BDF-0DAF-4047-986E-6D34E828DC73@stfx.eu> References: <576979FB.1020101@drgeo.eu> <3DB9E35F-1098-4909-9B12-EBA6C1FF7C55@stfx.eu> <2F703392-6E05-4370-881C-3FC32AB0AE17@stfx.eu> <77F14221-FB6C-4DEC-B04D-197F7453793A@inceptive.be> <3D4B142C-D765-417B-98B8-02B9F7F01245@inceptive.be> <05A8B113-2778-4EEB-BA0C-3ECFDC01FFCF@inceptive.be> <5EE0AA82-A849-4C98-9BCE-33BB64DF3148@inceptive.be> <18C39BDF-0DAF-4047-986E-6D34E828DC73@stfx.eu> Message-ID: It is great to see free software in action. Thanks Hilaire Le 25/06/2016 10:59, Sven Van Caekenberghe a ?crit : > Very strange and annoying, I copied Johan's .44 version into the official Zn repositories. -- Dr. Geo http://drgeo.eu From philippe.marschall at gmail.com Sun Jun 26 16:38:30 2016 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Sun Jun 26 16:38:33 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: <576979FB.1020101@drgeo.eu> Message-ID: On Wed, Jun 22, 2016 at 1:33 PM, Hilaire wrote: > > > Le 22/06/2016 09:40, Philippe Marschall a ?crit : >> Ok, it's likely in the server adapter before Seaside actually kicks in >> then. Can you set a break point in GRPharoUtf8Codec >> #invalidUtf8? >> >> My suspect would be ZnZincServerAdaptor >> #convertMultipart: >> >> If you can send us the string it's trying to convert that would be helpful. > > > The string argument of GRPharoUtf8Codec>>decode: > > is > > aString ->'Identit?s certifi?es.pdf' > > printed as this in the Debugger. As we know Pharo does not use UTF8 > internally it is suspect to see an utf8 string correctly printed in > Pharo, right? You are seeing a UTF-8 string that has already been decoded to Pharo/Unicode therefore it displays correctly. Then Seaside/the adaptor tries to decode it a second time which fails. > Does it looks like a Latin1 ?: > > aString asByteArray do: [:each| Transcript show: each hex ; space] > > 16r49 16r64 16r65 16r6E 16r74 16r69 16r74 16rE9 16r73 16r20 16r63 16r65 > 16r72 16r74 16r69 16r66 16r69 16rE9 16r65 16r73 16r2E 16r70 16r64 16r66 > > So indeed, GRPharoUtf8Codec>>decode: already received a decoded utf8 > string to latin1, then obviously fail. Correct. > Now looking back in the stack as you suggested, then decoding already > took place at: > > ZnMimePart>>fileName > "Pathnames are often silenty encoded using UTF-8, > this is a no-op for ASCII, but will fail on Latin-1 and others" > ^ (self detectContentDispositionValue: 'filename') > ifNotNil: [ :encodedFileName | encodedFileName asByteArray utf8Decoded ] > > > The timecode of this method is 10/10/2014 from Sven > > The second place where the decode takes place is (Zinc-Seaside package): > > ZNZincServerAdaptor>>convertMultipartFileField: part > | file | > (file := WAFile new) > fileName: (self codec decode: part fileName); > contentType: part contentType printString; > contents: part contents asByteArray. > ^ file > > Timecode is 11/14/2014 from Johan, where the decode was added. > > > This two methods use too different decoding methods (duplication?), one > from the Grease package, the other from ZN package. > > My opinion is the Zinc-Seaside package should not try to decode, or > preferably use the ZN decode method (utf8Decoded), but it will bring an > error on already decoded string. The output of Zinc-Seaside must be decoded UTF-8 in Pharo encoding. How that is achieved is up to the Zinc-Seaside package. Just to be sure, you are working with an up to date Zinc version? Cheers Philippe From hilaire at drgeo.eu Tue Jun 28 13:31:08 2016 From: hilaire at drgeo.eu (Hilaire) Date: Tue Jun 28 13:31:13 2016 Subject: [Seaside] Re: GRInvalidUtf8Error: Invalid UTF-8 input In-Reply-To: References: <576979FB.1020101@drgeo.eu> Message-ID: <57727C1C.5030000@drgeo.eu> I think we sorted out the problem. See the other discussion in the thread. Thanks Hilaire Le 26/06/2016 18:38, Philippe Marschall a ?crit : > The output of Zinc-Seaside must be decoded UTF-8 in Pharo encoding. > How that is achieved is up to the Zinc-Seaside package. Just to be > sure, you are working with an up to date Zinc version? -- Dr. Geo http://drgeo.eu From pdebruic at gmail.com Thu Jun 30 03:07:29 2016 From: pdebruic at gmail.com (Paul DeBruicker) Date: Thu Jun 30 03:48:32 2016 Subject: [Seaside] Re: Pharo 5, seaside 3.2 and magritte 3 In-Reply-To: <1466859286755-4903247.post@n4.nabble.com> References: <1466859286755-4903247.post@n4.nabble.com> Message-ID: <1467256049795-4904141.post@n4.nabble.com> I don't use magritte but in the ConfigurationOfMagritte you can paste this method and then use the load instructions below it to use Seaside 3.2. version360: spec spec for: #'common' do: [ spec blessing: #'development'. spec description: 'Switch to Seaside 3.2'. spec author: 'PaulDeBruicker'. spec timestamp: '06/29/2016 20:40'. spec project: 'Grease' with: #'release1.2'; project: 'Seaside3' with: #'release3.2'. spec package: 'Magritte-Model' with: 'Magritte-Model-SeanDeNigris.465'; package: 'Magritte-Tests-Model' with: 'Magritte-Tests-Model-DiegoLont.38'; package: 'Magritte-Seaside' with: 'Magritte-Seaside-EstebanMaringolo.359'; package: 'Magritte-Deprecated' with: 'Magritte-Deprecated-NickAger.7' ]. spec for: #'squeakCommon' do: [ spec package: 'Magritte-Tests-Pharo-Model' with: 'Magritte-Tests-Pharo-Model-lr.4'; package: 'Magritte-Pharo-Seaside' with: 'Magritte-Pharo-Seaside-lr.5'; package: 'Magritte-Morph' with: 'Magritte-Morph-SeanDeNigris.95'; package: 'Magritte-Pharo-Tools' with: 'Magritte-Pharo-Tools-NickAger.3' ]. spec for: #'squeak' do: [ spec package: 'Magritte-Pharo-Model' with: 'Magritte-Pharo-Model-NickAger.26' ]. spec for: #(#'pharo1.x' #'pharo2.x') do: [ spec package: 'Magritte-Pharo-Model' with: 'Magritte-Pharo-Model-DiegoLont.39' ]. spec for: #(#'pharo3.x' #'pharo4.x' #'pharo5.x') do: [ spec package: 'Magritte-Pharo3-Model' with: 'Magritte-Pharo3-Model-JohnCBorden.4' ]. spec for: #(#'pharo4.x') do: [ spec project: 'MagritteGlamourForPharo40' with: '1.0'. spec package: 'Magritte-GT' with: 'Magritte-GT-SeanDeNigris.5' ]. spec for: #'gemstone' do: [ spec project: 'GsCore' with: '0.242'. spec package: 'Magritte-GemStone-Model' with: 'Magritte-GemStone-Model-dkh.4'; package: 'Magritte-Tests-GemStone-Model' with: 'Magritte-Tests-GemStone-Model-DaleHenrichs.1'; package: 'Magritte-GemStone-Seaside' with: 'Magritte-GemStone-Seaside-DaleHenrichs.2' ] (ConfigurationOfMagritte3 project version: '3.6.0') load: #('Tests' 'Seaside'). Then the only tests that fail are the ones pertaining to MAStraitMementoTest and thats because that class name is mispelled (should be MAStraightMemento) and the MAStraitMementoTest>>#actualClass method should be MAStraitMementoTest>>#actualClass ^ MAStraightMemento I'd guess that there are some problems in the seaside implementation that could be easily fixed and you'll have an easier time if you run through the tests after changing the MADescriptionEditor class>>#initialize method to open a debugger in the image when an error comes up in the examples like this MADescriptionEditor class>>#initialize " self initialize. " | app | app := WAAdmin register: self asApplicationAt: 'magritte/editor'. app exceptionHandler: WADebugErrorHandler And then trying the examples at 127.0.0.1:8080/magritte/editor If somebody with commit rights to the Magritte repo wanted to make and submit those changes that would be great I know it doesn't answer your question but it should get you down the path to getting everything you need working. Hope this helps Paul francescoagati wrote > Hi, > i have try yo use magritte 3 and seaside 3.2 inside pharo 5. With seaside > works all good. But when i try to install magritte 3. Magritte say that > need the seaside html5 canvas package. > > The error is: > 'Error name not found: Seaside-HTML5' > > These are the packages i use: > > Metacello new > configuration: 'Seaside3'; > repository: > 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > version: ?3.2.0'; > load > > Gofer it > smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo50'; > configurationOf: 'Magritte3'; > loadVersion: #stable. > > There is compatibility between magritte3 and seaside 3.2 on pharo 5? > Thanks > Francesco -- View this message in context: http://forum.world.st/Pharo-5-seaside-3-2-and-magritte-3-tp4903247p4904141.html Sent from the Seaside General mailing list archive at Nabble.com. From mldavis at chaparralwest.com Thu Jun 30 14:33:09 2016 From: mldavis at chaparralwest.com (mldavis@chaparralwest.com) Date: Thu Jun 30 14:33:17 2016 Subject: [Seaside] Seaside Error - No Secure Generator Available Message-ID: <000601d1d2dc$53902a10$fab07e30$@chaparralwest.com> Seaside 3.1 & 3.2 running on Windows 10 Since yesterday, all of my images of Seaside on two different machines are getting this error when I connect to them from http://localhost:8080 : Seaside Walkback ---------------------------------------------------------------------------- ------ WAError: no secure key generator availble because seeding failed Debug Full Stack Stack Trace thisContext WANoSecureKeyGeneratorAvailable class(GRObject class)>>error: self WANoSecureKeyGeneratorAvailable thisContext WANoSecureKeyGeneratorAvailable(GRObject)>>error: self a WANoSecureKeyGeneratorAvailable thisContext WANoSecureKeyGeneratorAvailable>>keyOfLength: self a WANoSecureKeyGeneratorAvailable thisContext WAHashCache>>store: self a WAHashCache thisContext [ cache store: anObject ] in WAMutualExclusionCache>>store: self a WAMutualExclusionCache ---------------------------------------------------------------------------- - The multi image & different machine impact makes me wonder if this was caused by a Windows 10 update, which come without warning now? Can anyone help me? Thanks, mike --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160630/b0e354c4/attachment-0001.htm From mldavis at chaparralwest.com Thu Jun 30 17:34:16 2016 From: mldavis at chaparralwest.com (mldavis@chaparralwest.com) Date: Thu Jun 30 17:34:20 2016 Subject: [Seaside] Seaside Error - No Secure Generator Available In-Reply-To: <38B9975C-DB0B-4EC6-8C5B-BD218468350C@me.com> References: <000601d1d2dc$53902a10$fab07e30$@chaparralwest.com> <38B9975C-DB0B-4EC6-8C5B-BD218468350C@me.com> Message-ID: <008c01d1d2f5$a094c5a0$e1be50e0$@chaparralwest.com> David, Many thanks. I would never have figured this out. It worked exactly as you said, in all my images. Some of these are on different machines and yet, they all suddenly started with this same error, all the same day???? At least two of these have been running for over a week without the error (starting, stopping, making changes etc). I wonder what triggered it.. Anyway thank you so much: It was in Seaside 3.2 loaded into Pharo 5 build 50760 running on Zinc server on Windows 10 latest stable. Regards, mike From: David Pennington [mailto:lhdavid@me.com] Sent: Thursday, June 30, 2016 9:21 AM To: mldavis@chaparralwest.com; Seaside - general discussion Subject: Re: [Seaside] Seaside Error - No Secure Generator Available I had this problem when running seaside in my VAST Smalltalk image. I was advised as follows by Instantiations: I can reproduce this. Looks like Seaside wants to generate random numbers to use as keys for session caches. If a secure RNG (via OpenSSL) is not available in Vast then it produces this walkback...even for http. If it's not found at startup, then it installs a 'WANoSecureKeyGeneratorAvailable' which produces an error when asked for a key. To get around this, try changing the key generator method to the following below. This will force it to fallback to using EsRandom as the RNG. In the meantime, we will revisit this internally to see if we can disconnect the OpenSSL requirement from the session cache keys. Thanks for bringing this up....please let me know if the change described below solves your issue. WANoSecureKeyGeneratorAvailable>>keyOfLength: anInteger ^super keyOfLength: anInteger Long Haired David A.K.A. David Pennington lhdavid@icloud.com On 30 Jun 2016, at 15:33, mldavis@chaparralwest.com wrote: Seaside 3.1 & 3.2 running on Windows 10 Since yesterday, all of my images of Seaside on two different machines are getting this error when I connect to them from http://localhost:8080 : Seaside Walkback ---------------------------------------------------------------------------- ------ WAError: no secure key generator availble because seeding failed Debug Full Stack Stack Trace thisContext WANoSecureKeyGeneratorAvailable class(GRObject class)>>error: self WANoSecureKeyGeneratorAvailable thisContext WANoSecureKeyGeneratorAvailable(GRObject)>>error: self a WANoSecureKeyGeneratorAvailable thisContext WANoSecureKeyGeneratorAvailable>>keyOfLength: self a WANoSecureKeyGeneratorAvailable thisContext WAHashCache>>store: self a WAHashCache thisContext [ cache store: anObject ] in WAMutualExclusionCache>>store: self a WAMutualExclusionCache ---------------------------------------------------------------------------- - The multi image & different machine impact makes me wonder if this was caused by a Windows 10 update, which come without warning now? Can anyone help me? Thanks, mike Virus-free. www.avast.com _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160630/ebf1ae18/attachment.htm From johan at inceptive.be Thu Jun 30 17:45:36 2016 From: johan at inceptive.be (Johan Brichau) Date: Thu Jun 30 17:45:41 2016 Subject: [Seaside] Seaside Error - No Secure Generator Available In-Reply-To: <008c01d1d2f5$a094c5a0$e1be50e0$@chaparralwest.com> References: <000601d1d2dc$53902a10$fab07e30$@chaparralwest.com> <38B9975C-DB0B-4EC6-8C5B-BD218468350C@me.com> <008c01d1d2f5$a094c5a0$e1be50e0$@chaparralwest.com> Message-ID: <213F7E1D-C891-4816-ACE0-C7553427D80A@inceptive.be> Hi, This should only happen if you have Seaside-Security loaded. Can you confirm that this is the case? I don?t have a Windows 10 machine, so it might take some to time figure this one out. Johan > On 30 Jun 2016, at 19:34, mldavis@chaparralwest.com wrote: > > David, > > Many thanks. I would never have figured this out. > > It worked exactly as you said, in all my images. Some of these are on different machines and yet, they all suddenly started with this same error, all the same day???? At least two of these have been running for over a week without the error (starting, stopping, making changes etc). I wonder what triggered it?. > > Anyway thank you so much: It was in Seaside 3.2 loaded into Pharo 5 build 50760 running on Zinc server on Windows 10 latest stable. > > Regards, > > mike > > From: David Pennington [mailto:lhdavid@me.com ] > Sent: Thursday, June 30, 2016 9:21 AM > To: mldavis@chaparralwest.com ; Seaside - general discussion > > Subject: Re: [Seaside] Seaside Error - No Secure Generator Available > > I had this problem when running seaside in my VAST Smalltalk image. I was advised as follows by Instantiations: > > I can reproduce this. > Looks like Seaside wants to generate random numbers to use as keys for session caches. If a secure RNG (via OpenSSL) is not available in Vast then it produces this walkback...even for http. > If it's not found at startup, then it installs a 'WANoSecureKeyGeneratorAvailable' which produces an error when asked for a key. > > To get around this, try changing the key generator method to the following below. This will force it to fallback to using EsRandom as the RNG. > In the meantime, we will revisit this internally to see if we can disconnect the OpenSSL requirement from the session cache keys. > Thanks for bringing this up....please let me know if the change described below solves your issue. > > WANoSecureKeyGeneratorAvailable>>keyOfLength: anInteger > ^super keyOfLength: anInteger > > Long Haired David > A.K.A. David Pennington > lhdavid@icloud.com > > > >> On 30 Jun 2016, at 15:33, mldavis@chaparralwest.com wrote: >> >> Seaside 3.1 & 3.2 running on Windows 10 >> >> Since yesterday, all of my images of Seaside on two different machines are getting this error when I connect to them from http://localhost:8080 : >> >> Seaside Walkback >> >> ---------------------------------------------------------------------------------- >> WAError: no secure key generator availble because seeding failed >> Debug Full Stack >> >> Stack Trace >> thisContext >> WANoSecureKeyGeneratorAvailable class(GRObject class)>>error: >> self >> WANoSecureKeyGeneratorAvailable >> thisContext >> WANoSecureKeyGeneratorAvailable(GRObject)>>error: >> self >> a WANoSecureKeyGeneratorAvailable >> thisContext >> WANoSecureKeyGeneratorAvailable>>keyOfLength: >> self >> a WANoSecureKeyGeneratorAvailable >> thisContext >> WAHashCache>>store: >> self >> a WAHashCache >> thisContext >> [ cache store: anObject ] in WAMutualExclusionCache>>store: >> self >> a WAMutualExclusionCache >> ----------------------------------------------------------------------------- >> >> The multi image & different machine impact makes me wonder if this was caused by a Windows 10 update, which come without warning now? >> >> Can anyone help me? >> >> Thanks, mike >> >> >> Virus-free. www.avast.com >> _______________________________________________ >> seaside mailing list >> seaside@lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > Virus-free. www.avast.com _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160630/9bb4df4a/attachment-0001.htm From marianopeck at gmail.com Thu Jun 30 18:25:42 2016 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Thu Jun 30 18:25:45 2016 Subject: Seaside-Security for GemStone [WAS] Re: [Seaside] Seaside Error - No Secure Generator Available Message-ID: On Thu, Jun 30, 2016 at 2:45 PM, Johan Brichau wrote: > Hi, > > This should only happen if you have Seaside-Security loaded. > Hi Johan, Nice package!! I wasn't aware of it. It contains some nice filters. Do you know if it works in GemStone too (from what I could see in the configuration, it's only for Pharo)? Thanks in advance, Cheers, -- Mariano http://marianopeck.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20160630/66815c0e/attachment.htm