MultiDomain | WordPress plugin to allow multiple | Content Management System library
kandi X-RAY | MultiDomain Summary
kandi X-RAY | MultiDomain Summary
A WordPress plugin to allow multiple mirrored domains with different configurations under WordPress
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Get the current domain
- Add a domain if it s a domain .
- Shortcode function .
- Return the domain name .
- Get the current domain .
- Get siteurl .
- Return the home .
- Get blogdescription .
- Get the current stylesheet .
- Get the domain template .
MultiDomain Key Features
MultiDomain Examples and Code Snippets
Community Discussions
Trending Discussions on MultiDomain
QUESTION
In WooCommerce, on https://shop.example.com/my-account/lost-password/
when I submit a valid user e-mail, I get redirected to the wp-login form.
Specifically with 302 to https://shop.example.com/wp-admin/
, which then redirects me 302 to https://shop.example.com/wp-login.php?redirect_to=https%3A%2F%2Fshop.example.com%2Fwp-admin%2F&reauth=1
(I watch it in devtools network tab).
Entering a wrong e-mail works and gives error message.
I've tested that the nonce gets validated in class-wc-form-handler.php
.
Any ideas of reasons for this?
My WooCommerce is running on a subdomain, using Multidomain plugin.
Thanks!
...ANSWER
Answered 2021-Mar-05 at 12:20WooCommerce redirects using wp_safe_redirect
, which checks for allowed_redirect_hosts
. These can be added as in this blogpost:
QUESTION
I have problem configuring my old site which I upgraded from TYPO3 9.5 to 10.4. In TYPO3 9.5 I had a multidomain setup using one root page (a page with option is_siteroot set to true) and mapping multiple domains to this root page, so that e.g. the domains example.org, example.com and example.net all mapped to the same root page and thus showed the same content in frontend but had different urls. I was able to do that by configuring the root page as a site with domain example.org in the new site-module and then in the list module adding multiple domain records (example.org, example.com and example.net) to this root page.
Now the problem is, that after upgrading to TYPO3 10.4 the possibility to add domain records in the list module is no longer available and thus I'm not able to map multiple domains to the same root page. I can access the domain example.org that is configured in the site-module but now I wonder how I can configure the site so that also the domains example.com and example.net are mapped to the same root page.
The only possibility I currently see is to clone the whole page tree and then map the other domains to separate root pages. But the problem here is that all the content then has to be maintained in all three page trees and that is not a practicable solution for me because the content shown should be always the same for alle three domains.
Is it possible to configure this somehow, so that the domain mapping works again as described above?
Thanks in advance.
...ANSWER
Answered 2020-Oct-14 at 09:16One option would be adjusting your .htaccess
file to set a suitable environment variable in case the requested HTTP host matches your expected list of hosts:
QUESTION
There is a multidomain setup (domains next to each other on the same level), each domain has their own search page and configuration. I've tried...
...ANSWER
Answered 2019-Dec-04 at 07:49According to the comment in the code (typo3/sysext/indexed_search/Classes/Controller/SearchController.php, Line 232):
Setting the list of root PIDs for the search. Notice, these page IDs MUST have a TypoScript template with root flag on them!
Basically this list is used to select on the "rl0" field and page ids are registered as "rl0" only if a TypoScript template record with root flag is there.
This happens AFTER the use of $this->searchRootPageIdList above because the above will then fetch the menu for the CURRENT site - regardless of this kind of searching here. Thus a general search will lookup in the WHOLE database while a specific section search will take the current sections.
In a multi domain setup we have set rootPidList
to the overall root page (in this case id=457).
defaultOptions.sections
is set like this:
defaultOptions.sections=rl{$customer_theme.search.level}_{$customer_theme.root}
{$customer_theme.search.level}
is set to 1 or 2 depending on the availability of more than one language per country.
{$customer_theme.root}
is the root page (marked by the root page flag).
e.g. for Indonesia (english) we use level = 2 and root = 12947.
QUESTION
I have just started working on typo3-10 and I'm looking to make 3 websites with different domain urls.
In typo3-9 i usually define the domains using the "domain record" in the list module, but in typo3 10 I can't find it. It seems that the domain record is no longer available in typo3-10
My issue is that each site are under the same domain with a predefined identifier, i would like to have a different domain for each website.
Can somebody explain how the multidomain works in typo3-10 ? thanks in advance
...ANSWER
Answered 2019-Oct-15 at 09:54Since TYPO3 9, the domain handling has changed quite a lot. The new way to create multi-language and/or multi-domain setups is using site configurations. There's a new backend module called "Sites" where you can configure your domains and languages.
If you want to manage three different websites with three different domains, create three different site configurations in the "Sites" module.
You can find detailed informations in the official TYPO3 docs.
QUESTION
Im using a multidomain Typo3 installation with an absolute absRefPrefix path in my Typoscript. No I want to include the hreflang for Google. Its working so far, but I need to change the domain url for special languages.
This is what works for translating the links, but without changing the main url:
...ANSWER
Answered 2019-May-24 at 13:57For anybody who has the same Problem. For me I found the following solution:
I create the hreflang HMENU
QUESTION
TYPO3 9.5.5 I have a multidomain website using a combination of multiple page trees and several languages per tree. I have one page tree delivering content in German. This one is available on domain.de, domain.at and domain.ch. Then more trees for domain.com, domain.nl and so on (as the content structure differs very much in different languages).
Now I want to set baseVariants for local development and stage servers. I have a site config like this:
...ANSWER
Answered 2019-Apr-01 at 14:00This feature is not possible via the GUI but can be added in the yaml file directly.
QUESTION
We run a TYPO3 multidomain system and added https support to our TYPO3 domain [typo3domain]
. All other domains still run without https support (http only).
https works perfect for [typo3domain].
Redirect of all non https request to TYPO3 backend (lockSSL) works perfect as well. [typo3domain]/typo3
redirects automatically to https://[typo3domain]/typo3
Now our problem:
If a editor [domain1] edits some content on https://[typo3domain]/typo3
and goes to page -> view page
then https://[domain1]
is called, but this does not work (invalid certificate), because [domain1] is a non ssl domain.
How can i fix this?
...ANSWER
Answered 2019-Feb-20 at 15:22You can set the preview domain in the root page TSconfig of the non-https sites, including the protocol:
QUESTION
I have multiple subdomains and they all use the same database with the same user table.
When I login to a.domain.com I want also to be logged in to b.domain.com, etc.
I've found multidomain-sso (https://github.com/0k/multidomain-sso) but our problem is that we can have up to 100 subdomains, and I'm afraid that the approach of mutlidomain-sso will slow the login process, because it visits every subdomain through AJAX.
How can I login to one subdomain and be logged in to the other 100 subdomains also?
...ANSWER
Answered 2019-Feb-08 at 16:56login is based on cookie and session data . you need to set php session id(PHPSESSID) to set in a cookie with main domain. you can login in main domain or set your cookie to access your domain and subdomains.
QUESTION
Im currently building an application that will reside at app.mydomain.com which is running on Heroku. All users will have their own entry points, like app.mydomain.com/client1, app.mydomain.com/client2, etc. I want clients to be able to setup their own domain (www.clientdomain.com) and cname it to their entry point. I understand this is pretty straight forward up until now.
All my DNS is handled by Cloudflare and I believe I can configure Cloudlfare into Full (Strict) mode, all I need to do is install their Origin Cert onto my Heroku dyno. This will ensure that all direct connects to my domain will be secure (going to app.mydomain.com/client1).
Question is, how does a client go about getting an SSL'ed connection for their domain; do I need to get a multidomain cert and start adding domains to it as I get clients, or am i supposed to install their cert onto Heroku (I believe I can only install 1 so thats a no go) or is it supposed to live on Cloudflare somewhere, or are there additional options I'm not seeing (I hope there are!).
Im not wondering what to do for my own domains, but rather, how do clients setup an SSL connection with their domains that resolve onto my servers.
This is rather perplexing!
The flow would be (I think): User Browser -> Clients DNS -> (cname to) My Cloudflare -> Heroku
...ANSWER
Answered 2018-Dec-20 at 20:37I'm currently building an application that will reside at app.mydomain.com which is running on Heroku. All users will have their own entry points, like app.mydomain.com/client1, app.mydomain.com/client2, etc. Question is, how does a client go about getting an SSL'ed connection for their domain; do I need to get a multidomain cert and start adding domains to it as I get clients?
If you are going to use the same Heroku app for all of your clients (I think this is a bad idea by the way, but you might be required to) - then yes - you should get a multi-domain certificate and keep adding domains to it as your list of clients expand.
Original answer - which explains SSL + Load Balancing on Heroku.Im currently building an application that will reside at app.mydomain.com which is running on Heroku. I was clients to be able to setup their own domain www.clientdomain.com and cname it to mine.
You will need a wildcard certificate to cover your subdomain (for the app.mydomain.com). You'll have use that cert in heroku.
...all I need to do is install their Origin Cert onto my Heroku dyno.
You are correct - except it's not on your Heroku dyno, it's on your Heroku app endpoint. There's a good read here: https://serverfault.com/questions/68753/does-each-server-behind-a-load-balancer-need-their-own-ssl-certificate
If you do your load balancing on the TCP or IP layer (OSI layer 4/3, a.k.a L4, L3), then yes, all HTTP servers will need to have the SSL certificate installed.
If you load balance on the HTTPS layer (L7), then you'd commonly install the certificate on the load balancer alone, and use plain un-encrypted HTTP over the local network between the load balancer and the webservers (for best performance on the web servers).
So you should install your SSL certificate to your Heroku endpoint and let Heroku handle the rest.
Question is, how does a client go about getting an SSL'ed connection; do I need to get a multidomain cert and start adding domains to it as I get clients, am i supposed to install their cert onto Heroku (I believe I can only install 1 so thats a no go) or is it supposed to live on Cloudflare somewhere?
If you're referring to adding servers to your service from heroku, all you need to do is increase the number of web-dynos. Heroku will handle the load balancing in between these dynos. Your SSL certificate should be resolved in the load balancer so your dynos will be serving requests for the same endpoint. You shouldn't need another SSL certificate for the endpoint you've defined - as long as you're serving traffic from multiple dynos attached to it.
QUESTION
We have a simple route defined like the following one:
Route ...ANSWER
Answered 2018-Aug-02 at 17:57There is a section in Laravel documentaion under title Forcing A Route To Be Served Over HTTPS. It does not mention generated URL for the route, but I can see in Illuminate\Routing\UrlGenerator
code this settings is respected in getRouteScheme
method. So adding a new value http
/https
to the action array should do the trick:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install MultiDomain
PHP requires the Visual C runtime (CRT). The Microsoft Visual C++ Redistributable for Visual Studio 2019 is suitable for all these PHP versions, see visualstudio.microsoft.com. You MUST download the x86 CRT for PHP x86 builds and the x64 CRT for PHP x64 builds. The CRT installer supports the /quiet and /norestart command-line switches, so you can also script it.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page