I noticed an bug while just installing 1.3.0 (haven’t converted from PPP to WLPE yet). Seems [+user.lastlogin+] isn’t parsing at all. This was working in 1.1.1, IIRC.
Total # of Logins works like it should, however.
case 'deleteprofilesimple':
if (in_array('deleteprofile', $disableServices)){return;}
return $displayProfileDeleteTpl;
break;
case 'deleteprofilesimple':
if (in_array('deleteprofilesimple', $disableServices)){return;} // NOTE: added simple to in_array check
return $displayProfileDeleteTpl;
break;
case 'deleteprofilesimple':
if (in_array($service, $disableServices)){return;} // NOTE: Using the $service variable
return $displayProfileDeleteTpl;
break;
case 'confirmdeleteprofilesimple':
if (in_array('confirmdeleteprofile', $disableServices)){return;} // <-- Why not confirmdeleteprofilesimple?
case 'confirmdeleteprofilesimple':
if (in_array($service, $disableServices)){return;}
When using friendly alias paths, you must have a base href in your HEAD with the site URL to avoid this issue. Adding a / in front simply makes the path absolute to the web root, and thus, not portable.
So since this is in a "folder" called /mysymphonic, I would need to make a template just for it, and put in the base href?
<base href="[(site_url)]"/>
Hmm...a quick question about custom fields.
Since I’m using a custom table, if I let WLPE know that (via the parameter for it), when I make a new field that doesn’t exist right now in &customfields, like the emailprivate, I assume that WLPE will create that field and populate it? Or do I have to create the field myself? PPP made you create the fields before you could populate them.
(Sorry for all of the questions lately...this script is a LOT more complex than PPP was.)