-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Working RealUrl Configuration #44
Comments
Did you already try the autoconfig included in EXT:blog? See the configuration example in TYPO3 Backend > System > Blog: RealURL SetupThe blog extension provides a configuration for EXT:realurl. To get nice looking URLs add the following realurl configuration to your project setup:
Which would be something like the example below with 1,2 and 3 being the page uids.
The above example will override the complete RealURL config, don't copy and paste. It's just to get the idea where to put the config. |
Hi Andreas,
Any idea what can be wrong. Maybe wrong place of the configurations? |
Hey Jürgen, your configuration seems to be fine. I just copied it to a project with EXT:blog installed and
I get proper speaking URLs for blog, tags, authors and categories. Maybe you could try backing up your RealURL tables and truncate them (on a test environment)? Andreas |
Hi Andreas, THe only thing which I did not do is "force flushed TYPO3 caches". Can I set this in some TS Script, because i do have limited shell access and do not know if this will work. Jürgen |
Hi Jürgen, when doing a Regarding the category: I'm sure you checked your IDs – unfortunately I've no other idea regarding your setup. RealURL stores the alias in Andreas |
Hi Andreas, |
Hi Again, do not ask why, but now it is working :-) |
Hi,
Using Typo3 8.7.24
Blog 8.7.4 and
RealURL 2.5.0
I found some configuration examples for RealURL and the Blog extension, but none of them worked.
Does somebody have a working config to get good looking URLS for the combination listetd above?
Would be great.
Best regards,
Jürgen
The text was updated successfully, but these errors were encountered: