We are in the process of making PHP-Nuke Titanium fully compatible with all themes and modules of PHP-Nuke and any PHP-Nuke Fork.

The 86it Developers Network has one goal in common and quite frankly this is how it should have been from the beginning. All things Nuke means that if you write a module for PHP-Nuke Titanium, PHP-Nuke Platinum, or the US version of PHP-Nuke Evolution Xtreme they will all be compatible with one another.

The 86it Developers Network will work with anyone writing a new CMS or would like to convert a CMS so that it meets the Nuke network's global standards.

We have no intention of ever removing compatibility for old modules or themes. The only time something will be removed is when it is no longer capable of working with the current PHP versions that are used in our Developer Network. We do not believe in taking things away from the good folks in the developer world and we will keep things updated and available on the network at all times. In the event that you have a theme or module that was written that seems to be having a compatibility issue, just let us know, and we will help re-write and modify it so that it works with all versions of PHP-Nuke.

A new copyright system has been put in place for all themes and modules and it is very easy to use. All you do is edit the module or theme copyright.php file and hit save or with new themes, you would upload your new copyright file to the themes root folder. If it is a module the same applies, you will edit or put the new copyright file in the root of the new module directory.

PHP-Nuke itself was the very first CMS to ever be created in the internet world and it is here to stay forever. There is not a whole lot of acknowledgment in the online world because, well people have not been educated in this area of internet history. The Francis Framework was intended for Internet Desktop Applications, not mobile phones or tablets. This is no longer the case in 2023 as all of the PHP-Nuke systems have been updated so that any website running PHP-Nuke or any PHP-Nuke fork easily identifies what type of device is being used when a person logs on to a website built with PHP-Nuke or any fork of PHP-Nuke. The only time that tables are an acceptable form of design is when you're creating an Internet Desktop Application. This is because desktop applications use in most cases a locked-width dynamic design system, and the only time they do not, is if a developer or programmer is so lazy that they take the easy way out and design their website solely for mobile, TV, or tablet access. By doing that they are taking a shortcut so that they do not have to write as much code and even the large corporations take this shortcut to keep from having to write a website that adheres to device-type cosmetics specifically. 

 What makes PHP-Nuke and all PHP-Nuke Forks the best?

PHP-Nuke allows you to use PROCEDURAL code and OOP code. It is able to use any Symfony library, meaning the 50 most popular libraries in the world used to develop online mobile and desktop web applications all work with PHP-Nuke. Symfony was not the 1st standard but it is now the standard foundation on which all of the best PHP applications are built. The reason that this is awesome is that you can speed up the creation and maintenance of your PHP-Nuke website application. End repetitive coding tasks and enjoy the power of having the choices needed to control your project and code.

Here is a list of the Symfony components that can be used in PHP-Nuke:
https://symfony.com/components

The technical requirements for PHP-Nuke:

Before running your PHP-Nuke site or creating your first PHP-Nuke module you must:

• Install PHP 8.2 or higher and these PHP extensions (which are installed and enabled by default in most PHP 8 installations): Ctype, iconv, PCRE, Session, SimpleXML, and Tokenizer;
• Install Composer, which is used to install PHP vendor libraries.

Instead of using the entire Symfony framework, we use its vendor libraries only. We do this because our framework supports more than just Bootstrap and quite frankly we are not interested in having anything to do with a framework that makes you adhere to their strict setup rules and developer guidelines as this puts a damper on your programming and design capabilities.

PHP-Nuke comes with Rector built in which will allow you to refactor old legacy code when creating modules or even themes. Rector is a PHP tool that you can run to get an instant upgrade or automated refactoring. It helps with the PHP-Nuke module and theme upgrades, it improves your code quality. Also, it helps with type-coverage and getting to the latest PHPStan level.

If you see something somewhere that you like, make no mistake it can be ported into a module. The PHP-Nuke module system is designed for that reason specifically, any application can be setup and run as a module allowing the dynamic module and theme system to do its magic. 

