Jump to content
apeisa

Multisite

Recommended Posts

the page is hidden.

is all abit backwards currently, I can no longer get to the multi site page as it redirects me to the homepage but with the wrong domain name.

echo "subdomain: " . $modules->Multisite->subdomain;

this gives me Home which every domain i plugin


I unhide the page and it appearded active in the menu making it look like it was home for both domains, which is very confusing

Share this post


Link to post
Share on other sites

Well it would give you current multisite domain. As it redirects to the domain it looks like it works. If you could give access I'm sure I can figure it out.

Share this post


Link to post
Share on other sites

I think it may cause you would not setup main homepage as root but also as multisite subfolder. Never tried a setup you have but cant say without testing and reating the code.

Share this post


Link to post
Share on other sites

I use soma's module on different sites without problems. Some with root set as one domain, children pages with others and some with different children pages and root not defined as domain. This cannot be the problem.

Share this post


Link to post
Share on other sites

We use the module on a lot of sites too like MadeMyDay's setup. Never had any real trouble.

Share this post


Link to post
Share on other sites

will try and delete the apache settings as I can't see anything else that might be wrong for that incoming domain in PW. If not I'll have to abandon the multisite and spin out to it's own PW install. Thanks for everyones help though and I'll report back

Share this post


Link to post
Share on other sites

I'm I was (solution below) experiencing the same as below on PW 2.5.2, after installing via softaculus(which uses minimal site profile) on a cpanel based hosting:

Currently I'm trying to get this to work, but I'm seriously questioning if I'm using this right. What I initially thought that had to do the following steps:

1) Make sure all the traffic from www.seconddomain.com points to the home directory of the www.maindomain.com. (checked)
2) Install the module and make sure that www.seconddomain.com is added to the textarea. (checked)
3) Create a new page with the template 'home' with the title matching the domain - in this case www.seconddomain.com. Status of the page is published and hidden. (checked)

Then I thought I have to add another page to make this work:

4) Create a page with a template underneath the 'second' homepage called 'Testpage'. Status of the page is published.

I can reach the page using the following URL:
 

http://www.maindomain.com/www.seconddomain.com/testpage/
But I can't reach the page using this URL:

http://www.seconddomain.com/testpage/
Things I've noticed

1. When I try to reach www.seconddomain.com it displays a 404 error. (see below).
 

except,

When I try to reach www.seconddomain.com it displays as if I'm using www.maindomain.com

Also, http://www.seconddomain.com/www.seconddomain.com/ redirects to http://www.seconddomain.com/

SOLVED: needed to add www.seconddomain.com to $config->httpHosts in /site/config.php

  • Like 2

Share this post


Link to post
Share on other sites

Hi I am using Nginx and for me your solution is not working. 

My plan was to redirect subdomains to the specific subpages the plugin was for me the best way to do this.

I added the sites named sub1.domain.com, sub2.domain.com, ... in the textarea and in the $config->httpHosts array. 

When I send the request to the sub1.domain.com I get the home page of domain.com but not to the sub1.domain.com page which is created under the root.

Is it possible that I have to change something in the Nginx Conf? 

Share this post


Link to post
Share on other sites

Hello,

it seems I have the same problem addressed here before.

I've upgraded PW to 2.5.18, previous it was PW 2.4.1

All went well, except for the Mulltisite module... 

It's working, but not as it previously did... the links actually include the second domain

http://www.domain2.com/domain2.com/test-page/

before it was:

http://www.domain2.com/test-page/ [which return a 404 page]

which is the idea off course... also with google in mind, it's not ideal....

did I miss something somewhere?

