I understand your idea but what do you set the Search Form criteria to? That is how can I tell which article to search for?
It also assume that is there is one search result, it goes directly to that article. I've never tried that with Seblod, is that be behavior? I've used over software that is the case but it isn't the norm.
Imperfect solution: Add a hidden menu item for a Category Blog. Set the sort order as you see fit and then automatically any content/article view from the Seblod list inherits the next/previous from it.
Normally this might be fine, but I'm sorting in my seblod list by alias (because alphabetical is spoiled by "the" in some of titles).
So it is "close" but not in the same order as my seblod list order.
I hope some day that this gets integrated into seblod list. It is apparent from other posts in the forum that it is desired.
Far as I can read, that only displays on the search results. I'm wanting a next/previous on the cck article itself after coming to it from the search results. The goal is to between the various article in the search results without returning to the search results. Article to Article.
Yes JMG but the content link from your first search can redirect to the second search with limit to 1 and next/previous.
The issue here is about SEO/link and to have not multiple link to the same content. If it's not issue for you (intranet, extranet) you can apply this solution or the one that you already applied (with category view and native joomla previous/next feature).
About alphabetical order you can always add another field to select the right letter you wish to classify your content and order the list in regards of this field.
Has anybody managed to get this scenario working? I have tried:
1.) Creating a new list for pagination purposes with the Seblod Search Pagination field
2.) Created "list" module assigning new pagination list taking in article ID parameter which will be used to base the prev/next resources on
3.) Assigned List module below my main search & list menu item via Module field
When I call the page I currently get the selected item displayed in the list, but the Pagination Next/Previous buttons don't display. Actually the only way I can get them to display is using a menu item and "Search and List" but even then during my tests they don't work (direct only to the homepage which has no content currently).
I'm guessing here the Search Pagination field does not work under List module, is this correct? If it is is there any alternative to this problem? I have maybe 300+ items and hard coding this would be tedious and really go against the reasoning for using CMS as JMG stated.
If you need any more information do let me know. I am a newbie to Seblod so maybe I'm missing something really simple here?
Would this be a feature you would ever consider as core Joomla offers same? There would be about 400~ items so I don't think showing all and JS to hide is an option for me. I will work around it, manually linking but it is not really efficient at all. Fortunately I don't need to offer the user choice for ordering!
I notice Bes above states:
"best choice is to use 2 SEBLOD lists. But it's more complicated, it's true."
I'm not sure I understand what is meant by this statement, or how it would work in a scenario where the pagination prev/next will appear under content view?
I'm puzzled now, whether the issue here is as original topic of this thread (buttons to move between the articles) or to show previous/next buttons for pagination (e.g. to get next 10 or 50 articles), this 2 are completely different things.
I think the confusion initially is regarding the op title and the Search Pagination field that was brought up. I do not want to change my blog "list" view pagination from numeric to instead "previous/next" page. My requirement is under the item/content view to have a previous/next item.
I should be able to achieve same with a simple SQL statement and I will look into this when I have some time. It is not pagination I require, or the original poster. Simply when a user accesses an article from a list or blog layout, the "content" view, we would like previous/next buttons appearing.
I managed to get the concept of this working by appending all the required properties (ID of category, item etc.) to the URL under my Bootstrap button (simple anchor link with btn class).
This works fine until SEF urls are activated and then obviously the URL parameters are no longer available or accessible (except for my custom one).
My question is how is it possible to collect this datas from the seblod database using before render field under the content view? Because I've tried many methods and couldn't get any to work! Once I do this I can easily construct my SQL query to do the logic.
Right, I finally managed to get this problem sorted (even if in a roundabout way). I will share more detailed explanation if interested however here is what I did in a nutshell. Under Search and List form, where my content was linked to under the Item view, I edited the link properties to include a custom variable:
myvar=$cck->getValue('custom id value'). This ID will be used in the ordering of the items, and also is unique to identify the item.
Now when we call the link to the content page, an additional GET request value will be in the URL, &myvar=<content>. We can use this to build our query..
Using the custom php code in beforerender field I took this value using $_GET[''];, and from this value was able to construct my SQL query to locate the next and previous object in SQL query.
I then used JRoute::_() to build my prev/next button links, to retain the SEF URLs for SEO reasons.
One of the downsides to this workaround is a new GET variable must exist under the page in order for it to work. This is because we cannot seem to be able to get content value using beforerender in the content view i.e: $cck->getValue() (and before and after store do not support the content view as per documentation). Maybe this is by design, a bug or? I'm not too sure.
Another problem with this method is accessing the item directly without the GET data, maybe even the item from a search engine, you won't get the prev/next buttons unless you access the same or another item from the search and list object. but for now it will do the job for my purpose.