DPagebreak/Page Navigation Content Plugin

Notices aren't the same as errors but I can't really help if I can't reproduce them

I appreciate the information you have shared and it has given me some insight but I'm afraid its still not enough for me to give you a definitive answer for a fix.

I can toss out some guesswork and the rest of the questions I asked about Joomla version and browser etc again ...

Starting from the first notice that's the check to see if the page is the sites home page. *Guessing* since the notice is coming from the Itemid which should be an integer anyway and not require converting, I'm thinking perhaps its a modRewrite or maybe SEF thing perhaps its a conflict with another plugin or module ...

Do you use SEF, modRewrite (ie .htaccess) and if so does the notices occur with it turned off?

Is your site live, can I get a link to it?

I do a lot of troubleshooting for other extensions and have gotten pretty good at doing it just by looking at the pages that errors occur on, if you don't want to continue discussing this publicly please PM me any information you can and I will do my best to resolve your issues.

Something you might try and I don't know what the affects will be is change line 67 to ... ... or maybe ... ... but I don't know if it will help or not.

Its very difficult to troubleshoot blind

Hi there,

I see. Thanks for letting me know about that. I am quite sure it must be some conflicts with other components (or SEF) if not because of major hacking that is done on the site.

Since it is not my site (and have no clue if changing any core/external codes will break other things on the site), will show you the site on frontend helps?

Maybe I can give you administrator access if that helps. The Notice was up too for "JomComment" and the developers managed to get rid of it (just a quick fix).

I wish I can turn the SEF off to test but again it is not my site and I am not sure if the site owner allows me to do that.

I shouldn't need admin access at all just looking at the frontend is all I might need. If you can link me to the JomComment issue it might help also, Azrul and his team are a lot better coders than I am, looking into their fix for you could really help me figure out the problem.

What version of php do you use?
Just a thought because I'm currently only able to test 5.2.9, sometimes 5.3+ causes similar issues.

I understand about not being able to try everything I ask :oops: I do appreciate everything you have and can do to help me troubleshoot this issue.

Hi there,

You got PM

Oh I asked the guy who did the quick fix for JomComment but looks like he's MIA at the moment -_-

btw, for your info its PHP 5.2.6

I have managed to reproduce these notices locally and will get to work on solving the issues.

Please note I only see the notices when I have error reporting set to maximum in Global configuration.

If you are using System-Default, none or Simple as error reporting they are not displayed. I know this is inconvenient if you are on a dev server but if live it should not be a problem for most. Until I can solve these issues I either recommend changing the error reporting setting or disabling DPagebreak.



I also made mention of the MTU plugin but after some testing it actually seems to have no affect on DPagebreak at all. I apologize for that confusion I have been troubleshooting extensions that are not compatible with the MTU plugin and sense the JS looked like MT 1.1.2 compliant code I thought there would be conflicts.

So there are no *known* conflicts with MTU at this time after all

cXc,

I see. Oh thanks for the tips and advice!

I am still not giving up on this plugin since I know its capability and functionality, though some of us already taking it back old school, if you know what I mean.

It's already great to know there is such plugin to work with Flexi, can't thank you enough!

Thanks for the information regards to MTU. But MTU does break the template system on Flexi backend though. I guess that is totally unrelated :roll:

I do know what you mean about taking it back to old school, there used to be hundreds of extensions I would consider during design ... now there is less than 10

I have actually been working on this plugin in one form or another for over a year, probably closer to 2, so at this point its pretty much got all the " bells and whistles " I can think of. Its just fixing the issues like the ones you have found that I need to focus on. My entire goal with DPagebreak was to have a flexible pagebreak that works with *all* content parsing extensions and that provides options no other extension has. So far it works in most CCK's and form builders and does what I wanted so I guess it's off to a decent start

As far as getting rid of the notices goes, I have that sorted now and will be updating the plugin later today, I'm looking into one feature that was present in previous unreleased versions now to see if I can implement it again

