Jump to content
apeisa

Multisite

Recommended Posts

@Soma in your README, at the bottom, you write:
 

Quote

Since the whole concept is all a pretty hack, I found that it comes with some complications that can't be solved in an elegant way. So for example the biggest issue is that you can't crosslink pages via the RTE Link plugin, since it doesn't know about Multisite. So you'll end with wrong URL's when for example you link from a page of one site to a page of another site. If that's an issue it's still possible to copy the ProcessPageEditLink.module and modify the root parent for the page tree select. I'd be glad to help out with an example there.

I was doing a few tests just now. For me, it all works wonderfully (well, at least in a local setup). Did you change something recently in that regard and forgot to edit the readme?
 

Share this post


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

@Soma in your README, at the bottom, you write:
 

I was doing a few tests just now. For me, it all works wonderfully (well, at least in a local setup). Did you change something recently in that regard and forgot to edit the readme?
 

Yeah that's not anymore. There's a parser on page render now.

Share this post


Link to post
Share on other sites

The module is working otherwise great (thanks a lot!), but when visiting www. subdomain, the URLs of the rootParent children lack the domain.

$siteRoot = $page->rootParent;
$nav = "";
foreach ($siteRoot->children as $child) {
  $nav .= "<a href='$child->url'>$child->title</a>\n";
}

This produces urls like https://pagename

I can use <a href='/$child->name'> instead to make them work as relative URLs, but it would be nice to know what is going wrong.

Setup:

- Home
  - mysite.com
  - myothersite.com

$config->MultisiteDomains = array(
    "mysite.com" => array(
            "root" => "mysite.com",
            "http404" => 27
        ),
    "www.mysite.com" => array(
            "root" => "mysite.com",
            "http404" => 27
        ),
    "myothersite.com" => array(
            "root" => "myothersite.com",
            "http404" => 1017
        ),
    "www.myothersite.com" => array(
            "root" => "myothersite.com",
            "http404" => 1017
        )
);
$config->httpHosts = array('mysite.com','www.mysite.com','myothersite.com','www.myothersite.com');

If I don't have the separate www. entries in MultisiteDomains, it does not work. It just throws me to the "Home" page, if I try to navigate to www. subdomain.

Share this post


Link to post
Share on other sites

Maybe I'm missing something here but I ran into minor problems setting this up for domains that contain a hyphen.

First of all the setup is multisite AND multilanguage.
PW 3.0.130, Multisite Module from Github, 3 domains, 2 languages

Link from ProcessWire Backend: http://abelt.test/en/alexander-abelt.test/ gets wrongly redirected to http://abelt.test/en/alexander- and not to http://alexander-abelt.test/en/.

In this case it's not a real deal-breaker as it's only a setup I need for some of my domains and I know how to work around this but nonetheless I'd like to know if I have to change something or if it is a hiccup here.

Share this post


Link to post
Share on other sites
5 minutes ago, wbmnfktr said:

Maybe I'm missing something here but I ran into minor problems setting this up for domains that contain a hyphen.

First of all the setup is multisite AND multilanguage.
PW 3.0.130, Multisite Module from Github, 3 domains, 2 languages

Link from ProcessWire Backend: http://abelt.test/en/alexander-abelt.test/ gets wrongly redirected to http://abelt.test/en/alexander- and not to http://alexander-abelt.test/en/.

In this case it's not a real deal-breaker as it's only a setup I need for some of my domains and I know how to work around this but nonetheless I'd like to know if I have to change something or if it is a hiccup here.

I think this can happen if your multisite root page name has also the domain name in it. You should avoid that. Just rename it to something else

 

On 3/31/2019 at 9:34 PM, Beluga said:

The module is working otherwise great (thanks a lot!), but when visiting www. subdomain, the URLs of the rootParent children lack the domain.


$siteRoot = $page->rootParent;
$nav = "";
foreach ($siteRoot->children as $child) {
  $nav .= "<a href='$child->url'>$child->title</a>\n";
}

This produces urls like https://pagename

I can use <a href='/$child->name'> instead to make them work as relative URLs, but it would be nice to know what is going wrong.

Setup:

