timdietrich

yilbber -- EasyWeb is designed to make Web publishing data stored in a FileMaker database easy. While the example database is an example of a Contacts database, it really doesn't matter what the data represents. It could be products, orders, club members, race results, etc. To use EasyWeb with another database, you would just configure EasyWeb to point to the database, and specify the layouts that you want to use to display the "list" and "detail" views. Hope this helps explain what EW is. ~ Tim

​Shmuel -- Please see this thread: http://fmforums.com/forums/topic/97157-setting-up-fmeasyweb-questions/ ~ Tim

​Greg -- I believe that if you change the name of this folder - /Library/FileMaker Server/HTTPServer/htdocs/PHP Code/ - to - /Library/FileMaker Server/HTTPServer/htdocs/easyweb/ - then you would be able to reach the site using: http://127.0.0.1/fmeastweb/index.php ~ Tim

You could modify the index.php file so that it always includes the "form.php" file, using something like this: if ( isset ( $_GET [ 'recordID' ] ) ) or TRUE {... You would also need to modify the "/form/form-record-get.php" file so that, instead of retrieving a record by its ID, it did a find based on the UUID value instead. That should do it. ~ Tim

Juergen -- That's good news. I'm glad you were able to get it working. ~ Tim

Ok - I think you can easily fix this by making "index.php" a default document. There are some instructions on how to do that here: http://blog.winhost.com/configuring-a-default-document/ Another option is to modify EasyWeb itself. That's a bit trickier, but if you want to go that route, let me know. ~ Tim

This looks like an issue with how your Web server is configured... If you try this - http://69.77.156.90/fmeasyweb/index.php?page=2 - it works. Are you running IIS or Apache? ~ Tim

Glad you got it working. To customize EasyWeb, poke around in the "customizations-form.php" and "customizations-list.php" files. Try uncommenting out some of the things that I've disabled, and see what the impact is on the pages that are generated. And, of course, you can experiment with the CSS / themes - either create your own or modify the existing themes. You have control over how things appear (fonts, styles, colors, border, etc). Have fun! ~ Tim

Hi everyone. From what I can tell, the reason that some of you are seeing the PHP warnings (for things such as undefined variables) is that your PHP configurations are set to "strict" mode. You can hide the warnings by adding this line to the index.php file (in the EasyWeb root folder): // Disable all error reporting. error_reporting(0); Place that after the header comments, just before the "// Initialize EasyWeb" comment. That should suppress the warnings. Those of you who are getting the "Call to undefined function mcrypt_get_iv_size()" error, the problem seems to be that your PHP builds are missing an encryption linbrary. For reference: http://stackoverflow.com/questions/27633584/php-fatal-error-call-to-undefined-function-mcrypt-get-iv-size-in-appserv ~ Tim

You're seeing the warnings because of how your hosting provider has PHP configured. Here's some guidance on how to disable the deprecation warnings: http://stackoverflow.com/questions/2803772/turn-off-deprecated-errors-php-5-3 ~ Tim

Brian -- That looks right to me. You might want to try putting EasyWeb in the root - although you shouldn't have to do that. (EasyWeb will run in a subdirectory.) ~ Tim

Brian -- What does the URL look like that you're using to access EasyWeb? -- Tim

Brian -- It sounds like the "encryption-load.php" file is missing. It should be in the web app's "/core" folder. Perhaps it was missed when uploading or copying to your Web server? ~ Tim

Hello. You should be able to use either the IP address of the server or a domain / subdomain name. If that's not working, what error is being reported? ~ Tim

Sky -- Thanks for the quick feedback. Regarding the container issue: If you haven't already, drag the container file on to the layout that you are using for the form view. It's not enough that be included as a visible field when viewing the layout as a table - It has to be physically on the layout. That should do it. Also,, fmFoo is on the way. I'm hoping to release that in the next day or two. I just need to work up the documentation. Stay tuned. ~ Tim

Hi everyone. I'm happy to announce that FMEasyWeb is finally available for beta testing. With EasyWeb, you can provide Web-based access to your FileMaker databases without needing to write code. It's a convenient way to quickly publish data to the Web and make it available to either the general public or to authorized users. And like many of my other FileMaker solutions, EasyWeb is being made available via an open source license. For more information about EasyWeb, or to download it, please visit: http://fmeasyweb.com Thanks! ~ Tim

Doug, The "?" is usually an indication that either an ExecuteSQL call has failed (meaning that the SELECT statement was invalid for some reason) or that something else that required dynamic evalulation failed. Are you sure that all of the ES_ fields have been setup correctly? And do you get this error for every sync, or only under certain conditions? Tim

"Tim obviously wasn't thinking that you might be modifying the hosted files directly with the same device that you are doing the sync." Actually, I was. And while developing EasySync, that's exactly what I was doing: Using my workstation as if it were a mobile device, updating records on it, and with it to update records directly on the host. The Device ID concept was added specifically to address the "round trip" issue. You wrote, "Because I usually push up a minor amount of data it's a minor problem that if what I push up also gets pulled back down, i.e. roundtrips." For many, it is a huge issue. Imagine that you've pushed up several photos or other binary data in container fields. "Round tripping" that data can easily become a nightmare. "...but I'm not good enough to write that statement and maybe neither was Tim." I'm not sure what to make of that. A lot of work went into making EasySync work as seamlessly as it does. The level of abstraction involved to pull that off was insane. I made EasySync an open source solution for several reasons. The primary reason was to share it with the community, and provide a sync framework that was easy to implement and extremely affordable (you can't beat "free"). Sync support is a critical feature for many mobile solutions. In fact, not having it can be a show stopper in some cases. My hope was that EasySync would help developers meet that need, sell more FileMaker Go-based solutions, and help the FileMaker platform in general. But another reason for making it open source was to provide code that was fully unlocked and easily modifiable to meet specific needs. If you don't need the Device ID, and if round tripping isn't an issue for your solution, then disable it. - Tim

That error will show up in your logs if debugging is enabled - or if somewhere in the code a Show Dialog script step is being called when a server side script runs. It's nothing to worry about. - Tim

In your scenario, can you confirm that when user "A" syncs at hour 3, that the server's timestamp for the new record really is "1" and not "3"? I would test this myself, but I just don't have the bandwidth right now - and probably won't for 3 to 4 weeks.

Hello. EasyMaps uses the Google Map API's "fitBounds" method to automatically set the boundaries of the map as it is initially displayed. This loads the map in such a way that all of the pins that have been dropped are visible in the initial view. Once the map has loaded, you can zoom it manually. -- Tim

Marc -- When syncing with debug mode enabled, just before the "Table Name for Payload Record" dialog is displayed (and shows the table name as "?[[bR]]ES_Projects"), there is a dialog that shows what the entire payload record is. The dialog title is something like "Payload Record n"... What does it show for the value of that record? Also, if there is a record before that one, what is its value? -- Tim

With the way that you are syncing, I think you should only need to set the ES_Exclude value on the server. On the client side, the thought was that it would be used to delay the pushing of records to the server. For example, a work order that wasn't quite ready to be "submitted" yet. -- Tim

Hello! The problem be a result of the global field ("globals::areaFilter") that you're using to filter the records. EasySync makes heavy use to the Perform Script on Server script step. When scripts are called with PSoS, the Draco session that is initiated on the server does not inherit the values of the global fields that were set by the client. You might want to try passing the "areaFilter" value via the $$additional_push_info and $$additional_pull_info variables, which you can set in the "EasySync Settings" script. This gives you the ability to send additional custom info during the push and pull phases. Good luck! -- Tim

Perhaps some of the records are in an archived state, and as a result, unlikely to change. If so, you could exclude those from the Sync Check entirely - and that might improve things. -- Tim