Download the PHP package smichaelsen/autourls without Composer
On this page you can find all versions of the php package smichaelsen/autourls. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download smichaelsen/autourls
More information about smichaelsen/autourls
Files in smichaelsen/autourls
Package autourls
Short Description Zero configuration speaking URLs for TYPO3
License
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package autourls
autourls
Zero configuration speaking URLs for TYPO3 8
After installing autourls your TYPO3 website will have speaking URLs without any configuration.
Installation
composer require smichaelsen/autourls
Afterwards just install it in the Extension Manager as usual.
Cool! Does it replace realurl?
No. autourls offers only limited functionality and is no match to realurl in terms of features and flexibility.
Okay, then what does it do?
It just creates a speaking path for each page based on its rootline. So the rootline "Service > About us" results in the path /service/about-us.
- It respects the
nav_titlefield ofpages. - It respects the
config.absRefPrefixTypoScript setting. - Shortcut pages are handled correctly (their path is the one from their target page, just like in realurl)
Caching and Expiry
- For each query string the resulting speaking path will be cached in the database and will be assigned an expiry date of about one day.
- After expiration the speaking path will be created again, so that renamed record names etc will be respected.
- "Old" speaking paths (which are expired) will remain accessible.
- If
config.no_cache = 1speaking paths will immediately expire, so they will be regenerated on every page load. - If you need to expire a path manually, don't clear the whole database table! Go to
tx_autourls_mapand setencoding_expiresto 0 for the desired record(s).
What about extension parameters?
autourls comes with native (basic) support for the news extension.
Extensions can register themselves by calling \Smichaelsen\Autourls\ExtensionParameterRegistry::register() in their ext_localconf.php.
Take a look at the ExtensionParameterRegistry class header for more explanation.
If you want an extension to be supported by autourls you can contact the extension author and ask if they want to include the registration.
If they refuse, you can also open an issue for autourls. I'm willing to add support for common open source extensions.
And of course if you have some kind of package/template extension, you can also register support there too.
What about multi language handling?
Yes! If you use the L GET parameter to indicate the language (which is very common in TYPO3) it gets automatically rewritten and the page path or extension records are localized accordingly. All with zero configuration!
What about mountpoints, workspaces, ...?
Not supported yet. Those might follow as there is demand for it.
How can I configure ...?
You can't. Until now autourls is literally zero configuration.
But that doesn't fit my requirements!
Okay, just go with realurl then :)
