yes, this is a bug which requires a fix but you can use the button id or name:
#button-name{
// styles here
}
button[name="button-name"]{
// styles here
}
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
the update works fine, what error do you get ? the where statement can be as simple as this:
column_name=123 //123 is the value of the column_name in the row you want to update
the next v8 update is supposed to be ready soon hopefully, I have already added a delete data action
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
The following config works perfectly here, how do you do it ? if its the same then your database server may have some special settings blocking it

Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
I think it may not be working because your "Save data" does not have any data source or data to be saved
The next update should display the SQL code executed in the debug info, that should make it more clear where is the error coming from
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.