1) The string is interpolated into JavaScript string which is
delimited using double quotation marks - using double quotation
marks in it breaks JavaScript parsing. The impact is unknown
but at least some JavaScript code does not get executed later.
2) The anchor was unproperly closed causing void anchor to appear.
This is clearly visible on the rendered page.
Change-Id: I90cdcdd81c6af67f940c1811b1b9c05f9309ba15
Nobody maintains our askbot website, and questions there go
unanswered. In the spirit of simplification, make the site
read-only (so that old answers can still be found) and redirect
users to the openstack-discuss mailing-list and Stack Overflow
(which has a decent openstack community answering questions).
Read-only config values documented at:
https://github.com/ASKBOT/askbot-devel/blob/master/askbot/conf/access_control.py
Change-Id: I33d9d7c87a5a17138fcdc37ee8f8b16cda2248d5
Include the following fixes:
- openstackid.o.o openid provider and related bug fixes
- new multilanguage model
As the upstream askbot introduced a new branching model,
it also includes changes that brake the configuration. So
the addition of new settings.py backed by two reasons:
- keep the commit ref and settings change atomic (originally
the settings.py come from puppet-askbot module for production)
- provide a separate, and visible settings.py for ask.o.o,
as ask-staging.o.o already using settings.py-staging.erb to
handle system breaking changes.
The original and later reverted change id:
I79155c611386724b510a4cd5f2f544f98c74f3b9
Change-Id: I5b64f9183cc11fa0efed4e581b4b7002f0191764
This reverts commit a4115be981.
The upgrade seems to have only partly completed, so reverting this
in an attempt to roll it back for now while we investigate.
Change-Id: I3aa077dd5040d75287f75c7da04aec9d52a68473
Include the following fixes:
- openstackid.o.o openid provider and related bug fixes
- new multilanguage model
As the upstream askbot introduced a new branching model,
it also includes changes that brake the configuration. So
the addition of new settings.py backed by two reasons:
- keep the commit ref and settings change atomic (originally
the settings.py come from puppet-askbot module for production)
- provide a separate, and visible settings.py for ask.o.o,
as ask-staging.o.o already using settings.py-staging.erb to
handle system breaking changes.
Change-Id: I79155c611386724b510a4cd5f2f544f98c74f3b9
Radosław Piliszek