I've created the connections that use the same database tables and models but display data in a different way.
I noticed that moving from one to another connecitons remain stored values of ordered fields asc or desc and navigation pages.
I think are the values stored in the session that does not change when you switch to another connection.
I noticed that moving from one to another connecitons remain stored values of ordered fields asc or desc and navigation pages.
I think are the values stored in the session that does not change when you switch to another connection.
I temporarily solved by changing the name of the model of the connections. I had created the connection with copy and they had the same model.
I also added a button that does the reset and restores the initial order after ordering a column.
I saw now that the session has this array:
I think also enter the name of the connection in the array of the session of sorts would solve the problem.
I also added a button that does the reset and restores the initial order after ordering a column.
I saw now that the session has this array:
$_SESSION['cgore']['GCore\Extensions\Chronoconnectivity\Controllers\Lists']['my_model']
I think also enter the name of the connection in the array of the session of sorts would solve the problem.
Hi Vales,
Yes, this is the behavior of the framework, the connection's name doesn't play any roles which means that you should have a different model name in order to avoid this issue.
Regards,
Max
Yes, this is the behavior of the framework, the connection's name doesn't play any roles which means that you should have a different model name in order to avoid this issue.
Regards,
Max
This topic is locked and no more replies can be posted.
