• Content count

  • Joined

  • Last visited

About ensoph

  • Rank
  • Birthday 12/24/1988
  1. So will the delta updates be available for normal download too? An official git repository would be the best idea, but I guess I can make my own.
  2. That's true, I could keep doing it myself; however, this also applies to any feature request I might think of. The rationale for implementing this one is the same as ever: because it would hugely benefit a part of your customers. I'm just saying that uploading everything through FTP every time shouldn't be the only officially supported way, because it's insecure and error-prone. A git-based solution, like the one I proposed, would be great for my workflow, but frankly any other upgrade system I can think of would be better than what we have now.
  3. Yes, I know (although I probably wouldn't choose php), but it would be nice to have an official and integrated solution. Just my 2¢.
  4. That's what I already do, but it's far from a perfect workflow, especially because file permissions "break" every time. An officially supported system, coupled with some maintenance CLI tools, would go a long way towards making my forum's maintenance easier.
  5. FTP uploading is a relic from the past: it's an error-prone, time consuming and insecure (no hash checking) method that shouldn't even be considered in serious deployments. I'm not saying that it shouldn't be offered, since (I guess) many of your customers are still on shared hosting, but you should at least offer some alternatives for those of us who have access to a dedicated server / VPS. A git-based deployment system would probably be the best option here, since minor updates would just be a matter of running `git pull` (and visiting the update script, or — even better — running it from the CLI). The files' integrity would be guaranteed, the entire operation would run in seconds instead of minutes, and mistakes could be reverted easily. It would also make it *very* easy to spot malicious or unwanted code in the forum's filesystem, and it would make tools like the whitespace/file permission checker unnecessary. The next best thing would be offering .patch files for minor updates. They weight a fraction of the full package's size and they too are applied in a matter of seconds. I hope that 4.0 brings some needed innovation in this area. Thanks for listening.
  6. will you consider supporting Redis as a cache backend? it's similar to memcached...
  7. i solved this on my forum. now it stores the avatar's last edit time in the database as a query string (the file's name in the filesystem stays the same), i.e. profile/photo-2.jpg?1320180009. since it involves (literally) two lines of code, it would be nice to see this activated by default. in /admin/sources/classes/member/photo.php, find this (should be line 127): $save = array( 'pp_main_photo' => $photo['final_location'], and replace with: $save = array( 'pp_main_photo' => $photo['final_location'].'?'.time(), then find this (line 130): 'pp_thumb_photo' => $photo['t_final_location'], and replace with: 'pp_thumb_photo' => $photo['t_final_location'].'?'.time(), haven't had any problem so far, though it might (or might not) break avatar-related cleanup tools.
  8. yes, this is also what most other forum packages do.
  9. i'm having this issue too. tracker says it has been solved, but it doesn't seem so...
  10. right now, if i want to move all activities in the system scheduler to cron, i have to manually disable all of them one by one, get the curl commands and add cron formatting. it would be easier for us with a shell to just have a function that disables all activities and outputs all of them as a formatted crontab which includes the time preset, ready to be pasted in crontab.
  11. very nice! since I use a localized version of the forum, these improvements are really welcome. some other ideas: - providing example pages/screenshots/descriptions for those strings which are difficult to find "in live action", to disambiguate them according to context - a cleaner, divided by language lang packs section - hiring professional translators for the most popular languages. some translations right now are clearly made by amateurs, and contain A LOT of dumb grammar errors or inappropriate wordings. - or, if the previous option is too expensive, setting up some sort of centralized wiki-like interface to translate languages, like facebook translations, where users/customers can propose and vote on better string translations, so if there are mistakes they can be easily corrected by crowdsourcing. this could also be done by some third-party site (if i only had the PHP skillz i would've done that myself), but it would be nice to site it official, since lots of big companies (again, facebook is the best example) are doing it.