Updating The Website Content - Revision history

Beta: typo fix

2024-09-10T01:15:41Z

typo fix

← Older revision		Revision as of 18:15, 9 September 2024
Line 22:		Line 22:
	* '''THERE IS NO BACKUP''' (I mean there kind of is, but not like there is for this wiki) '''so be careful with your changes!'''		* '''THERE IS NO BACKUP''' (I mean there kind of is, but not like there is for this wiki) '''so be careful with your changes!'''
	* Since the webpage updater is "Legacy" code (as of 2024-09-09) it is janky as hell and hard to update. The only way to improve this would be to re-implement it in Symfony code. Maybe some day.		* Since the webpage updater is "Legacy" code (as of 2024-09-09) it is janky as hell and hard to update. The only way to improve this would be to re-implement it in Symfony code. Maybe some day.
	* If you want a link do the file on the webpage, it's in the index. Rather than "Edit Page Content" click "Go To Page." As simple as it seems, this is a pain to try to make work on the edit page as long as it's legacy code, so ... sorry about that.		* If you want a link to the file on the webpage, it's in the index. Rather than "Edit Page Content" click "Go To Page." As simple as it seems, this is a pain to try to make work on the edit page as long as it's legacy code, so ... sorry about that.
	* Always have a date in the field. If any of the dates are empty, there will be an error. We've mostly resolved this, but it still pops up now and again on really old pages.		* Always have a date in the field. If any of the dates are empty, there will be an error. We've mostly resolved this, but it still pops up now and again on really old pages.
	* nl2br checkbox means that any line breaks you have will be on the webpage. You normally want this box checked, but sometimes it helps to turn it off for doing things like ordered or unordered lists in html.		* nl2br checkbox means that any line breaks you have will be on the webpage. You normally want this box checked, but sometimes it helps to turn it off for doing things like ordered or unordered lists in html.

Beta: more info on permissions

2024-09-10T01:07:41Z

more info on permissions

← Older revision		Revision as of 18:07, 9 September 2024
Line 1:		Line 1:
	== Before you start, you need: ==		== Before you start, you need: ==

	* To be staff and have the proper permissions in the staff system to update the webpage. ~~Most~~ department heads have this position so you can maintain your own content.		* To be staff and have the proper permissions in the staff system to update the webpage.
			** Some department heads have this position so you can maintain your own content.
			** Social media staff have access to update the webpage.
			** If you need to update something on the page and don't have access, you can either reach out to Social Media or ask the admin to grant you permissions so you can handle it yourself.

	== Steps ==		== Steps ==

Beta: no backup

2024-09-10T01:02:07Z

no backup

← Older revision		Revision as of 18:02, 9 September 2024
Line 17:		Line 17:
	== Things to know ==		== Things to know ==

	* Since the webpage updater is "Legacy" code (as of 2024-09-09) it is janky as hell and hard to update. The only way to improve this would be to re-implement it in Symfony code. Maybe some day.		* '''THERE IS NO BACKUP''' (I mean there kind of is, but not like there is for this wiki) '''so be careful with your changes!'''
			* Since the webpage updater is "Legacy" code (as of 2024-09-09) it is janky as hell and hard to update. The only way to improve this would be to re-implement it in Symfony code. Maybe some day.
	* If you want a link do the file on the webpage, it's in the index. Rather than "Edit Page Content" click "Go To Page." As simple as it seems, this is a pain to try to make work on the edit page as long as it's legacy code, so ... sorry about that.		* If you want a link do the file on the webpage, it's in the index. Rather than "Edit Page Content" click "Go To Page." As simple as it seems, this is a pain to try to make work on the edit page as long as it's legacy code, so ... sorry about that.
	* Always have a date in the field. If any of the dates are empty, there will be an error. We've mostly resolved this, but it still pops up now and again on really old pages.		* Always have a date in the field. If any of the dates are empty, there will be an error. We've mostly resolved this, but it still pops up now and again on really old pages.

Beta: add more things to know

2024-09-10T00:51:50Z

add more things to know