The majority of people that used PHP-Nuke liked to take advantage of the dynamic theme system designed by Francisco Burzi (Frank) intended to be used for Internet Desktop Applications.

Now people will like using PHP-Nuke because it has the best of both worlds and also has the ability to use the CSS Grid Layout Module alongside the Francis Framework which was designed solely for Internet Desktop Applications. The CSS Grid Module originally was intended for mobile, TV, and tablet website access allowing it to resize to fit all of our smaller less expensive devices. It offers a grid-based layout system, with rows and columns, making it easier to design web pages without having to use floats and positioning, which is used by the Francis Framework. It took a little while but the CSS Grid Module properties are now currently supported by all modern browsers. In short, the Francis Framework was designed to size up and the CSS Grid Layout Module was created to size down.

Data Scientist / Programmer   name: Ernest Allen Buffington   email: ernest.buffington[at]gmail.com   www: https://theghost.86it.us   github: https://github.com/ernestbuffington

Hello,

A very dear friend of mine has died and I am trying to deal with this the best way that I can,

I am still working on the code on a daily basis, PHP-Nuke Titanium v4.0.4 is now available for download on the repo.

There are some breaking changes due to the new version of PHP.

Support for all of the older versions of PHP has gone away. We now only have support for PHP 7.2 and up.

There are no real reasons to continue support for versions of PHP prior to 7.2.

If you have a module or software that will not run we can help you get it running for PHP 7.2 and up.

We are going to add support for any and all versions of nuke including Platinum.

Data Scientist / Programmer   name: Ernest Allen Buffington   email: ernest.buffington[at]gmail.com   www: https://theghost.86it.us   github: https://github.com/ernestbuffington

I just added mod_rewrite to all versions of PHP on the developer server.

I am about to restart Apache so if you experience a hiccup that is why...

I have also added PHP v8.2 to php-fpm

I Bumped the PHP version on the PHP-Nuke Titanium developer server to v8.2.3

We are now running Alma Linux v8.7.0

Data Scientist / Programmer   name: Ernest Allen Buffington   email: ernest.buffington[at]gmail.com   www: https://theghost.86it.us   github: https://github.com/ernestbuffington

Here is the skinny on PHP-Nuke Titanium:

I work on it every day and the speed at that I have been moving is unbelievable.

A lot of things need work and a lot of additions are being worked on silently in the background.

I'm working on a global Form system for the code and to use when coding modules. It will make module creation very easy and a lot more fun.

A new Frequently asked question system is being created and it will replace the regular FAQ module.

The login system is being changed to support multiple applications like phpbb3 and others.

A new admin Templating system will be in place that will be used with the new Form system. You won't even know it changed except for the fact that it will be way cleaner and a lot of handling will be done with Ajax!

New system security is being implemented that will make this code amazingly secure!

