The site is running on and OLD version of MySQL and an older version of PHP, but new enough for the WordFence plugin. But again, if I activate it, the site breaks.
]]>In the PHP file, I save the data in the database, but in WordPress, it displays as a question mark.
$mysqli = new mysqli(DB_SERVER, DB_USERNAME, DB_PASSWORD, DB_DATABASE);
$mysqli->set_charset("utf8mb4");
$sql = "INSERT INTO wp_st_room_availability (post_id,check_in,check_out,number,post_type,adult_dbl_price,adult_price,child_price,child_nb_price,infant_price,extra_bed_price,status,priority,number_booked,parent_id,allow_full_day,number_end,booking_period,is_base,adult_number,child_number,room_price_modified,modified_by)
VALUES ('$_room_id', '$_stamp', '$_stamp', '$_room_stock', 'hotel_room', '$_room_dbl_c', '$_room_sgl_c', '$_room_chdwb_c', '$_room_chdnb_c', '$_room_infant_c', '$_room_tpl_c', '$_status', NULL, 0, '$_hotel_id', 'on', NULL, 0, 0, 1, 0, NOW(), '$_modifier_name')";
$result = $mysqli->query($sql);The data stored in the database through WordPress is also read as unintelligible characters when read by this PHP file.
ù??§ù… ú??§?±úˉ?2?§?±
Searching the internet, I found out that the problem is in the charset. In the wp-config.php file, the value
define( 'DB_CHARSET', 'latin1' ); is set.
This WordPress site uses the Traveler theme, and I don’t know how to find out what charset it uses.
I tried utf-8, utf8mb4 and latin1 in my PHP file, but the problem was not solved.
I will be grateful if you help me to find the problem and solve it.
]]>I am having issues with my server overloading. I have been asked to check out my mySQL database for autoload issues.
I have about 11 records for stm_ccb_form_settings_UNIQUEID all set to autoload. No matter what me setting this to “no” another record appears.
How can I stop this from autoloading please? I do not have the strong testimonial form on the front end of my website – Only admin can add testimonials.
Please advise asap
]]>I plan a project based on wpDataTables and would like to know about pros, contras and known limitations with using of remote MySQL over PostgreSQL as separate db/data sources.
Searching in your forum I found only a limited set of threads, without needed informations.
With “known limitations” I mean things like a need of pgsql driver for PostgreSQL connection, which usually isn’t a part of standard WordPress host setup and needs a root server.
I just want to verify that the actionscheduler plugin handles group replication in MySQL correctly? It seems like that wp_actionscheduler_actions is not created correctly and I just wonder if the primary keys are created correctly for that table?
]]>da dieses Plugin nicht mit Litespeed kompatibel ist, musste ich es wieder entfernen. Leider werden die Daten in der Datenbank nicht automatisch entfernt und nun muss ich alles durchsuchen. Sehr umst?ndlich. K?nnte man verbessern.
BG
guckmada
]]>The client has complained about the speed of the website, the live website is https://victoriancornice.co.uk/ but I have a replica of the website setup as a staging website that I am working on for debugging.
The staging website that is on the same server seems to be running quicker than the live website, not sure why.
I have checked the logs on the server and keep coming across the following error which I believe could be a major part of the website being slow.
PHP Fatal error: Uncaught RuntimeException: Unable to release actions from claim id 0. in /wordpress/plugins/woocommerce/9.3.1/packages/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php:1042 Stack trace: #0 /wordpress/plugins/woocommerce/9.3.1/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(406): ActionScheduler_DBStore->release_claim(Object(ActionScheduler_ActionClaim)) #1 /wordpress/plugins/woocommerce/9.3.1/packages/action-scheduler/classes/ActionScheduler_FatalErrorMonitor.php(52): ActionScheduler_HybridStore->release_claim(Object(ActionScheduler_ActionClaim)) #2 /wordpress/core/6.6.2/wp-includes/class-wp-hook.php(324): ActionScheduler_FatalErrorMonitor->handle_unexpected_shutdown('') #3 /wordpress/core/6.6.2/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #4 /wordpress/core/6.6.2/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #5 /wordpress/core/6.6.2/wp-includes/load.php(1280): do_action('shutdown') #6 [internal function]: shutdown_action_hook() #7 {main} thrown in /wordpress/plugins/woocommerce/9.3.1/packages/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 1042
Let me know if there is anything else I can provide to assist.
Thank you,
Javed