fritzmg/contao-multidomain-rebuild-index

This package is abandoned and no longer maintained. No replacement package was suggested.

Mini extension that makes rebuilding the search index possible for multidomain.

1.0.3 2016-11-24 09:56 UTC

Requires

• php: >=5.2
• contao-community-alliance/composer-installer: *
• contao/core: ~3.0

Replaces

• contao-legacy/multidomain_rebuild_index: 1.0.3

LGPL-3.0+

• Fritz Michael Gschwantner

• search
• index
• multidomain
• contao
• rebuild

README

Contao Multidomain Rebuild Index

Rebuilding the search index via the backend of Contao actually creates an AJAX request for every page in the sitemap of every website root of the Contao installation. Thus, in order to be able to rebuild the search index in multidomain installations you need to set custom response headers for any page request that Contao handles, due to CORS. The headers are:

Access-Control-Allow-Headers: X-Requested-With
Access-Control-Allow-Origin: …

The first header is necessary, because Contao uses the MooTools Request class, which always adds the X-Requested-With request header (see mootools.net/core/docs/1.5.2/Request/Request). The second header allows AJAX requests from other domains.

Adding these headers could be done via the .htaccess:

<IfModule mod_headers.c>
  Header set Access-Control-Allow-Headers X-Requested-With
  Header set Access-Control-Allow-Origin http://example.org
</IfModule>

The value for the Access-Control-Allow-Origin header should be changed to the domain (and scheme) with which you access the Contao back end.

However this does not work in every server environment for requests that are handled by PHP via FastCGI for example (see http://serverfault.com/a/383063/143519). In that case you would need to set these headers directly in the vhost configuration of Apache.

This extension helps with cases where that is not possible. By installing this extension the headers are automatically set for any front end page output. The Access-Control-Allow-Origin header is automatically set to the domain with which you accessed the Contao back end. No configuration is needed for this extension.

Note: further problems can arise, if you use HTTPS on some of the domains. AJAX requests to resources via HTTP are not possible when using HTTPS. In that case you need to make sure that you either:

• log into the backend via HTTP
• or force HTTPS for all domains

Note: this extension is not needed, if you use Contao ^3.5.25 or Contao >=4.3.6.