prupdated

+Clients
  • Content count

    129
  • Joined

  • Last visited

1 Follower

About prupdated

  • Rank
    IPB Full Member

Recent Profile Visitors

8,405 profile views
  1. PHP7 Compatibility

    I've worked in the server IT departments of some very large companies before. There's no way we would jump on a major release like this until probably 6-12 months at the earliest. There would be a vocal set of internal customers who would want it immediately for whatever new features it has. But as the 'server guys' we have to support it. Once we put it out, and it breaks, we own it now. There are also a hundred and one unintended consequences that nobody foresaw - we have support tools, customers have third party apps they use, etc. I don't think it's unreasonable at all to expect at least a several month delay before anything like this should even be on the radar. At the end of the day, the software needs to be stable and reliable.
  2. (BD4) Moods

    Very nice. Good to see moods back.
  3. Profile Songs

    Thumbs up. Very cool. Working great. 
  4. Profile Backgrounds

    Working good. Nice to let members customize their profile a little bit more.
  5. (BIM41) Topic Thumbnail

    Very nice layout for a more visual look rather than the traditional text based layout.
  6. Prune/mass move topics

    Thanks for the suggestion. I tried it before but search is lost on archived topics. Generally it would be a good idea except for the functionality loss. The load times now are fine while not losing the functionality when archiving. It was just the size of an individual forum that was the problem. Hence, moving topics could be a decent solution for this and other problems, maintenance, or many other reasons why one might want to bulk move. I've worked around it for now doing my best with SQL scripting to move older topics out of the main forum each night while updating the various related counters. Most likely I'm missing something though. So it would be nice to have an official routine.
  7. Prune/mass move topics

    This should really move up the priority list. I have a forum with nearly 4 million posts and 600k topics. In IPB3, the size of the forums didn't seem to matter. In IPB 4, the site chokes up and delays about 2-3 seconds every time someone would click on a forum with a large number of topics in it. By large, I mean several hundred thousand topics and millions of posts. Clicking on a smaller forum is no problem and happens fast. This is a 12 core server with 32 GB of RAM running at 3.2 GHz, MariaDB, etc. and various optimizations, CDN, etc. The only way I could even use IPB4 without reverting back to IPB 3 and reconsidering my alternatives, was to chop up the forums into smaller ones. The main forum being about 50k topics max. Most likely the way I do it is not the best through various SQL statements. But to keep the site moving with sub second load times, I push out topics over 90 days old into an annual forum. I know there's an archive option, but the last time I tried that I didn't like that it took those topics out of searches and member's history. I'd rather just have an option to move topics to another forum after X days without the archiving.
  8. Preview Post Button

    Great job. Sometimes it's good to just get a second look at something before posting it.
  9. Portal

    Great. Members love this design over the default forum look.
  10. Post Anonymously in Forums

    One of the most popular plugins on our board for a long time. Glad to see it with 4.X.
  11. Anti-Spam IPS4

    Very good. Seems to catch almost everything. Been using it almost a year.
  12. The only way I found around it was to write a relatively simple front end script to manage people's secondary groups through SQL. It's just an array field in the member table. Then everything else runs natively without other programs and hooks using resources. I don't think this would be viewed favorably on the cloud though. It's probably an idea for stand alone server eyes only. It does has the advantage of having everything else running natively without substantial performance hits though.
  13. CJ Menu

    It seems very good so far. It is essential for taking the navigation menu beyond just the basics.
  14. This needs to be brought back. 
  15. Thumbnails in IP4.0 Abysmal

    Generally images displayed on a page should match their served size. HTML scaling is not generally appropriate. Most page speed ranking services will also tell you this. https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/image-optimization#delivering-scaled-image-assets They will even take it a step further and go into sprite use depending on your sites use of images. As it is, for years I have had to work around this in IPB by manually editing various templates, system files and settings to pull my images from a caching resize script. These are some of the optimization techniques I would rather see implemented in IPB.  The example on page 1 of this thread is simply HTML scaled and is the same as the full size image. Instead of using 150KB it should probably use 50KB. If you have 10 images like this, now you're up to 1 MB of unnecessary extra transfer for the page.