×
Please submit new Bug Reports on GitHub: github.com/Jensen-Technologies/component-creator-issues/issues
Frontend Logout
Samuel
Yeni Üye
Posts: 3
8 yıl 4 ay önce #1382
Yazan: Samuel
Frontend Logout, Samuel tarafından oluşturuldu
Hi,
I had some problems with my component and tried to report this as a bug. Some things were fixed, but there is still some weird behavior when I try to edit a component in the frontend:
If I add an item in the frontend, and click afterwards on edit, I need to fill in my credentials again. It seems the action logged me out!
Can anybody confirm this? (I am using a fresh Joomla installation and just build the component)
I had some problems with my component and tried to report this as a bug. Some things were fixed, but there is still some weird behavior when I try to edit a component in the frontend:
If I add an item in the frontend, and click afterwards on edit, I need to fill in my credentials again. It seems the action logged me out!
Can anybody confirm this? (I am using a fresh Joomla installation and just build the component)
Şu kullanıcı(lar) Teşekkür etti: Andy
Lütfen sohbete katılmak için Giriş ya da Hesap açın.
Andy
Yeni Üye
Posts: 7
8 yıl 2 ay önce - 8 yıl 2 ay önce #1425
Yazan: Andy
Andy tarafından Frontend Logout konusunda yanıtlandı
I've seen this happen with components I've created.
Oddly enough, it seemed to only occur on Chrome and Safari running on OSX not in Firefox on Windows 7 or Linux. This made me think there is subtle difference in the way sessions are handled in OSX, though I'm not sure.
I created the component that displayed this in July 2016. I'm not sure if regenerating the components would resolve this issue.
This is in Joomla 3.6.2 on PHP 5.6.25.
Oddly enough, it seemed to only occur on Chrome and Safari running on OSX not in Firefox on Windows 7 or Linux. This made me think there is subtle difference in the way sessions are handled in OSX, though I'm not sure.
I created the component that displayed this in July 2016. I'm not sure if regenerating the components would resolve this issue.
This is in Joomla 3.6.2 on PHP 5.6.25.
Son Düzenleme: 8 yıl 2 ay önce Düzenleyen:Andy
Lütfen sohbete katılmak için Giriş ya da Hesap açın.
Andres Maeso
Platin Üye
Posts: 338
8 yıl 2 ay önce #1431
Yazan: Andres Maeso
Andrés Maeso
Customer relations manager at Joomla Component Creator.
This email address is being protected from spambots. You need JavaScript enabled to view it.
Andres Maeso tarafından Frontend Logout konusunda yanıtlandı
hi
I've sent this to our developers but please note that this community forum is not actively watched for bug reports by our support. If you find a bug please don't hesitate to send it to our contact form www.component-creator.com/en/help/contact we try to tackle them as they come to keep our sysem bug-free.
Regards,
Andrés.
I've sent this to our developers but please note that this community forum is not actively watched for bug reports by our support. If you find a bug please don't hesitate to send it to our contact form www.component-creator.com/en/help/contact we try to tackle them as they come to keep our sysem bug-free.
Regards,
Andrés.
Andrés Maeso
Customer relations manager at Joomla Component Creator.
This email address is being protected from spambots. You need JavaScript enabled to view it.
Şu kullanıcı(lar) Teşekkür etti: Andy
Lütfen sohbete katılmak için Giriş ya da Hesap açın.
Andy
Yeni Üye
Posts: 7
8 yıl 2 ay önce #1432
Yazan: Andy
Andy tarafından Frontend Logout konusunda yanıtlandı
I think I found the cause, it may help, so I'll describe it here.
All our systems run on https, but the links seemed to not set the http/https in them. Digging into the code I found that tweaking the calls to jroute fixed the issue.
In the code, in the list view, some had a single parameter, like...
JRoute::_('index.php?option=com_piota_content_import&view=content_import');
...so I changed them to...
JRoute::_('index.php?option=com_piota_content_import&view=content_import', false, 0);
...though actually I don't think this fixed my issue.
And some had three parameters, like...
JRoute::_('index.php?option=com_piota_content_import&task=contentimportitemform.edit&id=0', false, 2);
...which I changed to...
JRoute::_('index.php?option=com_piota_content_import&task=contentimportitemform.edit&id=0', false, 0);
...this was the fix that solved the problem.
Looking at the joomla docs at...
docs.joomla.org/Supporting_SEF_URLs_in_your_component
..it says...
$ssl is an integer value that specifies whether the URI should be secure. It should be set to 1 to force the URI to be secure using the global secure site URI, 0 to leave it in the same state as when it was passed, and -1 to force the URI to be unsecure using the global unsecure site URI.
...so I'm not sure what the "2" as a third parameter in the component was doing, but zero, false or leaving it blank would be ok I think.
Hope that helps, let me know if you have any questions or if anything doesn't make sense.
All our systems run on https, but the links seemed to not set the http/https in them. Digging into the code I found that tweaking the calls to jroute fixed the issue.
In the code, in the list view, some had a single parameter, like...
JRoute::_('index.php?option=com_piota_content_import&view=content_import');
...so I changed them to...
JRoute::_('index.php?option=com_piota_content_import&view=content_import', false, 0);
...though actually I don't think this fixed my issue.
And some had three parameters, like...
JRoute::_('index.php?option=com_piota_content_import&task=contentimportitemform.edit&id=0', false, 2);
...which I changed to...
JRoute::_('index.php?option=com_piota_content_import&task=contentimportitemform.edit&id=0', false, 0);
...this was the fix that solved the problem.
Looking at the joomla docs at...
docs.joomla.org/Supporting_SEF_URLs_in_your_component
..it says...
$ssl is an integer value that specifies whether the URI should be secure. It should be set to 1 to force the URI to be secure using the global secure site URI, 0 to leave it in the same state as when it was passed, and -1 to force the URI to be unsecure using the global unsecure site URI.
...so I'm not sure what the "2" as a third parameter in the component was doing, but zero, false or leaving it blank would be ok I think.
Hope that helps, let me know if you have any questions or if anything doesn't make sense.
Şu kullanıcı(lar) Teşekkür etti: George Taylor, Ruud van Lent
Lütfen sohbete katılmak için Giriş ya da Hesap açın.
Ruud van Lent
Yeni Üye
Posts: 4
7 yıl 10 ay önce #1467
Yazan: Ruud van Lent
Ruud van Lent tarafından Frontend Logout konusunda yanıtlandı
Hi Andy,
ran into this post when trying to figure out what was happening on my https site with the buttons to publish / edit / delete / etc.
As it turned out your keen investigation fixed all of these issues for me
I have searched the code for all instances with the faulty ', 2' value as ssl parameter in JRoute and now all of my crashing / error 500 / logout / login issues have gone when using the buttons on the lists and forms. I just committed this value (leaving it empty) and everything works again.
Thanks for sharing this!
regards,
Ruud.
ran into this post when trying to figure out what was happening on my https site with the buttons to publish / edit / delete / etc.
As it turned out your keen investigation fixed all of these issues for me
I have searched the code for all instances with the faulty ', 2' value as ssl parameter in JRoute and now all of my crashing / error 500 / logout / login issues have gone when using the buttons on the lists and forms. I just committed this value (leaving it empty) and everything works again.
Thanks for sharing this!
regards,
Ruud.
Lütfen sohbete katılmak için Giriş ya da Hesap açın.
Andy
Yeni Üye
Posts: 7
7 yıl 10 ay önce #1468
Yazan: Andy
Andy tarafından Frontend Logout konusunda yanıtlandı
Hi Ruud
Glad that was helpful
Cheers
Andy
Glad that was helpful
Cheers
Andy
Lütfen sohbete katılmak için Giriş ya da Hesap açın.
Sayfa oluşturma süresi: 0.062 saniye