Jump to content
apeisa

Multisite

Recommended Posts

I've just managed to set this up, and whilst it took a while it can be done.

Again - took for ever to realise that the domain needed to be in the config->httpHosts file.

Then you realise your sitemaps are all broken because the title with the domain doesn't have a url, it points to itself. So I played around with multilevel subdomains etc, and it all works kinda well now - http://dayswithoutincident.net/site-map/

the sub domain verison just implements the site-map template at the moment, but i needed to change the  templates and the php include files in order to achieve this.

Share this post


Link to post
Share on other sites

Yes that's the intended for the moment. The Module does the auto-redirect, I can't figure out how to send it to the other subdomain at the moment with out doing string manipulations.

At the moment its kind of like  if $page-> url ="/" && $page->id != 0 and its title is in the host file, then etc... to fix the directs.

If I can solve the other part then I'll look into it, but for now it's actually working really well :)

Cheers

John

  • Like 1

Share this post


Link to post
Share on other sites

Hello everyone,

I'm having the same problem. Funny thing is, it worked until I left for a week. Came back, no more luck ...

The subdomain homepage works //sub.domain.de/

Every child page //sub.domain.de/page/ gets redirected to //sub.domain.de/

Then I get 

Notice: Undefined index: it in /site/modules/Multisite/Multisite.module on line 68

Accessing //domain.de/sub.domain.de/page works fine

I tried debugging it using error_log at a lot of places but can't figure it out. Apeisas original module does the same but without the notice. Something tells me it could be a server configuration issue since all I did was update Apache. Everything works fine though so I can't see a reason why this won't work.

Has anyone found a solution? I'm halfway in my project and need multisite for this to work!

Thanks,

thomas

Share this post


Link to post
Share on other sites

This isn't working for me.

I have added the domain to the module and the page on the site root with exactly the same domain. Testing always leads to the main homepage.

Accessing firstsite.com/secondsite.com is leading to the root as it's supposed to. With the module uninstalled, firstsite.com and firstsite.com/secondsite.com turn out different pages as expected. But with the module installed, they all deliver the homepage.

I'm running PW 2.6.8

Share this post


Link to post
Share on other sites

Well I got it working, thanks to VeenarM's post. I needed to add the second domain to config->httpHosts.

How can I set this up via API?

I mean my site lets users register and gives them a private page. I want to automatically set thing up so they can just point their domain to my server and get a webstie.

Share this post


Link to post
Share on other sites

I find this to be an incredibly useful module!

I wish it worked as intended :(

If you are actually having a problem, could you please be more specific and detail what your issues are?  Thanks.

  • Like 3

Share this post


Link to post
Share on other sites

If you are actually having a problem, could you please be more specific and detail what your issues are?  Thanks.

I've got a large project coming up and went with Option #1 [https://processwire.com/api/modules/multi-site-support/]

Mostly because I need the organization (I AM an organized fellow).

When I tried Option #2, I just encountered a bit of complexity, that's all really. Option #1 was fairly quick and simple to implement.

I wish it worked as intended  :(

I was a little confused for a while. Didn't know if I had to edit my /etc/hosts file or my vhosts to "point" to the main domain.

Then after I got it all worked out and it went smoothly, I was not able to access a URL without the trailing slash:

mainsite.dev/ -> worked fine :) 

mainsite.dev/testpage1/ -> worked fine :)

test.mainsite.dev/ -> worked fine :) 

test.mainsite.dev/testpage2/ -> worked fine :)
test.mainsite.dev/testpage2 -> threw a 404 error, page not found, without the trailing slash
 
I did all my testing on localhost, Debian Jessie 8.2. I doubt it was a server config. My Digital Ocean droplet is nearly identical to my home setup, so I am certain I would have had issues there as well. I just did not deploy to verify 100%.
 
So, I just went back to Option #1 after reading all these 8 pages and testing out every option and code snippet offered. But no worries though :) 

Share this post


Link to post
Share on other sites

Hello all.
In the past I've made a lot with TYPO3, but now I've done my first project with PW, and it works well. Now I have a new project with a multidomain site which I want to
realize with PW. So I installed the multisite module from https://github.com/apeisa/Multisite/blob/master/Multisite.module.

And now I have a problem with this.

There are 5 Domains.

- MainDomain.de (with webspace/php/mysql on Server A)
- MyDomain2.de (only Domain hosted on Server B)
- MyDomain3.de (only Domain hosted on Server B)
- MyDomain4.de (only Domain hosted on Server B)
- MyDomain5.de (only Domain hosted on Server B)

MainDomain is the standard PW Site and full functionally on my DevServer. I've created the MyDomains under the homepage and made them hidden and made the entrys in the module settings. There is also an entry for each Domain in config.php.

On Server B I've made redirects for the domains to http://MainDomain.de/MyDomain2.de, http://MainDomain.de/MyDomain3.de

and so on and I hope I've done it right.

When I'm logged in into PW and open MyDomain2.de the browser shows MainDoman.de/MyDomain2.de and I can see the content of MyDomain2.de