A lot of old code is being replaced with more modern PHP code. (I use procedural code where I can because I'm not lazy)

We are keeping the theme system intact while doing this and making it so that it supports multiple theme formats.

When we are done there will be a mobile version and a desktop version which I am working on now.

Data Scientist / Programmer   name: Ernest Allen Buffington   email: ernest.buffington[at]gmail.com   www: https://theghost.86it.us   github: https://github.com/ernestbuffington

We just upgraded MariaDB from Version: 5.5.5-10.3.37 to Version: 5.5.5-10.3.38

Release date: 6 Feb 2023

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on GitHub. On GitHub you can view more details of the revision and view diffs of the code modified in that revision.

• Includes all fixes from MariaDB 10.2.44
• Revision #c73985f2ce 2023-01-28 14:30:46 +0200
  • MDEV-30010 post-push: fixing test results.
• Revision #2279dddad6 2023-01-24 19:41:29 +0100
  • MDEV-30457 Windows, signtool error "No file digest algorithm specified."
• Revision #7fe932444d 2023-01-05 20:08:01 +0200
  • MDEV-30323 Some DDLs like ANALYZE can complete on parallel slave out of order
• Revision #3aa04c0deb 2023-01-24 19:35:16 +0200
  • MDEV-30010 Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964
• Revision #f513d71538 2023-01-23 15:54:49 -0800
  • MDEV-30081 Crash with splitting from constant mergeable derived table
• Revision #d69e835787 2022-11-03 14:56:50 -0600
  • MDEV-29639: Seconds_Behind_Master is incorrect for Delayed, Parallel Replicas
• Revision #2ed598eae8 2023-01-24 13:30:22 +0200
  • Added comments re JOIN::all_fields, JOIN::fields_list
• Revision #c45630327c 2023-01-23 10:38:27 +0200
  • Update 10.3 HELP tables
• Revision #074bef4dca 2023-01-21 00:09:58 -0800
  • MDEV-30248 Infinite sequence of recursive calls when processing embedded CTE
• Revision #f18c2b6c8a 2023-01-23 13:10:24 +0200
  • MDEV-15178: Filesort::make_sortorder: Assertion `pos->field != null |
• Revision #00150ff8d4 2023-01-19 06:52:54 +0200
  • Fix connect bson.cpp warning
• Revision #244bf37c73 2023-01-19 06:49:47 +0200
  • Fix mroonga warning of use-after-free
• Revision #567b681299 2022-11-15 14:39:30 -0800
  • Minimize unsafe C functions usage - replace strcat() and strcpy() (and strncat() and strncpy()) with custom safe_strcat() and safe_strcpy() functions
• Revision #ea270178b0 2023-01-19 21:43:29 +0100
  • MDEV-30052 Crash with a query containing nested WINDOW clauses
• Revision #6fe882cd85 2023-01-19 17:53:51 +0100
  • Add my_afree after my_alloca in early return case
• Revision #0ddbec40fb 2022-11-09 16:41:19 +0400
  • MDEV-23335 MariaBackup Incremental Does Not Reflect Dropped/Created Databases
• Revision #489b556947 2023-01-17 17:52:16 +0200
  • MDEV-30422 Merge new release of InnoDB 5.7.41 to 10.3
• Revision #834650c7cf 2023-01-16 14:59:59 +0100
  • New CC 3.1
• Revision #7a98d232e4 2023-01-11 18:57:44 +0300
  • MDEV-30378 Versioned REPLACE succeeds with ON DELETE RESTRICT constraint
• Revision #eb145e5ad7 2023-01-12 10:38:38 +0800
  • fix typos
• Revision #b194c83b7b 2021-06-03 11:24:34 -0600
  • MDEV-25277: mysqlbinlog --verbose cannot read row events with compressed columns: Don't know how to handle column type: 140
• Revision #53c4be7bc0 2022-12-13 15:44:24 +0100
  • MDEV-30220: rsync SST completely ignores aria-log-dir-path
• Revision #b84f3fa769 2022-12-13 14:59:24 +0100
  • MDEV-30157: Galera SST doesn't properly handle undo* files from innodb
• Revision #e4a4aad7cf 2022-12-13 10:32:21 +0100
  • pre-MDEV-30157 & pre-MDEV-28669: fixes before the main corrections
• Revision #b928c849d2 2023-01-04 13:01:47 +0300
  • MDEV-28602 Wrong result with outer join, merged derived table and view
• Revision #b218dfead2 2023-01-11 08:37:27 +0200
  • Remove an unused parameter
• Revision #56948ee54c 2023-01-10 10:45:03 +1100
  • clang15 warnings - unused vars and old prototypes
• Revision #d7f447915c 2023-01-08 09:53:09 +1100
  • MDEV-30342 Wrong "Truncated incorrect DECIMAL value" warning/error
• Revision #e64e6768e0 2023-01-08 09:26:50 +1100
  • MDEV-17093: SOURCE_REVISION in log (postfix - not in help)
• Revision #b21832ef15 2022-10-26 22:08:32 -0700
  • MDEV-27624 Wrong result for nested left join using not_exists optimization
• Revision #af0ff8b455 2022-12-08 19:34:00 +0000
  • MDEV-17093: SOURCE_REVISION in log and handle_fatal_signal
• Revision #758c24dae2 2023-01-04 18:32:54 +0800
  • fix typos
• Revision #e51a1d6fc0 2023-01-03 10:48:57 +1100
  • MDEV-30329: mariadb-service-convert resets systemd service to default User=root
• Revision #21223c0461 2022-12-18 16:30:26 +0100
  • MDEV-29988 group by fix
• Revision #908c48a34d 2022-12-18 14:30:36 +0100
  • fixes for json.json_table and main.func_json in --ps
• Revision #60f646e2f3 2022-12-14 14:36:27 +0100
  • MDEV-29988: (spider fix) Major performance regression with 10.6.11
• Revision #37a316c01d 2022-12-09 21:10:25 +0700
  • MDEV-29988: Major performance regression with 10.6.11
• Revision #a9b31b0814 2022-12-09 11:50:05 +0700
  • MDEV-29988: (revert) Major performance regression with 10.6.11
• Revision #8760f6907c 2022-12-28 12:10:38 +0100
  • MDEV-30102 file missing in development libraries
• Revision #ca23558a05 2022-12-12 13:18:46 +0100
  • --skip-name-resolve=0 didn't work
• Revision #d78ac04ee6 2022-12-09 14:32:58 +0100
  • ignore changes in submodules when committing everything
• Revision #eba099184e 2022-12-05 00:21:28 +0100
  • MDEV-30151 parse error 1=2 not between/in
• Revision #f8adc47b69 2022-12-06 15:48:13 +0100
  • MDEV-19071 Wrong results when using STDDEV_SAMP() and view
• Revision #6710fe4b42 2022-12-26 08:23:16 +0100
  • MDEV-30293: mariabackup fail with --galera-info option without Galera
• Revision #72e2d1d220 2022-12-27 00:02:02 +0300
  • MDEV-25004 Refactorings
• Revision #e056efdd6c 2022-12-27 00:02:02 +0300
  • MDEV-25004 Missing row in FTS_DOC_ID_INDEX during DELETE HISTORY
• Revision #68c437bad6 2022-12-27 00:02:01 +0300
  • MDEV-25004 restart_bindir option to restart server from different location
• Revision #5d506ac201 2022-12-27 00:02:01 +0300
  • MDEV-25004 vers_force_trx option to force transactional System Versioning
• Revision #7c5609fb64 2022-12-20 17:41:24 -0600
  • typos
• Revision #3ddc00dc3b 2022-12-13 16:06:13 +0300
  • MDEV-30225 RR isolation violation with locking unique search
• Revision #3f63aa18a7 2022-12-07 20:19:05 +1100
  • MDEV-29562 Spider table charset error should happen correctly

Data Scientist / Programmer   name: Ernest Allen Buffington   email: ernest.buffington[at]gmail.com   www: https://theghost.86it.us   github: https://github.com/ernestbuffington

Ghost Mode Mod has been updated.

Several things have been affected by the update:

1. The Members List now works Correctly - No more lowercase queries - If you need to look someone up and they used lowercase on their nickname you must use the search users feature.
2. When in Ghost Mode other users will only be able to Private Message you from the Forum area if you have made a recent post.
3. The Sort button was fixed in the Member List.
4. When in Ghost Mode the only person able to view your profile are the Admins and Yourself.
5. When in Ghost Mode you are completely anonymous and are only known by your callsign/nickname.
6. When in Ghost Mode your name will not appear in the Members List - (only admins will see your name in the members' list).
7.  No more lowercase queries in the Forum Admin section either - If you need to look someone up that used lowercase on their nickname you must use the search user feature.
8. When in Ghost mode you will not show up in Currently Viewing or Online Information.
9. When in Ghost Mode the Forum area will not show you in the Recently Visited list or Currently Online Browsing List.

You can switch to Ghost Mode by editing your profile.

Data Scientist / Programmer   name: Ernest Allen Buffington   email: ernest.buffington[at]gmail.com   www: https://theghost.86it.us   github: https://github.com/ernestbuffington

New PHP Nuke Titanium Installer, now available on the Repo

I'm sure we will find some bugs and I will fix them along the way.

I tested the installer for 2 weeks and squashed as many bugs as I could find.

To run the installer just point your browser to https://your.domain.com/setup the rest is self-explanatory.

Data Scientist / Programmer   name: Ernest Allen Buffington   email: ernest.buffington[at]gmail.com   www: https://theghost.86it.us   github: https://github.com/ernestbuffington

Hello,

Blog Submissions has been broken for some time now and now it is fixed.

The mailer for Blog Submissions is now fixed as well.

In the PHP-Nuke Titanium v4.0.4 release there will be some database modifications for:

1. Blog Archives
2. Blog Submit
3. Blog_Topics
4. Blogs
5. Blogs_Top

ToDo:

1. Modify Post Blog so that it uses the user aid (NickName) instead of the admins, bypassing the user writes garbage!

Data Scientist / Programmer   name: Ernest Allen Buffington   email: ernest.buffington[at]gmail.com   www: https://theghost.86it.us   github: https://github.com/ernestbuffington

Hello Everyone,

I have kidney disease and I'm feeling a little under the weather.

I am going to get some rest for a bit and I will be back shortly...

Data Scientist / Programmer   name: Ernest Allen Buffington   email: ernest.buffington[at]gmail.com   www: https://theghost.86it.us   github: https://github.com/ernestbuffington

So, we are not allowed to use <font> tags anymore right?

Yea I thought the same thing, However, if your site is designed in HTML 4 <font> tags are still going fine??

Deprecated as it may be, the font tag is still the only thing that works universally across pretty much all email clients, old and new. Bear in mind that email is not the web and it's still positively antediluvian. Some email services do unspeakable things; I've encountered one that blindly stripped all HTML tags (ignoring provided plain-text versions), and converted linked images to attachments, resulting in an unreadable mess. Even contemplating having inline styles working in the face of such vandalism is truly wishful.

Want to know where the big hole is? Hotmail. Hotmail, live.com, and outlook.com strip or replace inline styles, yes, started as far back as 2013. Blame Microsoft, Hotmail, live, outlook.com, and outlook. They have all gotten considerably worse over the years (e.g. floats were dropped from outlook.com 10 years ago, outlook dropped background images in 2007, and they've not been seen since).

Inline styles work in Gmail, but it strips anything outside the body tag. Some corporate mail filters (like BlackSpider/WebSense) do exactly the opposite, so if you want to be completely sure about your styling, you need to put a style tag in the head tag, another copy of it within the body (invalid, but it works), the same styles inline (look at the premailer project), and finally the same styling using font tags. Yes, it's insane, but no amount of wishing is going to make the problem go away. You can of course drop some of these, but by doing so you're implicitly accepting that it's not going to look the same in some places. You need to look at your audience - a new mobile music site can probably get away with it, but a corporate pension provider probably needs to be living in 2003 font-tag land.

Fortunately, Apple Mail, iOS Mail, and iCloud all have vastly superior HTML handling as their Campaign Monitor table shows, as does the email standards project. With the majority of mobile reading using some flavor of WebKit, rendering on mobile is generally much more consistent (and mostly better) which sucks because most of us can afford desktops and use them on the daily.

You could simply say that it's not worth the effort - anyone using crappy mail readers clearly doesn't care that much what their email looks like, but that doesn't mean that your styling isn't going to break.

The old FONT tag is needed to achieve some email styling, for example changing the color of an anchor is something that is hard in different email clients, this will not work well in some clients:
<a href="url-here"style="color:orange">click here</a> but this will work in most all the cases: <a href="url-here"><font color="green">click here</font></a>.

I say all these companies and developers need to move with the time and fix all this so inline styling is all that will be needed!

Holy shit, why are all HTML/e-mail developers and companies stuck in 2003?

Data Scientist / Programmer   name: Ernest Allen Buffington   email: ernest.buffington[at]gmail.com   www: https://theghost.86it.us   github: https://github.com/ernestbuffington