* This reference was added in the very distant past
* But jquery.history.js itself has never been in the repo
* pyconau-2017 team resolved the dilemma but dropping
jquery.history.js into the repo
* But as near as I can tell, this does nothing except in obsolete
older browsers. The fact that it's been broken ever since it was
"added" is highly suggestive of it never having ever been used or
needed
* So, trim the fat. It's possible that this might break an older
browser that needs the functionality jquery.history.js provides -
except that such a browser would *already* be broken because
jquery.history.js has never actually been around to be used.
* If we ever do need this functionality, we can revert this
change.. and then we'd have to drop in jquery.history.js. In that
circumstance,
https://github.com/pyconau2017/symposion/commit/34bc7c0 may be of interest.
* Adds an env variable to .env to turn on dev mode
* Uses the inbuilt django auth rather than saml when in dev mode
* For laziness, re-uses the admin login form for the non-admin login
make_dev_container now comes up ready to be logged into by any
user. No non-admin users are preconfigured; but you can add one at
http://localhost:28000/admin/auth/user/add/, log out, and then hit
http://localhost:28000/ to log in as the new user.
Editing a miniconf, on save, the code looks in settings for
ADMIN_USERNAMES, and as it does not exist, we stack-trace and 502 to the
user.
Add the attribute to settings.py
So django keeps strict synchronization between its code and migrations
so that it can help generating new migrations. These are the additional
suggested migrations. A lot of these are a null effect, some are things
like transforming an unsigned integer to a signed integer. So not super
urgent on a small scale, but worth doing to keep django happy.
We need to have people who are submitting a miniconf proposal agree to
releasing the material. The easiest way to do this is to just make it a
proposal like the other two types. We don't have audience type for
miniconf, instead of deleting it just have a default - it's easier.
WARNING: This requires a real migration to be performed before use.
Update the recording and materials release to say Linux Australia, not
Pycon Australia. This generates a migration because the model text has
change - but also because in the 0001_initial migration it appears that
this help text is stored as a byte string.
This is a bit weird, but realistically running this migration is not
going to cause us any problems so just add it so we don't end up
fighting django along the way.
DEBUG is something that should never be turned in on prod. As such,
lets be extremely specific on what we expect to process.
As we'll be taking this in from the environment, it's ensured we will
get a string. So we'll always get and only handle this in string
form. If it's anything else, it's an operational error and we bail.
(Note: bool('0') is truthy, so we make sure we leverge our string -> int
-> bool every time, so corectness can be noticed if it is not)
Remove in-app stale resources and their branching of different cons.
Remove dist and move everyting into static/src.
Remove unused stale resouces such as less and hbs, etc.
I cannot find the benifit to this over the base editor.
Tabs work, but that's pretty minimal. And tabs don't work on GitLab or
GitHub, so I don't feel not having that is substantual to functionality.
The bootstrap renderer did not do anything to signify required rows. We
can do this by adding a class for CSS to work on, and add this field in
a more simplified manner.
label-required == append ' *'
I'm not against putting this back, however, it doesn't work quite as one
would expect, so I'm removing it as its functionality is more confusing
that working.
Is this really the best way to address this?
If you unselect AU, then it never comes back. It leaves its value in
the textbox pre-filled if it ever got a value, leaving the field
pre-filled with an Aus state even if the person is New Zealand.
Most of our attendees are from but a few countries, we should make these
equal effort to fill in.
Boot custom CSS, and put some base, standard css in its place.
Shame I did not start with fresh Bootstrap4, but oh well.
Some more templates could be made to make this less messy, which would
be good.
We don't have these mini-confs (yet).
We don't want these files.
We're not going to rename the release in 0010 and drop all the extra
tables in 0011, we're going to toss them on the cutting room floor and
call it good.
They're in git, we can look at this commit and past ones on how to
recreate these for new proposal additions going forward.
This causes template rendering to blow out of proportion on certain
views. I don't care enough about this feature to spend time fixing it.
It has not provided me any value to this point.
One such view is ^/tickets/profile$ however there are others where I saw
this, yet do not remember which ones they were.
This removes images, and giant headers, and makes the text - not white.
The next layer down in CSS is blue, so that's it for now.
This helps understand what's on the page visually, so this, at the
least, make testing easier for now.
This should eradicate wagtail from the project.
While wagtail may be nice, our goals are to keep all things public, and
having things locked behidn a DB is congruent to that plan.
All in all, the django project only leveraged a single wagtail feature,
"richtext" which has been hacikly removed and will result in bad display
of however it comes up. But this is on homepage.html, which will be
removed and covered up with a static website, which means we should be
able remove homepage entirely from this project.
This reduction hopefully makes the monolith easier to understand,
maintain, and wield.
While 1.7.0 exhibits a similar issue, we would need to re-verify and
re-patch this library with a new 1.7.0 monkeypatch.
This is ultimately only an annoyance. It only occours when we've
already 500'd, and this just means we get a second 500. As such it's
not critical.
Boxes takes content directly from the DB and drops it into the django
templates. This is rather ugly and goes against keeping as much as we
can in static locations. As such, this is being dropped.
Works in prod mode, dies in dev with a warning/error
Doco seems to suggest that mixing these directories together is an
error as it means user uploads mingle with site files.
- remove a whole bunch of comments, they're useless
- Update TimeZone to Sydney
- Don't colocate MEDIA (user uploads), with STATIC in fact,
how is this set, Django has a safety check for this and bails.
- Do not store a default SECRET_KEY in git.
We'll set a random one by default, so things "just work"
It would also be acceptable to not set it and let DJ bail
- We dont want to log to a file. Our disks are ephemeral.
- We likely will not overlay a production settings.py over this one.
We need to implement something that is more container friendly in the
future. This will be env-vars or a config file.
Removed additional (and completely superfluous) styling in app.css that was otherwise making
our site look gluggy.
Mod'd fixtures (and updated db) to reflect PyCon rather than PinaxCon.
Nearly there. Much rubbish / cruft ripped out of site_base.html and content_page.html.
Had to modify cms_pages/models.py to accommodate a "simple" layout option in the homepage
editor.
Still some stuff to do. Styling not quite there yet, but want to checkpoint this.
* Adds schedule fragment script
* removes spurious logging
* Displays the right tab on DOM load.
* Load today’s schedule if we’re during the conference.
* remove TODO
* Optional track name with room name on schedule, access schedule by day eg /schedule/?day=Monday
* Changed to using a Track model rather than a char field
* Updates settings and requirements
* First pass at attendee profile
* Imports the registration templates; defines attendee profile models etc.
* First pass at themeing the registration form.
* First page of the registration form: done!
* Makes form validation nicer
* Adds populate_inventory
* Improves the additional items page
* Allows for rendering of formsets.
* Adds support for formset extending.
* Removes formset delete buttons
* Review page is LCA-ified
* Fixes some formset behaviour
* Fixes urls.py
* LCA-ifies product_category.html
* Invoices
* Credit card payments
* s/register/tickets/
* Show registration features only whilst products are available (think about this better, later)
* Updates the attendee profile form page
* Form tidy-up
* Makes it so that address info is copied from attendee profile to the address details are autofilled in Stripe.
* Adds feature to offer Australians a dropdown list of states rather than free text.
* Allow toggling of void invoices.
* Adds backgrounds to the headers in the registration process
* Improves the review page
* Adds “Linux Australia” to invoice details.
* Do not show balance due on void/refunded invoices.
* More thumbing
* Adds a link back to reports on each report.
* Tokenisation language.
* Another bug in credit card processing.
* Adds stripe refunds to options
* Removes spurious dashboard button.
* Tidies up the presentation of discounts.
* Tidies up presentation of voucher form.
* Fixes sponsor logo appearance with adblock.
* Front page tweaks
* Lets us specify alternative URLs in homepage panels
* more
* Updates discount amounts.
* More website fixes
* Changes language on pay invoice button
* Adds contact details to the invoice template.
* Updates the currency message in the invoice template.
* Explicitly includes e-mail address, because theme_contact_email doesn’t propagate
* Changes payment text.
* s/registration/selections/
* Removes final face palm
* Fixes lack of speaker dinner tickets for actual presenters.
* Adjusts wording in invoice e-mails
* Invoice wording.
* (FIX)
* Fixes margins on lists and tables
* Improvements arising from those CSS fixes.
* Changes description tags.
* Factors rendering of external links into its own template. Automagical!
* Adds wagtail templates for keynotes on the front page
* Migrates to Wagtail 1.6
* Migrates content pages to be a streamfield. Flexibility++.
* Fixes editing of ContentPage bodies
* Adds floating images to content pages
* Fixes the layout of floating images
* Adds anchor links to content pages.
* Adds presentation link to the keynote speaker block model
* LCA-ifies the schedule list
* Refactors cms_pages/content_page into a new base template
* cms_pages/content_page now derives from abstract_content_page
* news_index_page now derives from abstract_content_page
* news_page now derives from abstract_content_page.html
* utility_page now uses the content_page base template
* Factors out _right_floating_image.html
* Themes the presentation detail page
* Themes the speaker profile page.
* Themes the schedule list page.
* Minor work on schedule_conference.html
* Themes schedule_detail.html
* Replaces cradle.svg
* Adds a background image to the schedule pages
* Adds libravatar fallback for speaker profile images
* Adds new background images (must update colophon)
* Adds some magic so that we can have slightly different presentation backgrounds for different pages.
* Adds the sponsor block to the bottom of the page.
* Adds sponsor logos to footer.
* All migrations are now in this tree
* Fixes wagtail migrations
* Adjusts presentation_detail to allow for miniconfs (i.e. no target audience)
* Adds unpublishing to presentation detail
* Adds ScheduleHeaderParagraph, which allows us to add some text to the header of schedule pages.
* Adds NamedHeaderParagraph. It allows us to store header paragraphs in the CMS.
* Date formatting in the schedule
* First step for fixing images
* Allows us to automagically load the colophon
* Adds “publish changes” button.
* Can login with email address
* Replaces the monkey patch on send_mail, and replaces it with a monkey patch on EmailMessage’s constructor.
* Removes spurious print statements.
* Minimum viable changes to get schedule to display (#64)
* All migrations are now in this tree
* Replaces the monkey patch on send_mail, and replaces it with a monkey patch on EmailMessage’s constructor.
* Removes spurious print statements.
* Modifications to review_admin.html
* Adds “submit & jump to random proposal” button
* If user has a speaker profile, display their speaker profile name alongside their comments instead of their user name.
* Simple form input fields now use TakeFlight styling
* Styles the form widgets as per the styles in our CSS
* Styling of TextArea now matches the remaining input types
* Adds is_last modifier to navigation dropdown
* Adds admin for talk, tutorial, and miniconf proposals
* Adds an RSS feed
* Adds a link to the RSS page
* Unbreaks the old news index page
* Adds never_cache to the login page, removes the never cache middleware from the settings
* Invokes the site tree fix from previous fixes.
* Adds a disclaimer noting that previous years’ accounts have not been carried over.
Fixes#43
* Adds proposal type to the proposal summary page.
Fixes#40
* Adds travel/accommodation assistance to the proposals page, but makes it only visible to speakers in the proposal, or review managers.
Fixes#41.
Fixes#42.
* Reduces a lot of the whitespace in the header and footer.
Fixes#44
* Proposals review page now shows information for every speaker on a proposal.
Fixes#45
* Makes sure that non_field_errors are displayed by forms.
Fixes#37
* Adds Facebook svg button, and adds Facebook link type to models
* CSS work from takeflight, 30 June 2016
* Adds drop-down menus for navigation
* Adds mobile menus for navigation
* Minor tweak to mobile nav headings
* Makes the logo a link back to the homepage
* Updates the footer to the current version, removing sponsor logos for the moment.
* Fixes an incorrect link in dashboard
* Disables the symposion sponsors app
* Adds redirect links for login/logout; adds THEME_CONTACT_EMAIL value
* Re-adds colophon/copyright message.
* Adds AceMarkdownEditor widget
* Tidies up the generated HTML
* Tidies up form snippet behaviour
* Proposals forms now use the markdown editor
* Monkey patches the markdown editor into the speaker form.
* Adds missing field to proposal details
* Fixes#10 — adds a link to random unreviewed proposals
* Minor tweaks
* Proposals forms now have a header panel
* Adds panels to the speaker forms
* Imports latest pinax accounts templates
* speakers/base and proposals/base now derive from utility_page.html
* Most login forms now derive from take flight themes
* Missed email_confirm
* More accounts bits
* Restructures login form
* Puts submit etc buttons inside fieldset borders
* Themes speaker_edit.html
* speaker_create now uses takeflight theme
* proposal_submit_kind now uses takeflight theme
* fixes bug in form_snippet
* Optimises proposals_submit_kind
* proposal_submit now uses wagtail theme
* Proposal_edit now uses new theme
* More forms
* Proposal details page now loads from take flight theme
* proposal_fields now looks nicer under the take flight theme
* proposal_speaker_manage rethemed
* Adds inset_illustration as a drop-down of svg data rather than as an uploady thing.
* Adds external link types to the homepage models
* Migrations
* Initial site template with our new shiny templates
* Moves all lca2017-specific assets to lca2017 subdirectory; symlinks from dist
* Reflects changes in site_base
* Deletes most of new assets in dist/
* WIP home page
* Adds external link list support
* Adds white-right panel type to the home page
* Removes an oops
* Adds copyright text to the site.
* Updates the remaining illustrations to be more compact.
* Adds illustration field to content_page, and adds fields into the news page.
* News index page
* News page is done!
* Formats the dates properly
* Commits migrations
* Optimises SVG files
* better logo
* oops
* Removes margin on logo.
* Optimises svgs, and uses tania’s originals
* One more
* Adds basic wagtail app to the website
* Renames lca_website to cms_pages for clarity; re-instates pinax-boxes until we remove them from the templates
* OOPS
* Just Enough Wagtail
* Removes the template view homepage from urls.py
* OOPS
* Makes the home page use a stream field
* Removes an irrelevant migration that I accidentally introduced.
