Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; Smarty has a deprecated constructor in /home4/maritim5/public_html/forums/libs/smarty/Smarty.class.php on line 64
Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; bbcode has a deprecated constructor in /home4/maritim5/public_html/forums/libs/bbcode.inc.php on line 5
Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; mailer has a deprecated constructor in /home4/maritim5/public_html/forums/libs/mailer.inc.php on line 7
Fatal error: Uncaught Error: Call to undefined function mysql_connect() in /home4/maritim5/public_html/forums/libs/mysql.inc.php:22 Stack trace: #0 /home4/maritim5/public_html/forums/libs/ubbthreads.inc.php(88): sql->connect() #1 /home4/maritim5/public_html/forums/ubbthreads.php(41): require_once('/home4/maritim5...') #2 {main} thrown in /home4/maritim5/public_html/forums/libs/mysql.inc.php on line 22
If I had to guess. It would be your host upgraded your php version to 7.XX Your version of ubb is not compatible. I recall that php 5.6 is pretty much the highest you can go. with ubb7.5.8
Last edited by Ruben; 06/20/20191:31 PM.
Blue Man Group There is no such thing as stupid questions. Just stupid answers
Fatal error: Uncaught Error: Call to undefined function mysql_connect() in /home4/maritim5/public_html/forums/libs/mysql.inc.php:22 Stack trace: #0 /home4/maritim5/public_html/forums/libs/ubbthreads.inc.php(88): sql->connect() #1 /home4/maritim5/public_html/forums/ubbthreads.php(41): require_once('/home4/maritim5...') #2 {main} thrown in /home4/maritim5/public_html/forums/libs/mysql.inc.php on line 22
Its quite simple really; someone upgraded PHP on the server. PHP7 does not have the mysql_connect function (as the mysql_ functions have been depreciated and replaced by their mysqli_ counterparts), and any scripts that rely on it will present this error (anything coded prior to PHP7 without MySQLi support); you'll need to either roll PHP back to PHP5 or upgrade to UBB.threads 7.7.x.
You'll probably also want to check any PHP scripts installed on your server as there are likely other scripts showing the same behavior.
Sorry that you had to wake up and find your site is now throwing errors. Its never fun when that happens.
Good news though, you can easily upgrade to the current version of UBB.threads, which fully supports PHP 7 and MySQLi.
Below are some versioning explanations you may find helpful:
The versions of PHP which UBB.threads 7.5.8 is compatible with, are PHP 5.2 - PHP 5.6. The current version of UBB.threads is 7.7.1, and is compatible with PHP 5.4 - PHP 7.3. https://www.php.net/manual/en/migration70.incompatible.php
PHP 4 can connect to a MySQL database using the MySQL extension. PHP 5 can connect to a MySQL database using either MySQL or MySQLi extension. PHP 7 can connect to a MySQL database using the MySQLi extension (the "i" stands for improved) https://phppot.com/php/mysql-vs-mysqli-in-php/
UBB.threads 7.0.0 to UBB.threads 7.6.2 uses the MySQL extension. UBB.threads 7.7.0 and newer uses the MySQLi extension.
--
When your host emails you that they are upgrading critical services, telling you to upgrade your hosted scripts to compatible versions; at the risk of any down time, its highly advised that you find out what that means, and resolve any potential issues before their date.
An example of what that email may have looked like:
Quote
[WEBHOST] is dedicated to providing you with the best resources for you and your website. So, we’re excited to announce that we will be upgrading all of our servers to newer versions of Apache and providing newer versions PHP (including PHP 7.2 & 7.3). The upgraded versions provide better data processing, which can improve the performance and speed of your website.
When will maintenance begin? We will start the maintenance process on [DATE] and will continually monitor your website. We anticipate less than 5 minutes of slowness/downtime during the upgrade itself.
We recommend updating all of your web installations to the latest version--including WordPress, Joomla, Drupal or any other Content Management Tool that you may use--as soon as possible. For custom or unique PHP code, please see the PHP Migration Guide.
Last edited by isaac; 06/20/20193:08 PM. Reason: fixed typos
Yes, you'd simply follow the standard upgrade instructions; the mysqli_ functions are used by default in 7.7.0+, no mysql_ functions exist in the 7.7 series.
I uploaded the 7.7.1 files and changed the permissions for all of the directories and files as stated, but when I try to use the upgrade.php file I receive the following error:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@maritime-sda-online.com to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
I have the Install Directory set as 777 and the php and tmpl files also set at 777, but were previously at 666 but still didn't work, which is why I changed them all to 777.
I am still getting the following error when using http:/mysite.com/forums/install/upgrade.php
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@maritime-sda-online.com to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Last edited by Ruben; 06/23/20191:12 PM. Reason: edited url to keep private
If you are upgrading then there should not have been a need to change file/folder permissions. You would have just overwrote the files when you uploaded them. Normally the file permissions would not be changed. But some host do not allow 777 and you would need to change it to 755. And even though you will navigate to the install folder it would be upgrade.php you run not install.php.
Cpanel will not allow scripts to execute under a directory with 777 permissions for "security".
Under cpanel your install and admin directories should be 755, the rest should follow standard install instructions. I'm not sure the setting offhand (still in the middle of the forest) but this is a setting that generally only happens in cpanel instances (I'm sure you could find it in the search).
The Install Guide said to use 777 for directories and 666 for files, but said later below that it may need to be 755 and 644 respectively instead of 777 and 666.
I have now changed the permissions to 755 and 644, but upgrade.php still isn't working yet.
Giz, The install guide covers the file/folder permissions and exceptions. perfectly. But it has no mention of the install folder.
I noticed that, but will now change the files to 644 to see if that makes a difference, as I forgot to do that.
Like I said, it literally only affects cpanel, and is a setting within whm to allow this behavior like every other system. BUT the install directory itself needs no special permissions in any case.
Mod security is a php module, contact your host with the exact error from your logs (and not the error printed to your browser, as the logs will include the mod security rule).
There isn't anything we can do regarding server security modules.
There is a server log feature in UBB but it is only for mysql and it would need to be enabled.
For mod_security it is a php module.. So it would be a error log for php. You may not have access to it depending on your hosting plan. But I would look in cpanel or whm. whichever is available. Look for something about logs and php.
Or try file manager in cpanel and see if you have a similar folder above the root if you are able.
Or you may need to just call the host to check.
Blue Man Group There is no such thing as stupid questions. Just stupid answers
Should be an entry for every 406 error in the webserver log, additionally they could disable mod security, it's more of a hindrance than anything else in my experience.
If it's not in your error logs it could be in a combined set of logs in the access logs, but isn't something related to the UBB.
I called them back and they had me on hold for awhile before telling me that the error log is in the root directory, and, as they don't even have access to that, they have issued a ticket for the Level 2 Techs to look at sometime tomorrow, this being Sunday.
I hope they will resolve the issue tomorrow.
Why do they have Mod Security in the first place??? Does it actually protect them???
If some of the rules in the modules matched in scripts that preform malicious behaviors it could, but in my experience hosts don't edit the default rule set which will trigger on a significant amount of legitimate scripts.
You can search these forums for "not acceptable"and 406 to see several instances that we've had to deal with troubleshooting in the past.
I am receiving the following WARNING in Admin CP and wondering how to fix that:
WARNING: Your PHP max_input_vars setting is set to a low value. Your current setting is 1000; the default setting is 1000. Based on your current number of forums, a minimum setting of 3540 is recommended. Your forum may have issues such as a blank configuration file, missing settings, or unexpected script behavior if you continue. Please see the "Issues with the PHP 'max_input_vars' Setting" entry on the UBBDev Wiki for more information.
That is a UBB warning about a detected server configuration issue; the System Requirements Test can fully test your server configuration vs recommended options.
If you click the link in the warnings they will open a page with more information...
You don't seem to understand; the UBB is detecting that your server value is low, too low to write all of the configuration values in one stream for all of the forums you have. The effect here is to make your server not write a 0 byte configuration (clearing out your configuration when you make changes) as the server is currently configured to only allow a small value.
Again, this is reporting that YOUR SERVER (not UBB.threads) has a low value... The goal is to have your host increase any low values, the System Requirements Test tool will report any other values that may need changed as well; most shared hosts will not allow users to make server level configuration changes.
This is a warning notice about your server configuration. it's there to notify you of a potential issue you could have because of that way your server is configured.
all the information is detailed in the warning link you quoted.
This is a warning notice about your server configuration. it's there to notify you of a potential issue you could have because of that way your server is configured.
all the information is detailed in the warning link you quoted.
Even though there are still a few glitches, including the Log In tab on the top right of the green menu bar, if I click on a private forum link from the right column it will give me a message with the log in option below the message. I am then able to log in using that log in option.
Once I am in I am able to access the Admin Dashboard/CP via the Admin Access tab in the green menu bar.
Could there be a command problem when trying to use the log in tab?
It shows all those weird stuff when you place your mouse over the Log In Tab.
as clarification, you said you were using Bluehost as your hosting company?
I also use bluehost, but on a pro account. I have zero of the issues you have mentioned in this thread.
I am curious about the ftp software you use to transfer your files.
or are you using their ftp web online interface?
getting back to your original question, are you modifying the php.ini that in the root of your account, or one that's in a sub directory somewhere? I believe bluehost now only supports php.ini "single mode." and no longer does "directory mode" for boxes they've just updatded to php 7.x
again, the value may be something you can easily ask you host for assistance with
your website customizations do not look to be mobile friendly. and you have errors in your HTML.
you'll need to a) update your custom header, custom footer, and b) correct all of your customizations with HTML errors in them.
for A, you can disable viewport at Control Panel > Primary: Advanced settings > Disable Viewport
this will prevent your screen from rearranging things on mobile devices. and they will be locked in to a minimum with of 600px or similar. I don't remember the exact width, but it's a feature toggle that was added for sites that are in transition or that don't want to support layouts for mobile devices.
Last edited by isaac; 06/24/20199:58 AM. Reason: added screenshot of site with viewport disabled
I forgot about this glitch when clicking on Forum Help:
Parse error: syntax error, unexpected '' (T_ENCAPSED_AND_WHITESPACE), expecting '-' or identifier (T_STRING) or variable (T_VARIABLE) or number (T_NUM_STRING) in /home4/maritim5/public_html/forums/languages/english/faq.php on line 42
When trying to send an email to 24 selected users, I am receiving the following error message:
Script: /home4/maritim5/public_html/forums/admin/dosendemail.php Line#: 191 SQL Error: Column 'USER_ID' in where clause is ambiguous SQL Error #: 1052 Query: SELECT COUNT(*) FROM ubbt_USERS as t1, ubbt_USER_PROFILE as t2, ubbt_USER_DATA as t3, ubbt_USER_GROUPS as t4 WHERE t2.USER_ACCEPT_ADMIN_EMAILS <> 'Off' AND t1.USER_ID <> '1' and t2.USER_ACCEPT_ADMIN_EMAILS <> 'Off' and t1.USER_ID = t2.USER_ID and t1.USER_ID = t3.USER_ID and t1.USER_ID = t4.USER_ID AND USER_ID NOT IN ('986') and t3.USER_LAST_VISIT_TIME > '1546300799' GROUP BY t1.USER_ID ORDER BY t1.USER_ID ASC
When trying to send an email to 24 selected users, I am receiving the following error message:
Script: /home4/maritim5/public_html/forums/admin/dosendemail.php Line#: 191 SQL Error: Column 'USER_ID' in where clause is ambiguous SQL Error #: 1052 Query: SELECT COUNT(*) FROM ubbt_USERS as t1, ubbt_USER_PROFILE as t2, ubbt_USER_DATA as t3, ubbt_USER_GROUPS as t4 WHERE t2.USER_ACCEPT_ADMIN_EMAILS <> 'Off' AND t1.USER_ID <> '1' and t2.USER_ACCEPT_ADMIN_EMAILS <> 'Off' and t1.USER_ID = t2.USER_ID and t1.USER_ID = t3.USER_ID and t1.USER_ID = t4.USER_ID AND USER_ID NOT IN ('986') and t3.USER_LAST_VISIT_TIME > '1546300799' GROUP BY t1.USER_ID ORDER BY t1.USER_ID ASC
Is this a bug that needs fixing???
It is also showing up in the mysql log error:
Script: /home4/maritim5/public_html/forums/admin/dosendemail.php - Line: 191 SELECT COUNT(*) FROM ubbt_USERS as t1, ubbt_USER_PROFILE as t2, ubbt_USER_DATA as t3, ubbt_USER_GROUPS as t4 WHERE t2.USER_ACCEPT_ADMIN_EMAILS <> 'Off' AND t1.USER_ID <> '1' and t2.USER_ACCEPT_ADMIN_EMAILS <> 'Off' and t1.USER_ID = t2.USER_ID and t1.USER_ID = t3.USER_ID and t1.USER_ID = t4.USER_ID AND USER_ID NOT IN ('986') and t3.USER_LAST_VISIT_TIME > '1546300799' GROUP BY t1.USER_ID ORDER BY t1.USER_ID ASC - Column 'USER_ID' in where clause is ambiguous
[quote=Daryl Fawcett]When trying to send an email to 24 selected users, I am receiving the following error message:
Script: /home4/maritim5/public_html/forums/admin/dosendemail.php Line#: 191 SQL Error: Column 'USER_ID' in where clause is ambiguous SQL Error #: 1052 Query: SELECT COUNT(*) FROM ubbt_USERS as t1, ubbt_USER_PROFILE as t2, ubbt_USER_DATA as t3, ubbt_USER_GROUPS as t4 WHERE t2.USER_ACCEPT_ADMIN_EMAILS <> 'Off' AND t1.USER_ID <> '1' and t2.USER_ACCEPT_ADMIN_EMAILS <> 'Off' and t1.USER_ID = t2.USER_ID and t1.USER_ID = t3.USER_ID and t1.USER_ID = t4.USER_ID AND USER_ID NOT IN ('986') and t3.USER_LAST_VISIT_TIME > '1546300799' GROUP BY t1.USER_ID ORDER BY t1.USER_ID ASC
Changelog 2019-06-16 [FIX] MySQL 5.7+ fixes to correctly handle GROUP BY clauses. This is a code fix, not a band-aid patch, such as reconfiguring your SQL MODE settings to add "TRADITIONAL" or removing "ONLY_FULL_GROUP_BY" from it.
BTW, Are you aware that you can edit your posts. You dont need to reply to yourself over and over again. 50 of the 70 posts in this thread are by you, just replying to yourself.
