Support/Comments for PHx - My Forums

Re: Support/Comments for PHx

rethrash — Dec 06, 2008, 09:08 AM

Good point Zi ... think I’ll lock this one down now. Create new posts here.

Re: Support/Comments for PHx

zaigham — Dec 05, 2008, 02:10 PM

Just a friendly note, please start a new topic in the forum since PHx got a dedicated one. It’ll help to reduce the length of the specific thread, which is a bit difficult to follow... 15 pages... you know

http://modxcms.com/forums/index.php/board,328.0.html

Re: Support/Comments for PHx

antirem — Dec 03, 2008, 01:56 PM

Thanks... i feel like and idiot now. We have a site that has all the commonly used codes that we use and we just duplicate it for each new site so it had the old info.

Thanks!

quick question... it seems like phx could be used to escalate user privlege... some sites have a lot of manager users and if you put in phx code you might be able to say this page has this type of security needed etc..

im sure there are other plugins the let you add shells.. so maybe its not a sizeble threat.

Re: Support/Comments for PHx

Metaller — Dec 03, 2008, 02:18 AM

Set correct path in system settings tab - tools - configuration - Interface & Features - Resource path. Seems it must be

/mnt/target03/358650/www.arezombiesattacking.com/web/content/assets/

Re: Support/Comments for PHx

antirem — Dec 03, 2008, 01:01 AM

I made a folder in /assets/plugins called "phx" and dumped all the contents of the latest version in there... so there is a /assets/plugins/phx/phx.parser.class.inc.php and etc....
I copied all of the contents of phx.plugin.txt in my new plugin called "PHx".. then i set the system event to "OnParseDocument"

(i am doing everything right)

This results in the modx error of..

« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« PHP Parse Error »
 
PHP error debug
  Error: 	include_once(/assets/plugins/phx/phx.parser.class.inc.php) [function.include-once]: failed to open stream: No such file or directory	 
  Error type/ Nr.: 	Warning - 2	 
  File: 	/mnt/target03/358650/www.arezombiesattacking.com/web/content/manager/includes/document.parser.class.inc.php(745) : eval()'d code	 
  Line: 	10	 
 
Parser timing
  MySQL: 	0.0121 s	(3 Requests)
  PHP: 	0.1680 s	 
  Total: 	0.1801 s

The file IS there... i am not calling phx even yet.

What should i do?

Re: Support/Comments for PHx

asamax01 — Aug 24, 2008, 02:00 PM

Parsing arrays (or other complex variables)

Hi,
maybe I’m heading for a very hard way to solve a simple issue - please help me.

I’m using phx through Chunkie class in a snippet (not installing phx as a plugin).
Everithing seems ok. Very useful the new template-file feature!

My snippet needs to output simple or complex variables: strings or arrays (of strings and of arrays of...). I’ve got to use a template regardless type of variables (type and composition can’t be foreseen).
I modified method CreateVars of Chunkie class, because it seems not possible to pass an array to a modifier:

function CreateVars($value = '', $key = '', $path = '') {
$keypath = !empty($path) ? $path . "." . $key : $key;
	if (is_array($value)) {
	    		
	     // added
	     //		type		name		fields
	     $info_string =	'array'.',' .	$keypath.',' .	implode(',' , array_keys($value));
	    		 				
             foreach ($value as $subkey => $subval) {
	     $this->CreateVars($subval, $subkey, $keypath);
	}
			
	// added
	$this->CreateVars($info_string, '__info', $keypath);			
	}
	else {
		$this->phx->setPHxVariable($keypath, $value);
	}
}

By this, if I pass an array:

$aaaa = array( "field1" => 5, "field2" => array( "field21" => 2));

as phx variable ’aaaa’ I get the placeholders:

[+aaaa.__info+] = "array,aaaa,field1,field2" (added placeholder containing type, name, fields list)
[+aaaa.field1+] = "5" (no news)
[+aaaa.field2.__info+] = "array,aaaa.field2,field21" (added placeholder containing type, name, fields list)
[+aaaa.field2.field21+] = "2" (no news)

while I can’t get placeholders for aaaa and aaaa.field2 because they’re not simple variables.

In this way I can create a template like

[+phx:input=`[+aaaa+]`:elements=`[+aaaa.__info+]`+]

which calls method elements:

' . $var_name . ' = ' . $var_type . '

';
$string .= '
';

foreach ($var_fields_array as $fieldname) {
	$field_placeholder = '[+' . $var_name . '.' . $fieldname . '+]';
	$options_placeholder = '[+' . $var_name . '.' . $fieldname . '.__info' . '+]';
	$string .= '' . $fieldname . ' = ' . '[+phx:input=`' . $field_placeholder . '`:elements=`' . $options_placeholder . '`+]' . '
';
}
$string .= '
';

return $string;
?>

which calls itself each time an element is an array.

the output is
aaaa = array
- field1 = 5
- field2 = aaaa.field2 = array
- field21 = 2

This is the only way I found to explore complex variables: I only have to know the variable name - no need to know if it is simple, an array and which fieldnames.
Of course this is just a test.

Two questions:
1 - Is there a different simple way to pass arrays as variables and use them with phx placeholders when the template doesn’t know field names?
2 - Is there a way to use templates within a modifier code (avoiding html tags into the modifier).
(3 - any other suggestion is welcome..)

thanks in advance

Re: Support/Comments for PHx

TobyL — Jun 30, 2008, 10:18 AM

Perhaps in your case a dedicated snippet which does all the logic TV testing and simply outputs the results would be more appropriate. Sounds to me you are trying to solve something in the template which really is better suited to be solved directly in php.

Re: Support/Comments for PHx

paulb — Jun 29, 2008, 11:02 AM

Thanks for the reply. Yeah, that will work, but I usually have to put large amounts of information in the conditional area, so I’d have to repeat all of that over and over again. I could create a chunk, and maybe that’s what I’ll have to do, but I end up creating a lot of chunks that way that could be avoided if there were a simpler combined conditional statement.

The real pain is creating complex nested conditions that combined "and" and "or" logic. It gets very messy very quickly. For one thing, it’s hard for me to keep track of all of the conditions being processed when the conditions are spread around in so many places. I’m more likely to make errors, and it’s harder to debug because you can’t do it at a quick glance. All of the conditions get mixed in with complex content that also has conditions. It’s very messy.

Re: Support/Comments for PHx

Metaller — Jun 29, 2008, 01:26 AM

You can split this condition on several:

[+tv1:isnot=``:then=`At least one of these is not empty.`:else=`
[+tv2:isnot=``:then=`At least one of these is not empty.`:else=`
[+tv3:isnot=``:then=`At least one of these is not empty.`+]
`+]
`+]

As you says, it is not as elegant as a single conditional statement but it works.

Re: Multiple conditions in PHx

paulb — Jun 28, 2008, 01:17 PM

Quote from: Metaller at Jun 28, 2008, 06:00 PM

You can use multiple variables like that

[+tv1:isnot=``:then=`
[+tv2:isnot=``:then=`
Template Variable 1 and Template Variable 2 are not empty
`+]
`+]

That will work for some things -- though it is not as elegant as a single conditional statement -- but a common situation for me is the need to check to see if at least one value is not empty. In other words, I need an "or" condition, something like this:

if ( ($tv1 != '') || ($tv2 != '') || ($tv3 != '') ) echo 'At least one of these is not empty.';