When I'm not logged in into PW and open MyDomain2.de I get a redirection error and nothing shows up. Maybe I'm a little bit stupid but I can't locate my error for hours.

Maybe someone is able to help me.

Share this post


Link to post
Share on other sites

Hi tom moe and welcome to the world of processwire :)

You have to set your A records of all domains to the server IP of the server that is running the multisite installation of processwire (server a in your case)

A redirect won't work! Good luck :)

Share this post


Link to post
Share on other sites

me once again ;)

Notice: Undefined index: it in /var/www/html/site/modules/Multisite.module on line 68

https://github.com/somatonic/Multisite/blob/master/Multisite.module#L68

i got this error today when i switched debug mode "on". PW 2.6.2

what is the "it" get parameter or what does it stand for?

changing this

$new_it = $_GET['it']; // we store it to later append it back

to that

$new_it = $this->it; // we store it to later append it back

solved the problem. the undefined index warning only appears on "root" pages when no further urlsegments are defined.

$this->it is set on line 45:

$this->it = (isset($_GET['it'])) ? ltrim($_GET['it'], '/') : '';

@soma:

any news on a new version? i think you mentioned it somewhere?! :)

Share this post


Link to post
Share on other sites

Sorry for not replying. I was too busy, not only with updating this module. :)

There's now a new dev version that fixes issues and improves some things. 

https://github.com/somatonic/Multisite/tree/dev

For example the biggest change is that the configuration is now set in the config.php via an array in $config->MultisiteDomains

$config->MultisiteDomains = array(
    "dev.domain.com" => array( // domain name can be used to map to root page
            "root" => "www.domain.com", // page name for the root page
            "http404" => 27
        ),
    "dev.domain2.com" => array(
            "root" => "www.domain2.com",
            "http404" => 5332
        ),
);

This allows for different domain configurations on a dev and live stage, and since it's not in DB (via the module config) it can be easily transfered with a dump without worrying to overwrite or change the settings.

Also there's no need to change the domain "root" pages name, as it's not directly coupled to the requesting domain. So you only change the array keys (=domain).

Since the whole concept is all a pretty hack, I found that it comes with some complications that can't be solved in a 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 Muiltisite. So you'll end with wrong URL's when for example 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.

Further, the structure of a multisite install needs to be

- Web (PW root page, I call it always "Web" since it isn't the homepage anymore)
   - www.domain.com (primary site home)
     - 404 Page
   - www.domain2.com (a second site home)
     - 404 Page
   ...

I think I heard people were using a different structure in the current old version like:

- Homepage (main site home)
   - About
   - Projects
   - 404 Page
   - www.domain2.com (second site home)
     - 404 Page
   - www.domain3.com (a third site home)
     - 404 Page
   ...

But this wasn't ever recommended and it can lead to complications.

----

Again since this module is pretty much a hack, I'm not officially supporting and releasing this module. Use at your own risk. We use it in various projects now and while it works fine with all it's little drawbacks, the new version is little more solid.

I would rather like to see if there's a way for a more integrated and supported way in the core. But not even sure how this could work out. Ryan may has some ideas or maybe thinks this isn't something PW could support. - Note that there's multisite core support, but it's for different DB's and "site" folders, but that's a different case altogether.

Take care

Soma

  • Like 6

Share this post


Link to post
Share on other sites

Does page->editable() work when you are on a sub website url?   My edit this page code isnt working.

I wasnt sure if it was a bug in my setup or if the code does't allow this?

I am using soma's version.

Share this post


Link to post
Share on other sites

Ha!  Found it.

It appears if you login with www.suburl.com/admin/ it works fine on suburl.com, but if you login to mainurl.com/admin it will not print if you are on suburl.com.

I was logged into the main url and trying to edit the page on the sub url!

Share this post


Link to post
Share on other sites

Thanks for this module, it works even as expected in a 3.x ProcessWire installation.

But it took me a while to understand how this module works and what I have to set up. At the end it's pretty easy but I had to read 9 forum pages and failed initially by installing the wrong module. I summarized all collected information and updated the Readme file (see PR at Github), maybe someone else could benefit from this.

To prevent others from installing the old module as well, could @apeisa or someone else having access rights maybe add a litte note to the first post?

One more thing: I use MarkupSEO and got some trouble overriding the module config data for each site. Unfortunately I found no way to hook into that specific function and decided to submit a PR as well. Now I can use the following config:

$config->MultisiteDomains = array(
  'domain1.com' => array( 
    'root' => 'www.domain1.com' 
  ),
  'domain2.com' => array( 
    'root' => 'www.domain2.com', 
    'http404' => 1932,
    'markupSEO' => array(
      'piwikAnalyticsIDSite' => 12,
      'titleFormat' => '{title}'
    )
  )
);
  • Like 9

Share this post


Link to post
Share on other sites

Hi justb3a, thanks for your effort. A simple like didn't feel sufficient enough. I use soma's new version on several sites and didn't even consider creating a readme. Great work.

edit: and soma too offcourse for creating the new version :)