- Home
  - mysite.com
  - myothersite.com


$config->MultisiteDomains = array(
    "mysite.com" => array(
            "root" => "mysite.com",
            "http404" => 27
        ),
    "www.mysite.com" => array(
            "root" => "mysite.com",
            "http404" => 27
        ),
    "myothersite.com" => array(
            "root" => "myothersite.com",
            "http404" => 1017
        ),
    "www.myothersite.com" => array(
            "root" => "myothersite.com",
            "http404" => 1017
        )
);

$config->httpHosts = array('mysite.com','www.mysite.com','myothersite.com','www.myothersite.com');

If I don't have the separate www. entries in MultisiteDomains, it does not work. It just throws me to the "Home" page, if I try to navigate to www. subdomain.

My guess is that this comes from the fact you have domain.com and www.domain.com. You want to avoid that, cause the script isn't clever enough to know which is which. In any case you want to avoid having two domains setup for the same site. You should redirect your www to non www or the other way around.

  • Like 1

Share this post


Link to post
Share on other sites
4 minutes ago, Soma said:

I think this can happen if your multisite root page name has also the domain name in it. You should avoid that. Just rename it to something else

Ok... I see the problem.

alexander-abelt.test shares one of the other domains abelt.test in it which I can't really avoid as these are or will be my domains (just with another .tld of course) I want to use later on.

As this has no further effects on maintaining content, building menus and whatever so far I guess I can ignore that linking/redirecting issue for now.

Thanks for pointing that out.

Share this post


Link to post
Share on other sites

Ah reading againg. 

9 minutes ago, wbmnfktr said:

Ok... I see the problem.

alexander-abelt.test shares one of the other domains abelt.test in it which I can't really avoid as these are or will be my domains (just with another .tld of course) I want to use later on.

As this has no further effects on maintaining content, building menus and whatever so far I guess I can ignore that linking/redirecting issue for now.

Thanks for pointing that out.

Ah reading again, I'm not 100% sure why this happens in your case. (but most likely what i said anyway :)) What is the setup config? And what Module version?

Share this post


Link to post
Share on other sites
2 minutes ago, Soma said:

but most likely what i said anyway 🙂

It works aside from that redirect issue so... I guess I will survive. 😉 

2 minutes ago, Soma said:

What is the setup config? And what Module version?

PW 3.0.130, Multisite Module from Github (says 0.1.2), 3 domains, 2 languages on Linux (Ubuntu), Apache 2.4, PHP 7.2

Page tree:

Screenshot-20190507-151451.png.2ed4cfd809345aba190eb75fd278f6e6.png

config.php

$config->MultisiteDomains = array(
    "abelt.test" => array( // domain name is used to map to root page
            "root" => "abelt.test", // page name for the root page
            "http404" => 1031
        ),
    "alexander-abelt.test" => array( // funktioniert nicht mit /en/ auf Home
            "root" => "alexander-abelt.test",
            "http404" => 1029
        ),
    "kettenburg14.test" => array(
            "root" => "kettenburg14.test",
            "http404" => 1030
        )
);

$config->httpHosts = array('abelt.test', 'alexander-abelt.test', 'kettenburg14.test');
// $config->httpHosts = array_keys($config->MultisiteDomains);

 

Share this post


Link to post
Share on other sites
4 minutes ago, wbmnfktr said:

It works aside from that redirect issue so... I guess I will survive. 😉 

PW 3.0.130, Multisite Module from Github (says 0.1.2), 3 domains, 2 languages on Linux (Ubuntu), Apache 2.4, PHP 7.2

Page tree:

Screenshot-20190507-151451.png.2ed4cfd809345aba190eb75fd278f6e6.png

config.php


$config->MultisiteDomains = array(
    "abelt.test" => array( // domain name is used to map to root page
            "root" => "abelt.test", // page name for the root page
            "http404" => 1031
        ),
    "alexander-abelt.test" => array( // funktioniert nicht mit /en/ auf Home
            "root" => "alexander-abelt.test",
            "http404" => 1029
        ),
    "kettenburg14.test" => array(
            "root" => "kettenburg14.test",
            "http404" => 1030
        )
);

