Recommended Posts

We've started the work for it. We've also identified a number of issues with some of our mods (we have a lot) that will work a lot better in 3.4, plus we're also hoping that the Subscriptions (IPB team unofficial mod/hack) will be updated, but aren't ruling out just making it compatible ourselves so we can upgrade, but obviously we don't want to add more work to an already huge task :p

From what I hear most of our common mod hacks have already been worked into our testing area and I'll also be doing some work there tomorrow and the coming week (mainly testing etc).

I hope we can do it in February, so hold off on the feature requests for the current board atm.

Shortly before the upgrade we may also want some feedback on a few things, mainly to do with off topic forum presentation and permissions.

Neowin will also return with a new theme, either with the upgrade, or shortly after it. The main thing is ensuring everything works properly.

Link to comment
https://www.neowin.net/forum/topic/1134374-the-upgrade-to-34/
Share on other sites

BTW, in the https://www.neowin.net/credits section, you guys dont talk much about IPB (and the mods you use) and the software/OS you run. Would be nice.

http://community.invisionpower.com/blog/1174/entry-8192-ipboard-34-dev-update-best-answer-feature/

This feature is much needed on Neowin :)

BTW, in the https://www.neowin.net/credits section, you guys dont talk much about IPB (and the mods you use) and the software/OS you run. Would be nice.

Actually it does say the latest stable RHEL/CentOS, MySQL, Apache, PHP.

That said I thought there was discussion about upgrade MySQL and PHP for performance... will that be happening or has it already happened? (not that you want to add work to the current work :p)

Good luck. There have been lots of editor issues and please also keep in mind there may be some theme wonkies. There have been some MAJOR theme revamps from 3.2 to 3.4 so please keep that in mind.

stuff is smoother when you upgrade a X.X.x to an X.X.y release but if you upgrade from a X.X.x release to a X.Y.x release that's when stuff gets wonky.

my theme transition from 3.3 to 3.4 was very drastic and me, and lots of people had to redo our themes as a result and that was a pain because I had to wait for my theme author to fix it so I had to stick with a visual skin for a while... but then the visual editor skin grew on me and I ended up keeping it... however the friend and the client didn't want to do that so they waited and it took 2 weeks.

For those with template issues post-upgrade:

Please run the template merge tool from the following ACP area:

Look & Feel > Look & Feel > Template Merge

Then run the report on it

Then go to:

Look & Feel > Template Merge Reports > Choose your skin

After you've done that go to the following ACP area:

System>Tools and Settings>Cache mgmt>and scroll down and re-cache the skinsets

Also you may want to rebuild the templates as well from the following ACP area:

Look & Feel > Template Tools

Run the following:

Recache Skin Sets

Rebuild Master Skin Data

Clean Up Tools

I wish the best for your custom forum software though and It would be cool if you released that and got into offering it to people. I would love to help with it too... . I'm really curious about it.

I hope that you keep the current skins that are available now.

All the current skins will be gone, including mobile. They'll have to be recreated on 3.4, whenever that happens. Blame IPB for their god awful skinning system on that one.

  • Like 2

All the current skins will be gone, including mobile. They'll have to be recreated on 3.4, whenever that happens. Blame IPB for their god awful skinning system on that one.

So that means being stuck with a bright white theme for months. So much for the forums having any use...

So that means being stuck with a bright white theme for months. So much for the forums having any use...

nope, no bright white default theme like in times past. what is now known as midnight will be the default theme used when they upgrade

this was decided shortly after the last major upgrade took place

nope, no bright white default theme like in times past. what is now known as midnight will be the default theme used when they upgrade

this was decided shortly after the last major upgrade took place

Eh, it will be a white bright default theme most likely. We may have a dark alternative, but it won't be like what we have now.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!