It seemed like a reasonable guess, I haven’t checked out the specific architecture and am not familiar with the MediaWiki API or the extension being designed for non-programmers.
If web programming was clean and nifty, the wiki and the forum system would both reference the same user database on some MySQL backend. If it’s an “organically grown” mess, nevermind. But the API should still be well defined. Now, it was only an idle suggestion in case someone missed some low hanging fruit, I didn’t expect it to be some assured panacea. I’ve only ever done one php/mySQL website around 9 years ago, I don’t much care for web programming.
Could also just remove the whole “recent wiki edits” potion of the sidebar. It doesn’t provide much and takes up screen space on all the important pages.
Could also just remove the whole “recent wiki edits” potion of the sidebar. It doesn’t provide much and takes up screen space on all the important pages.
It’d be much improved if it simply filtered out the registration of new user accounts.
I see.
It seemed like a reasonable guess, I haven’t checked out the specific architecture and am not familiar with the MediaWiki API or the extension being designed for non-programmers.
If web programming was clean and nifty, the wiki and the forum system would both reference the same user database on some MySQL backend. If it’s an “organically grown” mess, nevermind. But the API should still be well defined. Now, it was only an idle suggestion in case someone missed some low hanging fruit, I didn’t expect it to be some assured panacea. I’ve only ever done one php/mySQL website around 9 years ago, I don’t much care for web programming.
Could also just remove the whole “recent wiki edits” potion of the sidebar. It doesn’t provide much and takes up screen space on all the important pages.
It’d be much improved if it simply filtered out the registration of new user accounts.