Show Navigation
Notices by Sean Tilley (dsh@deadsuperhero.com), page 14
-
@Mario Vavti In my case, they only appear on random settings pages, such as under /admin.
I could've sworn there was a text field somewhere that just contained layout preferences that could override what a theme dictated...
-
This is not a drill! I repeat. This is not a drill!
-
They become visible slightly later now (after the content has been loaded)...
-
Good thought @Mario Vavti , but that's originally where I listed it. Seems to work for accounts other than mine on my hub.
mod_network, mod_channel, and mod_profile all have it listed in region=right_aside
[widget=notifications][/widget]
-
Well done, Sean, you have successfully tested your ability to write in English!
-
@Sean Tilley check if the widget is registered in the pdl file. We do not overwrite custom pdl settings...
-
this is not a test!
-
Hmm, trying to figure out why my notifications aren't showing up in my custom theme. Seems to work for the dummy channel I set up.
@Mike Macgirvin I can't seem to remember, but is there a place where channel-specific theme overrides live? I think I have something specific to my channel that's preventing the notification widget from showing up, even though it's coded into my theme. It shows up occasionally on random settings pages, but that's about it. :/
-
@herzmeister der welten Are you saying that that plugin exists, or you want it to?
-
You have successfully completed your test, Sir.
-
@dsh Here's a comment from Mastodon.
-
This is yet another test testing the initial test just for testing purposes, if not more or even less of it. Or the opposite.
-
@dsh test failed err or err or pwease retwy!
-
This is a test.
-
Yes, these are important tips... that should be read before to start ...
-
@james_lamentus I can not confirm. "My" rules to save me from trouble are
- Leave most configs standard
- allow only few people on your hub
- stick to origin master and update Debian and Hubzilla and Plugins every day
- take always the most simple approach, for example letsencryt as simple shell script in favour of python letsencrypt client mess
- /update/ do not activate every possible plug-in to federate with "everybody". (I am sceptical what this does to the database if I think of the troubles with federations.)
- /update/ think before you change something at your hub
My hub now runs almost two years with two three single short disturbances- one blank white page because the plugins where not updated along with core. Solved
be by one single git pull - one manual change of the shell script for letsencrypt: They had to rename the project and changed the path to the config file
- /update/ Some weeks ago private messages became visible to others. Bad thing!. I deleted a clone that I forgot about and re-created a private group.
I would strongly recommend to use - "standard" installs via scripts to get Hubs that are comparable.
- keep the Hubs small
-
...or maybe the problem is another:
today everyone believes that can easily administer a site, on the one hand it is true, for certain sites, for certain software, but any person is not an administrator, to be an administrator you must have experience, you must know things, you must be an... administrator .
-
you are just an exception that confirms the rule ... all we know the many problems we have had during these years .. no one can disclaim
maybe you want to ask for @Seth Martin or others ?
In all these years just 4 or maybe 5 admins have managed quite easily to not have problems, or rather, to solve them without sweating blood, just 4 or 5 in how many? Hundreds? Everyone has problems, OK my friends.... but when the problems in the hubs become BIG, only a few people really work out.
So..not, hubzilla is not for "simple" admins, but for good admins.
-
to keep hubzilla going for years. ? Definitly YES.
-
you must be a Senior administrator
Hey, definitly NOT. (Speaking for myself: I am neither adminstrator nor Mr. Brain like the main devs of Hubzilla. I am just an interested layman who spent some time.)