allow XCLASSing for Bednarik\Cooluri\Core\Translate

[bednee]

This is core class, I don't think it's a good idea to xclass it. Why do you need it?

[h4de5]

would need this too. whenever we need to extend the functionality and options of cooluri that cannot be done through the config file.

[bednee]

What kind of functionality you need? Could others use this functionality? If so, how about making it part of the core, just raise a pull request and I will review the code.

Jan

⁣Odesláno z TypeApp ​

2. 3. 2017 16:43, 16:43, Andi notifications@github.com napsal/a:

      would need this too. whenever we need to extend the functionality and options of cooluri that cannot be done through the config file.

      -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/bednee/cooluri/pull/51#issuecomment-283689144

[h4de5]

I going through some diffs right now :)

• at one place we added another link_cache-like table that holds additional short urls and allows redirections to external sites or files. therefor it would be great to have an option to add this to lookUpInCache somehow.
• we change the way of how redirections (doktype = 4) are handled. so they only show the redirected content - but leave the url as it is. which was useful for shortcuts to the first subpage, to keep the shorter url.
• we had a problem with cached urls that included cHash'es. If additional get parameters where sent along to those pages, the cHash validation failed and showed an error on the website. I am not sure if this was a problem within cooluri or just with our setup.
• we added a javascript question prior the deletion of the link_cache table in the backend.
• we had to remove the usage of sessions. an option would be great there, but I think this is already on the list.

I am not sure, how useful this changes would be to the public. ( thus i agree a prompt in the backend would help everyone ;) ) We are working with cooluri for several years now and those changes where made due to customers requests. We patched cooluri on our side to enable those changes, but having more options in extending it using a proper "typo3" way would be appreciated.