Jump to content
adrian

Redirect Id Based Urls

Recommended Posts

Sorry @Nukro - I haven't tested with multisite. Perhaps if you can point me to where the problem is I can figure out a fix. Unfortunately I don't have time at the moment to setup the multisite module to test myself.

Let me know if you can narrow it down.

Share this post


Link to post
Share on other sites
16 hours ago, adrian said:

Sorry @Nukro - I haven't tested with multisite. Perhaps if you can point me to where the problem is I can figure out a fix. Unfortunately I don't have time at the moment to setup the multisite module to test myself.

Let me know if you can narrow it down.

Hi @adrian

False Alarm.. I tested it again and it looks like it's working :lol:. Since the template/pages were protected, I had to loggedin in the right "domain root/alias".

  • Like 1

Share this post


Link to post
Share on other sites

Hi @adrian

I have an question about urlSegments and your Module.

Let's say I have a url like this:

http://example.com/de/clinicroot.com/our-doctors/franz-muster/

I can access this site/url (http://example.com/de/clinicroot.com/our-doctors/) with the ID thanks to your module:

for example like this:

http://example.com/de/3412/ -> would redirect to -> http://example.com/de/clinicroot.com/our-doctors/

But how can I make it happen, that it would redirect to the url with the urlSegment? Is this somehow possible with your module? Or do I need to do some htaccess magic or something?

PS: At the moment my template code looks after the urlSegment, takes it and search it after the pagename(since franz-muster is the name of the page) in the db.

 

Greetings Nukro

Share this post


Link to post
Share on other sites

@Nukro - what you are after is certainly possible, but I am not sure the best way to make it handle everyone's need and not break current functionality for existing users because at the moment the module doesn't consider anything other than the page ID being somewhere in the URL. This allow ultimate flexibility in the URL, but obviously prevents detection of URL segments. I guess it could be a module config option to consider everything after the ID as segments that should be parsed.

Anyway, for now I have attached a version that should do what you want. Please test thoroughly and let me know how it goes. If it's working fine at your end, I'll probably make the urlSegment detection optional and release it.

ProcessRedirectIds.module

  • Like 2

Share this post


Link to post
Share on other sites
On 27.1.2017 at 10:15 PM, adrian said:

@Nukro - what you are after is certainly possible, but I am not sure the best way to make it handle everyone's need and not break current functionality for existing users because at the moment the module doesn't consider anything other than the page ID being somewhere in the URL. This allow ultimate flexibility in the URL, but obviously prevents detection of URL segments. I guess it could be a module config option to consider everything after the ID as segments that should be parsed.

Anyway, for now I have attached a version that should do what you want. Please test thoroughly and let me know how it goes. If it's working fine at your end, I'll probably make the urlSegment detection optional and release it.

ProcessRedirectIds.module

Thanks @adrian!

I will test the new version when we have finished the going live process of the website we are building. I had solved this problem last friday for the moment like this:

I activated urlSegments for the domain_root Template with this regex:

regex:^[1-999999]

Code at the beginning of the domain_root Templatefile:

if($input->urlSegment1){
	$id = $sanitizer->selectorValue($input->urlSegment1);
	$ziel = $pages->get("id=$id");
	if($ziel->id){
		if($ziel->is("template=news")){
			if($ziel->parent->id == 34044){
				$url = $overviews["news"].$ziel->name;
			}elseif($ziel->parent->id == 41821){
				$url = $overviews["media"].$ziel->name;
			}
		}
		$idMapping = array(
			"doctors" => $overviews["doctors"].$ziel->name,
			"specialties" => $overviews["specialties"].$ziel->name,
			"jobs" => $overviews["jobs"].$ziel->name,
			"signup-form-formbuilder" => $overviews["events"].$ziel->name,
			"baby" => $overview["baby"].$ziel->name,
			"news" => $url,
		);
		$session->redirect($idMapping[$ziel->template->name]);
	}
}

At the moment this quite works good for my needs.

 

Share this post


Link to post
Share on other sites

Hi @adrian

I have some Problem with the shortLinks. Your Module creates a Tab 'ShortLinks' for all pages with 3 links. The first one with only the id and the second one doesn't work anymore for me after I had installed an activated Multisite. But somehow the third one works. It looks like when the Link is starting with a id it redirects always to a blank page but all the other example links are working somehow.

 

Greetings

Orkun

Share this post


Link to post
Share on other sites

Yeah, I am not surprised those links don't work in the version of the module I posted for you - it is looking for url segments that don't exist. This is why I need to make looking for segments optional. As for the actual Shortlinks tab - I think it's probably time I got rid of that - I don't really think it serves a purpose - any thoughts?

Share this post


Link to post
Share on other sites
On 1.2.2017 at 3:35 PM, adrian said:

Yeah, I am not surprised those links don't work in the version of the module I posted for you - it is looking for url segments that don't exist. This is why I need to make looking for segments optional. As for the actual Shortlinks tab - I think it's probably time I got rid of that - I don't really think it serves a purpose - any thoughts?

Hi @adrian

What can I do for the moment, that it works again with only the id? Are you planning to release an update soon? 

In terms of the shortlink tab I think it doesn't really serves for a purpose.

Greetings Orkun

Share this post


Link to post
Share on other sites
8 hours ago, Nukro said:

What can I do for the moment, that it works again with only the id?

Can't you go back to the official released version?

Honestly I don't plan on spending too much time on this module - I don't think it gets much use. I created that new version for you to support url segments, but now it seems that you don't want them? Maybe I don't fully understand your needs. If you could give me a full explanation of all the scenarios you want supported I can take another go at it.

  • Like 1

Share this post


Link to post
Share on other sites

just wanted to mention that this works fantastically for multilingual sites, thanks @adrian

yoursite.com/en/pageID

yoursite.com/fr/pageID

yoursite.com/de/pageID

:)

 

I also modified the module slightly so that the "shortlinks" only display for superuser

in the module file

	public function ready() {

		// we're interested in page editor only
		if(wire('page')->process != 'ProcessPageEdit') return;

		// skip changing templates (only target the actual edit form)
		$id = (int)$this->input->get->id;
		if(!$id) return;

		// wire('page') would be the page with ProcessPageEdit
		// GET parameter id tells the page that's being edited
		$this->editedPage = wire('pages')->get($id);

		// don't even consider system templates
		if($this->editedPage->template->flags & Template::flagSystem) return;
		// Display only for superuser so get current user and check if user is superuser
		$user = wire('users')->getCurrentUser();
        if($this->isAllowed($this->editedPage) && $this->editedPage->id != 1 && $user->isSuperuser()){
			$this->addHookAfter('ProcessPageEdit::buildForm', $this, 'addShortURLLinks');
		}
	}

 

  • Like 1

Share this post


Link to post
Share on other sites

I have an external php script (launched by cron) that uses ProcessWire (i.e. by including index.php, as explained here).

I have the ProcessRedirectIds module installed, and when I run the script I get this warning:

Notice: Undefined index: REQUEST_URI in /var/www/www.mysite.example/site/assets/cache/FileCompiler/site/modules/ProcessRedirectIds/ProcessRedirectIds.module on line 66

Obviously there is no REQUEST_URI in this case, but the module seems not aware of this possibility...

 

  • Like 1

Share this post


Link to post
Share on other sites

Hi @Mike-it - I have updated the module to fix this.

I have also done a lot of code cleanup and a few improvements.

Let me know how it goes.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory (pending approval) Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...