Remove Create Ticket Button

Hello,

This is not a feature of the plugin i am afraid.
however you could remove it manually in the templates/nav_bar.php

the “created by osticket” is not added by our plugin it is most likely your (email) templates in osTicket it self.

the Alert emails that our plugin uses are set in the email templates section of our plugin.

We are currently working on improving that section a little by adding the subject field and the admin create email template in the next version.

however they only affect emails send from our plugin not cron mails or anything else. if you disable the create email functionality the only mail still send by our plugin is if you reply as admin or customer (or create a ticket as admin).

Regards,
Marco

Thanks! I managed to remove the “Create Ticket” button from the page you suggested. Thank you!

Not sure if I follow on the email though.

Trying to use the email piping feature of osTicket to create new tickets. I have form setup already that can send the info, just need to know how to send to osTicket to create a new ticket.

not sure if i understand your last question then.
as the way you generally create the ticket is by using the create ticket function in our plugin and/or mail cron.

the aim there is to avoid sending people to osticket website pages it self.

Yes, I would like to bypass ticket creation in plugin.

Only email creation of tickets.

There should be no interaction whatsoever with the osTicket website pages.

Well then everything should already be done?

If you configured osTicket with cron –> our plugin reads tickets from osTicket DB and matches it with your wordpress user/email address

so besides disabling the create button as you done now there’s nothing more to be done

Not sure I follow on cron. I’ve seen a cron setting but wasn’t sure what to do with it. My email is setup for fetching with user info, but still fuzzy on how to make it work.

well, all that is osTicket it self and not related to the bridge plugin in wordpress.

the way how to set the cron job up with your server depends on the type of server, control panel etc.

the information that needs to be configured within osticket it self can be found here:
https://osticket.com/wiki/POP3/IMAP_Setting_Guide

Looking at settings, and see Fetch on Auto Cron.

Fetch Emails using Auto-cron
Enables periodic email fetching using an internal task manager triggered by Agents’ activity.

Please note that emails will not be fetched if no one is logged in to Staff Control Panel. External task scheduler is highly recommended for predictable fetch intervals.

So I have to enable this in addition to enabling fetching on the email itself?

Oh, I see. I’ll have a look at the link you’ve provided.

Okay, I get it. Read through the link, and my host provides a cron scheduler. I have the time interval setup, but I’m still fuzzy on the path:

nobody /path/to/php /path/to/api/cron.php

What am I putting here?

Also, do I still check the “Fetch on Auto Cron” selection in osTicket Admin?

Please forgive if these questions are a bit novice, but I rarely find myself on the backend like this.

unfortunatly i can not tell the path to your cron, that very much depends on the server setup and configuration of where your site is located.

if you don’t know the server path there are some scripts that can tell you where your files is located or simply ask your host what to fill in there.

auto cron if you check the help button is only if your visiting the osticket site and not lets say every 5 – 10 minutes.

if you want it to check 5 – 10 minutes regardless if people are visiting your osticket site the email fetching should be enabled and autocron disabled.

Though questions about osTicket it self can best be asked in the osTicket support forums, we don’t deal much with the osTicket side of settings besides for the few setups we manage our selfs for our own sites.

Thank you very much for your help. Feels like I’m almost there with this one. I appreciate your guidance to the fullest!

Awesome Sauce! Got it to work. Thanks again!!!