Edited by arjen
  • Like 5

Share this post


Link to post
Share on other sites

Glad I could help. Here are just two litte things I noticed  ;)

The link in the first post to the current wip version is broken. It contains %C2%A0 at the end which leads to a 404 Github page.

You can get the current dev version here
<a href="https://github.com/somatonic/Multisite/tree/dev%C2%A0" ...

The latest ProcessWire devns version 3.0.15 introduces view panels, unfortunately this module swallows them. This is no big deal, I just wanted to mention it. As soon as I uninstall the Multisite module, the panel appears instantly.

Share this post


Link to post
Share on other sites

Glad I could help. Here are just two litte things I noticed  ;)

The link in the first post to the current wip version is broken. It contains %C2%A0 at the end which leads to a 404 Github page.

You can get the current dev version here
<a href="https://github.com/somatonic/Multisite/tree/dev%C2%A0" ...

The latest ProcessWire devns version 3.0.15 introduces view panels, unfortunately this module swallows them. This is no big deal, I just wanted to mention it. As soon as I uninstall the Multisite module, the panel appears instantly.

Thanks for the hint, it's fixed. I thought I tested the link! :)

Considering this module and future development of PW. Yeah, I was playing around with that yesterday, but couldn't see a solution. Unfortunately I knew this would one day lead to complications. :/

After little experimenting I think we need to rethink $page->url rewrites Multisite does in the admin and consequently in the front-end. I always feared it was maybe dangerous/adventurous and would lead to problems sooner or later. There's so many things to consider it's crazy.

So, after long thinking and testing, I'm heading towards letting the $page->url alone, to not get in the way as much as possible.

Then we just have to make sure 2 things:

1. when an url is viewed containing a "domain" in its path that is recognized, to redirect the correct domain/url. So a view link will just work.

2. to have correct url on the front-end output, we can parse the $page->render() output and replace/fix those urls output from templates and RTE's.

This way such new features like the "View" options work out of the box. Also cross Domain linking in RTE would work also.

 
I got a test version working so far but not sure about what to further consider with this new approach.
  • Like 4

Share this post


Link to post
Share on other sites

The Multisite module (latest Version 0.0.6 from https://github.com/somatonic/Multisite/tree/dev) doesn't work correctly with the new link abstraction (since PW 3.0.6). When activated, the link abstraction feature adds the URL-parts of the Multisite-folders back to the URLs, so you'll end up with URLs like http://example.com/example.com/some-folder/some-page/ instead of http://example.com/some-folder/some-page/

I wrote a workaround, but unfortunately - since I didn't find a way to hook into the link abstraction - it's a core hack. I had to modify the methods sleepLinks() and wakeupLinks() in /wire/core/MarkupQA.php. In sleepLinks() I'm overriding the link modification, when a link points to a page, which doesn't belong to the current Multisite-branch. And in wakeupLinks() I'm stripping the Multisite-folder domain names from the given URLs. Since that doesn't make much sense in the long run, I wondered if anyone has a better solution?

@ryan Ryan, could you perhaps make the link abstraction hookable?

Or am I missing something? Every hint is very well appreciated. Thanks in advance!

Share this post


Link to post
Share on other sites
On 19.7.2016 at 0:40 AM, siilak said:

Nice upgrade for a module. I tested it on latest ProcessWire DEV version and only error I get is Front-End Page Editor error.

Added a video. Maybe there is a simple solution for that :)

https://www.dropbox.com/s/ox5tzdkide3lrlp/error.mp4?dl=0

I can't reproduce this one, it's working fine here. What versions are you using? What is the error?

  • Like 1

Share this post


Link to post
Share on other sites

Yes, I made clean install and its ok now. I think it was my own fault.

Share this post


Link to post
Share on other sites
15 hours ago, nurkka said:

The Multisite module (latest Version 0.0.6 from https://github.com/somatonic/Multisite/tree/dev) doesn't work correctly with the new link abstraction (since PW 3.0.6). When activated, the link abstraction feature adds the URL-parts of the Multisite-folders back to the URLs, so you'll end up with URLs like http://example.com/example.com/some-folder/some-page/ instead of http://example.com/some-folder/some-page/

I wrote a workaround, but unfortunately - since I didn't find a way to hook into the link abstraction - it's a core hack. I had to modify the methods sleepLinks() and wakeupLinks() in /wire/core/MarkupQA.php. In sleepLinks() I'm overriding the link modification, when a link points to a page, which doesn't belong to the current Multisite-branch. And in wakeupLinks() I'm stripping the Multisite-folder domain names from the given URLs. Since that doesn't make much sense in the long run, I wondered if anyone has a better solution?

@ryan Ryan, could you perhaps make the link abstraction hookable?

Or am I missing something? Every hint is very well appreciated. Thanks in advance!

Testing this, I'm not seeing any problems with what you're saying. Link abstraction works here.

Though it's an experimental feature and not sure where this leads to, same as with this module. Highly experimental.

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 teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...