Good morning.
I have a CONNECTION in Chronoconnectivity 5 in which I put a page limit set at 50, but on my web page shows only two at a time. I can not understand why. But if I close the browser and delete cookies back to see how to set 50 records.
I have a CONNECTION in Chronoconnectivity 5 in which I put a page limit set at 50, but on my web page shows only two at a time. I can not understand why. But if I close the browser and delete cookies back to see how to set 50 records.
Hi Fasano,
I don't quite understand what the problem is?
I think that the limit is probably stored in the User session so changes don't take effect until the session is cleared and restarted.
Bob
I don't quite understand what the problem is?
I think that the limit is probably stored in the User session so changes don't take effect until the session is cleared and restarted.
Bob
Hi Bob
01 attached what I set
02 attached what I see
This happens to all connections
Fasano
01 attached what I set
02 attached what I see
This happens to all connections
Fasano
Hi Fasano,
If you log out and log in again, or clear your browser cache - is the limit then show with the new value? If so then I think that this is just because the value is saved in the User session data.
Bob
If you log out and log in again, or clear your browser cache - is the limit then show with the new value? If so then I think that this is just because the value is saved in the User session data.
Bob
HI Bob
ok .... it is a problem of cookies. I deleted cookies and came back completely normal. I did well on other browsers on which I was trying. The problem is that if you encounter the same problem, I can as often delete cookies, it would be absurd. But I do not understand how I can do
Fasano
ok .... it is a problem of cookies. I deleted cookies and came back completely normal. I did well on other browsers on which I was trying. The problem is that if you encounter the same problem, I can as often delete cookies, it would be absurd. But I do not understand how I can do
Fasano
Hi Fasano,
This shouldn't be any problem to a 'normal' user - test using a different browser. I think that it is only when you change the settings then test using the same browser that you see this 'odd' result.
Bob
This shouldn't be any problem to a 'normal' user - test using a different browser. I think that it is only when you change the settings then test using the same browser that you see this 'odd' result.
Bob
HI Bob
It actually works now .... but just run my login and that of others here that the problem reappears. I am going crazy!!!!
You can try to see you too Bob. I am sending you the link privately.
Fasano
It actually works now .... but just run my login and that of others here that the problem reappears. I am going crazy!!!!
You can try to see you too Bob. I am sending you the link privately.
Fasano
Hi Fasano,
It has something to do with putting the listing in K2. If you check the direct form link
Bob
It has something to do with putting the listing in K2. If you check the direct form link
/index.php?option=com_chronoconnectivity5&cont=lists&act=index&ccname=Juniores
or remove the template from the K2 listing /juniores.html?tmpl=component
then all of the records show, It's only when the template + K2 are used that it only shows 2 records.
Bob
Hi Fasano,
Sorry but I can't work out what is happening. It looks as if logging in to K2 and to the site as a Joomla! User use different settings. Very odd.
Bob
Sorry but I can't work out what is happening. It looks as if logging in to K2 and to the site as a Joomla! User use different settings. Very odd.
Bob
Hi Bob
I do not know for what reason inexplicable .... at least for me .... now that I have reversed models of a connection that did not work, it does the right !! Now I try on the other connections.
Maybe I understood.
When using connections in the model they should be used and not different model with the same name as the data stored in the sessions of the connections overlap making a mess.
So for each connection is used a model other than this is the general rule that applies to everyone.
Fasano
I do not know for what reason inexplicable .... at least for me .... now that I have reversed models of a connection that did not work, it does the right !! Now I try on the other connections.
Maybe I understood.
When using connections in the model they should be used and not different model with the same name as the data stored in the sessions of the connections overlap making a mess.
So for each connection is used a model other than this is the general rule that applies to everyone.
Fasano
This topic is locked and no more replies can be posted.