cityjohn

I have to dissapoint you, we’ve been changing a lot on the website and I can’t tell you exactly how to replicate it. The redirect is currently done by:

add_action('check_admin_referer', 'scratchcode_logout_without_confirm', 10, 2);
function scratchcode_logout_without_confirm($action, $result){
    /**
    * Allow logout without confirmation
    */
    if ($action == "log-out" && !isset($_GET['_wpnonce'])):
        $redirectUrl = 'https://website.nl/'; 
        wp_redirect( str_replace( '&', '&', wp_logout_url( $redirectUrl.'?logout=true' ) ) );
        exit;
    endif;
}

Which now seems to work but I can still reach the page if I go to website/login. I changed the standard links with a plugin called hide-my-WP. Can I disable this redirect somewhere in Customizer? Because no matter what why would I want people to see an empty login customizer page… In hide-my-WP an option is set to show a 404 page when people try to reach /login.

I do have the full version and it stored its tables using no prefix under ‘wpdatatables_#’ which I thought was very odd. It’s worth noting that my actual prefix is wpD. Just wanted to let you guys know.

Wait no that’s not correct, I have a plugin called WPdatatables that makes its own tables without a the wpD prefix and simple uses wp.

Hmm I got this error:

“The storage engine for the table doesn’t support r…”

I don’t know if it matters but I have only 2 registered admins.

(I wanted to change the prefix because I’m building an application on top of wordpress and I need my own tables so I wanted to clean up the messy prefix.)

Thanks! I figure there is no difference between showing the shortcodes and the pages. One huge problem was that Elementor would not load the pages.

If I remove modal popup and filterable gallery it works…

Hey Peter,

Thanks for getting back to me faster than anyone before, really sorry I wasn’t able to return the favor haha. After dropping the index I still got this error:

The following ALTER TABLE statement failed
ALTER TABLE <code>startracker_tutors</code> MODIFY COLUMN <code>ID</code> int(10) NOT NULL AUTO_INCREMENT;
ALTER TABLE <code>startracker_tutors</code> ADD PRIMARY KEY (<code>ID</code>);
Incorrect table definition; there can be only one auto column and it must be defined as a key

While trying to make it a primary key.

If I take out the “auto_increment” to first make the ID column a Key it returns this error:

The following ALTER TABLE statement failed
ALTER TABLE <code>startracker_tutors</code> MODIFY COLUMN <code>ID</code> int(10) NOT NULL;
ALTER TABLE <code>startracker_tutors</code> ADD PRIMARY KEY (<code>ID</code>);
Duplicate entry '0' for key 'PRIMARY'

Currently no column is set as ‘Key’ and I’m not able to set one, so I’m taking your advice and rebuilding the entire table.

Since I’m building a tutor-pupil tracking database I’m taking my time to design it properly and preempt any future needs that may arise, therefor I’ve installed Microsoft Access to create the outline first and then re-create it in wpda. I don’t suppose it’s possible to use a mysql client in combination with wpda publisher?

I’m also looking for whether I can merge the wp-user table with my users table and allow users to manage their own contact details. This would eliminate the need for users to be added by an administrator. But I’m not quite sure if this is a good idea.

Thanks so much for the plugin man, learned a ton!