rubenvl

@baned thanks

It’s quite troublesome for us to change the field since we use BI later to calculate some lead rating according to all form questions and changing this will obligate us to change our code.

Anyway thanks for the procedure, I will try it in the future, once Im ready to update our BI system too.

Thx!

Hi.

Some update on this ? I have the same issue.

Without IPN: I don’t see the payment reflected.
With IPN: Paypal does not accept the request.

thanks.

Alex,

that is the error i was getting until I tried what I said in my former message.

jchambo.

that fixed up to us also. thank you so much !

DC=domainname,DC=local

no OU.

Marco,

Great, as always! This version works fine !!!!

THANK YOU !!! BEDANKT !!! XIEXIE!!!

Hi Marco,

MySQL Version:5.5.35-0ubuntu0.12.04.2

No other issues detected before. It′s a zpanel installation I gave u access once time ago.

Regards,
Ruben

Hi Marco,

I have downloaded and installed the plugin again, but during the installation and the plugin, as well that when puting the database information, I got many errors. I also see the interfice quite strange.

Errors:

Warning: extract() expects parameter 1 to be array, boolean given in /wp-content/plugins/key4ce-osticket-bridge/ost-bridge.php on line 98

Warning: extract() expects parameter 1 to be array, boolean given in /wp-content/plugins/key4ce-osticket-bridge/ost-bridge.php on line 109

Warning: extract() expects parameter 1 to be array, boolean given in /wp-content/plugins/key4ce-osticket-bridge/admin/ost-config.php on line 96

WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ”ost_ticket__cdata'( ticket_id int(11) unsigned NOT NULL DEFAULT ‘0’, subj’ at line 1]
CREATE TABLE IF NOT EXISTS ‘ost_ticket__cdata'( ticket_id int(11) unsigned NOT NULL DEFAULT ‘0’, subject mediumtext, priority mediumtext, priority_id bigint(20) DEFAULT NULL, PRIMARY KEY (ticket_id) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

WordPress database error: [Unknown column ‘priority_id’ in ‘field list’]
INSERT INTO ost_ticket__cdata (ticket_id,subject,priority,priority_id) VALUES (‘1’, ‘osTicket Installed!’, ‘Normal’, ‘2’)

I have checked the option of 1.9.4 or above, which is my OST installation.

The first two errors appeared during the installation, before I was able to put any information.

Thanks for your help!

Ok, I had the same problem here. I will wait for this update.

Thanks Marco ! ??

I was in Beijing. Now I’m back in Barcelona but looking again for a job back in China ??

With /%category%/%postname%/ or /%postname%/ it does not work for me (same problem as yesterday, empty page). Just the default system “?p=123” loads the page.

Also I was trying now changing manually the url address with the default system to try different things, and many of them are not working, such:
– When I create a ticket this gets registered in osticket but without name, mail.
– When i want to see a ticket it says that the ticket does not exist
– etc…

I suppose it’s all related with the hardcoded links. But at least looks like we find the error.

Feel free to use the test environment I’ve created, since it’s a clean install of the both systems. Just tell me where I can send you the passwords if you need it.

Thanks.

Rubén.

Funny! I also moved to China after NL! hahaha

I found it !! I was preparing a full test environment for you and I found where the problem comes. When in permalinks I use the default system it works, when I switch to the postname one, it does not work.

Happens the same with a clear new installation of osticket and wp with the standard theme.

And if I use the default permalink system, I can see the ticket list, but when I click to a create new ticket, it goes to the home page.

Just tell me some private way I can send you all the users and passwords (wp, ftp, oscticket…) and you can try whatever you need.

XieXie!

Dank u wel!! (I think you’re from NL, I’ve lived in Amsterdam for a year)

I’m just trying the performance of WP with OsTicket in a test environment for another project but I just think that this also can happen to other users with other themes, so maybe it’s useful for you to know it.

tot ziens!

No.

In off-line mode there is no error.

So, it’s a theme problem, right ?

Just something that can be relevant.

If I go to your plugin settings, and I put it “offline”, the message works on the webpage:

Thank you for your interest in contacting us.

Our system is currently offline for maintenance, please check back later.

It shows the message well in the right part, so the shortcode is working.

But if I put it on again: nothing appears.

Hi,

I don’t know if its related, but in debug mode I can see this error in the page of the shortcode:

Warning: Cannot modify header information – headers already sent by (output started at /wp-content/plugins/sitepress-multilingual-cms/inc/language-switcher.php:791) in /wp-includes/pluggable.php on line 1121

Just thinking that can be related with WPML I deactivate the WPML plugin, but anyway I get this error:

Warning: Cannot modify header information – headers already sent by (output started at /wp-includes/class.wp-scripts.php:144) in /wp-includes/pluggable.php on line 1121

If it’s something pure of the theme I’m using, don’t worry, I will work on it. I was just worried that the problem is related with your plugin, since other plugins like woocommerce that also use shortcodes are working fine.

Thanks.

Hi!

Cache:

I’ve no cache activated. Anyway just in case I installed a plugin to clear cache and it was empty.:
WP-Cache (0KB)

0 Cached Pages
0 Expired Pages
WP-Super-Cache (0KB)

0 Cached Pages
0 Expired Pages

The way you create the page is by using the ost-Config? (you can enter the landing page name there –> it will create the page for you).
Yes. I did it this way.
Also, just in case, I’ve created a second page and put the shortcode, same result (not loading).

As far as where you put the actual OSTicket system it doesn’t matter where it’s put (can be anywhere) aslong as the DB settings are properly filled.
Fine! anyway I don’t think the problem is there, because in my wp-admin panel I can see the tickets of osticket.

Thanks.