Morning = Stuart,
You = mentioned “I have include [FLUSHDATABASES] in the ajax = call” = ….am I correct to say that you are either doing a GET or POST Ajax = call to a file sitting on the server that has the tags to execute the = flush webdna tag?
If so = …can share the ajax call script and the page called by it so that = I can try to assist you. It is indeed strange that the change is stored = in RAM but not committed into the DB even with all the settings you = mentioned. Regardless …after the update, the uncommitted change = should still be showing up when called upon by other pages relying on = it.
Cheers = TDn
From:<= /b> = talk@webdna.us <talk@webdna.us>
Sent: Wednesday, = February 19, 2020 07:39 AM
To: WebDNA Talk List = <talk@webdna.us>
Subject: [WebDNA] COMMITDATABASE in = linux unix 64bits FastCGI version = 8.6
I am having = an issue with a couple of dbs.
Permissions are correct = 775
Ownership is correct = www-data:www-data
I = am updating the db with an ajax call, I open the db ofter it has been = modified and the mod is there in the db.
The ajax call does a replace on the = db.
There is no error reported = from the ajax call.
The WebDNA preference is = "Automatically commit databases to disk after = modification"
The problem is that another page on the site is = dependant on the new value. This new value is not being = found.
I = have include [FLUSHDATABASES] in the ajax call to force the db to clear = however it is still not finding the new = value.
If I use the WebDNA admin to [FLUSHDATABASES] then the page finds the new = value.
Any ideas ?
-------------------------------------------------------= -- This message is sent to you because you are subscribed to the mailing = list talk@webdna.us To = unsubscribe, E-mail to: talk-leave@webdna.us archives: = http://www.webdna.us/p= age.dna?numero=3D55 Bug Reporting: support@webdna.us
Morning = Stuart,
You = mentioned “I have include [flushdatabases] in the ajax = call” = ….am I correct to say that you are either doing a GET or POST Ajax = call to a file sitting on the server that has the tags to execute the = flush webdna tag?
If so = …can share the ajax call script and the page called by it so that = I can try to assist you. It is indeed strange that the change is stored = in RAM but not committed into the DB even with all the settings you = mentioned. Regardless …after the update, the uncommitted change = should still be showing up when called upon by other pages relying on = it.
Cheers = TDn
From:<= /b> = talk@webdna.us <talk@webdna.us>
Sent: Wednesday, = February 19, 2020 07:39 AM
To: WebDNA Talk List = <talk@webdna.us>
Subject: [WebDNA] COMMITDATABASE in = linux unix 64bits FastCGI version = 8.6
I am having = an issue with a couple of dbs.
Permissions are correct = 775
Ownership is correct = www-data:www-data
I = am updating the db with an ajax call, I open the db ofter it has been = modified and the mod is there in the db.
The ajax call does a replace on the = db.
There is no error reported = from the ajax call.
The WebDNA preference is = "Automatically commit databases to disk after = modification"
The problem is that another page on the site is = dependant on the new value. This new value is not being = found.
I = have include [flushdatabases] in the ajax call to force the db to clear = however it is still not finding the new = value.
If I use the WebDNA admin to [FLUSHDATABASES] then the page finds the new = value.
Any ideas ?
-------------------------------------------------------= -- This message is sent to you because you are subscribed to the mailing = list talk@webdna.us To = unsubscribe, E-mail to: talk-leave@webdna.us archives: = http://www.webdna.us/p= age.dna?numero=3D55 Bug Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...