Entries will not save

Resolved cressr
(@cressr)

7 years, 8 months ago

Hi,
I have used this plug in on other sites without any issues, however on a new site I have an issue that no entries will save, either on the front or back end. Tries disabling all other plugins and changing themes, including using the WP 2017, but nothing worked.
The test under settings also failed, results below.

Standard test: Failed.
Emoji test: Failed.
Test
This test will attempt to save two test entries, one with standard text and one with Emoji.

WordPress version: 4.9.8 (db: 38590)
WordPress theme: SG Circus
Active plugins: Array ( [0] => contact-form-7/wp-contact-form-7.php [1] => donation-button/donation-button.php [2] => duplicate-post/duplicate-post.php [3] => google-maps-widget/google-maps-widget.php [4] => gtranslate/gtranslate.php [5] => gwolle-gb/gwolle-gb.php [6] => maintenance/maintenance.php [7] => paypal-donations/paypal-donations.php [8] => pets/pets.php [9] => rename-wp-login/rename-wp-login.php [10] => simple-event-planner/simple-event-planner.php [11] => wp-super-cache/wp-cache.php )
PHP Version: 7.1.5
MySQL Version: 10.1.32-MariaDB
MySQL Charset: MySQL Charset: utf8mb4
MySQL / MySQLi: mysqli
MySQL variables: Array ( [character_set_client] => utf8mb4 [character_set_connection] => utf8mb4 [character_set_database] => utf8 [character_set_filesystem] => binary [character_set_results] => utf8mb4 [character_set_server] => latin1 [character_set_system] => utf8 [character_sets_dir] => /usr/local/mariadb/10.1.32/share/charsets/ )

The page I need help with: [log in to see the link]

Viewing 13 replies - 1 through 13 (of 13 total)

Plugin Author Marcel Pol
(@mpol)

7 years, 8 months ago

Sometimes this hapens but it is not always clear why.
If you run the uninstall function in the settings of the plugin, and activate the plugin again, does it work?

You an check the database tables, there should be a wp_gwolle_gb_entries and a wp_gwolle_gb_log table.

In the past there was a report from a user that used hosting through Azure, which doesn’t support myIsam database collation. Could that be the case?

Thread Starter cressr
(@cressr)

7 years, 8 months ago

Tried that, no difference. I am not hosting this site myself, I’m not sure what server it is on, I’ll check it out and advise.

Thread Starter cressr
(@cressr)

7 years, 8 months ago

OK, the site is hosted on WEDOS, also I have just looked at the database and there are no tables! That’s obviously why it won’t work. Any ideas on what to do?

Plugin Author Marcel Pol
(@mpol)

7 years, 8 months ago

I haven’t heard of WEDOS. If they do not support MyIsam, they should have documentation on that. You could check that.

When you run the SQL query from gwolle-gb/admin/gb-upgrade.php, do you get an error? You can run that in something like PHPmyadmin. When you run it with Innodb instead of myisam, does it work?

Plugin Author Marcel Pol
(@mpol)

7 years, 8 months ago

I see they support myISAM, so that is not it.

They have utf8 as default, but I think the tables are made with that, and only upgraded to utf8mb4 afterwards.

Thread Starter cressr
(@cressr)

7 years, 8 months ago

Could I create the tables manually, if so what would the structure be?

Plugin Author Marcel Pol
(@mpol)

7 years, 8 months ago

This is the SQL command:

https://plugins.trac.ww.wp.xz.cn/browser/gwolle-gb/trunk/admin/gb-upgrade.php#L31

Make sure you use the right prefix. Default is wp_

Thread Starter cressr
(@cressr)

7 years, 8 months ago

OK, I have not done this before, so want to check understanding.
In the correct database
1) select SQL query
2) copy and paste the data
3) Does the wp_ go as the delimiter?
Then Go and the tables should be created?

Thread Starter cressr
(@cressr)

7 years, 8 months ago

I tried to run, ignored the delimiter, but got this error message:

Error
There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem

ERROR: Unknown Punctuation String @ 1
STR: <?
SQL: <?php
/*
** This file is used during activation or upgrading from a prior version.
**
** It uses the PHP function version_compare(). Usage:
** version_compare(OLD_VERSION_NUMBER,NEW_VERSION_NUMBER,'<‘)
** => TRUE, if the old version number is smaller than the new one.
*/

// No direct calls to this script
if ( strpos($_SERVER[‘PHP_SELF’], basename(__FILE__) )) {
die(‘No direct calls allowed!’);

SQL query:

<?php /* ** This file is used during activation or upgrading from a prior version. ** ** It uses the PHP function version_compare(). Usage: ** version_compare(OLD_VERSION_NUMBER,NEW_VERSION_NUMBER,'<‘) ** => TRUE, if the old version number is smaller than the new one. */ // No direct calls to this script if ( strpos($_SERVER[‘PHP_SELF’], basename(__FILE__) )) { die(‘No direct calls allowed!’);

MySQL said:

#1064 – You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘<?php
/*
** This file is used during activation or upgrading from a prior ver’ at line 1
Plugin Author Marcel Pol
(@mpol)

7 years, 8 months ago
```
CREATE TABLE
                                wp_gwolle_gb_entries 
                       (
                               id int(10) NOT NULL auto_increment,
                               author_name text NOT NULL,
                               author_id int(5) NOT NULL default '0',
                               author_email text NOT NULL,
                               author_origin text NOT NULL,
                               author_website text NOT NULL,
                               author_ip text NOT NULL,
                               author_host text NOT NULL,
                               content longtext NOT NULL,
                               datetime bigint(8) UNSIGNED NOT NULL,
                               ischecked tinyint(1) NOT NULL,
                               checkedby int(5) NOT NULL,
                               istrash varchar(1) NOT NULL default '0',
                               isspam varchar(1) NOT NULL default '0',
                               admin_reply longtext NOT NULL,
                               admin_reply_uid int(5) NOT NULL default '0',
                               book_id int(5) NOT NULL default '1',
                               PRIMARY KEY  (id)
                      ) ENGINE=MyISAM CHARACTER SET utf8 COLLATE utf8_general_ci;
```
Just the SQL code 🙂
Try this (untested).
- This reply was modified 7 years, 8 months ago by Marcel Pol.
Plugin Author Marcel Pol
(@mpol)

7 years, 8 months ago
```
  CREATE TABLE
                              wp_gwolle_gb_log 
                       (
                               id int(8) NOT NULL auto_increment,
                               subject text NOT NULL,
                               entry_id int(5) NOT NULL,
                               author_id int(5) NOT NULL,
                               datetime bigint(8) UNSIGNED NOT NULL,
                               PRIMARY KEY  (id)
                       ) ENGINE=MyISAM CHARACTER SET utf8 COLLATE utf8_general_ci;
```
And this for the logs.
Thread Starter cressr
(@cressr)

7 years, 8 months ago

OK I have it all working now. It appears that the privileges had not been set up properly by the host, found this after the SQL kept failing.
Thanks for all your help in this, much appreciate it as this is the best plugin for a Guestboook!

Plugin Author Marcel Pol
(@mpol)

7 years, 8 months ago

No problem, maybe I should have asked about that firsthand 🙂 I was thinking too difficult probably.

Good that it works now.

Viewing 13 replies - 1 through 13 (of 13 total)

The topic ‘Entries will not save’ is closed to new replies.