ProBlog List and ProEvent List on same page conflict
Permalink
I have submitted this as a support ticket but since two of these items have been circulating for a long time from other users I figure I would tap the community for any possible solutions.
Adding ProBlog List block to a page...
Blog posts are not limited to the number specified in the dialog box unless the "show pagination" box is checked (which i dont necessarily want).
If you check this however and there is a ProEvent List block (or another block that uses pagination i suspect) on the pge and click to page two in the paginator (?) you receive an error... "Page "2" does not exist. The currentPage must be inferior to "1""
Also and separately, there seems to be an issue still that has been previously reported.
"Call to a member function getController() on a non-object"
I thought I was receiving this because I did not specify which page type to limit the problog list block to but it also may be related to unchecking "Display page aliases"
Any ideas on how to fix these would be great. Most importantly is the post display limit. I don't want the pagination so the second issue would not be a problem. The third issue is more of a problem when I hand this over to a client to manage. I cant really say "just dont touch that button, it will break the page".
Thanks in advance.
Chris
Adding ProBlog List block to a page...
Blog posts are not limited to the number specified in the dialog box unless the "show pagination" box is checked (which i dont necessarily want).
If you check this however and there is a ProEvent List block (or another block that uses pagination i suspect) on the pge and click to page two in the paginator (?) you receive an error... "Page "2" does not exist. The currentPage must be inferior to "1""
Also and separately, there seems to be an issue still that has been previously reported.
"Call to a member function getController() on a non-object"
I thought I was receiving this because I did not specify which page type to limit the problog list block to but it also may be related to unchecking "Display page aliases"
Any ideas on how to fix these would be great. Most importantly is the post display limit. I don't want the pagination so the second issue would not be a problem. The third issue is more of a problem when I hand this over to a client to manage. I cant really say "just dont touch that button, it will break the page".
Thanks in advance.
Chris
If I understand correctly, are you saying these issues only occur when you try adding both blocks to the same page? But if listed separately there is no issues?
For problem #1 (limiting the number of posts displayed) the issue is independent. I put a ProBlog List block on a page by itself and the block shows all the posts regardlss of the limiting number you put into the dialog box.
For problem #2 (conflicting pagination blocks) the issue shows when ANY two blocks utilizing the core pagination function are on the same page even if only one has the pagination enabled. Mesuva and I ran into this problem a while back using his List of Files block on the same page as a ProEvents List block.https://github.com/concrete5/concrete5/pull/2032...
For problem #3 (Call to a member function... error) this is also independent as far as I can tell. And seems to be directly tied to UNchecking "display page aliases".
That clarify? Thanks for looking at this. As I mentioned the most important to me would be problem #1.
Cheers,
C
For problem #2 (conflicting pagination blocks) the issue shows when ANY two blocks utilizing the core pagination function are on the same page even if only one has the pagination enabled. Mesuva and I ran into this problem a while back using his List of Files block on the same page as a ProEvents List block.https://github.com/concrete5/concrete5/pull/2032...
For problem #3 (Call to a member function... error) this is also independent as far as I can tell. And seems to be directly tied to UNchecking "display page aliases".
That clarify? Thanks for looking at this. As I mentioned the most important to me would be problem #1.
Cheers,
C
I won't be much help for debugging anything with ProBlog as I've never purchased that. I do have a copy of ProEvents though that I could take a look at if thats the issue.
As far as limiting blog posts, if you just want to only show a certain amount of posts, you may be able to set some kind of CSS rules in your theme that hide them. It's not the correct way to do it, but maybe its better than nothing?
The CSS would be something like:
That psuedo code would in theory hide all posts the block outputs, then you just need to unhide the first three:
Hopefully you get some support from the author on how to solve your problem correctly!
As far as limiting blog posts, if you just want to only show a certain amount of posts, you may be able to set some kind of CSS rules in your theme that hide them. It's not the correct way to do it, but maybe its better than nothing?
The CSS would be something like:
.problog-list .list-item { display: none; }
That psuedo code would in theory hide all posts the block outputs, then you just need to unhide the first three:
Hopefully you get some support from the author on how to solve your problem correctly!
Thanks for the reply. That's kinda where I was going for an interim fix except I just Checked On Pagination and then used CSS to hide the pagination bar.
And still waiting to hear on my support ticket :)
And still waiting to hear on my support ticket :)
