| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
validated. This is to get around the issue that clicking submit without ever focusing and blurring the nickname field won't actually submit the form but only provide validation. It needs to be clicked again to submit. The first click processed the blur but remained on the page with no feedback. If somebody has better workarounds, please provide. The goal is to ensure that the name and the nickname are both validated before we can submit.
|
| |
|
|
|
|
| |
This reverts commit e332d1074f1b663ec66d37b0f575df2e41d5535c.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
and improved email notifications about new connections. Could not find a way to do this also for the generic notifications. Added hub domain of channel address on the new channel page. A few people on my hub didn't understood. This example will make it more clear. Some minor bits.
|
|
|
|
| |
for the first channel created by a new account. This simplifies channel creation by restricting the available options at registration time. The restriction is not applied to any additional channels created under the same account; and in any event can be changed immediately after channel creation, if desired.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
doing something in the background - trying to complete the nick field for them (and then check it before they submit).
|
| |
|
| |
|
|
|
|
| |
move smarty3 templates in "tpl/" folder, add util/precompile_smarty.php utility, add precompiled templates
|
|
|
|
| |
deal with the profile photo. Otherwise if you're really brave you could give it a go and see what happens. The worst that could happen is that it destroys the universe. Not a big deal. More likely you could end up with a bunch of imported things that have to be cleaned up. Less likely but entirely possible is that nothing useful will happen at all and it'll white screen.
|
| |
|
|
|