uncovery

And one more thing: The template HTML that you can add under “Advanced Template Settings” don’t work with the static frontpage.

• This reply was modified 7 years, 2 months ago by uncovery.

Hey there, thanks for the “pointing in the right direction”. While I still need to figure out how to do this, I have to say that the issue at hand here, from my perspective, is a bug.

A plugin that is offering to be a front page for wordpress should – in my opinion – not change that front page’s layout. If a “normal” static page would be at the front, the theme uses the correct template. Only your “virtual” page does not use it.

I have to admit that I am not 100% sure if the bug is in the theme or your plugin, and most likely either author will point at the other, but to me this is a bug that should be fixed.

• This reply was modified 7 years, 2 months ago by uncovery.
• This reply was modified 7 years, 2 months ago by uncovery.

Never mind solved it by upgrading to 2.0 manually, then migrating the data in the admin panel and lastly upgrading to 4.6

Thanks a lot for the kind review!
I am working on the next version already, hope it will be ready soon!

Marked as resolved now

nevermind. I forgot that I also have to update the version number in the main .php file header.

Thanks a lot, this is very helpful!

Here is the diff for the respective code:

https://github.com/uncovery/wpsc-support-tickets/commit/da2f64a91541460dfaafe03846cb0cbe585d259d

You can also just download the final file and diff it locally:

https://github.com/uncovery/wpsc-support-tickets/blob/da2f64a91541460dfaafe03846cb0cbe585d259d/wpsc-support-tickets.php

Thanks a lot for fixing those things and you open & honest answer. I am glad to help a bit with the code style and even add some more improvements if you are willing to accept pull requests:

I already tried to do some heavy cleaning work on the custom fields code:

https://github.com/uncovery/wpsc-support-tickets/commit/da2f64a91541460dfaafe03846cb0cbe585d259d

You can try out this version I made
https://github.com/uncovery/wpsc-support-tickets

i have fixed that problem and provided a pull-request:

https://github.com/wp-plugins/wpsc-support-tickets/pull/2

You can also download a complete version here:

https://github.com/uncovery/wpsc-support-tickets

Please tell me if it worked.

Fixed this and others in pull request:

https://github.com/wp-plugins/wpsc-support-tickets/pull/2

I found the issue: you have a incoherent permission naming. Sometimes its called

manage_wpsc_support_tickets

and sometimes

manage_wpsct_support_tickets

This messes all permissions and user roles up.

If I look at the tables, the last reply submitted by an admin has the timestamp 1391604588, but the last staff reply is timestamped at 1391575788, which is not in any of the replies listed as a timestamp.

The user is a site administrator.

I added a

session_start();

on line 16 of the bt.php file. This is a bug since the bridge does not only require you to have sessions enabled but also auto-start which is not a default setting on most servers anymore.