--- old +++ new @@ -1,5 +1,7 @@
* Test read-only mode in SFX
-* Test site wide messages in SFX+ * this doesn't work with Zend+ * would probably block logins, which we need to allow uploading new files+* Test site wide messages in SFX and make sure they work
* Test site wide messages in SFPY (/settings/admin vs configtree value)
These haven't been used for a while, so see how well they still work
size: --> 1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
summary: test read-only mode and site messages --> test site messages
Description has changed:
Diff:
--- old +++ new @@ -1,6 +1,7 @@
* Test read-only mode in SFX
* this doesn't work with Zend
* would probably block logins, which we need to allow uploading new files
+
* Test site wide messages in SFX and make sure they work
* Test site wide messages in SFPY (/settings/admin vs configtree value)
status: in-progress --> code-review
assigned_to: John Hoffmann ☠ --> Tim Van Steenburgh
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just changed the favicon.ico that was in sfx/www into a png and changed the 2 templates to use it, instead of the orange sf gif they were still using.
To test on sfx: edit /var/local/config/sf-local.json and put some text in site_notice
sfpy: edit /var/local/config/sfpy.json and put text in site_notice
Should get a drop down header on both sites.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sfx messages work fine. Sfpy message work fine as long as you don't use unicode chars, otherwise you get melty forge. Maybe we don't care, since we control the content anyway, but thought I'd mention it. If it's not worth fixing, feel free to close this ticket.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Diff:
Diff:
jwh/3141 (sfx and sfpy)
I just changed the favicon.ico that was in sfx/www into a png and changed the 2 templates to use it, instead of the orange sf gif they were still using.
To test on sfx: edit /var/local/config/sf-local.json and put some text in site_notice
sfpy: edit /var/local/config/sfpy.json and put text in site_notice
Should get a drop down header on both sites.
Sfx messages work fine. Sfpy message work fine as long as you don't use unicode chars, otherwise you get melty forge. Maybe we don't care, since we control the content anyway, but thought I'd mention it. If it's not worth fixing, feel free to close this ticket.