Skip to content
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

Pull instead of push? #4

Open
mmunz opened this issue Feb 2, 2023 · 2 comments
Open

Pull instead of push? #4

mmunz opened this issue Feb 2, 2023 · 2 comments

Comments

@mmunz
Copy link

mmunz commented Feb 2, 2023

The plugin is not usable on local systems or when the site is password protected.

eRecht24 Server answers | The eRecht24 server is not able to push new data into your TYPO3 page.

The docs state:

Sollte der Zugriff auf Ihre Website durch einen Passwortschutz (z. B. über die .htaccess-Datei) oder eine Passworteingabe des CMS geschützt sein, kann unsere Schnittstelle nicht mit Ihrer Website kommunizieren.

Wouldn't it be better to use pull instead of push, which would work in most scenarios?

@aschmutt
Copy link

aschmutt commented Feb 2, 2023

I think push is fine for updating from the erecht24 interface.
But adding a pull option as a scheduler task in TYPO3 would be great - the use case "behind htaccess" is very common.
If you need coding help on the scheduler tasks, let us know, we are both experienced TYPO3 developers.

@nmuens
Copy link

nmuens commented Feb 8, 2023

Hello Andrea,
Hello Manuel,

thank you for your feedback.
We are going to add a pull feature in an upcoming release. We do already offer a pull as part of all our other plugins (WordPress, Contao, Drupal, ...) and the API is capable to do so.

Currently we don't plan to implement a feature to bypass htaccess. We do have strong security concerns to do so as we would have to store passwords for clients unencrypted. Sorry, guys.

Kind regards
Nino

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants