Hi All,
I posted earlier and on my own replaced ManageSearch.php and I thought I had solved the Admin search problem where I couldn't reindex the data on my server. I have no problems under Search>>Weights and Search >>Settings, however, when I click Search Method, which is where I would normally reindex the data for more accurate searches for my members, I get this error.
An Error Has Occurred!
[] operator not supported for strings
At first, I figured it was the newer version of PHP I was using (7.2) so I dropped it back again and again, yet this error persists over and over no matter which version of PHP I use or win what configuration as in FastCGI, etc
As stated I have already replaced the manageSearch.php with the latest one for version 2.0.15 so I am comfortable assuming it is OK as is.
I also added the fix for index.php for string type errors thinking that may have contributed and still no joy. I understand 2.0.15 does not support PHP 7.2 so at this point, I am at a loss as I have went back to version 6.XX and even the normal release version for CentOS 7. It's driving me nuts because I am certain its a simple fix, yet there it is.
If anyone has any useful information to resolve this problem or has run into this issue and found a solution, well, I would be truly appreciative for any assistance in resolving it. It's not like it is a huge thing as everything else works perfectly BUT our forum has almost 4000 members and I am getting gripes about searches where there are no results even when they should be because my search data is so old. I haven't reindexed the search data for a long while now, and its beginning to create unruly and unhappy members and making me lose what little hair I have left :)
On a side note, I have no interest in using another search method like Google etc. We are an admin approved member's only PRIVATE forum and I don't even allow bot searches. We vet every member and try to guarantee their security and identities.
Thanks.
Mike
Hi Mike,
Sorry for no reply, if you still using 2.0.15 your really need to update to 2.0.17 a few bugs have been fixed aswell as support for newer php this may also fix your issue.
same problem here with 2.0.15 - so, this is a bug? and upping to .17 is the known fix?
Yes, and yes.
Assuming you don't also have a mod that changes something that isn't compatible with newer versions of PHP in the same area.
so an upgrade means that forum software changes but there is no database change, and mods will need to get reinstalled along with any custom themes and icons ... correct?
If you use the admin panel upgrade to install the patches, they install as mods and nothing else changes.
If you follow the big upgrade process (upload a new set of files), your mods will be wiped out.
where is the admin panel upgrade and will the 2.0.17 mod package upgrade work for 2.0.13 as well as 2.0.15?
looks like the mod patches will only move up one release point, so going from 15 to 17 requires first going to 16? and 13 to 14 to 15 to 16 and then 17?
Patches install as mods using the same function, the Package Manager.
Upgrading through patches does require that you go through each of them in order. So 2.0.13 does require 14, 15 and 16 before being able to install 2.0.17. This maintains any mods that you already have installed.
Or, as Arantor said, you can use the large upgrader which replaces all your files and resets your mods, but will jump you straight to 2.0.17 from any previous version.
thanx arantor and gary. will try the 13 to 14 upgrade first.
in using the patch upgrade from 13 to 14 i get a test failed for ./Themes/default/Profile.template.php
You should check the changes that the patch is trying to make to the file, and then make the changes manually after having the Package Manager take care of the rest.
Sometimes though, it can just be the version number only, if that's the case, then that's not something to worry about, but I'd probably sort that out anyways. :P
Quote from: Gary on August 08, 2020, 02:28:40 PM
You should check the changes that the patch is trying to make to the file, and then make the changes manually after having the Package Manager take care of the rest.
Sometimes though, it can just be the version number only, if that's the case, then that's not something to worry about, but I'd probably sort that out anyways. :P
thanx, but i have no clue what to check or what i'm doing.
If you click the little arrow icon, it'll show you a list of changes and which one specifically failed. You can then click the little paper icon to see what it was looking for and what it couldn't find and if you screenshot that we might be able to help...
thanx, images attached. this is going from 2.0.13 to 2.0.14 ...
image 1 - the failure
image 2 - the first failure data
image 3 - a copy of the second failure data (too long to screen capture)
image 4 - shows errors for ant's themes, i could always remove them and reinstall.
Which forum?
Link?
Would need admin and ftp access to do upgrades, don't have anything for that forum. If you uninstall/reinstall Ant's theme you'll break any mods that edited the theme. He changed a lot of code so it requires quite a few manual edits to install the patches.
not really concerned about ant's themes, more interested in the error shown above.
Per Arantor, upgrading to current version will fix the error. Should do that anyway as you're four updates behind, there were security patches. I see you have another forum at .13 and two at .15.
yes, i do need to upgrade and i always dread doing them. yes, four forums, two at 13 and two at 15. ack.
You'll have to fix your php versions, too. tradgang is 2.0.15 in php 5.5.18, tradmla 2.0.15 in 7.3.18, can't find bpg, and don't have any access to loopaddictions. If it's running in 7.x that could be causing the error. Look in Admin -> Support and Credits for version info.
Found it, bpg is 2.0.13 in 5.5.18.
the problem (complete failure of the forum search engine) is solely with tradmla.org ....
Version Information:
Forum version: SMF 2.0.15 (more detailed)
Current SMF version: SMF 2.0.17
GD version: bundled (2.1.0 compatible)
Database Server: MySQL
MySQL version: 5.1.63-community-log
PHP: 7.3.18
Server version: Apache
... the other three are running 5.5.18
it looks as if going from 15 to 16 for tradmla org will work, zero errors on the patch mod install, just don't want to execute the patch until i coordinate with the server manager for a complete backup. i'll see how it goes on monday or tuesday.
those three other forums will be going to php 7.3 soon, too.
Never seen that error before. Are you using a search index? You can try removing it, see if search works with no index, then create a new index. Otherwise may as well wait until you can do the upgrades. If you need help with it post here or pm me.
for tradmla.org, 2.0.15, when i go to 'search method' this is what comes up .... no search works for that forum.
Quote from: RFD on August 08, 2020, 07:38:31 PM
the problem (complete failure of the forum search engine) is solely with tradmla.org ....
Forum version: SMF 2.0.15 (more detailed)
PHP: 7.3.18
fairly sure 2.0.15 does not work on 7.3, not really sure if 7.2 worked....may need to lower your php version...I know that 2.0.17 works with 7.2, I don't think it works for 7.3 (or it mostly works but still some errors)
And the problem, as asserted right back in the first post (someone else's solved topic, I might add) is that you're running code that doesn't work on 7.1+ on 7.1+.
right - clearly in the case of the tradmla.org forum, the search engine problem is with the php 7.3 version versus its 2.0.15 SMF release.
going from 15 to 16 looks like it will work ok, and i will implement that patch mod on tuesday after the entire system is server backed up. if all is well, i'll see what happens with 16 going to the final 17.
if i understand patch mods correctly, as opposed to a "large upgrade", it will render the upgrade to 2.0.16 but will not affect themes, icons, profiles, avatars, attachments, threads, posts, etc.
Yup, because it works exactly like any other mod. (Because it is a mod itself)
thanx for the confidence boost, arantor! <thumbs up!>
another thought - after the server backup, would it be best to go into maintenance mode when implementing a patch upgrade?
You can if you want, but usually isn't needed. Patches update you to the next version immediately on install.
So it's down to your personal choice if you want to go into maintenance mode during patch upgrades.
thanx gary.