$config->httpHosts = array('abelt.test', 'alexander-abelt.test', 'kettenburg14.test');
// $config->httpHosts = array_keys($config->MultisiteDomains);

 

Yes the problem is most likely that both sites share the same names in it.

abelt.test is in both setups and even in the root name. Just rename the root to something else more unique would do the trick. It's not something you would see anyway. 

"abelt.test" => array( // domain name is used to map to root page
            "root" => "abelt", // page name for the root page
            "http404" => 1031
        ),
    "alexander-abelt.test" => array( // funktioniert nicht mit /en/ auf Home
            "root" => "alexander",
            "http404" => 1029
        ),
  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

That did the trick perfectly!

Changing root and the page names fixed it. Didn't really get that the page's name doesn't have to be the domain actually.

Share this post


Link to post
Share on other sites

An additional sitenote here:

Changing the root name to something different than the domain is not enough.
If that page name appears anywhere else at the end of an URL the hiccup is back.

root = abelt
Problematic page URL = /about-abelt/ 
Problematic page URL = /about/abelt/
Working page URL = /about-abelt-whatever/

As to make sure I don't run into any issues with this I changed my root page names to something a cat would write while walking over the keyboard.

An additional sitenote here:

Changing the root name to something different than the domain is not enough.
If that page name appears anywhere else at the end of an URL the hiccup is back.

root = abelt
Problematic page URL = /about-abelt/ 
Problematic page URL = /about/abelt/
Working page URL = /about-abelt-whatever/

As to make sure I don't run into any issues with this I changed my root page names to something a cat would write while walking over the keyboard.

Share this post


Link to post
Share on other sites
21 minutes ago, wbmnfktr said:

An additional sitenote here:

Changing the root name to something different than the domain is not enough.
If that page name appears anywhere else at the end of an URL the hiccup is back.

root = abelt
Problematic page URL = /about-abelt/ 
Problematic page URL = /about/abelt/
Working page URL = /about-abelt-whatever/

As to make sure I don't run into any issues with this I changed my root page names to something a cat would write while walking over the keyboard.

An additional sitenote here:

Changing the root name to something different than the domain is not enough.
If that page name appears anywhere else at the end of an URL the hiccup is back.

root = abelt
Problematic page URL = /about-abelt/ 
Problematic page URL = /about/abelt/
Working page URL = /about-abelt-whatever/

As to make sure I don't run into any issues with this I changed my root page names to something a cat would write while walking over the keyboard.

I don't have cats 😛

Yes that's true. I know the "redirect if domain name is found in url" would need even a much more sophisticated parsing method, but it gets too complicated for my brain. I think having random strings as root name would be a much easier solution.

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, Soma said:

I don't have cats

That could become a problem then. You should add it as a requirement to the module nonetheless. 😉

2 minutes ago, Soma said:

would need even a much more sophisticated parsing method, but it gets too complicated for my brain.

Not needed when everything was set up correctly with this things in mind. You know about that and do the necessary things. I'm relatively new to this setup and had to work through this. Now I know too.

2 minutes ago, Soma said:

I think having random strings as root name would be a much easier solution.

It is. Actually it could make other things easier when debugging. As I see some weird strings instead of domain(.tld) now I don't falsely think of domain names and such things. I know right away it's something different and where it comes from.

Share this post


Link to post
Share on other sites

How do you guys handle developing on local machines regarding Multisite? Often I download the production database and I have different config.php, but I'm starting to dislike that approach 🙂 I can off course put all the environment stuff in an .ini and read with parse_ini. 

$config->MultisiteDomains = array(
    'www.realdomain.com' => array(
            'root' => 'www.realdomain.com',
            'http404' => 1045
        ),
    'realdomain.localhost' => array(
            'root' => 'realdomain.localhost',
            'http404' => 1045
        ),
    'www.anotherrealdomain.com' => array(
            'root' => 'www.anotherrealdomain.com',
            'http404' => 1046
        ),
    'anotherrealdomain.localhost' => array(
            'root' => 'anotherrealdomain.localhost',
            'http404' => 1046
        ),
  );

