L
|
lewis 5/3/2016 |
I would be interested as well. |
![]() |
need2sleepDevClub member 5/15/2016 |
Use "%" before your search query. |
![]() |
HJB 5/16/2016 |
Modify generated ..._lookupsuggest.php file |
![]() |
lefty author 5/16/2016 |
Modify generated ..._lookupsuggest.php file Find all occurencies of this line there: QUOTE $LookupSQL .= "BandName LIKE '".db_addslashes($value)."%'";and replace them with: QUOTE $LookupSQL .= "BandName LIKE '%".db_addslashes($value)."%'"; P.S. (as well set AJAX to start only after 3 characters are entered to keep server operations cool) searchSuggest function in include\ajaxsuggest.js file: -------------------------------------------------------------------------- function searchSuggest(oEvent,oElement,searchType) { if(oElement.value.length<3) return; oEvent=window.event || oEvent;
|
![]() |
HJB 5/17/2016 |
https://xlinesoft.com/phprunner/docs/ajax_features.htm |
![]() |
lefty author 5/17/2016 |
https://xlinesoft.com/phprunner/docs/ajax_features.htm Lookup wizard as Edit box with AJAX popup ... check TABLE DEPENDENCY options seen on the right of the relevant section.
|
![]() |
lefty author 5/17/2016 |
https://xlinesoft.com/phprunner/docs/ajax_features.htm Lookup wizard as Edit box with AJAX popup ... check TABLE DEPENDENCY options seen on the right of the relevant section.
|
![]() |
HJB 5/18/2016 |
@John - I took the "global settings" on bandname oriented AJAX from my archive and most probably it's only valid from some previous PHPR versions. Anyway, global settings have NOTHING to do with your problem at all, say, to only pick certain information related to the ADD/EDIT field from a particular table. As the code above is highly complex and as well the "Edit box with Ajax Popup" dedicated pick-up dependencies are only MAIN table oriented rather than ANY ELSE table, so, in my opinion, the only way to solve the problem is a) to look at the SQL QUERY BUILDER inside PHPR to see where the links between whatsoever are lined-up (to get a general good graphical overview rather than to run through coded lines) and <img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=reply&id=79390&image=1&table=forumreplies' class='bbc_emoticon' alt='B)' /> to drill a little bit deeper into SQL QUERY options (e.g. via Google) to manually adjust the table content dedications per ADD/EDIT field then. Say, in my opinion, the only time and energy way to go is to manually draw lines inside the PHPR's SQL query builder to those very table(s) you are eyeing on on per different ADD/EDIT fields on Ajax Popups with some freshly gained knowledge base on SQL QUERIES, TABLE POINT, FILTERING and else. Finally, on global settings, it seems that PHPR v8.1 is already equipped with same: |
![]() |
lefty author 5/18/2016 |
@John - I took the "global settings" on bandname oriented AJAX from my archive and most probably it's only valid from some previous PHPR versions. Anyway, global settings have NOTHING to do with your problem at all, say, to only pick certain information related to the ADD/EDIT field from a particular table. As the code above is highly complex and as well the "Edit box with Ajax Popup" dedicated pick-up dependencies are only MAIN table oriented rather than ANY ELSE table, so, in my opinion, the only way to solve the problem is a) to look at the SQL QUERY BUILDER inside PHPR to see where the links between whatsoever are lined-up (to get a general good graphical overview rather than to run through coded lines) and <img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=reply&id=79398&image=1&table=forumreplies' class='bbc_emoticon' alt='B)' /> to drill a little bit deeper into SQL QUERY options (e.g. via Google) to manually adjust the table content dedications per ADD/EDIT field then. Say, in my opinion, the only time and energy way to go is to manually draw lines inside the PHPR's SQL query builder to those very table(s) you are eyeing on on per different ADD/EDIT fields on Ajax Popups with some freshly gained knowledge base on SQL QUERIES, TABLE POINT, FILTERING and else. Finally, on global settings, it seems that PHPR v8.1 is already equipped with same: Citing excerpt out of https://xlinesoft.com/phprunner/docs/ajax_features.htm#lookupaseditbox Note: If for some reasons you don't want to use AJAX-based functionality then all you need to do is to change the $useAJAX and $suggestAllContent variables value in the include\appsettings.php file to false. $useAJAX = false; $suggestAllContent = false; unquote Yet, as said, that issue is of secondary character while dedication of specific table content to various ADD/EDIT fields under AJAX Popup is a primary issue to get hopefully solved by you as per suggestions above.
|
![]() |
HJB 5/19/2016 |
@John - As I said, I took that code from my ARCHIVE (I'm a registered user since PHPR v2.0) and as time goes by, I mean, new versions and upgrades are coming out, I do not have the time to run a properly updated code snippets "warehouse" at all. So, such code must have been shifted elsewhere and easily to get located by e.g. usage of "notepad++" where the built-in SEARCH feature allows to run through the WHOLE generated files seen within the output directory, finally listing in which .php files such code had been found. Accordingly, to get me nailed on trial to assist somewhere sometime, I beg for your understanding that 1st this forum is NOT a support oriented one and 2nd the time investments did not really payback at all, partially resulting in a kind of shitstorm (I had a serious encounter with a Newbie from on this forum Singapore who tried to convince me, a since PHPR 2.0 registered user is only a MORON). Finally, I had been waiting very long time (say, now almost 6 months) to now, here by PHPRUNNER 9.0 beta release to get "newTLD" mail support, PHP 7.0 support and finally the best, to see BOOTSTRAP in place, yet meanwhile most clients ran away (no big problem for me as my motto is: "WE DON'T SELL WINE BEFORE ITS TIME" has its own market value) and shifted over to a fresh clientel base now where I need to throw some ballast out of the hot balloon to reach out to some height here. So, due to lesser time to creep through either machined and manually coded lines, I beg your pardon. |