CrikeyWeb

I completely understand that Peter, and appreciate that no application can suit the many ‘specific needs’ of each user. I am a huge fan of WPDA as you should know ??

It is somewhat unfortunate, but the very nature of my application is going to be many new visitors with few returning. I won’t go into detail but essentially once one visitor uses my application, they won’t need it again for another 10 years! So this is why first time visitor page load speed is quite important.

Your solution worked perfectly, I didn’t think of loading it in the footer, thanks muchly!

Thanks for looking into this Peter.
I have conducted several tests with GTMetrix and pingdom. The payload of pdfmake is 337k https://imgur.com/a/mLs5RWU

I understand that the browser will cache this and if any visitor has visited any site ‘recently’ with the javascript then it will be cached… also Cloudflare CDN is always fast :-D.

The first rule of optimsation is “if you don’t use it, lose it”.
I also noticed that if I disabled the vfs_fonts (for pdfmaker) these two combined reduced the page DOM by approximately 900k!

I have attempted to both deregister and dequeue the scripts in functions.php but to no avail.

function pdfmake_deregister_script() {
  wp_deregister_script( 'wpdapro_jquery_datatables_pdfmake');
  wp_deregister_script( 'wpdapro_jquery_datatables_vfs_fonts');
}
add_action( 'wp_deregister_script', 'pdfmake_deregister_script', 100 );

Any ideas what is going on here?

Thanks!
Paul

• This reply was modified 2 years, 8 months ago by CrikeyWeb.

Sure I will be playing with it tomorrow and will post it once I figure it out.

Cheers ??

That’s great, thanks, works 90% as you’ve supplied it already, so sure just a few tweaks and it will be there! Excellent work!

Ahh OK, and no need to apologise. ‘Tis a shame though! I can probably get around $_GET params.

I’m definitely interested in teh full text search add-on, I think it’ll do very well.

Thanks again for your help today and teaching me some CSS ??

Enjoy your evening!

PAul

Hey Peter,
*That* is awesome!! Thankyou!

Glad it got your interest and I hope this will work for anyone else wanting the same display.

I guess unfortunately that there’s no way to display the field names as well? so I guess that’s the display:none, right? As soon as I adjust that to display then it all goes out of whack. I guess it loops side by side easily without the <thead>?

Thought to self: Hmm I wonder if it really needs the field names anyway?

Also if you could provide the syntax for putting the $_GET parameters into the where clause that would be awesome.

Hey again… I misread your response, from the first set I disabled paging, then when setting the dom, of course it was ignored. So thanks your solution with paging enabled for the 3 rows works great! <facepalm>

Thanks Peter,
The code added doesn’t seem to make any difference, but as you say, it’s untested. Looks like I have some reading to do ??

I’ll dig into it and will let you know I appreciate your time.

For now please can you advise how I get the Where clause to use $_GET parameters? I am using v3.1.4.

Thanks

The example page was just pure text, for demo purposes. I’m not sure what you mean by “turn” the tables? But, yes, vertical would be a start, however how would the columns list side by side?

No, there’s no paging required. Essentialy it is searching for an engineer by postcode and the type of engineer, so the page is (pseudo);

/website-url/page-with-custom-php-template?engineer_type=Electrical&area=SOMEWHERE

The results will never be more than 3, so no paging required. Unfortunately due to the database data there is, strictly speaking, more than 3 results as there are several Towns in the database with the same postcode which by default are listed with WPDA, in my SQL (outside of using WPDA) I am using DISTINCT and LIMIT 3, which may not be perfect, but does provide the functionality desired.

It seems that I’m not able to use DISTINCT or LIMIT in the sql_where clause within Data Publisher? Perhaps there is something I’m not aware of with WPDA that can do this?

I would consider removing all the Town references to remove the duplication of the postcodes as it’s a “nice to have” to search via Town, but not strictly required at this stage of the application.

I attempted to reference the input types as you suggested for the table search, but I am definitely missing something here. Where the does hidden <input> references go, in the page template or in Publisher somehow?

I hope this is’nt too much of a pain Peter! The application is “so close* to completion!

If the desired output simply can’t be done with WPDA, then that’s OK!

I will continue using WPDA for the backend administration and custom code the page template/search results page with PHP variables looping through the SQL array.

Cheers!

Hi Peter,
Thanks for the super quick response, much appreciated.
What you have supplied might just do what I need.

For the display reference (apologies for the poor output formatting from the OP!), here’s something I just knocked up. Which shows broadly the output desired.

Thanks!
Paul