Kuler SQL pagination in base stack?

That would be very useful, @Gary. I’ve used a number of CRUD scripts and they’ve all been, er, cruddy!

OK thanks - basic question - is the stack on my page in RW automatically updated to the new version (1.6.7). I have closed and reopened RW, the new stack is sat in the stack list but the stack on my page is still showing 1.6.6. On each of my 80 pages. Each full of stacks inside each one - please tell me I don’t have to rewrite all the pages…

@Gary taking courage in both hands - any way to have a search box on the page so client can find a product within the 31,000 books in the database (without downloading the whole shebang which I think is how your Search function works at present)

Open you RW project and go to a stacks page … any stacks page and open up your stacks library.

Clic on “Updates” and the Stacks plugin will check to see if there are any updates to your stacks. If there are it will give you an opportunity to update all of them or select ones.

No, thats all done. New stack there automatically. But all my pages still show the old stack, wondered indeed hoped those 80 pages will automatically get updated to the new version becaue it hasnt happened so far.

You only have to update a stack one time not once for every project you have or even every page.
Just one time to update. You may want to completely close out of RW and restart it and after you do that then EVERY RW project that uses that stack will automatically upgrade.

Now, it WILL NOT update your website, you will need to re-publish pages to your website so they can benefit from the update.

Thanks. I only asked because i had closed down the project and RW too and it didnt update to the new stack. I will see tomorrow.

@Gary RW is playing up because it downloaded your new version automatically but did NOT in fact. Said it had, but in Finder, no. Updated stack in project, no. Been on another thread about this and eventually. Pro Table is there.
And… you’ve cracked it - I now get pagination, search and buttons for print etc.

One oddity - first screen shot shows web site display (haven’t updated actual web site yet), second screenshot shows local web site (using ampps). I’m suddenly get a red circular + sign instead of the second column appearing. And if I click the + it becomes a - and the second column appears beneath it.

I’ll keep playing, but no settings were changed…

That green button is supposed to be part of the “responsive” feature built into the DataTables Framework. In the next update I will provide an option to remove it.

It is supposed to do that on smaller screens, this way the visitor doesn’t get lost in all of the content on a small screen.

@Gary. Ah im red/green colour blind. So, finally got there but cant use it cos it blocks out a whole column of data. Ill play tomorrow in the hope that i can persuade it that it it isnt mobile, or check that it works ok on a desktop (which would get me thru til you change it). Close!

@Gary Unfortunately, though you have the pagination solved, I cannot even update my site because of this new button that hides a column, and I need to! So I’m stuck. Shame you popped that in last minute as all my book details are listed in the 2nd column, the one you’re hiding from view!! Await you making that feature optional …
Pity the ProTable stack isn’t unpinnable within a partial (me having to replicate 80 pages!) since it has different keywords in every page - yet I now need to tweak a setting for the background colour now that the pagination details have emerged.

Hi @jnorris235 -
The responsive feature isn’t new, it has been there for a few years and have not received a complaint on it to date (except for you). However since you are in a bind, I will see if I can add an option to remove the responsive nature of the table and push that out today.

Also, for the sake of everyone else that keeps getting notices in their inbox with each posting, perhaps it would be better to move this to a private email instead.
gary@kuler.solutions

Gary

Many thanks. Will await 1.6.8 of the ProTable stack.
The responsive feature wasn’t there last week!
End of thread, then.
Bad news for you - I bought the CRUD stack…
Thank you once more!

Jon Norris

:stuck_out_tongue_winking_eye: Herefordshire’s favourite Childrens Entertainer - WizardWonky.co.uk ** Book Me Now!

jnorris235 http://forums.realmacsoftware.com/u/jnorris235 Jon Norris http://forums.realmacsoftware.com/u/jnorris235
October 3
Many thanks. Will await 1.6.8 of the ProTable stack.
The responsive feature wasn’t there last week!
End of thread, then.
Bad news for you - I bought the CRUD stack…
Thank you once more!

Jon Norris

Herefordshire’s favourite Childrens Entertainer - WizardWonky.co.uk http://wizardwonky.co.uk/ ** Book Me Now!

Visit Topic http://forums.realmacsoftware.com/t/kuler-sql-pagination-in-base-stack/9433/100 or reply to this email to respond.

In Reply To

Gary http://forums.realmacsoftware.com/u/gary Addon Developer
October 3
Hi @jnorris235 http://forums.realmacsoftware.com/u/jnorris235 - The responsive feature isn’t new, it has been there for a few years and have not received a complaint on it to date (except for you). However since you are in a bind, I will see if I can add an option to remove the responsive nature of the table and push that out today. Also, for…
Visit Topic http://forums.realmacsoftware.com/t/kuler-sql-pagination-in-base-stack/9433/100 or reply to this email to respond.

To unsubscribe from these emails, click here http://forums.realmacsoftware.com/email/unsubscribe/13d42b14904fa28689aae5456f8596199bf5b899712c89165fb3e75b48919165.

LOL … Yeas the responsive feature has been there since late 2014 and since the very beginning of the PRO Table (the PROTable has never not had it).
Also, I already pushed out the 1.6.8 version earlier this morning. You should check for updates via Stacks to get it. Let me know if it gets you going.
Gary

All done, thank you, brilliant job

@jnorris235- I know that people must be getting tired of being alerted every time you and I interact on this forum. PLEASE consider using my email address to send communication.
gary@kuler.solutions

1 Like

Although, to be fair, it is an object example in patient support for your clients! I salute you, Monsieur Kuler. Your Kuler stacks have always worked brilliantly for me, and I look forward to trying CRUD as soon as I can think of a clever use for it.

4 Likes

Actually I am quite interested. I would buy anything from Gary right now, if I could use it :slight_smile:

1 Like

End result. Huge thank you to @Gary for his amazing patience. Unfortunately he couldn’t replicate my problem. My fields were longer than his example and overflowed the table cells. Either the text formatted and the pagination failed or vice versa.

To avoid text either overflowing or simply being cut off I added this css into a css box (Joe Workman) in a partial so it was included on all 80 pages. Gary has all his cells as “nowrap” - and weirdly the way to stop this was to add white-space. And the pagination stayed working. No credit due to me, I just fiddled til it worked!
td.column_1 {
white-space: normal !important;
}
And the !important was vital.

Secondly. His CRUD stack worked perfectly, whereas the proTable stack seemed not to for me. I used the CRUD stack as a client search facility by hiding the Add and Edit buttons with this css. I still have the table cell widths to solve (20 odd fields to cram in and unable to layout yet).

.simplecrud-current  {
visibility:hidden;
}

a[data-task=“create”] {
visibility:hidden;
}

a[data-task=“csv”] {
visibility:hidden;
}

Also with the Search usage of the CRUD stack the column widths are only the width of the column heading - whereas the data would just word-wrap underneath it giving a deep column of half words making it unreadable.
Fixed with, on the actual page:
.simplecrud-row {
white-space: nowrap;
}

Pretty good stacks!!! One thing I did learn, but don’t understand, is keep republishing. Sometimes it works OK sometimes not.

1 Like