I'm using Soma's version BTW [also tried with Apeisa's version, same thing FYI].

Greetings...

Share this post


Link to post
Share on other sites

How is your setup?

Looks like there's maybe this issue with newline in the config textarea for domain

If you change

$this->subdomainsArray = explode("\r\n", strtolower($this->subdomains));

To

$this->subdomainsArray = explode("\n", strtolower($this->subdomains));

Does it work?

This is the code that should do a redirect when a real url containing the domain is found.

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

But even then even if the redirect isn't working the page should still show fine. Nothing there in the module that would do a 404.

The 404 seems to be an issue that the domain isn't found. But that wouldn't come from updating PW after all.

  • Like 1

Share this post


Link to post
Share on other sites

Wow, fast!

I've changed the line, but no effect...

oh, it's working... only the subdomain url isn't stripped and I have no idea why... 

Originally the second domain had a different template [which I called multisite_home], but somehow since the upgrade that is ignored [per default it uses 'home']. Which I don't mind actually.

Foreach domain I do have a 'homepage' call...

$homepage = $pages->get(1'); for the root

$homepage = $pages->get(1373'); for the second domain

it used to work just fine...

Thx!

Edit: deleting the domains in the module makes no difference, so I guess the module isn't working at all.... Maybe I should revert back to 2.4.x

Edit2: reverting back to 2.4.1 and everything works as expected again [will try again with an 2.5.xx later]

Edit3: reverted back the line you suggested to edit, the \r is back while textarea is being saved :-)

Edited by videokid

Share this post


Link to post
Share on other sites

I don't use MAMP, but what you have to basicly is this:

1) Install ProcessWire with for example the domain maindomain.localhost which points to /Arjen/Sites/maindomain.com/.

2) Make sure it's working fine and install the Multisite plugin.

3) Create an entry in your virtual host file and point that domain to the domain in step 1. For example point seconddomain.localhost to /Arjen/Sites/maindomain.com/ as well.

4) Now both maindomain.localhost and seconddomain.localhost will load the same website.

5) Follow instructions above.

There is no need for this complexity. If you are already using a vhost that works it might help if you simply add more server aliases to your vhost config ie. :

ServerAlias *.domain.dev
ServerAlias *.domain.dev.*.xip.io
 
for me resulting in:
 
# project-domain.dev.conf
<VirtualHost *:80>
    DocumentRoot "/home/dirr/to/server/project-name"
    ServerName project-domain.dev
    ServerAlias project-domain.dev.*.xip.io
    ServerAlias *.project-domain.dev
    ServerAlias *.project-domain.dev.*.xip.io

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    <Directory /home/dirr/to/server/project-name>
        Options FollowSymLinks
        Allow from All
        AllowOverride All
    </Directory>
</VirtualHost>
 
In my case the project-name is a symlink pointing to the root of the project,
and project-domain is the domain for the project that you added to hosts file

Share this post


Link to post
Share on other sites

Thanks for sharing bitlinguist. You are right, there are several ways to accomplish this. In the case you can control the vhost there is indeed no need for a second vhost file since you can use an alias. The point I tried to explain (in simple steps with basic apache knowledge) is that you need two domains to point to to same server directory.

Share this post


Link to post
Share on other sites

hi guys!

unfortunately i can't get soma's version of the module to work. i have a vagrantbox and configured my hosts file to serve the following domains:

config.hostsupdater.aliases = ["web.dev", "multi1.web.dev", "multi2.web.dev", "web1.dev", "web2.dev", "www.web1.dev", "www.web2.dev"]
  • i can reach a clean 2.6 installation via all domains
  • i installed somas module
  • i created 2 new pages: /home/www.web1.dev and /home/www.web2.dev
  • when i visit www.web1.dev -> still the frontpage of the installation (default intermediate profile); same for www.web2.dev
  • i can visit those pages via www.web1.dev/www.web1.dev/ and same for web2

i tried apeisa's version and it worked - unfortunately i did not make it to get subdomains working (site1.web.dev, site2.web.dev). but anyway i would prefer to use somas module :)

do you think that could be related to vagrant? unfortunately i have no live server where i can try it out at the moment...

help would be very, very appreciated!

ps: module configuration:

www.web1.dev
www.web2.dev

tried everything with and without www

Share this post


Link to post
Share on other sites

I was a bit confused at first because i did not see the update on the 'official' Github repo (apeisa/Multisite). Wouldn't it be worthwhile to add this to there?

Share this post


Link to post
Share on other sites

hey soma,

i did some testing the last hours and found out, that example.com/admin does NOT work while example.com/admin/ (with trailing slash) does.

not really a big problem, but maybe there is a quick and easy fix for that?

thanks again for your support - everything else working like a charm so far!

Share this post


Link to post
Share on other sites

i have the following problem:

www.site1.dev -> works

sub1.site1.dev -> works

but

site1.dev -> works

sub1.site1.dev -> doesn't work

any fix for this?

Share this post


Link to post
Share on other sites

Sorry Bernhard haven't noticed your earlier posts.

I experienced something like that with the backend admin url, but not sure anymore what it was. I have a project where I use it but that is a even a newer version than the current. So I might have it already fixed there.