Either way I'll release it and the editor-xtd button, I will most likely create a new button to address the <hr /> trouble that occurred as many CCK's have removed the button from their editors. Should be a rather quick and simple extension to get created, just an edited version of "Editor Button - Pagebreak".

I also plan to get the SVN's updated for Google Code and Joomla Code today, I might even list in JED, so I guess I should get back to work if I want to make sure I get everything done lol

[EDIT] I didn't get everything done ... no SVN updates, no JED but did get the new feature added and all support files ready

I just have to finish adding the options and do a little more testing

I had to rename the Editor Button plugins, they were actually named backwards and we now have a DPagebreak button to insert the pagebreak <hr /> and DP Style button to select the items TOC style ... anyway, I will get to the main plugin today (November 20, 2010) ... I may be adding another class to the DP Style - Example plugin CSS but the editor buttons shouldn't need to be updated for 1.4.8 [/EDIT]

~cXc~ wrote: I do know what you mean about taking it back to old school, there used to be hundreds of extensions I would consider during design ... now there is less than 10

Hehe

~cXc~ wrote: I have actually been working on this plugin in one form or another for over a year, probably closer to 2, so at this point its pretty much got all the " bells and whistles " I can think of. Its just fixing the issues like the ones you have found that I need to focus on. My entire goal with DPagebreak was to have a flexible pagebreak that works with *all* content parsing extensions and that provides options no other extension has. So far it works in most CCK's and form builders and does what I wanted so I guess it's off to a decent start

Its more than just decent. I think it's awesome and useful!

As far as getting rid of the notices goes, I have that sorted now and will be updating the plugin later today, I'm looking into one feature that was present in previous unreleased versions now to see if I can implement it again

Either way I'll release it and the editor-xtd button, I will most likely create a new button to address the <hr /> trouble that occurred as many CCK's have removed the button from their editors. Should be a rather quick and simple extension to get created, just an edited version of "Editor Button - Pagebreak".

I also plan to get the SVN's updated for Google Code and Joomla Code today, I might even list in JED, so I guess I should get back to work if I want to make sure I get everything done lol

Oh I wish I am coder to help/contribute as well but I am far from it But I can always help with testing or some minor stuffs

Keep us posted

Updated DPagebreak Plugin to version 1.4.9b
Added DPagebreak Editor Button version 1.0.1
Updated DP Style Editor Button to version 1.0.4
Updated DP Example Style to version 1.0.2

DPagebreak Plugin 1.4.9b Changes
[-] Removed developer snapshot that was included with 1.4.9 initial release, some unused residual files remain.
[$] Added and updated some language strings.
[*] Plugin was processing item titles whether they were used or not, partially implemented fix :oops: 1.5.0 will have full fix.
[*] Removed error reporting set to maximum notices.

DPagebreak Editor Button 1.0.1 *NEW*
[+] DPagebreak plugin check to show button.
[+] Hide standard pagebreak button if enabled.
[^] Changed image used for the editor button.
[!] Copied and renamed standard Joomla! pagebreak plugin.

DP Style Editor Button 1.0.4 Changes
[^] Changed image used for the editor button.
[$] Updated some language strings for the plugin.
[!] Renamed plugin to make more sense and allow for DPagebreak plugin to be used for pagebreaks.

DP Example Style 1.0.2 Changes
[!] Fixed version number in XML file.

There may have been a couple other changes but that's the ones I remember.

So far the 1.5.0 version will have the complete fix for item titles not being used and if I can figure out why the preloader doesn't work with com_content and get that fixed I'll include it also. For those curious I'm trying to preload by using JS to hide the content until its loaded then remove the loading gif background. I do not like the idea of hiding my content with CSS then having JS show it because of possible conflicts or JS being disabled and content never being displayed.

If I update any of the other plugins in the set it will most likely be adding the DPagebreak plugin check to the DP Style editor button, I can't think of anything the other buttons are missing.

As always, thanks for everyone's support and for helping me troubleshoot DPagebreak.

Message I replied to was removed