I have a lot of domains in the multisite. Would love to hear your approaches.  

Share this post


Link to post
Share on other sites
8 minutes ago, arjen said:

How do you guys handle developing on local machines regarding Multisite? Often I download the production database and I have different config.php, but I'm starting to dislike that approach 🙂


$config->MultisiteDomains = array(
    'www.realdomain.com' => array(
            'root' => 'www.realdomain.com',
            'http404' => 1045
        ),
    'realdomain.localhost' => array(
            'root' => 'realdomain.localhost',
            'http404' => 1045
        ),
    'www.anotherrealdomain.com' => array(
            'root' => 'www.anotherrealdomain.com',
            'http404' => 1046
        ),
    'anotherrealdomain.localhost' => array(
            'root' => 'anotherrealdomain.localhost',
            'http404' => 1046
        ),
  );

I have a lot of domains in the multisite. Would love to hear your approaches.  

I have a config-dev.php for dev server or local setup. and the "root" stays the same just the domains are different.

  • Like 1

Share this post


Link to post
Share on other sites

Ah, the good old -dev approach. That might work here too. I used to have it everywhere, but I've switched to more generic config.php which reads a config.ini which is outside my version control. The big disadvantage here is when you have a lot of customisations in your config.php. Thanks for reminding me.

Share this post


Link to post
Share on other sites

We have a local config.env.php file which is read by our general config.php.

Everything that is commun is in config.php, but local settings are kept in config.env.php.

In config.php:

/**
 * Environment configuration file
 * 
 */
$configFile = $config->paths->site . 'config.env.php';
 
 @require_once($configFile);
  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, arjen said:

How do you guys handle developing on local machines regarding Multisite?

