AppGini Community Forums

jsetzer wrote: ↑

2024-10-22 07:32

First idea which came into my mind as a starting point:

Inject an iframe:

src = TABLENAME_view.php?Embedded=1&parameter_for_filtering=123

In TABLENAME_init() hook check for parameter and use $options for filtering.

This will show an embedded Table View without any header/menu/footer and list the filtered records. This will already consider user permissions.

2nd problem. [...] make the filter/logic work

function tasks_init(&$options, $memberInfo, &$args)
{
	// TEST filtering
	$my_filter = Request::val("custom_filter");
	switch ($my_filter) {
		case 'closed':
			$options->QueryWhere = "WHERE task_states1.is_finished";
			break;
		case 'open':
			$options->QueryWhere = "WHERE NOT task_states1.is_finished";
			break;
	}
}

...?custom_filter=matched

1. Check this URL in your browser: http://localhost/v4update/RoutingActionInformation_view.php?custom_filter=matched
   Does it work at all?
2. If not, add some debugging, for example:
   

   Code: Select all

   function RoutingActionInformation_init(&$options, $memberInfo, &$args) {
     // TEST filtering
     $my_filter = Request::val("custom_filter");
     var_dump($my_filter);
   
     switch ($my_filter) {
       case 'matched':
         $options->QueryWhere = "WHERE RoutingActionInformation.ControlNumber = Documents.ControlNumber";
         break;
       case 'unmatched':
         $options->QueryWhere = "WHERE RoutingActionInformation.ControlNumber != Documents.ControlNumber";
         break;
     }
     var_dump($options->QueryWhere);
     exit();
   }
   

   Reload your browser and check if there is matched and WHERE RoutingActionInformation.ControlNumber = Documents.ControlNumber in output.
3. If so, remove the debugging-lines (var_dump(...), exit()), reload page, then, in Admin Area, check for failed SQL queries. We don't know your table names nor do we know your column-names. Perhaps there is a typo or different column-naming.
4. If there are failed SQL queries, double check your column names and your $options->QueryWhere statement, then, in Admin Area clear error-queries, in Users Area reload your table view page, go back to Admin Area and check if there are new error-queries.
5. As soon as your table view filter works, go on with embedding <iframe/>.
   Tip: add &Embedded=1 to your URL. As already mentioned, this will remove header from your embedded table view.

not that good at programming

• In TABLENAME_init() hook function, var_dump($options->QueryFrom); and var_dump($options->QueryWhere);
• Check both outputs to see obvious errors like different table names or misspelled aliases
• If, after resolving obvious SQL errors, table view still does not work as expected, let AppGini build your final SQL query and check the results in your favourite SQL tool (for example Adminer or PhpMyAdmin):
  
  Change table names and where-clause accordingly:
  

  Code: Select all

  function TABLENAME_init(&$options, $memberInfo, &$args)
  {
  	// your filtering logic here
  	// change QueryWhere depending on custom filter parameters
  	// Replace QueryWhere according to YOUR specific condition(s)
  	$options->QueryWhere = "WHERE `TABLENAME`.`id` IN (1, 2, 3, 5, 8, 13, 21, 34, 55)";
  
  	// enable debugging: true|false
  	$debug = true;
  
  	if ($debug) {
  		$sql = $options->buildQuery($options->QueryFieldsTV);
  		echo "<p>Clipboard-copy and test the following SQL command in your SQL tool:</p>";
  		echo "<code>{$sql}</code>";
  		exit;
  	}
  	
  	// ...
  }
  

  This is the dumped SQL statement in my scenario:
  

  

  chrome_naaO8gdYAS.png (73.6 KiB) Viewed 6924 times

• Open your SQL tool, paste the dumped SQL command, run the query and check the results. As long as your SQL tool cannot run your query, AppGini generated code cannot run your query neither. Your SQL tool may give more detailed information about the error.
• If you cannot find the mistake by yourself, post outputs from var_dump($options->QueryFrom);, var_dump($options->QueryWhere); and especially $sql here, maybe we can see it.
• As mentioned before, there are situations in which QueryWhere already contains content due to permissions. Then do not concat " WHERE ..." but " AND ..."

[...] <iframe /> [...], where should I add it?

Question: does it work now? Any feedback welcome.

http://localhost/v4update/children-Rout ... Embedded=1

• TABLENAME_view.php
  Opens a table view for TABLENAME
• TABLENAME_view.php?SelectedID=1
  Opens a detail view for TABLENAME, showing record, identified by primary key (AKA id) =1, if exists.
• TABLENAME_view.php?SelectedID=1&Embedded=1
  Same as above but in Embedded-mode without navbar

if (!$selectedID) 
  $html .= '<iframe src="TABLENAME_view.php?Embedded=1" width="100%" height="300"></iframe>';