← Older revision		Revision as of 17:51, 9 September 2024
Line 17:		Line 17:
	== Things to know ==		== Things to know ==

	* Always have a date in the field. If any of the dates are empty, there will be an error. We've mostly resolved this, but it still pops up now and again on really old pages.		* Since the webpage updater is "Legacy" code (as of 2024-09-09) it is janky as hell and hard to update. The only way to improve this would be to re-implement it in Symfony code. Maybe some day.
			* If you want a link do the file on the webpage, it's in the index. Rather than "Edit Page Content" click "Go To Page." As simple as it seems, this is a pain to try to make work on the edit page as long as it's legacy code, so ... sorry about that.
			* Always have a date in the field. If any of the dates are empty, there will be an error. We've mostly resolved this, but it still pops up now and again on really old pages.
	* nl2br checkbox means that any line breaks you have will be on the webpage. You normally want this box checked, but sometimes it helps to turn it off for doing things like ordered or unordered lists in html.		* nl2br checkbox means that any line breaks you have will be on the webpage. You normally want this box checked, but sometimes it helps to turn it off for doing things like ordered or unordered lists in html.
	* Very limited html is allowed. Allowed HTML Tags: '''<nowiki><p> <a> <br></nowiki> <nowiki><img></nowiki> <nowiki><b> <i> <u> <strong> <center> <div> <span> <font> <code> <ul> <ol> <li> <blockquote></nowiki>''' (Since it has huge potential to break the page we do not allow <nowiki><hr></nowiki> or <nowiki><table>)</nowiki>		* Very limited html is allowed. Allowed HTML Tags: '''<nowiki><p> <a> <br></nowiki> <nowiki><img></nowiki> <nowiki><b> <i> <u> <strong> <center> <div> <span> <font> <code> <ul> <ol> <li> <blockquote></nowiki>''' (Since it has huge potential to break the page we do not allow <nowiki><hr></nowiki> or <nowiki><table>)</nowiki>
	* Because other html tags are stripped out, some pages may break if you try to update them because we've directly added the html into the database. Just pay attention to what html is being used. '''DO NOT UPDATE THE CONTACT PAGE; YOU WILL BREAK THE MAILCHIMP FORM'''		* Because other html tags are stripped out, some pages may break if you try to update them because we've directly added the html into the database. Just pay attention to what html is being used. '''DO NOT UPDATE THE CONTACT PAGE; YOU WILL BREAK THE MAILCHIMP FORM'''
	* If you change a section to "archive" it hides it in the database and there's no UI to get it back. If you did this by mistake someone with direct database access has to fish it out of the database; there is no other UI for admin to fix this. Be absolutely sure you want it gone forever (or as close to forever as it gets in this situation).		* If you change a section to "archive" it hides it in the database and there's no UI to get it back. If you did this by mistake someone with direct database access has to fish it out of the database; there is no other UI for admin to fix this. Be absolutely sure you want it gone forever (or as close to forever as it gets in this situation).

Beta: start page

2024-09-10T00:36:43Z

start page

New page

== Before you start, you need: ==

* To be staff and have the proper permissions in the staff system to update the webpage. Most department heads have this position so you can maintain your own content.

== Steps ==

# Log into BACON (Registration system)
# Go to Staff Home (under "Other"). The header will turn red to show you you're in a different section of the website.
# Under "Other" (again), find and select "Website" under the Communication & Media subheader
# Notice the two links at the top that would allow you to make a whole new page, or edit our sponsorship images.
# Scroll down to the page you want to edit
# Click the link "Edit Page Content"
# Update the content as needed
# Click Submit.
# Ignore any cloudflare cache errors

== Things to know ==

* Always have a date in the field. If any of the dates are empty, there will be an error. We've mostly resolved this, but it still pops up now and again on really old pages.
* nl2br checkbox means that any line breaks you have will be on the webpage. You normally want this box checked, but sometimes it helps to turn it off for doing things like ordered or unordered lists in html.
* Very limited html is allowed. Allowed HTML Tags: '''<nowiki><p> <a> <br></nowiki> <nowiki><img></nowiki> <nowiki><b> <i> <u> <strong> <center> <div> <span> <font> <code> <ul> <ol> <li> <blockquote></nowiki>''' (Since it has huge potential to break the page we do not allow <nowiki><hr></nowiki> or <nowiki><table>)</nowiki>
* Because other html tags are stripped out, some pages may break if you try to update them because we've directly added the html into the database. Just pay attention to what html is being used. '''DO NOT UPDATE THE CONTACT PAGE; YOU WILL BREAK THE MAILCHIMP FORM'''
* If you change a section to "archive" it hides it in the database and there's no UI to get it back. If you did this by mistake someone with direct database access has to fish it out of the database; there is no other UI for admin to fix this. Be absolutely sure you want it gone forever (or as close to forever as it gets in this situation).