The other is something I see a problem with current implementation using strpos() on those domains. 

"site1.dev" is found in "sub1.site1.dev" thats why you have a problem. I'm not sure about a fix yet. I haven't got a testinstall I can play with currently, but will look into it soon. Thx.

  • Like 1

Share this post


Link to post
Share on other sites

hi soma, thank you - all the problems are not time critical for now ;)

shouldn't checking the strpos to be < 1 be enough for that?

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

if(strpos($httpHost, $subdomain) !== false AND strpos($httpHost, $subdomain) < 1) {

at least it works for me here on my dev.

but that is a even a newer version than the current

that makes me curious?! ;)

one other thing: I'm wondering why the module does not take the valid multisite-domains from the processwire config? i always have to add new domains in both locations. ok, that's not a big deal, but i'm sure there is some more important thing behind it? any problem i don't see that could appear when "synching" multisite hosts with pw config hosts?

Share this post


Link to post
Share on other sites

"it" is the GET parameter, what acts as access-point to ProcessWire. All requests are rewritten by the .htaccess file to something like this:

yourdomain.com/index.php?it=/subpage/moresubpages/test (see here)

Therefore it's strange that this index is undefined. It's one of few necessities in pw.

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 jploch
      Fieldtype Page Table Grid
      This is a sneak preview of a side project I've been working on for quite some time now. A lot of work and thought has gone into this, so I will most likely release this as a commercial module at some point in the near future. 

      As a designer (and developer) I get the appeal of a WYSIWYG editor. After playing around with some WYSIWYG page builder tools, I always felt something was wrong about them. So I decided to build my own PW version based on PageTable.

      Here is a small demo (using AdminThemeCanvas, but its working with other admin themes as well) :
      There is also a complete website that I built for a friend of mine using this module and some custom blocks.
      Concept
      This fieldtype shares a lot of features with PageTableExtended: it's also an extension of PageTable and renders the block templates in the backend and frontend (native PW templates and fields). You can also add your own css via module settings.
      The difference is, this fieldtype also gives you the ability to rearrange and resize elements in a visual way as well as enable inline editing for text, ckeditor and file fields. Similar (and promising) attempts have been made, but I wanted something based on native CSS grid instead of a CSS framework...so I built my own version. Most CSS frameworks are based on flexbox, which is great for layouting elements horizontally. With CSS grid, you can place elements horizontally and vertically, allowing for layouts that were not previously possible with CSS. Similar to webflow, this fieldtype uses javascript (in the backend) to let you manipulate CSS grid in a visual way to design fully responsive websites (or parts of them). It should still be possible to include a CSS framework if you like (just add the classes to your block markup and include the CSS via module settings).
      The CSS grid layout manipulations are saved in a single field as a JSON array and used to generate a dynamic stylesheet that you simply include in your main template (no inline styles). The styles are saved within the breakpoint you select and cascade down to smaller breakpoints. That means you can specify just the basic breakpoint and adjust other breakpoints if needed. The exception is the mobile breakpoint which will display everything in one column as a default (you can change the layout here too).
      The fieldtype also comes with an optional style panel to manipulate some additional CSS properties directly on the page. You can customize the panel or disable it completely from the module settings (and just use a CSS file that you include via module settings). The style panel is based on inputfields (nothing is saved to the database). This means that you just have to install the module and all fields are available to all blocks automatically (this can be customized). It also has the benefit that your installation is not flooded with fields; this module only installs one field.
      Don't want to give your customer all that power? Design features can be disabled for certain roles. The grid editor role can just edit the content and use the inline editing feature to edit content quickly. You can then also grant access individually to the style panel, resize or drag functionality.
      Features
      Blocks are just pages Blocks are defined by native PW templates and fields Manipulate CSS grid in a visual way to design fully responsive websites (or parts of them) Design features can be disabled for certain roles Inline editing of text, ckeditor and file fields The layout is 100% CSS grid (very small css file size) Simply drag and resize to manipulate grid items directly inside the backend Manipulate grid columns and rows directly on the page (use any number of columns you want) All style manipulations are saved as JSON and used to generate a dynamic stylesheet that you just include in your main template (no inline styles) Nested groups/grids (child pages of nested blocks are created under group parent) Global blocks work with page reference field (changes on one page, changes all blocks on all pages) Manual and auto placement of grid items Define custom icons for your blocks via native template settings (template -> advanced -> icon) Option to load lazysizes in the backend to enable lazy loading of assets with class lazyload Works with all default and ui-kit based admin themes If you have any questions or feedback, let me know.
    • By bernhard
      I built this module because I needed a versatile solution to replace tags and simple if-blocks in some E-Mails and PDF documents.
      If you only need to replace static tags (no if-conditions), then you can use default PW api and need no module:
      $str = "My favourite color is {color}."; $texttools = $sanitizer->getTextTools(); echo $texttools->populatePlaceholders($str, ['color' => 'red']); // output: My favourite color is red. Usage:
      See the two example Files in the folder /replacements

       
      Methods:
      replacementsTable()
      Renders an overview of all available replacements (see the example in the Module's config file:
       
      Create new Replacements:
      Simply copy the sample file and adopt to your needs.
       
      Download:
      https://gitlab.com/baumrock/RockReplacer
    • By bernhard
      DEPRECATED
      I'm using this module in several projects, but it will likely not see any updates in the future. I'm not happy with it and I'm looking for ways to develop better solutions. RockTabulator was my first try, but I'm also not 100% happy with that. The tabulator library is great, but my module implementation is not. I hope to get a good solution soon, but it will be a lot of work...
      ---
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/FieldtypeRockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
      German Translation File: site--modules--fieldtyperockgrid--fieldtyperockgrid-module-php.json
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support (please contact me via PM).
       
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By Paul Greinke
      Hi there. I wrote a custom module for one of my projects. In fact I maybe want to use my module in other projects too. In order to be variable and customizable  I need to implement some custom hooks into my module. So I can afterwards hook into the my functions in order to modify them to match the needs of the new project.
      I tried simply defining functions with the '__' prefix. But that did not work. I'm imagining something like the following:
      <?php class MyClass { public function ___someFunction() { // Do something } } // ready.php $this->addHookBefore('MyClass::someFunction', function($event) { // some customization }); Is there a way to accomplish that? 
    • By adrian
      Hi everyone,
      Here's a new module that I have been meaning to build for a long time.
      http://modules.processwire.com/modules/process-admin-actions/
      https://github.com/adrianbj/ProcessAdminActions
       
      What does it do?
      Do you have a bunch of admin snippets laying around, or do you recreate from them from scratch every time you need them, or do you try to find where you saw them in the forums, or on the ProcessWire Recipes site?
      Admin Actions lets you quickly create actions in the admin that you can use over and over and even make available to your site editors (permissions for each action are assigned to roles separately so you have full control over who has access to which actions).
       
      Included Actions
      It comes bundled with several actions and I will be adding more over time (and hopefully I'll get some PRs from you guys too). You can browse and sort and if you have @tpr's Admin on Steroid's datatables filter feature, you can even filter based on the content of all columns. 

      The headliner action included with the module is: PageTable To RepeaterMatrix which fully converts an existing (and populated) PageTable field to either a Repeater or RepeaterMatrix field. This is a huge timesaver if you have an existing site that makes heavy use of PageTable fields and you would like to give the clients the improved interface of RepeaterMatrix.
      Copy Content To Other Field
      This action copies the content from one field to another field on all pages that use the selected template.
      Copy Field Content To Other Page
      Copies the content from a field on one page to the same field on another page.
      Copy Repeater Items To Other Page
      Add the items from a Repeater field on one page to the same field on another page.
      Copy Table Field Rows To Other Page
      Add the rows from a Table field on one page to the same field on another page.
      Create Users Batcher
      Allows you to batch create users. This module requires the Email New User module and it should be configured to generate a password automatically.
      Delete Unused Fields
      Deletes fields that are not used by any templates.
      Delete Unused Templates
      Deletes templates that are not used by any pages.
      Email Batcher
      Lets you email multiple addresses at once.
      Field Set Or Search And Replace
      Set field values, or search and replace text in field values from a filtered selection of pages and fields.
      FTP Files to Page
      Add files/images from a folder to a selected page.
      Page Active Languages Batcher
      Lets you enable or disable active status of multiple languages on multiple pages at once.
      Page Manipulator
      Uses an InputfieldSelector to query pages and then allows batch actions on the matched pages.
      Page Table To Repeater Matrix
      Fully converts an existing (and populated) PageTable field to either a Repeater or RepeaterMatrix field.
      Template Fields Batcher
      Lets you add or remove multiple fields from multiple templates at once.
      Template Roles Batcher
      Lets you add or remove access permissions, for multiple roles and multiple templates at once.
      User Roles Permissions Batcher
      Lets you add or remove permissions for multiple roles, or roles for multiple users at once.
       
      Creating a New Action
      If you create a new action that you think others would find useful, please add it to the actions subfolder of this module and submit a PR. If you think it is only useful for you, place it in /site/templates/AdminActions/ so that it doesn't get lost on module updates.
      A new action file can be as simple as this:
      class UnpublishAboutPage extends ProcessAdminActions { protected function executeAction() { $p = $this->pages->get('/about/'); $p->addStatus(Page::statusUnpublished); $p->save(); return true; } } Each action:
      class must extend "ProcessAdminActions" and the filename must match the class name and end in ".action.php" like: UnpublishAboutPage.action.php the action method must be: executeAction() As you can see there are only a few lines needed to wrap the actual API call, so it's really worth the small extra effort to make an action.
      Obviously that example action is not very useful. Here is another more useful one that is included with the module. It includes $description, $notes, and $author variables which are used in the module table selector interface. It also makes use of the defineOptions() method which builds the input fields used to gather the required options before running the action.
      class DeleteUnusedFields extends ProcessAdminActions { protected $description = 'Deletes fields that are not used by any templates.'; protected $notes = 'Shows a list of unused fields with checkboxes to select those to delete.'; protected $author = 'Adrian Jones'; protected $authorLinks = array( 'pwforum' => '985-adrian', 'pwdirectory' => 'adrian-jones', 'github' => 'adrianbj', ); protected function defineOptions() { $fieldOptions = array(); foreach($this->fields as $field) { if ($field->flags & Field::flagSystem || $field->flags & Field::flagPermanent) continue; if(count($field->getFieldgroups()) === 0) $fieldOptions[$field->id] = $field->label ? $field->label . ' (' . $field->name . ')' : $field->name; } return array( array( 'name' => 'fields', 'label' => 'Fields', 'description' => 'Select the fields you want to delete', 'notes' => 'Note that all fields listed are not used by any templates and should therefore be safe to delete', 'type' => 'checkboxes', 'options' => $fieldOptions, 'required' => true ) ); } protected function executeAction($options) { $count = 0; foreach($options['fields'] as $field) { $f = $this->fields->get($field); $this->fields->delete($f); $count++; } $this->successMessage = $count . ' field' . _n('', 's', $count) . ' ' . _n('was', 'were', $count) . ' successfully deleted'; return true; } }  
      This defineOptions() method builds input fields that look like this:

      Finally we use $options array in the executeAction() method to get the values entered into those options fields to run the API script to remove the checked fields.
      There is one additional method that I didn't outline called: checkRequirements() - you can see it in action in the PageTableToRepeaterMatrix action. You can use this to prevent the action from running if certain requirements are not met.
      At the end of the executeAction() method you can populate $this->successMessage, or $this->failureMessage which will be returned after the action has finished.
       
      Populating options via URL parameters
      You can also populate the option parameters via URL parameters. You should split multiple values with a “|” character.
      You can either just pre-populate options:
      http://mysite.dev/processwire/setup/admin-actions/options?action=TemplateFieldsBatcher&templates=29|56&fields=219&addOrRemove=add
      or you can execute immediately:
      http://mysite.dev/processwire/setup/admin-actions/execute?action=TemplateFieldsBatcher&templates=29|56&fields=219&addOrRemove=add

      Note the “options” vs “execute” as the last path before the parameters.
       
      Automatic Backup / Restore
      Before any action is executed, a full database backup is automatically made. You have a few options to run a restore if needed:
      Follow the Restore link that is presented after an action completes Use the "Restore" submenu: Setup > Admin Actions > Restore Move the restoredb.php file from the /site/assets/cache/AdminActions/ folder to the root of your site and load in the browser Manually restore using the AdminActionsBackup.sql file in the /site/assets/cache/AdminActions/ folder I think all these features make it very easy to create custom admin data manipulation methods that can be shared with others and executed using a simple interface without needing to build a full Process Module custom interface from scratch. I also hope it will reduce the barriers for new ProcessWire users to create custom admin functionality.
      Please let me know what you think, especially if you have ideas for improving the interface, or the way actions are defined.
       
       
×
×
  • Create New...