Rename sites directory to be the new config repository
This commit is contained in:
parent
006992b900
commit
433e7eec80
31 changed files with 196 additions and 216 deletions
|
@ -7,18 +7,18 @@ user-friendly page aliases not only to the base URL, e.g. "about-us" (for
|
|||
"node/123"), but also to any of the common extensions of the base URL, e.g.
|
||||
"about-us/edit", "about-us/track", "about-us/revisions*" etc.
|
||||
|
||||
The extended aliases may also be used when specifying visibility control for
|
||||
The extended aliases may also be used when specifying visibility control for
|
||||
blocks (e.g. "about-us*"), or in fact anywhere where you are prompted to
|
||||
specify pages to include or exclude.
|
||||
NOTE: It is for this feature that you need to follow the INSTALLATION
|
||||
instructions below. If don't care about this feature just enable the module at
|
||||
NOTE: It is for this feature that you need to follow the INSTALLATION
|
||||
instructions below. If don't care about this feature just enable the module at
|
||||
Administer >> Site building >> Modules and you're away.
|
||||
|
||||
Requiring no configuration, the module then makes sure that these user-friendly
|
||||
(and SEO-friendly) aliases are shown everywhere, replacing their system-
|
||||
generated equivalents, whether it's in the browser address bar or on
|
||||
the page itself. Examples are the Edit, Track, Revisions etc. tabs, the page
|
||||
statistics pages as well as any other links on your pages. No more ugly URLs
|
||||
statistics pages as well as any other links on your pages. No more ugly URLs
|
||||
like node/123/revisons/456/view or user/7/track.
|
||||
|
||||
All of this makes everyone's user experience just that little more convenient
|
||||
|
@ -33,7 +33,7 @@ INSTALLATION
|
|||
|
||||
With your runkit in place proceed with either step a) or b) (preferred).
|
||||
|
||||
a) In file path_alias_xt, find the line //dl('runkit.so'). Remove the
|
||||
a) In file path_alias_xt, find the line //dl('runkit.so'). Remove the
|
||||
leading double slashes.
|
||||
Or
|
||||
b) Edit your php.ini. You can use drupal page /admin/reports/status/php to
|
||||
|
@ -42,7 +42,7 @@ INSTALLATION
|
|||
Add this line to the other extension lines in your php.ini:
|
||||
|
||||
extension = runkit.so
|
||||
|
||||
|
||||
Note: for Windows the correct line is "extension = php_runkit.dll".
|
||||
By the way, while you're down there, check that your php.ini has:
|
||||
|
||||
|
@ -53,7 +53,7 @@ INSTALLATION
|
|||
least display a clue as to what's going on.
|
||||
|
||||
1. As with any other module, uncompress the tar-ball, path_alias_xt.tar.gz, into
|
||||
the "sites/all/modules" subdirectory.
|
||||
the "modules" subdirectory.
|
||||
2. Just in case, if you are installing to a live site, put the site off-line at
|
||||
Site configuration >> Site maintenance. You will only need about 60 seconds.
|
||||
3. Visit Site building >> Modules to enable the path_alias_xt module. Press
|
||||
|
@ -64,7 +64,7 @@ INSTALLATION
|
|||
either step 4a or 4b.
|
||||
|
||||
4a.If you have placed the runkit extension in the /extension directory and have
|
||||
edited your php.ini as per step 0b, you now restart your Drupal stack (or
|
||||
edited your php.ini as per step 0b, you now restart your Drupal stack (or
|
||||
just Apache). If you did step 0a, no restart should be necessary.
|
||||
In either case, verify the runkit has been loaded at /admin/reports/status or
|
||||
at /admin/reports/status/php.
|
||||
|
@ -169,5 +169,5 @@ should match this by default. You can verify the active "extension_dir" on the
|
|||
|
||||
Windows
|
||||
-------
|
||||
To compile a PECL extension on Windows see for instance:
|
||||
To compile a PECL extension on Windows see for instance:
|
||||
http://blog.renangoncalves.com/2010/01/15/how-to-compile-a-pecl-extension-on-windows
|
||||
|
|
Reference in a new issue