Topic-icon Requested Users Page, Pagination doesnt work

Active Subscriptions:

None
12 years 1 month ago - 12 years 1 month ago #43487 by gokhan
Hi,

When i click on one of pagination number it redirects me to JFBC Dasboard;

/administrator/index.php?search=&limitstart=100&option=com_jfbconnect&view=&task=display&requestid=2&fbuserto=&fbuserfrom=&filter_order=
id&filter_order_Dir=DESC&boxchecked=0


please check this and give me solutions, i will aply it manuelly




File Attachment:
Last edit: 12 years 1 month ago by gokhan.
The topic has been locked.
Active Subscriptions:

None
12 years 1 month ago #43524 by gokhan
Any answer?
The topic has been locked.
Support Specialist
12 years 1 month ago #43528 by alzander
Had to investigate this one a little. The solution is a simple fix in the /administrator/components/com_jfbconnect/views/notification/tmpl/default.php file. Around line 128, you'll see:
<input type="hidden" name="view" value="<?php echo JRequest::getVar('view'); ?>"/>
Update that to:
<input type="hidden" name="view" value="notification"/>

Thanks for the report. This fix will be included in the 6.1 release, planned for late May.

Please let us know if you run into anything else!

Alex
The topic has been locked.
Active Subscriptions:

None
12 years 1 month ago #43554 by gokhan
Thank you very much, fixed :)
The topic has been locked.
Support Specialist
12 years 1 month ago #43557 by alzander
Glad to hear that got you going. Should you need anything else, just let us know.

Also, we received your username change request. That will be done over the next few days. We'll contact you when done.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
12 years 1 month ago #43566 by gokhan
Thank you Alex, for help and understanding

A note: I think you forgat to add this small change in 6.0.5, anyway i changed it manuelly, thanks again
The topic has been locked.
Support Specialist
12 years 1 month ago #43576 by alzander
Yeah, that change is not in 6.0.5. It would be in a 6.0.6 release, should it be necessary, but there isn't one planned right now. The change is very minor, but 6.0.5 was already in testing and we didn't want to restart testing to get this change in, due to it's very low severity.

If you run into anything else, or have any general feedback, as always, let us know!

Thanks,
Alex
The topic has been locked.