prupdated

+Clients
  • Content count

    136
  • Joined

  • Last visited

1 Follower

About prupdated

  • Rank
    Member

Recent Profile Visitors

8,655 profile views
  1. The 4.1.14 update was one of the most disruptive updates to my site in the last year or two. Immediately after updating I got tons of complains about members not being able to login and other issues. I have been running Easy Pages for quite a long time. I also experienced some of the same issues noted above. It didn't stop with the Easy Pages app either. There were many other problems - all of which worked fine before 4.1.14. At first, I was able to partially work around the new login url problem by doing some server based rewrites / redirects. Ultimately, more problems surfaced and I gave up and converted what Easy Pages I had to the regular Pages app. It seems over time, the Pages app has added much of the Easy Pages functionality to it anyway. This was still hard because many of the features I used it for I had to change or get rid of completely during the migration. After this, I had to uninstall Easy Pages. Then I also had to reset my Furls to defaults. Then recached the site. This fixed most of the problems. User logins were now working properly rather than retuning error pages. However there were still problems unrelated to Easy Pages. It seems after resetting Furls to defaults, there were a few native IPS calls still using the old format that were not reflected in the new default Furls. So I had to go into the source code and work around those. And second to last of my problems, a number of url formats I used for custom theme changes previously were now broken - such as calling a topic with just a dash after it and nothing else now required two dashes. And the last present of 4.1.14 was some type of IPS search index task update that caused my sql server to nearly lock up so bad it caused my website to timeout while it was running. After a few days, I was able to isolate this as the problem and just set my site to only index 3 days of data so it would calm down this problem. There is a thread about this problem elsewhere on the forum. So what went from a seemingly routine IPS incremental update, turned out to be the nightmare of the year for me. All told it probably took me a week to sort out the mess. I will certainly take all updates very seriously from now on with full backups done immediately before so I can immediate roll back and research when this type of thing happens again. I will also likely skip many of the updates since they can cause so many problems. As it is, it has become more common to find an increasing number of plugins and updates and template changes and urls breaking on each IPS update. I can see why the cost to develop modifications for IPS 4 has gone up. Their shelf life may be only as long as a few weeks until the next update. At the same time, the number of modifications and functionality / performance of the forum software itself are a mere fraction of what used to be available in the IPB 3 days. For crying out loud, to this day I still have to rely on using a Google search for indexing my forum rather than the built in high performance Sphinx searching of days gone by.
    This is great. Now members can see files in subcategories on my site instead of them appearing empty. A definite improvement. Thanks.
  2. Same problem here. I was able to work around it for now by editing this file: /applications/portal/extensions/core/FrontNavigation/Portal.php changed line reading: class _Portal to class _Portal extends \IPS\core\FrontNavigation\FrontNavigationAbstract I assume it has to do with some menu issue in 4.1 like is shown in one of the patches to 4.1.7 that refers to this type of error. I'm not sure if this workaround causes any other problems, but this at least got me going on 4.1.7 and easier than restoring back to 4.1.6.1. If you haven't upgraded yet, I would hold off until it's fixed though.
    Thumbs up. Very cool. Working great.
    Working good. Nice to let members customize their profile a little bit more.
  3. 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.
  4. 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.
    Great job. Sometimes it's good to just get a second look at something before posting it.
  5. With IPB 4.1.4 the sort order of portal topics does not seem to work if selecting to sort by topic start time. Rather, it sorts by default of last updated topic no matter what the setting. It worked correctly with IPB 4.1.3.2 . I had to change the sortBy line in portal.php from start_date to forums_topics.start_date and it then works as expected. Edit: Seems to be IPB bug with fix attached at following URL. After reversing my edit and applying the patch it works as expected again.
    One of the most popular plugins on our board for a long time. Glad to see it with 4.X.
  6. With IPB 4.1.4 the sort order of portal topics does not seem to work if selecting to sort by topic start time. Rather, it sorts by default of last updated topic no matter what the setting. It worked correctly with IPB 4.1.3.2 . I had to change the sortBy line in portal.php from start_date to forums_topics.start_date and it then works as expected.
  7. 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.
  8. I'm not getting a PM icon either. The PM is there. Just no icon. Notification settings are set correctly. And a regular PM works as expected. As soon as I send a regular PM to the new member, I get a 1 on the notification icon, and 2 on the PM. Before that nothing. Edit: I'm running IPB 4.1.3.2
  9. This needs to be brought back.
  10. 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.