Emstatay

Out of the off-line mode – running ok.
The modifications are needed in more than one location. So, message here if you need it …

Anyone interested to review/streamline this plugin?
Anyone still using it?
Happy to hear …

I have added the prefix option to the files (files available if needed).

The result is data in the settings is saved successfully (including status) and corresponds with osTicket. WP backend replies are sent just fine.

However, the front-end page for supportpage always opens in offline-mode.
Anyone have other suggestions …?

Hello!

I tried the plugin (juste used php/css to integrate 1.7 in WP before) and noted that I had an immediate problem because the table prefix is hardcoded (based on default ost_).

I am not that experienced in PHP but was able to modify the config to read my table (still hardcoded).

I would be interested to modify – update this PI since the website of the original DEV is down … should we fork this? Did you have anyone interested in this plugin and your extensive modifications?

Hello Everyone!

I had the same symptoms today. (1st try with the plugin).
The answer seems simple. The plugin has a hard-coded DB prefix of ost_ (assuming the default installation of osticket. Most auto installers will create or offer a different prefix for the tables.

FIX:
1) look at your installation (either PhpMyAdmin or the config of osTicket) and find your table prefix.
2) open /wp-content/plugins/osticket-wp-bridge/admin/db-setting-18.php

3) EDIT the following block

~
$config = get_option(‘os_ticket_config’);
extract($config);
$ost_wpdb = new wpdb($username, $password, $database, $host);
global $ost;
$config_table= “CHANGE: ost_ _config”;
$dept_table= “CHANGE: ost_ _department”;
$topic_table= “CHANGE: ost_ _help_topic”;
$email_temp_table= “CHANGE: ost_ _email_template”;
$ticket_table= “CHANGE: ost_ _ticket”;
$ticket_event_table= “CHANGE: ost_ _ticket_event”;
$thread_table= “CHANGE: ost_ _ticket_thread”;
$priority_table= “CHANGE: ost_ _ticket_priority”;
$ticket_cdata= “CHANGE: ost_ _ticket__cdata”;
$staff_table= “CHANGE: ost_ _staff”;
$ost_user= “CHANGE: ost_ _user”;
$ost_useremail= “CHANGE: ost_ _user_email”;
$directory=$config[‘supportpage’];
$dirname = strtolower($directory);
$version=$config[‘version’];
$category=@$_GET[‘cat’];
$status_opt=@$_GET[‘status’];
$ticket=@$_GET[‘ticket’];
~

Off course a permanent fix would be to add a variable for the prefix … ??
I am still looking to solve the “offline” page problem.
Seems the developer is “off-line” (his Hostgator expired …)
Anyone else needs this fixed?

Greets!

Hello Handoko:

why the need to remove and leave other entries in your DB?
Use the above instructions to login to your site – then REMOVE the plugin from within WP if you really do not want it. CLEAN REMOVAL!

Yes, I admit that I got myself logged out. However looking at the log of my site and the high number of:
a) attempted logins with admin (and other combinations)
b) attempted page loads of default WP page names with scripts
I WILL LEAVE the modifications made by this plugin for a while because I think there are ACTUAL attempts to get into my site which have been reduced to nothing but a 404 record! So the trouble of getting back in – I confider it a MINOR problem compared to the number of login attempt.

Therefore, please note that my suggestions above simply allow you “back-in” to your site and you may decide what to do with the plugin [orderly removal possible!]

nothing more … greets … Tatay

Hello (shawn00m & others):

I had the same problem. I could have caused it myself (in the MySQL back-end) or something else happened. I use KeePass to keep complicated passwords and the login URL and I just got 404 – no login page.

So I opened the htaccess file in the root directory of my site with a text editor (on-line or FTP – makes no difference).
IF you enabled blacklisting you may have many URLs at the top of that file. E.g.
# BEGIN Better WP Security
# Begin HackRepair.com Blacklist
RewriteEngine on
# Abuse Agent Blocking
RewriteCond %{HTTP_USER_AGENT} ^BlackWidow [NC,OR]

etc. – scroll down to the end.

LOOK FOR
RewriteRule ^open/?$ /wp-login.php?RandomString4urSite [R,L]

In your browser PASTE:
https://www.yourdomain.tld/wp-login.php?RandomString4urSite

You should be at your WP login-screen

Hope you had the same problem and this fixed it …
You just saved $40 in support (plus my $40 = nice dinner)

wishing you success with your fix …

Greets, Emstatay