Joined: 8/21/2009
Posts: 54
|
Version 7.66 SP2
We have just started using HTML forms and realized that, if the form is filled out on the production server, that is where the data resides. But if the form is filled out on our staging server (which we don't do except for testing purposes), then the data resides on the staging server until pushed up to production via e-sync.
This means that, when we log into the work area on our staging server, and run the reports on the form, we only see the data that was entered on the staging server and not on the production server.
We are set up where our editors only have access to the staging server and never touch the production server. Our e-sync is only one direction, from staging to production. So how do I get the data from the HTML form on the production server to show up in the reporting feature of the form on the staging server, where our editors have access?
I've talked with support and they suggested we give our editors access to the production server work area. Hmmmmmm. I thought the whole idea of a staging server is that it is not messed with by our editors. And besides, we do not have our LDAP authentication set up for the production server, etc. We also do not push our work area up to production in e-sync.
Any suggestions? How is anyone else handling data collected from an HTML form? Perhaps sending the data to an additional script that would add it to the staging server database?
Barbara
|
Joined: 10/2/2006
Posts: 325
|
So using eSync to download data is not an option for you?
Other than that, you can create web services on the production site for staging to pull data over.
Think outside the box.
Ektron CMS Smart Form XSLT = Great Design Idea w. Control
|
Joined: 8/21/2009
Posts: 54
|
If we download data using eSync, would it not overwrite all data we have on our staging server?
|
Joined: 10/2/2006
Posts: 325
|
Here are a couple of direct quotes from http://www.ektron.com/esync/
"With its intelligent synchronization technology, eSync is able to
securely move selected content bi-directionally: Web 2.0 sites have a
wealth of user generated content and membership information. That data
can now be synchronized back to the development side of the firewall."
"If conflicting versions of content exist, eSync’s configurable conflict
resolution engine ensures that you won’t lose your most up-to-date
content. The version that isn’t posted is saved in a history, along
with other previous versions, enabling you to track changes or restore
content, if the need arises."
|