You can also edit your local HOSTS file, so the domains always stay the same. Just remember to comment your hosts file when working on the live site 🙂

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By teppo
      MarkupMenu is a markup module for generating menu trees. When provided a root page as a starting point, it generates a navigation tree (by default as a HTML "<ul>" element wrapped by a "<nav>" element) from that point onwards. If you've also provided it with current (active) page, the menu will be rendered accordingly, with current item highlighted and items rendered up to that item and its children (unless you disable the "collapsed" option, in which case the full page tree will be rendered instead).
      Modules directory: https://modules.processwire.com/modules/markup-menu/ GitHub repository: https://github.com/teppokoivula/MarkupMenu Usage
      As a markup module, MarkupMenu is intended for front-end use, but you can of course use it in a module as well. Typically you'll only need the render() method, which takes an array of options as its only argument:
      echo $modules->get('MarkupMenu')->render([ 'root_page' => $pages->get(1), 'current_page' => $page, ]); Note: if you omit root_page, site root page is used by default. If you omit current_page, the menu will be rendered, but current (active) page won't be highlighted etc.
      A slightly more complex example, based on what I'm using on one of my own sites to render a (single-level) top menu:
      echo $modules->get('MarkupMenu')->render([ 'current_page' => $page, 'templates' => [ 'nav' => '<nav class="{classes} menu--{menu_class_modifier}" aria-label="{aria_label}">%s</nav>', 'item_current' => '<a class="menu__item menu__item--current" href="{item.url}" tabindex="0" aria-label="Current page: {item.title}">{item.title}</a>', ], 'placeholders' => [ 'menu_class_modifier' => 'top', 'aria_label' => 'Main navigation', ], 'include' => [ 'root_page' => true, ], 'exclude' => [ 'level_greater_than' => 1, ], ]); Note: some things you see above may not be entirely sensible, such as the use of {menu_class_modifier} and {aria_label} placeholders. On the actual site the "nav" template is defined in site config, so I can define just these parts on a case-by-case basis while actual nav markup is maintained in one place.
      Please check out the README file for available render options. I'd very much prefer not to keep this list up to date in multiple places. Basically there are settings for defining "templates" for different parts of the menu (list, item, etc.), include array for defining rules for including in the menu and exclude array for the opposite effect, classes and placeholders arrays for overriding default classes and injecting custom placeholders, etc. 🙂
      MarkupMenu vs. MarkupSimpleNavigation
      TL;DR: this is another take on the same concept. There are many similarities, but also some differences – especially when it comes to the supported options and syntax. If you're currently using MarkupSimpleNavigation then there's probably no reason to switch over.
      I'd be surprised if anyone didn't draw lines between this module and Soma's awesome MarkupSimpleNavigation. Simply put, I've been using MSN (...) for a number of years, and it's been great – but there have been some smallish issues with it, particularly with the markup generation part, and it's also doing some things in a way that just doesn't work for me – the xtemplates thing being one of these. In many ways it's less about features, and more about style.
      In MarkupMenu I've tried to correct these little hiccups, modernise the default markup, and allow for more flexibility with placeholder variables and additional / different options. MarkupMenu was built for ProcessWire 3.0.112+ and PHP 7.1+, it's installable with Composer, and I have a few additional ideas (such as conditional placeholders) on my todo list.
      One smallish and rather specific difference is that MarkupMenu supports overriding default options via $config->MarkupMenu. I find myself redefining the default markup for every site, which until now meant that each site has a wrapper function for MarkupSimpleNavigation (to avoid code / config repetition), and this way I've been able to omit that 🙂
      Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 If you're working on an earlier version of ProcessWire or PHP, use MarkupSimpleNavigation instead.
    • By Robin S
      Repeater Images
      Adds options to modify Repeater fields to make them convenient for "page-per-image" usage. Using a page-per-image approach allows for additional fields to be associated with each image, to record things such as photographer, date, license, links, etc.
      When Repeater Images is enabled for a Repeater field the module changes the appearance of the Repeater inputfield to be similar (but not identical) to an Images field. The collapsed view shows a thumbnail for each Repeater item, and items can be expanded for field editing.
      Screencast

      Installation
      Install the Repeater Images module.
      Setup
      Create an image field to use in the Repeater field. Recommended settings for the image field are "Maximum files allowed" set to 1 and "Formatted value" set to "Single item (null if empty)". Create a Repeater field. Add the image field to the Repeater. If you want additional fields in the Repeater create and add these also. Repeater Images configuration
      Tick the "Activate Repeater Images for this Repeater field" checkbox. In the "Image field within Repeater" dropdown select the single image field. You must save the Repeater field settings to see any newly added Image fields in the dropdown. Adjust the image thumbnail height if you want (unlike the core Images field there is no slider to change thumbnail height within Page Edit). Note: the depth option for Repeater fields is not compatible with the Repeater Images module.
      Image uploads feature
      There is a checkbox to activate image uploads. This feature allows users to quickly and easily add images to the Repeater Images field by uploading them to an adjacent "upload" field.
      To use this feature you must add the image field selected in the Repeater Images config to the template of the page containing the Repeater Images field - immediately above or below the Repeater Images field would be a good position.
      It's recommended to set the label for this field in template context to "Upload images" or similar, and set the visibility of the field to "Closed" so that it takes up less room when it's not being used. Note that when you drag images to a closed Images field it will automatically open. You don't need to worry about the "Maximum files allowed" setting because the Repeater Images module overrides this for the upload field.
      New Repeater items will be created from the images uploaded to the upload field when the page is saved. The user can add descriptions and tags to the images while they are still in the upload field and these will be retained in the Repeater items. Images are automatically deleted from the upload field when the page is saved.
      Tips
      The "Use accordion mode?" option in the Repeater field settings is useful for keeping the inputfield compact, with only one image item open for editing at a time. The "Repeater item labels" setting determines what is shown in the thumbnail overlay on hover. Example for an image field named "image": {image.basename} ({image.width}x{image.height})  
      https://github.com/Toutouwai/RepeaterImages
      https://modules.processwire.com/modules/repeater-images/
    • By EyeDentify
      Hello There Guys.

      I am in the process of getting into making my first modules for PW and i had a question for you PHP and PW gurus in here.

      I was wondering how i could use an external library, lets say TwitterOAuth in my PW module.
      Link to library
      https://twitteroauth.com/

      Would the code below be correct or how would i go about this:
      <?PHP namespace ProcessWire; /* load the TwitterOAuth library from my Module folder */ require "twitteroauth/autoload.php"; use Abraham\TwitterOAuth\TwitterOAuth; class EyeTwitter extends WireData,TwitterOAuth implements Module { /* vars */ protected $twConnection; /* extend parent TwitterOAuth contructor $connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET, $access_token, $access_token_secret); */ public function myTwitterConnection ($consumer_key, $consumer_secret, $access_token, $access_token_secret) { /* save the connection for use later */ $this->twConnection = TwitterOAuth::__construct($consumer_key, $consumer_secret, $access_token, $access_token_secret); } } ?> Am i on the right trail here or i am barking up the wrong tree?
      I don´t need a complete solution, i just wonder if i am including the external library the right way.
      If not, then give me a few hint´s and i will figure it out.

      Thanks a bunch.

      /EyeDentify
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By kongondo
      FieldtypeRuntimeMarkup and InputfieldRuntimeMarkup
       
      Modules Directory: http://modules.processwire.com/modules/fieldtype-runtime-markup/
      GitHub: https://github.com/kongondo/FieldtypeRuntimeMarkup
      As of 11 May 2019 ProcessWire versions earlier than 3.x are not supported
      This module allows for custom markup to be dynamically (PHP) generated and output within a page's edit screen (in Admin).
       
      The value for the fieldtype is generated at runtime. No data is saved in the database. The accompanying InputfieldRuntimeMarkup is only used to render/display the markup in the page edit screen.
       
      The field's value is accessible from the ProcessWire API in the frontend like any other field, i.e. it has access to $page and $pages.
       
      The module was commissioned/sponsored by @Valan. Although there's certainly other ways to achieve what this module does, it offers a dynamic and flexible alternative to generating your own markup in a page's edit screen whilst also allowing access to that markup in the frontend. Thanks Valan!
       
      Warning/Consideration
      Although access to ProcessWire's Fields' admin pages is only available to Superusers, this Fieldtype will evaluate and run the custom PHP Code entered and saved in the field's settings (Details tab). Utmost care should therefore be taken in making sure your code does not perform any CRUD operations!! (unless of course that's intentional) The value for this fieldtype is generated at runtime and thus no data is stored in the database. This means that you cannot directly query a RuntimeMarkup field from $pages->find(). Usage and API
       
      Backend
      Enter your custom PHP snippet in the Details tab of your field (it is RECOMMENDED though that you use wireRenderFile() instead. See example below). Your code can be as simple or as complicated as you want as long as in the end you return a value that is not an array or an object or anything other than a string/integer.
       
      FieldtypeRuntimeMarkup has access to $page (the current page being edited/viewed) and $pages. 
       
      A very simple example.
      return 'Hello'; Simple example.
      return $page->title; Simple example with markup.
      return '<h2>' . $page->title . '</h2>'; Another simple example with markup.
      $out = '<h1>hello '; $out .= $page->title; $out .= '</h1>'; return $out; A more advanced example.
      $p = $pages->get('/about-us/')->child('sort=random'); return '<p>' . $p->title . '</p>'; An even more complex example.
      $str =''; if($page->name == 'about-us') { $p = $page->children->last(); $str = "<h2><a href='{$p->url}'>{$p->title}</a></h2>"; } else { $str = "<h2><a href='{$page->url}'>{$page->title}</a></h2>"; } return $str; Rather than type your code directly in the Details tab of the field, it is highly recommended that you placed all your code in an external file and call that file using the core wireRenderFile() method. Taking this approach means you will be able to edit your code in your favourite text editor. It also means you will be able to type more text without having to scroll. Editing the file is also easier than editing the field. To use this approach, simply do:
      return wireRenderFile('name-of-file');// file will be in /site/templates/ If using ProcessWire 3.x, you will need to use namespace as follows:
      return ProcessWire\wireRenderFile('name-of-file'); How to access the value of RuntimeMarkup in the frontend (our field is called 'runtime_markup')
       
      Access the field on the current page (just like any other field)
      echo $page->runtime_markup; Access the field on another page
      echo $pages->get('/about-us/')->runtime_markup; Screenshots
       
      Backend
       

       

       
      Frontend
       

×
×
  • Create New...