From jonathan at exit445.com Thu May 7 12:04:49 2015 From: jonathan at exit445.com (Jonathan Schwartz) Date: Thu May 7 12:01:59 2015 Subject: [FX.php List] Section 508 Compliant Web app? Message-ID: <9AFDD3EA-56D5-4724-AA4A-6A265B413616@exit445.com> Has anyone done a web-accesible project that meets Section 508 requirements? http://webaim.org/standards/508/checklist This client requirement popped up at the last moment before getting an agreement signed with a local California State University. While some of the provisions of Section 508 involve applying industry-standard web design practices, most goes beyond. Way beyond. My first reaction is that the time and effort required to implement to these standards involves some *multiple* of effort compared to a non-compliant project. 2x? 3x? 5x? Feedback? Jonathan From bob at patin.com Thu May 7 12:11:46 2015 From: bob at patin.com (Bob Patin) Date: Thu May 7 12:08:53 2015 Subject: [FX.php List] Section 508 Compliant Web app? In-Reply-To: <9AFDD3EA-56D5-4724-AA4A-6A265B413616@exit445.com> References: <9AFDD3EA-56D5-4724-AA4A-6A265B413616@exit445.com> Message-ID: <75675288-102C-4337-9A10-2E88C4F5253A@patin.com> I don't know Section 508, but weren't you declared Section 8? :D Bob Patin Longterm Solutions bob@longtermsolutions.com 615-333-6858 FileMaker 9, 10, 11, 12 & 13 Certified Developer http://www.longtermsolutions.com - iChat: bobpatin@me.com Twitter: bobpatin ? FileMaker Consulting FileMaker Hosting for all versions of FileMaker PHP ? Full email services ? Free DNS hosting ? Colocation ? Consulting > On May 7, 2015, at 2:04 PM, Jonathan Schwartz wrote: > > Has anyone done a web-accesible project that meets Section 508 requirements? > > http://webaim.org/standards/508/checklist > > This client requirement popped up at the last moment before getting an agreement signed with a local California State University. While some of the provisions of Section 508 involve applying industry-standard web design practices, most goes beyond. Way beyond. > > My first reaction is that the time and effort required to implement to these standards involves some *multiple* of effort compared to a non-compliant project. 2x? 3x? 5x? > > Feedback? > > > Jonathan > > > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list From beverlyvoth at gmail.com Thu May 7 13:15:18 2015 From: beverlyvoth at gmail.com (BEVERLY VOTH) Date: Thu May 7 13:12:30 2015 Subject: [FX.php List] Section 508 Compliant Web app? In-Reply-To: <9AFDD3EA-56D5-4724-AA4A-6A265B413616@exit445.com> References: <9AFDD3EA-56D5-4724-AA4A-6A265B413616@exit445.com> Message-ID: <609E0030-4B46-4368-8AE5-8E286D581673@gmail.com> Yes, you need to have your "design" be compatible for Web Accessibility. This links list all the requirements. I'm sure the IWP and WebDirect are not compatible. :) the ideas is to have it ready for screen readers. Another link that might help: Yes, it's a lot of work! beverly On May 7, 2015, at 2:04 PM, Jonathan Schwartz wrote: > Has anyone done a web-accesible project that meets Section 508 requirements? > > http://webaim.org/standards/508/checklist > > This client requirement popped up at the last moment before getting an agreement signed with a local California State University. While some of the provisions of Section 508 involve applying industry-standard web design practices, most goes beyond. Way beyond. > > My first reaction is that the time and effort required to implement to these standards involves some *multiple* of effort compared to a non-compliant project. 2x? 3x? 5x? > > Feedback? > > > Jonathan From dale.bengston at gmail.com Thu May 7 14:55:46 2015 From: dale.bengston at gmail.com (Dale Bengston) Date: Thu May 7 14:52:55 2015 Subject: [FX.php List] Section 508 Compliant Web app? In-Reply-To: <609E0030-4B46-4368-8AE5-8E286D581673@gmail.com> References: <9AFDD3EA-56D5-4724-AA4A-6A265B413616@exit445.com> <609E0030-4B46-4368-8AE5-8E286D581673@gmail.com> Message-ID: <5C67C51E-E082-4D31-8A9C-A7B6C96BE316@gmail.com> Some of the requirements also address color-blindness. Note that most of these standards also increase your search rankings. Dale > On May 7, 2015, at 2:15 PM, BEVERLY VOTH wrote: > > Yes, you need to have your "design" be compatible for Web Accessibility. This links list all the requirements. I'm sure the IWP and WebDirect are not compatible. :) > > the ideas is to have it ready for screen readers. > > Another link that might help: > > Yes, it's a lot of work! > beverly > > On May 7, 2015, at 2:04 PM, Jonathan Schwartz wrote: > >> Has anyone done a web-accesible project that meets Section 508 requirements? >> >> http://webaim.org/standards/508/checklist >> >> This client requirement popped up at the last moment before getting an agreement signed with a local California State University. While some of the provisions of Section 508 involve applying industry-standard web design practices, most goes beyond. Way beyond. >> >> My first reaction is that the time and effort required to implement to these standards involves some *multiple* of effort compared to a non-compliant project. 2x? 3x? 5x? >> >> Feedback? >> >> >> Jonathan > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list From jonathan at exit445.com Thu May 7 15:00:47 2015 From: jonathan at exit445.com (Jonathan Schwartz) Date: Thu May 7 14:57:55 2015 Subject: [FX.php List] Section 508 Compliant Web app? In-Reply-To: <5C67C51E-E082-4D31-8A9C-A7B6C96BE316@gmail.com> References: <9AFDD3EA-56D5-4724-AA4A-6A265B413616@exit445.com> <609E0030-4B46-4368-8AE5-8E286D581673@gmail.com> <5C67C51E-E082-4D31-8A9C-A7B6C96BE316@gmail.com> Message-ID: <0DEC9903-718A-45DE-A2AA-381E35418E1E@exit445.com> Interesting, but not applicable in this case. It?s a password-protected site for students and staff only. J Jonathan Schwartz On May 7, 2015, at 1:55 PM, Dale Bengston wrote: > Some of the requirements also address color-blindness. Note that most of these standards also increase your search rankings. > > Dale > >> On May 7, 2015, at 2:15 PM, BEVERLY VOTH wrote: >> >> Yes, you need to have your "design" be compatible for Web Accessibility. This links list all the requirements. I'm sure the IWP and WebDirect are not compatible. :) >> >> the ideas is to have it ready for screen readers. >> >> Another link that might help: >> >> Yes, it's a lot of work! >> beverly >> >> On May 7, 2015, at 2:04 PM, Jonathan Schwartz wrote: >> >>> Has anyone done a web-accesible project that meets Section 508 requirements? >>> >>> http://webaim.org/standards/508/checklist >>> >>> This client requirement popped up at the last moment before getting an agreement signed with a local California State University. While some of the provisions of Section 508 involve applying industry-standard web design practices, most goes beyond. Way beyond. >>> >>> My first reaction is that the time and effort required to implement to these standards involves some *multiple* of effort compared to a non-compliant project. 2x? 3x? 5x? >>> >>> Feedback? >>> >>> >>> Jonathan >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list From tim.webko at gmail.com Thu May 7 15:50:46 2015 From: tim.webko at gmail.com (Tim 'Webko' Booth) Date: Thu May 7 15:47:53 2015 Subject: [FX.php List] Section 508 Compliant Web app? In-Reply-To: <0DEC9903-718A-45DE-A2AA-381E35418E1E@exit445.com> References: <9AFDD3EA-56D5-4724-AA4A-6A265B413616@exit445.com> <609E0030-4B46-4368-8AE5-8E286D581673@gmail.com> <5C67C51E-E082-4D31-8A9C-A7B6C96BE316@gmail.com> <0DEC9903-718A-45DE-A2AA-381E35418E1E@exit445.com> Message-ID: Dear Johnathan, Staff and students can and probably do have accessibility issues as well - I know when I was webmaster at the University of Sydney I had to adhere to all relevant accessibility standards... Cheers Webko On 8 May 2015 at 07:00, Jonathan Schwartz wrote: > Interesting, but not applicable in this case. It?s a password-protected > site for students and staff only. > > J > > Jonathan Schwartz > > > > > On May 7, 2015, at 1:55 PM, Dale Bengston wrote: > > > Some of the requirements also address color-blindness. Note that most of > these standards also increase your search rankings. > > > > Dale > > > >> On May 7, 2015, at 2:15 PM, BEVERLY VOTH wrote: > >> > >> Yes, you need to have your "design" be compatible for Web > Accessibility. This links list all the requirements. I'm sure the IWP and > WebDirect are not compatible. :) > >> > >> the ideas is to have it ready for screen readers. > >> > >> Another link that might help: < > https://wiki.whatwg.org/wiki/Accessibility> > >> > >> Yes, it's a lot of work! > >> beverly > >> > >> On May 7, 2015, at 2:04 PM, Jonathan Schwartz > wrote: > >> > >>> Has anyone done a web-accesible project that meets Section 508 > requirements? > >>> > >>> http://webaim.org/standards/508/checklist > >>> > >>> This client requirement popped up at the last moment before getting an > agreement signed with a local California State University. While some of > the provisions of Section 508 involve applying industry-standard web design > practices, most goes beyond. Way beyond. > >>> > >>> My first reaction is that the time and effort required to implement to > these standards involves some *multiple* of effort compared to a > non-compliant project. 2x? 3x? 5x? > >>> > >>> Feedback? > >>> > >>> > >>> Jonathan > >> _______________________________________________ > >> FX.php_List mailing list > >> FX.php_List@mail.iviking.org > >> http://www.iviking.org/mailman/listinfo/fx.php_list > > > > _______________________________________________ > > FX.php_List mailing list > > FX.php_List@mail.iviking.org > > http://www.iviking.org/mailman/listinfo/fx.php_list > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.iviking.org/pipermail/fx.php_list/attachments/20150508/497ee91d/attachment.html From jonathan at exit445.com Thu May 7 16:04:53 2015 From: jonathan at exit445.com (Jonathan Schwartz) Date: Thu May 7 16:02:09 2015 Subject: [FX.php List] Section 508 Compliant Web app? In-Reply-To: References: <9AFDD3EA-56D5-4724-AA4A-6A265B413616@exit445.com> <609E0030-4B46-4368-8AE5-8E286D581673@gmail.com> <5C67C51E-E082-4D31-8A9C-A7B6C96BE316@gmail.com> <0DEC9903-718A-45DE-A2AA-381E35418E1E@exit445.com> Message-ID: <375D5694-9A6A-48BE-B82A-B12D2BBB6194@exit445.com> Tim, Agreed. The ?Not Applicable? comment was in regards to search engine performance. Not having worked with Section 508 before, it?s hard to estimate the amount of extra time needed to generate compliant code. Again, I?m thinking that it is some multiple of the original estimate, versus an incremental amount. Jonathan Schwartz jonathan@exit445.com On May 7, 2015, at 2:50 PM, Tim 'Webko' Booth wrote: > Dear Johnathan, > > Staff and students can and probably do have accessibility issues as well - I know when I was webmaster at the University of Sydney I had to adhere to all relevant accessibility standards... > > Cheers > > Webko > > On 8 May 2015 at 07:00, Jonathan Schwartz wrote: > Interesting, but not applicable in this case. It?s a password-protected site for students and staff only. > > J > > Jonathan Schwartz > > > > > On May 7, 2015, at 1:55 PM, Dale Bengston wrote: > > > Some of the requirements also address color-blindness. Note that most of these standards also increase your search rankings. > > > > Dale > > > >> On May 7, 2015, at 2:15 PM, BEVERLY VOTH wrote: > >> > >> Yes, you need to have your "design" be compatible for Web Accessibility. This links list all the requirements. I'm sure the IWP and WebDirect are not compatible. :) > >> > >> the ideas is to have it ready for screen readers. > >> > >> Another link that might help: > >> > >> Yes, it's a lot of work! > >> beverly > >> > >> On May 7, 2015, at 2:04 PM, Jonathan Schwartz wrote: > >> > >>> Has anyone done a web-accesible project that meets Section 508 requirements? > >>> > >>> http://webaim.org/standards/508/checklist > >>> > >>> This client requirement popped up at the last moment before getting an agreement signed with a local California State University. While some of the provisions of Section 508 involve applying industry-standard web design practices, most goes beyond. Way beyond. > >>> > >>> My first reaction is that the time and effort required to implement to these standards involves some *multiple* of effort compared to a non-compliant project. 2x? 3x? 5x? > >>> > >>> Feedback? > >>> > >>> > >>> Jonathan > >> _______________________________________________ > >> FX.php_List mailing list > >> FX.php_List@mail.iviking.org > >> http://www.iviking.org/mailman/listinfo/fx.php_list > > > > _______________________________________________ > > FX.php_List mailing list > > FX.php_List@mail.iviking.org > > http://www.iviking.org/mailman/listinfo/fx.php_list > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list From tim.webko at gmail.com Thu May 7 16:15:54 2015 From: tim.webko at gmail.com (Tim 'Webko' Booth) Date: Thu May 7 16:13:02 2015 Subject: [FX.php List] Section 508 Compliant Web app? In-Reply-To: <375D5694-9A6A-48BE-B82A-B12D2BBB6194@exit445.com> References: <9AFDD3EA-56D5-4724-AA4A-6A265B413616@exit445.com> <609E0030-4B46-4368-8AE5-8E286D581673@gmail.com> <5C67C51E-E082-4D31-8A9C-A7B6C96BE316@gmail.com> <0DEC9903-718A-45DE-A2AA-381E35418E1E@exit445.com> <375D5694-9A6A-48BE-B82A-B12D2BBB6194@exit445.com> Message-ID: In my experience, there's a bit of effort to make the original 'html template' for the site compliant - then it's really not much more difficult after that. I always run my pages through the W3C Checker during development - saves a lot of time down the track. IMHO - it's less effort to make the pages compliant than, say, designing for IE6 (which I was forced to do for a particular project a while back... *shudder*) Cheers Webko On 8 May 2015 at 08:04, Jonathan Schwartz wrote: > Tim, > > Agreed. The ?Not Applicable? comment was in regards to search engine > performance. > > Not having worked with Section 508 before, it?s hard to estimate the > amount of extra time needed to generate compliant code. Again, I?m > thinking that it is some multiple of the original estimate, versus an > incremental amount. > > Jonathan Schwartz > jonathan@exit445.com > > > > On May 7, 2015, at 2:50 PM, Tim 'Webko' Booth wrote: > > > Dear Johnathan, > > > > Staff and students can and probably do have accessibility issues as well > - I know when I was webmaster at the University of Sydney I had to adhere > to all relevant accessibility standards... > > > > Cheers > > > > Webko > > > > On 8 May 2015 at 07:00, Jonathan Schwartz wrote: > > Interesting, but not applicable in this case. It?s a password-protected > site for students and staff only. > > > > J > > > > Jonathan Schwartz > > > > > > > > > > On May 7, 2015, at 1:55 PM, Dale Bengston > wrote: > > > > > Some of the requirements also address color-blindness. Note that most > of these standards also increase your search rankings. > > > > > > Dale > > > > > >> On May 7, 2015, at 2:15 PM, BEVERLY VOTH > wrote: > > >> > > >> Yes, you need to have your "design" be compatible for Web > Accessibility. This links list all the requirements. I'm sure the IWP and > WebDirect are not compatible. :) > > >> > > >> the ideas is to have it ready for screen readers. > > >> > > >> Another link that might help: < > https://wiki.whatwg.org/wiki/Accessibility> > > >> > > >> Yes, it's a lot of work! > > >> beverly > > >> > > >> On May 7, 2015, at 2:04 PM, Jonathan Schwartz > wrote: > > >> > > >>> Has anyone done a web-accesible project that meets Section 508 > requirements? > > >>> > > >>> http://webaim.org/standards/508/checklist > > >>> > > >>> This client requirement popped up at the last moment before getting > an agreement signed with a local California State University. While some > of the provisions of Section 508 involve applying industry-standard web > design practices, most goes beyond. Way beyond. > > >>> > > >>> My first reaction is that the time and effort required to implement > to these standards involves some *multiple* of effort compared to a > non-compliant project. 2x? 3x? 5x? > > >>> > > >>> Feedback? > > >>> > > >>> > > >>> Jonathan > > >> _______________________________________________ > > >> FX.php_List mailing list > > >> FX.php_List@mail.iviking.org > > >> http://www.iviking.org/mailman/listinfo/fx.php_list > > > > > > _______________________________________________ > > > FX.php_List mailing list > > > FX.php_List@mail.iviking.org > > > http://www.iviking.org/mailman/listinfo/fx.php_list > > > > _______________________________________________ > > FX.php_List mailing list > > FX.php_List@mail.iviking.org > > http://www.iviking.org/mailman/listinfo/fx.php_list > > > > _______________________________________________ > > FX.php_List mailing list > > FX.php_List@mail.iviking.org > > http://www.iviking.org/mailman/listinfo/fx.php_list > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.iviking.org/pipermail/fx.php_list/attachments/20150508/ccbb88fa/attachment-0001.html From beverlyvoth at gmail.com Thu May 7 16:22:49 2015 From: beverlyvoth at gmail.com (BEVERLY VOTH) Date: Thu May 7 16:20:00 2015 Subject: [FX.php List] Section 508 Compliant Web app? In-Reply-To: <375D5694-9A6A-48BE-B82A-B12D2BBB6194@exit445.com> References: <9AFDD3EA-56D5-4724-AA4A-6A265B413616@exit445.com> <609E0030-4B46-4368-8AE5-8E286D581673@gmail.com> <5C67C51E-E082-4D31-8A9C-A7B6C96BE316@gmail.com> <0DEC9903-718A-45DE-A2AA-381E35418E1E@exit445.com> <375D5694-9A6A-48BE-B82A-B12D2BBB6194@exit445.com> Message-ID: <0039A107-802A-4F63-AA01-38DFEF99FE07@gmail.com> When I worked with the Tx School for the Blind, the design was not "pretty", but was highly functional. Mostly you throw out the fancy stuff and make it like old HTML (early versions). Keep, mostly, in mind that screen readers go top to bottom and left to right. Columns will not allow for easy reading. And 'alt' everything that is not 'readable' text. Beverly On May 7, 2015, at 6:04 PM, Jonathan Schwartz wrote: > Tim, > > Agreed. The ?Not Applicable? comment was in regards to search engine performance. > > Not having worked with Section 508 before, it?s hard to estimate the amount of extra time needed to generate compliant code. Again, I?m thinking that it is some multiple of the original estimate, versus an incremental amount. > > Jonathan Schwartz > jonathan@exit445.com > > > > On May 7, 2015, at 2:50 PM, Tim 'Webko' Booth wrote: > >> Dear Johnathan, >> >> Staff and students can and probably do have accessibility issues as well - I know when I was webmaster at the University of Sydney I had to adhere to all relevant accessibility standards... >> >> Cheers >> >> Webko >> >> On 8 May 2015 at 07:00, Jonathan Schwartz wrote: >> Interesting, but not applicable in this case. It?s a password-protected site for students and staff only. >> >> J >> >> Jonathan Schwartz >> >> >> >> >> On May 7, 2015, at 1:55 PM, Dale Bengston wrote: >> >>> Some of the requirements also address color-blindness. Note that most of these standards also increase your search rankings. >>> >>> Dale >>> >>>> On May 7, 2015, at 2:15 PM, BEVERLY VOTH wrote: >>>> >>>> Yes, you need to have your "design" be compatible for Web Accessibility. This links list all the requirements. I'm sure the IWP and WebDirect are not compatible. :) >>>> >>>> the ideas is to have it ready for screen readers. >>>> >>>> Another link that might help: >>>> >>>> Yes, it's a lot of work! >>>> beverly >>>> >>>> On May 7, 2015, at 2:04 PM, Jonathan Schwartz wrote: >>>> >>>>> Has anyone done a web-accesible project that meets Section 508 requirements? >>>>> >>>>> http://webaim.org/standards/508/checklist >>>>> >>>>> This client requirement popped up at the last moment before getting an agreement signed with a local California State University. While some of the provisions of Section 508 involve applying industry-standard web design practices, most goes beyond. Way beyond. >>>>> >>>>> My first reaction is that the time and effort required to implement to these standards involves some *multiple* of effort compared to a non-compliant project. 2x? 3x? 5x? >>>>> >>>>> Feedback? >>>>> >>>>> >>>>> Jonathan >>>> _______________________________________________ >>>> FX.php_List mailing list >>>> FX.php_List@mail.iviking.org >>>> http://www.iviking.org/mailman/listinfo/fx.php_list >>> >>> _______________________________________________ >>> FX.php_List mailing list >>> FX.php_List@mail.iviking.org >>> http://www.iviking.org/mailman/listinfo/fx.php_list >> >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list >> >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list From malcolm at notyourhomework.net Mon May 11 14:19:48 2015 From: malcolm at notyourhomework.net (Malcolm Fitzgerald) Date: Mon May 11 14:16:46 2015 Subject: [FX.php List] Referencing output from fmresultset when element names contain hyphens Message-ID: <55510EE4.80401@notyourhomework.net> [ not strictly an FX question ] I've just fired a query at FMS requesting a reply in the fmresultset grammar and I'm using SimpleXML to handle the result. I dump everything into a variable called $fmresultset. This is fine and works well, until I want to look at the metadata, which looks like this. metadata->field-definition as $fld ) foreach ( $fmresultset->field-definition as $fld ) Neither works. How do I handle the hyphen? Malcolm From malcolm at notyourhomework.net Mon May 11 16:21:43 2015 From: malcolm at notyourhomework.net (Malcolm Fitzgerald) Date: Mon May 11 16:18:58 2015 Subject: [FX.php List] Referencing output from fmresultset when element names contain hyphens In-Reply-To: <55510EE4.80401@notyourhomework.net> References: <55510EE4.80401@notyourhomework.net> Message-ID: <55512B77.6070204@notyourhomework.net> On 12/05/2015 8:19 am, Malcolm Fitzgerald wrote: > [ not strictly an FX question ] > > I've just fired a query at FMS requesting a reply in the fmresultset > grammar and I'm using SimpleXML to handle the result. I dump > everything into a variable called $fmresultset. > > This is fine and works well, until I want to look at the metadata, > which looks like this. > > > > I'd like to use a foreach loop to build a table from the field > definitions and it should be as simple as this: > > foreach ( $fmresultset->metadata->field-definition as $fld ) > foreach ( $fmresultset->field-definition as $fld ) > > Neither works. How do I handle the hyphen? $fmresultset->{'field-definition'} $fmresultset->{'field-definition'}['name'] malcolm From chris at iViking.org Tue May 19 16:28:54 2015 From: chris at iViking.org (Chris Hansen) Date: Tue May 19 16:27:43 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php Message-ID: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> Hey Folks, I'm going to have to update my server hardware to test compatibility between FMS14 and FX.php, but I have started to receive questions about compatibility. Rather than wait for me to get around to a hardware upgrade (up to my ears in alligators right now...), I have a few questions for all y'all: 1) Has anyone tested FMS14 with FX.php? 2) For anyone who has, any particular observations, gotchas, etc.? 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 is still fixed in FMS14? Thanks! --Chris From bob at patin.com Tue May 19 16:35:06 2015 From: bob at patin.com (Bob Patin) Date: Tue May 19 16:35:10 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php In-Reply-To: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> References: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> Message-ID: <694D0620-F550-4F36-A52D-83FE5FEC9133@patin.com> I plan to put up a FMS14 server soon and will report back on how things go... Bob Patin Longterm Solutions bob@longtermsolutions.com 615-333-6858 FileMaker 9, 10, 11, 12 & 13 Certified Developer http://www.longtermsolutions.com - iChat: bobpatin@me.com Twitter: bobpatin ? FileMaker Consulting FileMaker Hosting for all versions of FileMaker PHP ? Full email services ? Free DNS hosting ? Colocation ? Consulting > On May 19, 2015, at 5:28 PM, Chris Hansen wrote: > > Hey Folks, > > I'm going to have to update my server hardware to test compatibility between FMS14 and FX.php, but I have started to receive questions about compatibility. Rather than wait for me to get around to a hardware upgrade (up to my ears in alligators right now...), I have a few questions for all y'all: > > 1) Has anyone tested FMS14 with FX.php? > > 2) For anyone who has, any particular observations, gotchas, etc.? > > 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 is still fixed in FMS14? > > Thanks! > > --Chris_______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list From jmaymailing at pointinspace.com Tue May 19 18:03:58 2015 From: jmaymailing at pointinspace.com (John May) Date: Tue May 19 18:04:01 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php In-Reply-To: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> References: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> Message-ID: <555BCF6E.4000100@pointinspace.com> I haven't tested, but can you detail the XML bug that was fixed in 13, and which rev fixed it? - John On 5/19/15 6:28 PM, Chris Hansen wrote: > Hey Folks, > > I'm going to have to update my server hardware to test compatibility > between FMS14 and FX.php, but I have started to receive questions > about compatibility. Rather than wait for me to get around to a > hardware upgrade (up to my ears in alligators right now...), I have a > few questions for all y'all: > > 1) Has anyone tested FMS14 with FX.php? > > 2) For anyone who has, any particular observations, gotchas, etc.? > > 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 > is still fixed in FMS14? > > Thanks! > > --Chris_______________________________________________ FX.php_List > mailing list FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > -- ------------------------------------------------------------------- John May : President http://www.pointinspace.com/ Point In Space Internet Solutions 800.664.8610 919.338.8198 Professional FileMaker Pro, MySQL, PHP & Lasso Hosting on shared, virtual and hardware dedicated servers From chris at iViking.org Tue May 19 20:52:09 2015 From: chris at iViking.org (Chris Hansen) Date: Tue May 19 20:50:57 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php In-Reply-To: <555BCF6E.4000100@pointinspace.com> References: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> <555BCF6E.4000100@pointinspace.com> Message-ID: <8AC14935-A2C7-42E5-95AD-A770B2739DEF@iViking.org> Hey John, It's the XML bug that made the 'FMAlt' datatype (and associated coding) necessary in FX.php when working with portals. Basically, when using FMPXMLRESULT, it would only output one field in a portal for each one that contained data -- so if you had a portal row with an empty value, everything in the field after that empty record value would be off. I called attention to it in an early release of FMS11 (before official release) and it was fixed, but then reappeared in FMS12, and remained most of the way through FMS13. It was fixed in the last couple of months, though the fix is not acknowledged in any of the version notes that I've looked at. Many of those on the list have fought with it and/or reported it to FMI. The reason that I'm wondering whether it's fixed in FMS14, is that the fix appeared when 14 was nearly complete... Best, --Chris > On May 19, 2015, at 6:03 PM, John May wrote: > > I haven't tested, but can you detail the XML bug that was fixed in 13, and which rev fixed it? > > - John > > > On 5/19/15 6:28 PM, Chris Hansen wrote: >> Hey Folks, >> >> I'm going to have to update my server hardware to test compatibility >> between FMS14 and FX.php, but I have started to receive questions >> about compatibility. Rather than wait for me to get around to a >> hardware upgrade (up to my ears in alligators right now...), I have a >> few questions for all y'all: >> >> 1) Has anyone tested FMS14 with FX.php? >> >> 2) For anyone who has, any particular observations, gotchas, etc.? >> >> 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 >> is still fixed in FMS14? >> >> Thanks! >> >> --Chris_______________________________________________ FX.php_List >> mailing list FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list >> > -- > > ------------------------------------------------------------------- > John May : President http://www.pointinspace.com/ > Point In Space Internet Solutions 800.664.8610 919.338.8198 > > Professional FileMaker Pro, MySQL, PHP & Lasso Hosting > on shared, virtual and hardware dedicated servers > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > From ted-fitzgerald at uiowa.edu Wed May 20 05:33:26 2015 From: ted-fitzgerald at uiowa.edu (Fitzgerald, Theodore C) Date: Wed May 20 05:33:30 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php In-Reply-To: <8AC14935-A2C7-42E5-95AD-A770B2739DEF@iViking.org> References: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> <555BCF6E.4000100@pointinspace.com>, <8AC14935-A2C7-42E5-95AD-A770B2739DEF@iViking.org> Message-ID: This bug is supposed to be fixed in 13? Do you know which version? Running 13v09 right now. I'll have to do some testing. I just finished a very bare bones codeigniter / fxphp install and pointed it towards FMS14 and didn't see anything out of the ordinary right away. I'm working on moving a more complex app (that I have to use fmalt with) over to 14 and will let you know how it goes... Ted ________________________________________ From: fx.php_list-bounces@mail.iviking.org [fx.php_list-bounces@mail.iviking.org] on behalf of Chris Hansen [chris@iViking.org] Sent: Tuesday, May 19, 2015 9:52 PM To: FX.php Discussion List Subject: Re: [FX.php List] FileMaker Server 14 and FX.php Hey John, It's the XML bug that made the 'FMAlt' datatype (and associated coding) necessary in FX.php when working with portals. Basically, when using FMPXMLRESULT, it would only output one field in a portal for each one that contained data -- so if you had a portal row with an empty value, everything in the field after that empty record value would be off. I called attention to it in an early release of FMS11 (before official release) and it was fixed, but then reappeared in FMS12, and remained most of the way through FMS13. It was fixed in the last couple of months, though the fix is not acknowledged in any of the version notes that I've looked at. Many of those on the list have fought with it and/or reported it to FMI. The reason that I'm wondering whether it's fixed in FMS14, is that the fix appeared when 14 was nearly complete... Best, --Chris > On May 19, 2015, at 6:03 PM, John May wrote: > > I haven't tested, but can you detail the XML bug that was fixed in 13, and which rev fixed it? > > - John > > > On 5/19/15 6:28 PM, Chris Hansen wrote: >> Hey Folks, >> >> I'm going to have to update my server hardware to test compatibility >> between FMS14 and FX.php, but I have started to receive questions >> about compatibility. Rather than wait for me to get around to a >> hardware upgrade (up to my ears in alligators right now...), I have a >> few questions for all y'all: >> >> 1) Has anyone tested FMS14 with FX.php? >> >> 2) For anyone who has, any particular observations, gotchas, etc.? >> >> 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 >> is still fixed in FMS14? >> >> Thanks! >> >> --Chris_______________________________________________ FX.php_List >> mailing list FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list >> > -- > > ------------------------------------------------------------------- > John May : President http://www.pointinspace.com/ > Point In Space Internet Solutions 800.664.8610 919.338.8198 > > Professional FileMaker Pro, MySQL, PHP & Lasso Hosting > on shared, virtual and hardware dedicated servers > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > _______________________________________________ FX.php_List mailing list FX.php_List@mail.iviking.org http://www.iviking.org/mailman/listinfo/fx.php_list From tcmeyers at troymeyers.com Thu May 21 11:53:44 2015 From: tcmeyers at troymeyers.com (Troy Meyers) Date: Thu May 21 11:53:52 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php Message-ID: <49160262.A9B6.4E43.AC7A.B72CE60F2E55@111.1267459> Chris, I'm just now setting up a FileMaker Server 14 for testing with the goal of switching to it. I skipped switching to Server 13 even though we are using FMP and FMPA 13 and Go 13. So, the most modern Server setup is with FMS 12, and using the FMAlt data type with FX. I'll be using Server 14 as a single-machine setup, but have FX and Apache and PHP on a separate Mac-mini machine that pulls the data out of Server 14 via XML. That is, not using FileMaker's web server setup, other than for supplying the XML. So that I'm using the most appropriate components for the test, what version FX, what version PHP should I get? I expect mine are "dated". I need a PHP that has GD (I think that's what it's called). If there is something specific you'd like for me to test with, let me know. -Troy > Hey John, > > It's the XML bug that made the 'FMAlt' datatype (and associated coding) > necessary in FX.php when working with portals. Basically, when using > FMPXMLRESULT, it would only output one field in a portal for each one > that contained data -- so if you had a portal row with an empty value, > everything in the field after that empty record value would be off. I > called attention to it in an early release of FMS11 (before official > release) and it was fixed, but then reappeared in FMS12, and remained > most of the way through FMS13. It was fixed in the last couple of > months, though the fix is not acknowledged in any of the version notes > that I've looked at. Many of those on the list have fought with it > and/or reported it to FMI. The reason that I'm wondering whether it's > fixed in FMS14, is that the fix appeared when 14 was nearly complete... > > Best, > > --Chris From chris at iViking.org Thu May 21 12:32:51 2015 From: chris at iViking.org (Chris Hansen) Date: Thu May 21 12:31:34 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php In-Reply-To: References: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> <555BCF6E.4000100@pointinspace.com> <8AC14935-A2C7-42E5-95AD-A770B2739DEF@iViking.org> Message-ID: <0751331B-7D1C-47D3-83A5-681E5A583F42@iViking.org> Yep. My tests were on FMS 13.09.905. --Chris > On May 20, 2015, at 5:33 AM, Fitzgerald, Theodore C wrote: > > This bug is supposed to be fixed in 13? Do you know which version? Running 13v09 right now. I'll have to do some testing. > > I just finished a very bare bones codeigniter / fxphp install and pointed it towards FMS14 and didn't see anything out of the ordinary right away. I'm working on moving a more complex app (that I have to use fmalt with) over to 14 and will let you know how it goes... > > Ted > ________________________________________ > From: fx.php_list-bounces@mail.iviking.org [fx.php_list-bounces@mail.iviking.org] on behalf of Chris Hansen [chris@iViking.org] > Sent: Tuesday, May 19, 2015 9:52 PM > To: FX.php Discussion List > Subject: Re: [FX.php List] FileMaker Server 14 and FX.php > > Hey John, > > It's the XML bug that made the 'FMAlt' datatype (and associated coding) necessary in FX.php when working with portals. Basically, when using FMPXMLRESULT, it would only output one field in a portal for each one that contained data -- so if you had a portal row with an empty value, everything in the field after that empty record value would be off. I called attention to it in an early release of FMS11 (before official release) and it was fixed, but then reappeared in FMS12, and remained most of the way through FMS13. It was fixed in the last couple of months, though the fix is not acknowledged in any of the version notes that I've looked at. Many of those on the list have fought with it and/or reported it to FMI. The reason that I'm wondering whether it's fixed in FMS14, is that the fix appeared when 14 was nearly complete... > > Best, > > --Chris > >> On May 19, 2015, at 6:03 PM, John May wrote: >> >> I haven't tested, but can you detail the XML bug that was fixed in 13, and which rev fixed it? >> >> - John >> >> >> On 5/19/15 6:28 PM, Chris Hansen wrote: >>> Hey Folks, >>> >>> I'm going to have to update my server hardware to test compatibility >>> between FMS14 and FX.php, but I have started to receive questions >>> about compatibility. Rather than wait for me to get around to a >>> hardware upgrade (up to my ears in alligators right now...), I have a >>> few questions for all y'all: >>> >>> 1) Has anyone tested FMS14 with FX.php? >>> >>> 2) For anyone who has, any particular observations, gotchas, etc.? >>> >>> 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 >>> is still fixed in FMS14? >>> >>> Thanks! >>> >>> --Chris_______________________________________________ FX.php_List >>> mailing list FX.php_List@mail.iviking.org >>> http://www.iviking.org/mailman/listinfo/fx.php_list >>> >> -- >> >> ------------------------------------------------------------------- >> John May : President http://www.pointinspace.com/ >> Point In Space Internet Solutions 800.664.8610 919.338.8198 >> >> Professional FileMaker Pro, MySQL, PHP & Lasso Hosting >> on shared, virtual and hardware dedicated servers >> >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list >> > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > From ted-fitzgerald at uiowa.edu Thu May 21 12:42:45 2015 From: ted-fitzgerald at uiowa.edu (Fitzgerald, Theodore C) Date: Thu May 21 12:42:49 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php In-Reply-To: <0751331B-7D1C-47D3-83A5-681E5A583F42@iViking.org> References: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> <555BCF6E.4000100@pointinspace.com> <8AC14935-A2C7-42E5-95AD-A770B2739DEF@iViking.org> <0751331B-7D1C-47D3-83A5-681E5A583F42@iViking.org> Message-ID: Hmm...It looks like you were right, it does seem to be fixed (for 13.09.905)! I will be testing this in 14 tonight and get back to you. Ted Application Developer ITS-Enterprise Services 2800 UCC University of Iowa -----Original Message----- From: fx.php_list-bounces@mail.iviking.org [mailto:fx.php_list-bounces@mail.iviking.org] On Behalf Of Chris Hansen Sent: Thursday, May 21, 2015 1:33 PM To: FX.php Discussion List Subject: Re: [FX.php List] FileMaker Server 14 and FX.php Yep. My tests were on FMS 13.09.905. --Chris > On May 20, 2015, at 5:33 AM, Fitzgerald, Theodore C wrote: > > This bug is supposed to be fixed in 13? Do you know which version? Running 13v09 right now. I'll have to do some testing. > > I just finished a very bare bones codeigniter / fxphp install and pointed it towards FMS14 and didn't see anything out of the ordinary right away. I'm working on moving a more complex app (that I have to use fmalt with) over to 14 and will let you know how it goes... > > Ted > ________________________________________ > From: fx.php_list-bounces@mail.iviking.org > [fx.php_list-bounces@mail.iviking.org] on behalf of Chris Hansen > [chris@iViking.org] > Sent: Tuesday, May 19, 2015 9:52 PM > To: FX.php Discussion List > Subject: Re: [FX.php List] FileMaker Server 14 and FX.php > > Hey John, > > It's the XML bug that made the 'FMAlt' datatype (and associated coding) necessary in FX.php when working with portals. Basically, when using FMPXMLRESULT, it would only output one field in a portal for each one that contained data -- so if you had a portal row with an empty value, everything in the field after that empty record value would be off. I called attention to it in an early release of FMS11 (before official release) and it was fixed, but then reappeared in FMS12, and remained most of the way through FMS13. It was fixed in the last couple of months, though the fix is not acknowledged in any of the version notes that I've looked at. Many of those on the list have fought with it and/or reported it to FMI. The reason that I'm wondering whether it's fixed in FMS14, is that the fix appeared when 14 was nearly complete... > > Best, > > --Chris > >> On May 19, 2015, at 6:03 PM, John May wrote: >> >> I haven't tested, but can you detail the XML bug that was fixed in 13, and which rev fixed it? >> >> - John >> >> >> On 5/19/15 6:28 PM, Chris Hansen wrote: >>> Hey Folks, >>> >>> I'm going to have to update my server hardware to test compatibility >>> between FMS14 and FX.php, but I have started to receive questions >>> about compatibility. Rather than wait for me to get around to a >>> hardware upgrade (up to my ears in alligators right now...), I have >>> a few questions for all y'all: >>> >>> 1) Has anyone tested FMS14 with FX.php? >>> >>> 2) For anyone who has, any particular observations, gotchas, etc.? >>> >>> 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 >>> is still fixed in FMS14? >>> >>> Thanks! >>> >>> --Chris_______________________________________________ FX.php_List >>> mailing list FX.php_List@mail.iviking.org >>> http://www.iviking.org/mailman/listinfo/fx.php_list >>> >> -- >> >> ------------------------------------------------------------------- >> John May : President http://www.pointinspace.com/ >> Point In Space Internet Solutions 800.664.8610 919.338.8198 >> >> Professional FileMaker Pro, MySQL, PHP & Lasso Hosting >> on shared, virtual and hardware dedicated servers >> >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list >> > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > _______________________________________________ FX.php_List mailing list FX.php_List@mail.iviking.org http://www.iviking.org/mailman/listinfo/fx.php_list From ted-fitzgerald at uiowa.edu Thu May 21 21:12:30 2015 From: ted-fitzgerald at uiowa.edu (Fitzgerald, Theodore C) Date: Thu May 21 21:12:34 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php In-Reply-To: References: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> <555BCF6E.4000100@pointinspace.com> <8AC14935-A2C7-42E5-95AD-A770B2739DEF@iViking.org> <0751331B-7D1C-47D3-83A5-681E5A583F42@iViking.org>, Message-ID: Chris, Just tested a more complex FX.php app on FileMaker Server 14 that previously required the use of 'fmalt' in 12 and 13v05 and it worked with 'fmpro7' in server 14. So it looks like the fix from 13v09 was carried over to 14. Ted ________________________________________ From: fx.php_list-bounces@mail.iviking.org [fx.php_list-bounces@mail.iviking.org] on behalf of Fitzgerald, Theodore C Sent: Thursday, May 21, 2015 1:42 PM To: FX.php Discussion List Subject: RE: [FX.php List] FileMaker Server 14 and FX.php Hmm...It looks like you were right, it does seem to be fixed (for 13.09.905)! I will be testing this in 14 tonight and get back to you. Ted Application Developer ITS-Enterprise Services 2800 UCC University of Iowa -----Original Message----- From: fx.php_list-bounces@mail.iviking.org [mailto:fx.php_list-bounces@mail.iviking.org] On Behalf Of Chris Hansen Sent: Thursday, May 21, 2015 1:33 PM To: FX.php Discussion List Subject: Re: [FX.php List] FileMaker Server 14 and FX.php Yep. My tests were on FMS 13.09.905. --Chris > On May 20, 2015, at 5:33 AM, Fitzgerald, Theodore C wrote: > > This bug is supposed to be fixed in 13? Do you know which version? Running 13v09 right now. I'll have to do some testing. > > I just finished a very bare bones codeigniter / fxphp install and pointed it towards FMS14 and didn't see anything out of the ordinary right away. I'm working on moving a more complex app (that I have to use fmalt with) over to 14 and will let you know how it goes... > > Ted > ________________________________________ > From: fx.php_list-bounces@mail.iviking.org > [fx.php_list-bounces@mail.iviking.org] on behalf of Chris Hansen > [chris@iViking.org] > Sent: Tuesday, May 19, 2015 9:52 PM > To: FX.php Discussion List > Subject: Re: [FX.php List] FileMaker Server 14 and FX.php > > Hey John, > > It's the XML bug that made the 'FMAlt' datatype (and associated coding) necessary in FX.php when working with portals. Basically, when using FMPXMLRESULT, it would only output one field in a portal for each one that contained data -- so if you had a portal row with an empty value, everything in the field after that empty record value would be off. I called attention to it in an early release of FMS11 (before official release) and it was fixed, but then reappeared in FMS12, and remained most of the way through FMS13. It was fixed in the last couple of months, though the fix is not acknowledged in any of the version notes that I've looked at. Many of those on the list have fought with it and/or reported it to FMI. The reason that I'm wondering whether it's fixed in FMS14, is that the fix appeared when 14 was nearly complete... > > Best, > > --Chris > >> On May 19, 2015, at 6:03 PM, John May wrote: >> >> I haven't tested, but can you detail the XML bug that was fixed in 13, and which rev fixed it? >> >> - John >> >> >> On 5/19/15 6:28 PM, Chris Hansen wrote: >>> Hey Folks, >>> >>> I'm going to have to update my server hardware to test compatibility >>> between FMS14 and FX.php, but I have started to receive questions >>> about compatibility. Rather than wait for me to get around to a >>> hardware upgrade (up to my ears in alligators right now...), I have >>> a few questions for all y'all: >>> >>> 1) Has anyone tested FMS14 with FX.php? >>> >>> 2) For anyone who has, any particular observations, gotchas, etc.? >>> >>> 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 >>> is still fixed in FMS14? >>> >>> Thanks! >>> >>> --Chris_______________________________________________ FX.php_List >>> mailing list FX.php_List@mail.iviking.org >>> http://www.iviking.org/mailman/listinfo/fx.php_list >>> >> -- >> >> ------------------------------------------------------------------- >> John May : President http://www.pointinspace.com/ >> Point In Space Internet Solutions 800.664.8610 919.338.8198 >> >> Professional FileMaker Pro, MySQL, PHP & Lasso Hosting >> on shared, virtual and hardware dedicated servers >> >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list >> > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > _______________________________________________ FX.php_List mailing list FX.php_List@mail.iviking.org http://www.iviking.org/mailman/listinfo/fx.php_list _______________________________________________ FX.php_List mailing list FX.php_List@mail.iviking.org http://www.iviking.org/mailman/listinfo/fx.php_list From chris at iViking.org Fri May 22 11:40:16 2015 From: chris at iViking.org (Chris Hansen) Date: Fri May 22 11:38:55 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php In-Reply-To: References: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> <555BCF6E.4000100@pointinspace.com> <8AC14935-A2C7-42E5-95AD-A770B2739DEF@iViking.org> <0751331B-7D1C-47D3-83A5-681E5A583F42@iViking.org> Message-ID: Huzzah! Thanks for the test, Ted. --Chris > On May 21, 2015, at 9:12 PM, Fitzgerald, Theodore C wrote: > > Chris, > > Just tested a more complex FX.php app on FileMaker Server 14 that previously required the use of 'fmalt' in 12 and 13v05 and it worked with 'fmpro7' in server 14. > > So it looks like the fix from 13v09 was carried over to 14. > > Ted > ________________________________________ > From: fx.php_list-bounces@mail.iviking.org [fx.php_list-bounces@mail.iviking.org] on behalf of Fitzgerald, Theodore C > Sent: Thursday, May 21, 2015 1:42 PM > To: FX.php Discussion List > Subject: RE: [FX.php List] FileMaker Server 14 and FX.php > > Hmm...It looks like you were right, it does seem to be fixed (for 13.09.905)! I will be testing this in 14 tonight and get back to you. > > Ted > > Application Developer > ITS-Enterprise Services > 2800 UCC > University of Iowa > > -----Original Message----- > From: fx.php_list-bounces@mail.iviking.org [mailto:fx.php_list-bounces@mail.iviking.org] On Behalf Of Chris Hansen > Sent: Thursday, May 21, 2015 1:33 PM > To: FX.php Discussion List > Subject: Re: [FX.php List] FileMaker Server 14 and FX.php > > Yep. My tests were on FMS 13.09.905. > > --Chris > >> On May 20, 2015, at 5:33 AM, Fitzgerald, Theodore C wrote: >> >> This bug is supposed to be fixed in 13? Do you know which version? Running 13v09 right now. I'll have to do some testing. >> >> I just finished a very bare bones codeigniter / fxphp install and pointed it towards FMS14 and didn't see anything out of the ordinary right away. I'm working on moving a more complex app (that I have to use fmalt with) over to 14 and will let you know how it goes... >> >> Ted >> ________________________________________ >> From: fx.php_list-bounces@mail.iviking.org >> [fx.php_list-bounces@mail.iviking.org] on behalf of Chris Hansen >> [chris@iViking.org] >> Sent: Tuesday, May 19, 2015 9:52 PM >> To: FX.php Discussion List >> Subject: Re: [FX.php List] FileMaker Server 14 and FX.php >> >> Hey John, >> >> It's the XML bug that made the 'FMAlt' datatype (and associated coding) necessary in FX.php when working with portals. Basically, when using FMPXMLRESULT, it would only output one field in a portal for each one that contained data -- so if you had a portal row with an empty value, everything in the field after that empty record value would be off. I called attention to it in an early release of FMS11 (before official release) and it was fixed, but then reappeared in FMS12, and remained most of the way through FMS13. It was fixed in the last couple of months, though the fix is not acknowledged in any of the version notes that I've looked at. Many of those on the list have fought with it and/or reported it to FMI. The reason that I'm wondering whether it's fixed in FMS14, is that the fix appeared when 14 was nearly complete... >> >> Best, >> >> --Chris >> >>> On May 19, 2015, at 6:03 PM, John May wrote: >>> >>> I haven't tested, but can you detail the XML bug that was fixed in 13, and which rev fixed it? >>> >>> - John >>> >>> >>> On 5/19/15 6:28 PM, Chris Hansen wrote: >>>> Hey Folks, >>>> >>>> I'm going to have to update my server hardware to test compatibility >>>> between FMS14 and FX.php, but I have started to receive questions >>>> about compatibility. Rather than wait for me to get around to a >>>> hardware upgrade (up to my ears in alligators right now...), I have >>>> a few questions for all y'all: >>>> >>>> 1) Has anyone tested FMS14 with FX.php? >>>> >>>> 2) For anyone who has, any particular observations, gotchas, etc.? >>>> >>>> 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 >>>> is still fixed in FMS14? >>>> >>>> Thanks! >>>> >>>> --Chris_______________________________________________ FX.php_List >>>> mailing list FX.php_List@mail.iviking.org >>>> http://www.iviking.org/mailman/listinfo/fx.php_list >>>> >>> -- >>> >>> ------------------------------------------------------------------- >>> John May : President http://www.pointinspace.com/ >>> Point In Space Internet Solutions 800.664.8610 919.338.8198 >>> >>> Professional FileMaker Pro, MySQL, PHP & Lasso Hosting >>> on shared, virtual and hardware dedicated servers >>> >>> _______________________________________________ >>> FX.php_List mailing list >>> FX.php_List@mail.iviking.org >>> http://www.iviking.org/mailman/listinfo/fx.php_list >>> >> >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list >> > > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > From KFutter at sbc.vic.edu.au Wed May 27 22:45:01 2015 From: KFutter at sbc.vic.edu.au (Kevin Futter) Date: Wed May 27 22:44:43 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php In-Reply-To: References: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> <555BCF6E.4000100@pointinspace.com> <8AC14935-A2C7-42E5-95AD-A770B2739DEF@iViking.org> <0751331B-7D1C-47D3-83A5-681E5A583F42@iViking.org> Message-ID: Is there any value in switching back to ?fmpro7? from ?fmalt?? Does it offer better performance? Kev On 23/05/2015 3:40 am, "Chris Hansen" wrote: >Huzzah! Thanks for the test, Ted. > >--Chris > >> On May 21, 2015, at 9:12 PM, Fitzgerald, Theodore C >> wrote: >> >> Chris, >> >> Just tested a more complex FX.php app on FileMaker Server 14 that >>previously required the use of 'fmalt' in 12 and 13v05 and it worked >>with 'fmpro7' in server 14. >> >> So it looks like the fix from 13v09 was carried over to 14. >> >> Ted >> ________________________________________ >> From: fx.php_list-bounces@mail.iviking.org >>[fx.php_list-bounces@mail.iviking.org] on behalf of Fitzgerald, Theodore >>C >> Sent: Thursday, May 21, 2015 1:42 PM >> To: FX.php Discussion List >> Subject: RE: [FX.php List] FileMaker Server 14 and FX.php >> >> Hmm...It looks like you were right, it does seem to be fixed (for >>13.09.905)! I will be testing this in 14 tonight and get back to you. >> >> Ted >> >> Application Developer >> ITS-Enterprise Services >> 2800 UCC >> University of Iowa >> >> -----Original Message----- >> From: fx.php_list-bounces@mail.iviking.org >>[mailto:fx.php_list-bounces@mail.iviking.org] On Behalf Of Chris Hansen >> Sent: Thursday, May 21, 2015 1:33 PM >> To: FX.php Discussion List >> Subject: Re: [FX.php List] FileMaker Server 14 and FX.php >> >> Yep. My tests were on FMS 13.09.905. >> >> --Chris >> >>> On May 20, 2015, at 5:33 AM, Fitzgerald, Theodore C >>> wrote: >>> >>> This bug is supposed to be fixed in 13? Do you know which version? >>>Running 13v09 right now. I'll have to do some testing. >>> >>> I just finished a very bare bones codeigniter / fxphp install and >>>pointed it towards FMS14 and didn't see anything out of the ordinary >>>right away. I'm working on moving a more complex app (that I have to >>>use fmalt with) over to 14 and will let you know how it goes... >>> >>> Ted >>> ________________________________________ >>> From: fx.php_list-bounces@mail.iviking.org >>> [fx.php_list-bounces@mail.iviking.org] on behalf of Chris Hansen >>> [chris@iViking.org] >>> Sent: Tuesday, May 19, 2015 9:52 PM >>> To: FX.php Discussion List >>> Subject: Re: [FX.php List] FileMaker Server 14 and FX.php >>> >>> Hey John, >>> >>> It's the XML bug that made the 'FMAlt' datatype (and associated >>>coding) necessary in FX.php when working with portals. Basically, when >>>using FMPXMLRESULT, it would only output one field in a portal for each >>>one that contained data -- so if you had a portal row with an empty >>>value, everything in the field after that empty record value would be >>>off. I called attention to it in an early release of FMS11 (before >>>official release) and it was fixed, but then reappeared in FMS12, and >>>remained most of the way through FMS13. It was fixed in the last >>>couple of months, though the fix is not acknowledged in any of the >>>version notes that I've looked at. Many of those on the list have >>>fought with it and/or reported it to FMI. The reason that I'm >>>wondering whether it's fixed in FMS14, is that the fix appeared when 14 >>>was nearly complete... >>> >>> Best, >>> >>> --Chris >>> >>>> On May 19, 2015, at 6:03 PM, John May >>>>wrote: >>>> >>>> I haven't tested, but can you detail the XML bug that was fixed in >>>>13, and which rev fixed it? >>>> >>>> - John >>>> >>>> >>>> On 5/19/15 6:28 PM, Chris Hansen wrote: >>>>> Hey Folks, >>>>> >>>>> I'm going to have to update my server hardware to test compatibility >>>>> between FMS14 and FX.php, but I have started to receive questions >>>>> about compatibility. Rather than wait for me to get around to a >>>>> hardware upgrade (up to my ears in alligators right now...), I have >>>>> a few questions for all y'all: >>>>> >>>>> 1) Has anyone tested FMS14 with FX.php? >>>>> >>>>> 2) For anyone who has, any particular observations, gotchas, etc.? >>>>> >>>>> 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 >>>>> is still fixed in FMS14? >>>>> >>>>> Thanks! >>>>> >>>>> --Chris_______________________________________________ FX.php_List >>>>> mailing list FX.php_List@mail.iviking.org >>>>> http://www.iviking.org/mailman/listinfo/fx.php_list >>>>> >>>> -- >>>> >>>> ------------------------------------------------------------------- >>>> John May : President http://www.pointinspace.com/ >>>> Point In Space Internet Solutions 800.664.8610 919.338.8198 >>>> >>>> Professional FileMaker Pro, MySQL, PHP & Lasso Hosting >>>> on shared, virtual and hardware dedicated servers >>>> >>>> _______________________________________________ >>>> FX.php_List mailing list >>>> FX.php_List@mail.iviking.org >>>> http://www.iviking.org/mailman/listinfo/fx.php_list >>>> >>> >>> _______________________________________________ >>> FX.php_List mailing list >>> FX.php_List@mail.iviking.org >>> http://www.iviking.org/mailman/listinfo/fx.php_list >>> _______________________________________________ >>> FX.php_List mailing list >>> FX.php_List@mail.iviking.org >>> http://www.iviking.org/mailman/listinfo/fx.php_list >>> >> >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list >> > >_______________________________________________ >FX.php_List mailing list >FX.php_List@mail.iviking.org >http://www.iviking.org/mailman/listinfo/fx.php_list [http://www.sbc.vic.edu.au/assets/images/email_logo.gif] St Bernard's College Celebrating 75 Years of Achieving Excellence By Learning And Doing Kevin Futter Webmaster Ph: +61392891095 | Mobile: Email: KFutter@sbc.vic.edu.au 41 Rosehill Road, Essendon, Victoria, 3040 | Ph: 03 9289 1000 | F: 9337 1741 | www.sbc.vic.edu.au ________________________________ This e-mail and any attachments may be confidential. You must not disclose or use the information in this e-mail if you are not the intended recipient. If you have received this e-mail in error, please notify us immediately and delete the e-mail and all copies. The College does not guarantee that this e-mail is virus or error free. The attached files are provided and may only be used on the basis that the user assumes all responsibility for any loss, damage or consequence resulting directly or indirectly from the use of the attached files, whether caused by the negligence of the sender or not. The content and opinions in this e-mail are not necessarily those of the College. From beverlyvoth at gmail.com Wed May 27 23:38:44 2015 From: beverlyvoth at gmail.com (Beverly) Date: Wed May 27 23:38:55 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php In-Reply-To: References: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> <555BCF6E.4000100@pointinspace.com> <8AC14935-A2C7-42E5-95AD-A770B2739DEF@iViking.org> <0751331B-7D1C-47D3-83A5-681E5A583F42@iViking.org> Message-ID: Fmpro7 is less verbose. -- sent from myPhone -- Beverly Voth -- > On May 28, 2015, at 12:45 AM, Kevin Futter wrote: > > Is there any value in switching back to ?fmpro7? from ?fmalt?? Does it > offer better performance? > > Kev > >> On 23/05/2015 3:40 am, "Chris Hansen" wrote: >> >> Huzzah! Thanks for the test, Ted. >> >> --Chris >> >>> On May 21, 2015, at 9:12 PM, Fitzgerald, Theodore C >>> wrote: >>> >>> Chris, >>> >>> Just tested a more complex FX.php app on FileMaker Server 14 that >>> previously required the use of 'fmalt' in 12 and 13v05 and it worked >>> with 'fmpro7' in server 14. >>> >>> So it looks like the fix from 13v09 was carried over to 14. >>> >>> Ted >>> ________________________________________ >>> From: fx.php_list-bounces@mail.iviking.org >>> [fx.php_list-bounces@mail.iviking.org] on behalf of Fitzgerald, Theodore >>> C >>> Sent: Thursday, May 21, 2015 1:42 PM >>> To: FX.php Discussion List >>> Subject: RE: [FX.php List] FileMaker Server 14 and FX.php >>> >>> Hmm...It looks like you were right, it does seem to be fixed (for >>> 13.09.905)! I will be testing this in 14 tonight and get back to you. >>> >>> Ted >>> >>> Application Developer >>> ITS-Enterprise Services >>> 2800 UCC >>> University of Iowa >>> >>> -----Original Message----- >>> From: fx.php_list-bounces@mail.iviking.org >>> [mailto:fx.php_list-bounces@mail.iviking.org] On Behalf Of Chris Hansen >>> Sent: Thursday, May 21, 2015 1:33 PM >>> To: FX.php Discussion List >>> Subject: Re: [FX.php List] FileMaker Server 14 and FX.php >>> >>> Yep. My tests were on FMS 13.09.905. >>> >>> --Chris >>> >>>> On May 20, 2015, at 5:33 AM, Fitzgerald, Theodore C >>>> wrote: >>>> >>>> This bug is supposed to be fixed in 13? Do you know which version? >>>> Running 13v09 right now. I'll have to do some testing. >>>> >>>> I just finished a very bare bones codeigniter / fxphp install and >>>> pointed it towards FMS14 and didn't see anything out of the ordinary >>>> right away. I'm working on moving a more complex app (that I have to >>>> use fmalt with) over to 14 and will let you know how it goes... >>>> >>>> Ted >>>> ________________________________________ >>>> From: fx.php_list-bounces@mail.iviking.org >>>> [fx.php_list-bounces@mail.iviking.org] on behalf of Chris Hansen >>>> [chris@iViking.org] >>>> Sent: Tuesday, May 19, 2015 9:52 PM >>>> To: FX.php Discussion List >>>> Subject: Re: [FX.php List] FileMaker Server 14 and FX.php >>>> >>>> Hey John, >>>> >>>> It's the XML bug that made the 'FMAlt' datatype (and associated >>>> coding) necessary in FX.php when working with portals. Basically, when >>>> using FMPXMLRESULT, it would only output one field in a portal for each >>>> one that contained data -- so if you had a portal row with an empty >>>> value, everything in the field after that empty record value would be >>>> off. I called attention to it in an early release of FMS11 (before >>>> official release) and it was fixed, but then reappeared in FMS12, and >>>> remained most of the way through FMS13. It was fixed in the last >>>> couple of months, though the fix is not acknowledged in any of the >>>> version notes that I've looked at. Many of those on the list have >>>> fought with it and/or reported it to FMI. The reason that I'm >>>> wondering whether it's fixed in FMS14, is that the fix appeared when 14 >>>> was nearly complete... >>>> >>>> Best, >>>> >>>> --Chris >>>> >>>>> On May 19, 2015, at 6:03 PM, John May >>>>> wrote: >>>>> >>>>> I haven't tested, but can you detail the XML bug that was fixed in >>>>> 13, and which rev fixed it? >>>>> >>>>> - John >>>>> >>>>> >>>>>> On 5/19/15 6:28 PM, Chris Hansen wrote: >>>>>> Hey Folks, >>>>>> >>>>>> I'm going to have to update my server hardware to test compatibility >>>>>> between FMS14 and FX.php, but I have started to receive questions >>>>>> about compatibility. Rather than wait for me to get around to a >>>>>> hardware upgrade (up to my ears in alligators right now...), I have >>>>>> a few questions for all y'all: >>>>>> >>>>>> 1) Has anyone tested FMS14 with FX.php? >>>>>> >>>>>> 2) For anyone who has, any particular observations, gotchas, etc.? >>>>>> >>>>>> 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 >>>>>> is still fixed in FMS14? >>>>>> >>>>>> Thanks! >>>>>> >>>>>> --Chris_______________________________________________ FX.php_List >>>>>> mailing list FX.php_List@mail.iviking.org >>>>>> http://www.iviking.org/mailman/listinfo/fx.php_list >>>>> -- >>>>> >>>>> ------------------------------------------------------------------- >>>>> John May : President http://www.pointinspace.com/ >>>>> Point In Space Internet Solutions 800.664.8610 919.338.8198 >>>>> >>>>> Professional FileMaker Pro, MySQL, PHP & Lasso Hosting >>>>> on shared, virtual and hardware dedicated servers >>>>> >>>>> _______________________________________________ >>>>> FX.php_List mailing list >>>>> FX.php_List@mail.iviking.org >>>>> http://www.iviking.org/mailman/listinfo/fx.php_list >>>> >>>> _______________________________________________ >>>> FX.php_List mailing list >>>> FX.php_List@mail.iviking.org >>>> http://www.iviking.org/mailman/listinfo/fx.php_list >>>> _______________________________________________ >>>> FX.php_List mailing list >>>> FX.php_List@mail.iviking.org >>>> http://www.iviking.org/mailman/listinfo/fx.php_list >>> >>> _______________________________________________ >>> FX.php_List mailing list >>> FX.php_List@mail.iviking.org >>> http://www.iviking.org/mailman/listinfo/fx.php_list >>> _______________________________________________ >>> FX.php_List mailing list >>> FX.php_List@mail.iviking.org >>> http://www.iviking.org/mailman/listinfo/fx.php_list >>> _______________________________________________ >>> FX.php_List mailing list >>> FX.php_List@mail.iviking.org >>> http://www.iviking.org/mailman/listinfo/fx.php_list >> >> _______________________________________________ >> FX.php_List mailing list >> FX.php_List@mail.iviking.org >> http://www.iviking.org/mailman/listinfo/fx.php_list > > > > [http://www.sbc.vic.edu.au/assets/images/email_logo.gif] > > St Bernard's College > Celebrating 75 Years of Achieving Excellence By Learning And Doing > Kevin Futter > Webmaster > Ph: +61392891095 | Mobile: > Email: KFutter@sbc.vic.edu.au > 41 Rosehill Road, Essendon, Victoria, 3040 | Ph: 03 9289 1000 | F: 9337 1741 | www.sbc.vic.edu.au > ________________________________ > This e-mail and any attachments may be confidential. You must not disclose or use the information in this e-mail if you are not the intended recipient. If you have received this e-mail in error, please notify us immediately and delete the e-mail and all copies. The College does not guarantee that this e-mail is virus or error free. The attached files are provided and may only be used on the basis that the user assumes all responsibility for any loss, damage or consequence resulting directly or indirectly from the use of the attached files, whether caused by the negligence of the sender or not. The content and opinions in this e-mail are not necessarily those of the College. > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list From tim.webko at gmail.com Thu May 28 00:22:07 2015 From: tim.webko at gmail.com (Tim 'Webko' Booth) Date: Thu May 28 00:22:12 2015 Subject: [FX.php List] FileMaker Server 14 and FX.php In-Reply-To: References: <9094907F-B4D5-4282-93F5-A608B5654225@iViking.org> <555BCF6E.4000100@pointinspace.com> <8AC14935-A2C7-42E5-95AD-A770B2739DEF@iViking.org> <0751331B-7D1C-47D3-83A5-681E5A583F42@iViking.org> Message-ID: Which is relative thing - XML is plenty verbose anyway, but Fmpro7 is less 'wordy' Cheers Webko On 28 May 2015 at 15:38, Beverly wrote: > Fmpro7 is less verbose. > > -- sent from myPhone -- > Beverly Voth > -- > > > On May 28, 2015, at 12:45 AM, Kevin Futter > wrote: > > > > Is there any value in switching back to ?fmpro7? from ?fmalt?? Does it > > offer better performance? > > > > Kev > > > >> On 23/05/2015 3:40 am, "Chris Hansen" wrote: > >> > >> Huzzah! Thanks for the test, Ted. > >> > >> --Chris > >> > >>> On May 21, 2015, at 9:12 PM, Fitzgerald, Theodore C > >>> wrote: > >>> > >>> Chris, > >>> > >>> Just tested a more complex FX.php app on FileMaker Server 14 that > >>> previously required the use of 'fmalt' in 12 and 13v05 and it worked > >>> with 'fmpro7' in server 14. > >>> > >>> So it looks like the fix from 13v09 was carried over to 14. > >>> > >>> Ted > >>> ________________________________________ > >>> From: fx.php_list-bounces@mail.iviking.org > >>> [fx.php_list-bounces@mail.iviking.org] on behalf of Fitzgerald, > Theodore > >>> C > >>> Sent: Thursday, May 21, 2015 1:42 PM > >>> To: FX.php Discussion List > >>> Subject: RE: [FX.php List] FileMaker Server 14 and FX.php > >>> > >>> Hmm...It looks like you were right, it does seem to be fixed (for > >>> 13.09.905)! I will be testing this in 14 tonight and get back to you. > >>> > >>> Ted > >>> > >>> Application Developer > >>> ITS-Enterprise Services > >>> 2800 UCC > >>> University of Iowa > >>> > >>> -----Original Message----- > >>> From: fx.php_list-bounces@mail.iviking.org > >>> [mailto:fx.php_list-bounces@mail.iviking.org] On Behalf Of Chris > Hansen > >>> Sent: Thursday, May 21, 2015 1:33 PM > >>> To: FX.php Discussion List > >>> Subject: Re: [FX.php List] FileMaker Server 14 and FX.php > >>> > >>> Yep. My tests were on FMS 13.09.905. > >>> > >>> --Chris > >>> > >>>> On May 20, 2015, at 5:33 AM, Fitzgerald, Theodore C > >>>> wrote: > >>>> > >>>> This bug is supposed to be fixed in 13? Do you know which version? > >>>> Running 13v09 right now. I'll have to do some testing. > >>>> > >>>> I just finished a very bare bones codeigniter / fxphp install and > >>>> pointed it towards FMS14 and didn't see anything out of the ordinary > >>>> right away. I'm working on moving a more complex app (that I have to > >>>> use fmalt with) over to 14 and will let you know how it goes... > >>>> > >>>> Ted > >>>> ________________________________________ > >>>> From: fx.php_list-bounces@mail.iviking.org > >>>> [fx.php_list-bounces@mail.iviking.org] on behalf of Chris Hansen > >>>> [chris@iViking.org] > >>>> Sent: Tuesday, May 19, 2015 9:52 PM > >>>> To: FX.php Discussion List > >>>> Subject: Re: [FX.php List] FileMaker Server 14 and FX.php > >>>> > >>>> Hey John, > >>>> > >>>> It's the XML bug that made the 'FMAlt' datatype (and associated > >>>> coding) necessary in FX.php when working with portals. Basically, > when > >>>> using FMPXMLRESULT, it would only output one field in a portal for > each > >>>> one that contained data -- so if you had a portal row with an empty > >>>> value, everything in the field after that empty record value would be > >>>> off. I called attention to it in an early release of FMS11 (before > >>>> official release) and it was fixed, but then reappeared in FMS12, and > >>>> remained most of the way through FMS13. It was fixed in the last > >>>> couple of months, though the fix is not acknowledged in any of the > >>>> version notes that I've looked at. Many of those on the list have > >>>> fought with it and/or reported it to FMI. The reason that I'm > >>>> wondering whether it's fixed in FMS14, is that the fix appeared when > 14 > >>>> was nearly complete... > >>>> > >>>> Best, > >>>> > >>>> --Chris > >>>> > >>>>> On May 19, 2015, at 6:03 PM, John May > >>>>> wrote: > >>>>> > >>>>> I haven't tested, but can you detail the XML bug that was fixed in > >>>>> 13, and which rev fixed it? > >>>>> > >>>>> - John > >>>>> > >>>>> > >>>>>> On 5/19/15 6:28 PM, Chris Hansen wrote: > >>>>>> Hey Folks, > >>>>>> > >>>>>> I'm going to have to update my server hardware to test compatibility > >>>>>> between FMS14 and FX.php, but I have started to receive questions > >>>>>> about compatibility. Rather than wait for me to get around to a > >>>>>> hardware upgrade (up to my ears in alligators right now...), I have > >>>>>> a few questions for all y'all: > >>>>>> > >>>>>> 1) Has anyone tested FMS14 with FX.php? > >>>>>> > >>>>>> 2) For anyone who has, any particular observations, gotchas, etc.? > >>>>>> > >>>>>> 3) Also, has anyone tested to see whether the XML bug fixed in FMS13 > >>>>>> is still fixed in FMS14? > >>>>>> > >>>>>> Thanks! > >>>>>> > >>>>>> --Chris_______________________________________________ FX.php_List > >>>>>> mailing list FX.php_List@mail.iviking.org > >>>>>> http://www.iviking.org/mailman/listinfo/fx.php_list > >>>>> -- > >>>>> > >>>>> ------------------------------------------------------------------- > >>>>> John May : President http://www.pointinspace.com/ > >>>>> Point In Space Internet Solutions 800.664.8610 919.338.8198 > >>>>> > >>>>> Professional FileMaker Pro, MySQL, PHP & Lasso Hosting > >>>>> on shared, virtual and hardware dedicated servers > >>>>> > >>>>> _______________________________________________ > >>>>> FX.php_List mailing list > >>>>> FX.php_List@mail.iviking.org > >>>>> http://www.iviking.org/mailman/listinfo/fx.php_list > >>>> > >>>> _______________________________________________ > >>>> FX.php_List mailing list > >>>> FX.php_List@mail.iviking.org > >>>> http://www.iviking.org/mailman/listinfo/fx.php_list > >>>> _______________________________________________ > >>>> FX.php_List mailing list > >>>> FX.php_List@mail.iviking.org > >>>> http://www.iviking.org/mailman/listinfo/fx.php_list > >>> > >>> _______________________________________________ > >>> FX.php_List mailing list > >>> FX.php_List@mail.iviking.org > >>> http://www.iviking.org/mailman/listinfo/fx.php_list > >>> _______________________________________________ > >>> FX.php_List mailing list > >>> FX.php_List@mail.iviking.org > >>> http://www.iviking.org/mailman/listinfo/fx.php_list > >>> _______________________________________________ > >>> FX.php_List mailing list > >>> FX.php_List@mail.iviking.org > >>> http://www.iviking.org/mailman/listinfo/fx.php_list > >> > >> _______________________________________________ > >> FX.php_List mailing list > >> FX.php_List@mail.iviking.org > >> http://www.iviking.org/mailman/listinfo/fx.php_list > > > > > > > > [http://www.sbc.vic.edu.au/assets/images/email_logo.gif] > > > > St Bernard's College > > Celebrating 75 Years of Achieving Excellence By Learning And Doing > > Kevin Futter > > Webmaster > > Ph: +61392891095 | Mobile: > > Email: KFutter@sbc.vic.edu.au > > 41 Rosehill Road, Essendon, Victoria, 3040 | Ph: 03 9289 1000 | F: 9337 > 1741 | www.sbc.vic.edu.au > > ________________________________ > > This e-mail and any attachments may be confidential. You must not > disclose or use the information in this e-mail if you are not the intended > recipient. If you have received this e-mail in error, please notify us > immediately and delete the e-mail and all copies. The College does not > guarantee that this e-mail is virus or error free. The attached files are > provided and may only be used on the basis that the user assumes all > responsibility for any loss, damage or consequence resulting directly or > indirectly from the use of the attached files, whether caused by the > negligence of the sender or not. The content and opinions in this e-mail > are not necessarily those of the College. > > _______________________________________________ > > FX.php_List mailing list > > FX.php_List@mail.iviking.org > > http://www.iviking.org/mailman/listinfo/fx.php_list > _______________________________________________ > FX.php_List mailing list > FX.php_List@mail.iviking.org > http://www.iviking.org/mailman/listinfo/fx.php_list > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.iviking.org/pipermail/fx.php_list/attachments/20150528/e6c332ab/attachment-0001.html