Permalinks Change?

Note:

I've just noticed I am also receiving an error message when trying to save:

E_ERROR: Call to undefined function permalink_cms_onSaveUpdatePermalinks()

Hope this helps!

:0/

Perch

Hi Perch,

It seems like permalink_cms_onSaveUpdatePermalinks function is not getting loaded on your page anymore.

I checked the code and the permalink_cms_onSaveUpdatePermalinks() function has been moved to /cmsb/plugins/permalinks/permalinks_cmsMenus.php since version 1.03.

And the permalinks_cmsMenus.php is only called if the logged in user is an admin.

To resolve this, you can either:

1. Include the permalinks_cmsMenus.php file in your add/edit page (not recommended because the functions inside this file are designed to be used in CMS admin pages)
2. Use permalink_add() function which returns an error if there is any. Ie: permalink is already in use

   // add/update permalink
$errors = permalink_add(@$_REQUEST['permalink'], $tableName, $recordNum);

Let me know how it goes!

UPDATE:

The permalink_add() doesn't do the permalink error checking, so it's better to include permalinks_cmsMenus.php file and use permalink_cms_onSaveUpdatePermalinks() function.

Thanks,

Hi Perch,

Have I added the new line correctly?

Looks good!

Currently my savePage does not "report" errors. (If there is a code problem it just doesn't work!)

1) In the unlikely event that there is a clash of permalinks, how would I feed the error back to my savePage - without breaking the anything (and losing the changes that could have been made to the page)?

The permalink_cms_onSaveUpdatePermalinks() function doesn't return the error message and instead, calls the die($error) function if there's an error.
So if you want to control the error reporting, you can copy the code and create your own version of this function that returns the error messages instead of dying. See the second step below.

2) What code would I use to check if a new permalink has been added to an input box and, if so, then update the required tables?

First, convert the input box value to SEO-friendly URL (converts spaces to dashes, removes non-alphanumeric characters):

$permalink = _permalink_generate_formatInputText($_REQUEST['permalink_input_box']);

Second, check $permalink for errors. The code below is derived from permalink_cms_onSaveErrorChecking() function (you can convert the code below to you own function):

// check if permalink already exists in database
$permalinkRecord = mysql_get('_permalinks', null, array('permalink' => $permalink)); 
$isAlreadyUsed   = $permalinkRecord && $permalinkRecord['recordNum'] != $recordNum && ($tableName != '_permalinks');

// error checking
$errors = '';
$requiredPrefix  = $GLOBALS['schema']['permalink']['defaultValue'];
if     (!$permalink)                              { $errors .= "You must enter a value for 'permalink'!"; }
elseif (preg_match("!^/!", $requiredPrefix))      { $errors .= "Permalink prefix can not start with a slash! Change the 'Default Value' for permalink field in Field Editor."; }
elseif ($permalink == $requiredPrefix)            { $errors .= "You must enter a value for 'permalink' after '" .htmlencode($requiredPrefix). "'!"; }
elseif (!startsWith($requiredPrefix, $permalink)) { $errors .= "Permalink must start with '" .htmlencode($requiredPrefix). "'!"; }
elseif (preg_match("|[^\w\-\./]|i", $permalink))  { $errors .= "Permalink can only contain these chars (a-z0-9/-.)!"; }
elseif (preg_match("!^/|/$!", $permalink))        { $errors .= "Permalink can not start or end with a slash!"; }
elseif (preg_match("!\.{2,}!", $permalink))       { $errors .= "Permalink can not include '..'!"; }
elseif (preg_match("!/{2,}!", $permalink))        { $errors .= "Permalink can not include '//'!"; }
elseif ($isAlreadyUsed)                           { $errors .= sprintf("Permalink '%s' is already in use, please choose another!", htmlencode($permalink)); }

Next, if there's no error, add/update the permalink of the record.
The permalink_add() function will take care of adding/updating the new permalink and will return an error if there is any.
If it doesn't return an error, you can continue with your other process, ie: update record.

if (!$errors) {
  // add/update permalink
  $errors = permalink_add($permalink, $tableName, $recordNum);
  
  if (!$error) {
    // do other stuff here, ie: update record
  }
}

Or you can do your other process first then add/update the permalink.

Finally, if there's an error, display it on your page.

NOTE: The code above are just examples and were not tested so you might need to tweak it more.

Let me know any questions!

Thanks,

Hi Daryl,

I allow myself to introduce a question here.

It would be possible to exclude the 'old' link in functions permalink_cms_onSaveUpdatePermalinks and permalink_add ?

It would be then possible to again use a link without having to remove it before in permalinks table.

Thanks!

Djulia

That works for me:

$permalinkRecord = mysql_get('_permalinks', null, "`permalink` = '".$permalinkText."' AND `old` = ''");


Your opinion? Thanks again!

Djulia

Hi Djulia.

It would be possible to exclude the 'old' link in functions permalink_cms_onSaveUpdatePermalinks and permalink_add ?

It would be then possible to again use a link without having to remove it before in permalinks table.

You would like to use permalink URL that is already used (old) by another record without having to delete it from the permalink table?

I wouldn't recommend doing it because we're using the old permalink to redirect the users to the current one when they visit the old URL. 
This is helpful for users who bookmarked a URL with an old permalink or when search engines or browsers cached the page's old URL, users will still get redirected to the correct page.

But if you don't mind the old permalinks, you can delete the old permalink record instead of updating it as an old record whenever you add a new one.
To do that, in permalink_add() function, change the block of code with comment "mark all other matching permalinks for this record as old" from mysql update to mysql delete.

I never tried this before and don't know what other negative effects it could cause so I'd like to suggest to do lots of testing first and see if the benefits of not checking the old permalink outweigh the negative effects of it.

Hope that helps!

Cheers,