Recently I came across a requirement where I went through all the features in Drupal HTML tables. At times I was startled to know the efficacy of the tables in Drupal 7. I would like to share the the same road trip I went through in Drupal 7. Let's begin with a step-by-step process to create tables inD7
Pager: no new to the dictionary of Web, plays an important role in reducing long scrolling and improvises the visual look of the site. One of the pages in my site lists statistics based details. It wasn't that appealing to go ahead with this page which had almost 100 plus items to display. At this point I had a sudden idea to split the statistics with the help of pager.
I stoked with this decision as I thought PagerDefault in Drupal can help me a hand. But later I recognized the same cannot be used in my case as it was not rendered with any query. What I had in my page was just array which was rendered by a theme_table(), to construct a pager for this proved my decision quite rugged. I leave no stones unturned to pick the best way to solve my need.
And finally I found a solution and created a pager. The below mentioned code proved worthy for a solution.,
Of late in two of my Drupal sites I found that pagers were not shown. This happened independent of active theme and modules generating the page (views, panels, or core blog module). Essentially I reproduced this in the Recent logs messages page and default Blogs listing page (?q=blog). Below is the snapshot of how it looked to me.
After spending a couple of hours I found it Views module, that was causing this problem. Strictly speaking this is not bug perhaps by design. It is found that two or more views sharing the same pager id is what likely to cause this issue. In my case, I was able to narrow down that the views invoked through a global context was causing this problem. Seriously I didn't find any options to change pager id instead I changed the view to show all items as I control the limit and order of items from Nodequeue. I suppose this could succour those come across this issue.