William Richardson

Ok, that's progress! On port 80, Rfm is communicating with FM server. The "UnableToOpenFileError" means Filemaker was unable to gain access to the Filemaker file "dbname". This usually means that...

It looks like create/edit actions are broken where portals are concerned. There is a special url syntax for specifying portal fields that goes something like this ``` ...-db=mydb&-lay=mylayout&-recid=1111&relationship::fieldname_in_portal_dot_recid.98765=some-fresh-data&-edit ``` for...

I reviewed the 2.1.7 code, and I can't find any indication that writing to portal records has ever worked in rfm. Are you sure your above example was a portal...

If a Filemaker field on a layout is from any other table than the one attached to the layout, it will be a related field and have the '::' in...

That code should work, if the field is on the layout you're referencing. If you could post (or gist) a raw xml from Filemaker, I can get a better idea...

Oh, that's excellent. I've been waiting for this one to come up but couldn't produce the issue myself with Filemaker as the data source. When sax parsing, it's considered perfectly...

Ok, should be fixed in sax-without-buffer & master branch now. I noted that Ox appears to eliminate an extra line-feed from source xml text nodes in ruby 1.8.7. This doesn't...

Hi @mknarciso , Just at a glance, it looks like ```.new``` is being called on ```OmniAuth::Slack```, which is a module and doesn't have a ```.new``` method. If you could post...

Hi @aguynamedben , thanks for the info. Maybe it's a load-order issue somewhere in the library... I'll dig into the code and see what I can find.

Hey folks, I had a look through the code, and I couldn't find any obvious point where this would happen. I wasn't able to reproduce it in my own examples,...