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
Askbot introduced the editor_deselector variable for the inplace
editor. Without this setting the site will be broken.
4ed16585ac
Change-Id: I2938651c2d469f1f0a1d11ed294c26117bbbae82
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
The askbot branches were separated by major versions, in the upstream
repository so this patch pins the ask-staging to the 0.7.x.
The 0.7.x. branch works with django version 1.5.x.
Settings.py now contains the new language configuration options,
including the ASKBOT_LANGUAGE_MODE settings and the required
captcha module.
Change-Id: Icd1052da20396601010315447a385fe7353391cd
This custom template is fixing the broken site of ask-staging.o.o
caused by the configuration change introduced in upstream
askbot-devel repository:
8854ef6dd4
Change-Id: Idf629d7a7908c71dca6a056cd31eb2319caa821c
Depends-On: Ic88b584cb60ab7f96c17e17b904c89200e10055d
The duplicated _version_ definition in the template prevented
the proper query of Chinese indexed content from Solr.
After the patch had been applied restart Solr and
reindex Chinese content:
sudo service jetty restart
cd /srv/askbot-sites/slot0/config
sudo python manage.py askbot_rebuild_index -l zh
Change-Id: Iaeabc73febc64c45996425225d3ee38db7f36f72
Add ask.openstack.org to openstack-infra. Setup an all-in-one
askbot site based on existing deployment, including apache,
redis,apache solr,postgresql. See askbot.rst for further
details. Refactored to depend on vamsee's puppet solr module.
Depends-On: Iffe07d3a34087cb15151787bc683208425a27594
Change-Id: I36504eac7b953c3cce3e21a3559ac95b1bc12da7
Radosław Piliszek