You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to go back to talking about the error pages.
With a simple script we can generate the SPID/CIE specific error pages from the generic error page (or also from the discovery page).
With single error pages we can redirect the errors to the right error page.
Vantages:
we an remove jinja from requisites
We can load the errors messages and other details from a json file
Is simple presonalize the template and the messages
example - in the new proposed discovery pages I have assigned an id 'main-errors' in the template:
frombs4importBeautifulSoupsoup=BeautifulSoup(open("static/error_page.html", "r").read())
errors= {'1.html': 'message_1', '2.html': 'message_2', '3.html': '<p>message 3</p>'} # or better a json fileforkeyinerrors.keys():
soup.find(id='main-error').string=errors[key]
open(key, "w").write(soup.prettify())
With six code line we can create all errors pages and is simple add this function on startup script
What don't you think? is it a solution or a complication?
The text was updated successfully, but these errors were encountered:
I'd like to get you in the current developements with the following scopes:
moving texts to .po files (gettext) and having i18n with at least italian and english
creating a setup script that replaces the constants in the static discovery page, according to what defined in the proxy (and its configured backends ...)
then I have concerns about bs4, probably we have new libraries that does that better, but this is not a priority.
I'll invite you in the next dev meeting
Hi @peppelinux and each others partecipants,
I would like to go back to talking about the error pages.
With a simple script we can generate the SPID/CIE specific error pages from the generic error page (or also from the discovery page).
With single error pages we can redirect the errors to the right error page.
Vantages:
example - in the new proposed discovery pages I have assigned an id 'main-errors' in the template:
With six code line we can create all errors pages and is simple add this function on startup script
What don't you think? is it a solution or a complication?
The text was updated successfully, but these errors were encountered: