A user encountered this error today: (I replaced private path info with "---")
QuoteType of error: Critical
Error message:
Wrong value type sent to the database. Integer expected. (page_id)
Function: Display
File: ---/Sources/Display.php
Line: 948
URL of page causing the error: ---
Is there currently a patch?
I see it's a known issue. https://github.com/SimpleMachines/SMF2.1/issues/5764
there was a PR fix merged 6 months ago....
Quote from: Kindred on May 13, 2021, 03:05:41 PM
there was a PR fix merged 6 months ago....
I'm running PrettyURLs that modifies that file. What's the best way to roll out those changes and keep the PrettyURL mod changes? What's the "proper SMF way" to do it?
what I mean is -- why are you not running a version that is less than 6 months old, given the 100+ fixes put into the code after the initial RC3 release? :P
why is smf providing a version which is older than 6 month ;)?
Quote from: albertlast on May 14, 2021, 09:35:24 AM
why is smf providing a version which is older than 6 month ;)?
Tehcnically, we are offering a later version as well - RC4 isn't out yet, but development version on Github is public.
Quote from: albertlast on May 14, 2021, 09:35:24 AM
why is smf providing a version which is older than 6 month ;)?
um because it's still in release candidate...it's not a stable version...there is constant changes being made to it, to which anyone can grab the latest version off of github, but it's still not a stable product, it is only for testing purposes.
Quote from: cpf on May 13, 2021, 09:33:54 PM
I'm running PrettyURLs that modifies that file. What's the best way to roll out those changes and keep the PrettyURL mod changes?
Best way to deal with Pretty URLs is do clean install to remove all code, drop database tables, delete code from .htaccess, and never, ever install it again. :P
Quote from: Sir Osis of Liver on May 14, 2021, 01:02:06 PM
Quote from: cpf on May 13, 2021, 09:33:54 PM
I'm running PrettyURLs that modifies that file. What's the best way to roll out those changes and keep the PrettyURL mod changes?
Best way to deal with Pretty URLs is do clean install to remove all code, drop database tables, delete code from .htaccess, and never, ever install it again. :P
I did that, but now my forum isn't pulling up.
I guess what I'm asking is what's the best SMF way to roll out the new file and put back the PrettyURLs (or any mod's) changes?
Quote from: shadav on May 14, 2021, 11:51:10 AM
Quote from: albertlast on May 14, 2021, 09:35:24 AM
why is smf providing a version which is older than 6 month ;)?
um because it's still in release candidate...it's not a stable version...there is constant changes being made to it, to which anyone can grab the latest version off of github, but it's still not a stable product, it is only for testing purposes.
I'll pull the latest versions off GH, but for those mods I have installed, I need to know the best way to deal with them to put them back.
Quote from: shadav on May 14, 2021, 11:51:10 AM
Quote from: albertlast on May 14, 2021, 09:35:24 AM
why is smf providing a version which is older than 6 month ;)?
um because it's still in release candidate...it's not a stable version...there is constant changes being made to it, to which anyone can grab the latest version off of github, but it's still not a stable product, it is only for testing purposes.
the github version is not packages in a way where the user can download and run the stuff,
he had to move the right files from others in the root and this expect to mutch know how of smf to make it right.
on the other hand, the users get blamed when they find bugs in the released smf version,
since the version is to old and many of the issue got fixed.
so when you don't care of the result of the finding of the released rc version, why you guys released it?
Quote from: cpf on May 14, 2021, 02:06:09 PM
Quote from: shadav on May 14, 2021, 11:51:10 AM
Quote from: albertlast on May 14, 2021, 09:35:24 AM
why is smf providing a version which is older than 6 month ;)?
um because it's still in release candidate...it's not a stable version...there is constant changes being made to it, to which anyone can grab the latest version off of github, but it's still not a stable product, it is only for testing purposes.
I'll pull the latest versions off GH, but for those mods I have installed, I need to know the best way to deal with them to put them back.
Since everybody prefers to squabble over other matters, I'll answer this. The procedure is just like a large upgrade—overwrite all files and re install all mods. Hope this helps.
There's no need for the hostility. RC4 will be coming, with the packages generated. It's just not there yet.
Quote from: live627 on May 14, 2021, 03:48:26 PM
Quote from: cpf on May 14, 2021, 02:06:09 PM
Quote from: shadav on May 14, 2021, 11:51:10 AM
Quote from: albertlast on May 14, 2021, 09:35:24 AM
why is smf providing a version which is older than 6 month ;)?
um because it's still in release candidate...it's not a stable version...there is constant changes being made to it, to which anyone can grab the latest version off of github, but it's still not a stable product, it is only for testing purposes.
I'll pull the latest versions off GH, but for those mods I have installed, I need to know the best way to deal with them to put them back.
Since everybody prefers to squabble over other matters, I'll answer this. The procedure is just like a large upgrade—overwrite all files and re install all mods. Hope this helps.
Excellent. Thank you!
Quote from: cpf on May 14, 2021, 02:06:09 PM
I'll pull the latest versions off GH, but for those mods I have installed, I need to know the best way to deal with them to put them back.
If you start out with a clean install, clean database, and clean .htaccess, you should be able to install 2.1 mods with package manager, assuming the mods have been updated to be compatible with latest github release. As noted, 2.1 is still in RC, so it's a moving target for mod authors.
Quote from: Sir Osis of Liver on May 14, 2021, 09:58:45 PM
Quote from: cpf on May 14, 2021, 02:06:09 PM
I'll pull the latest versions off GH, but for those mods I have installed, I need to know the best way to deal with them to put them back.
If you start out with a clean install, clean database, and clean .htaccess, you should be able to install 2.1 mods with package manager, assuming the mods have been updated to be compatible with latest github release. As noted, 2.1 is still in RC, so it's a moving target for mod authors.
It's a 10-year old DB converted from 2.016. From what I gather, I can just bring over all the files newer than the last RC3.
Would be best to upload the complete package and run upgrade.php, there may be changes to database.
Quote from: Sir Osis of Liver on May 16, 2021, 10:41:51 PM
Would be best to upload the complete package and run upgrade.php, there may be changes to database.
Will do, thank you. I'll report back.