Hello I'm stuck with Duration Field, I'd need to use some field for adding time and I guess this field could be the one, this is the error page I get when migrating to 2.7.6 https://cloudup.com/cFV3_hxSU7B/f
(I could evaluate also paid intervention, in case)
I don't understand a heck of OO-php :smile:
@Manaus looks like a problem with how the field is being set
@Manaus I cannot say if this is related to the Duration field or not
it looks like the data in the database is not ok
Are you able to re-save the section ?
Hello Symphony enthusiasts. I recently moved a site to a new server, and now the ordering/filtering is misbehaving. I can't order entries within Symphony by a date field, and the entries on the frontend which are being ordered by the same date field are not displaying correctly either. Anyone encountered this before?
mysql 5.5.60, php 5.5.9
The main difference is I'm using the cachelite plugin, so I wonder if this effects it at all... page has been excluded and cache has been flushed.
Oh and Symphony 2.7.0, Cachelite 2.1.1
@pixelninja are you able to save the config.php file via the backend ? looks like the file is not writable
Also, update your datefield to the latest version
finally, cachelite should not be an issue for the backed
concur with @nitriques that’s a common issue when we put the config as a read-only on production. We have been going around it through an extension which stores this on a per user basis. (we don’t want our production configs to be writeable in 99% of cases)
Hi @nitriques and @jonmifsud, Yes the config is writeable. The config file wouldn't effect the front end would it? The datasource output is being effected too which is very weird. I'm not sure if it's date field specific as all table fields won't reorder (which would definitely suggest the config.php, but I can definitely save to it).
I'm not much of a MySQL dev, would there be some compatibility issue with Symphony's sortable function perhaps?
@pixelninja no the config shouldn’t impact datasources at all.
What error do you get in the datasource?
There is no error, it pulls through entries correctly but the sort order is ignored
But it's just the sort order. Datasources can be filtered fine, and entries within Symphony can be filtered fine.
So it must be something in the Symphony sortable class right?
@nitriques Hi (sorry for the delay), I can resave the section if the field is not present, but I get the error otherwise...
@pixelninja does the sort works if you delete all sorts from the config file ?
@Manaus looks like the field is not working with the new Symphony and needs upgrading