Thread

Hi Robin,

Tried sending a PM but your mailbox is full. Guess that must mean a lot of people are trying to get ahold of you 😉 Anyway, just wanted to check in and see if you’ve had a chance to log into the site and get a deeper look under the hood regarding this issue?

Also want to make sure I don’t accidentally lock you out while I’m doing any further work on the site.

Please keep me posted and thanks again for your help!

Pinging Robin regarding an update for you

Apologies, David.  I turn PM’s off, preferring to stick with email.  Which has the unfortunate side effect of always saying my mailbox is full.

It looks like there was a glitch with the login information.  I’m dropping you another email now to make sure we have the needed info.

Hi Robin, No worries, I have your email and am sending the info now. Thanks!—David

Ha- got it this time (though it went to spam folder- weird!).  K- the problem is the Logiq Pagination add-on.  I disabled all extensions briefly- and it went back to showing the properly selected page number.

We can’t really support third party software, but let me give it a quick look and see if I can spot why it’s going wrong.

hmm, interesting.

IIRC, I did testing with Logiq Pagination both on and off and was having the same problem either way. My tests showed the plugin affecting styling but not changing pagination behavior. Also it’s fine everywhere on the site except the author pages. Very strange.

Ouch- that would complicate things.  For my test?  I disabled all extensions (which causes no data loss) as opposed to disabling the single extension.  Then reloaded the page and pagination worked as I expected it to.  SO- yes, it’s possible there’s an interaction going on. 

Someone on Devotee noted it could conflict w/other add-ons that also write their own pagination.  In a quick skim of the extensions table, it doesn’t look like anything else was using the same hook, so I decided it was unlikely.  But- it’s certainly not impossible.

That said- it IS similiar to a bug solved a while back- if the extension is pretty verbatim from that old code, that could be the cause.  Was certainly what I’m hoping for.

While I poke code- you might want to try disabling all extensions and giving it a quick test as well.  archives/author/13/ is where I tested it w/extensions disabled and it appeared to work.

OK,  I just did a test where I removed ONLY Logiq Pagination and that did fix the problem. Re-enabling it even with default parameters brings it right back.

So I think we can safely narrow it down to the Logiq Pagination extension. Either my memory is wrong or I was testing for a different problem.

That said, since you’ve seen this issue before, is there any info in your notes on how it was eventually solved?

The extension is functionally identical to Bystrom Pagination Extension (v.1.2)  which works perfectly on the EE1.6.9 site. See:

http://www.stretcher.org/archives/author/13/

Also,

I’ve been in touch with the original developer, Michael Byström. He’s handed the plug-in off to Logiq, but there’s no contact info at the Logiq site.

Do you know of way to achieve the same functionality if I have to ditch this plug-in?

We use it to change the text for the NEXT and PREV links and the FIRST and LAST markers, as well as adding css IDs

Can I just add needed rules directly in my main style sheet? What other options are there for styling pagination if I need to go that route?

Thanks!

Hi David,

Glad we got this narrowed down! While we can’t support 3rd-party extensions, I suspect you could achieve something similar without using extensions by using a little bit of jQuery. If you’d like I can move this over to the CodeShare Corner to get you further input, since there are likely a few approaches.

Hi Brandon,

Yes, go ahead and move to Codeshare and let’s see what people suggest.

Also still curious what Robin did to fix this in the past as it might hopefully apply here. Thanks!

Heh- sorry, was poking.  Think I got it fixed- simply a matter of adding:

$p_config['num_tag_close']   = $ld_num_tag_close;
                
                // Allows $config['cur_page'] to override
        $p_config['uri_segment'] = 0;

Those last two lines are new.  And do what the say- you need to set the uri_segment config value to 0, otherwise CI is going to use the uri to figure out the current page- in the above case, it was thinking ‘13’.

So yep- anyone runs into the same problem- the tweak above to the add-on should do the trick.

And hopefully?  This means you’re good to go, David!

Nailed it!!! Thank you Robin!!!  😊

For my future reference - where did you add those new lines of code? Template, config file, somewhere else???

This is awesome! A couple more CSS tweaks and we’re good for launch!

Oh- it’s in the extension file itself… ext.logiq_pagination.php - something along those lines.  I closed the file or I’d be more specific.  On the plus side- it means there was no hacking w/core code.  Just have to be careful if you update that extension- make sure it’s got the fix in it.

Aha! so it’s a bug in the extension itself. I suspected as much and was in the middle of writing an email to Michael Byström to see if he had an earlier 2.0 compatible version when you posted your fix. You should bill Logiq for your time, LOL!

Many thanks for your outstanding support. Everything’s done and we’re finally ready to go!

best,
David

David,

Glad Robin was able to sort you out here.

Please also note with this extension from personal experience if you turn on Cache Dynamic Channel Queries? in your General Preferences it will also generate an error