[stevland]

Thanks for your post, @fachmarkt.

I realize now that something is messy with the languages. I am still looking into it and will get back to you. Thank you for your patience.

[stevland]

Sorry for the delay. This sounds like it may be a permissions issue with the files in /osta/css/themes. 

Are you using a Linux-based or an IIS web server?

A quick and dirty workaround for this is to manually add your hex color values to /osta/css/themes/custom.css. 

[stevland]

Sorry @jranshaw, I didn’t see your message right now.

I’m not sure what could be causing this. It may be an osTicket (rather than and osTicket Awesome) glitch, so you may want to try asking in their forums.

But here is something that comes to mind that you can try.

You could try specifically coding your links like so:

<a href="#anchor" target="_self">Anchor Link</a>

This wouldn’t normally be necessary, as _self is always the default. _self tells the browser to open the link in the same window, whereas _blank tells the browser to open the link in a new window (more info).

Perhaps this workaround will override whatever is going on in your FAQ’s. I hope that it does.

[stevland]

Thanks for your detailed report, @aeromarine.

That’s odd. 

My first suggestion would be to try another browser, but it sounds like you already have.

Can you please visit the profile page in Chrome and open Dev Tools > Console and see if there are any errors?

I notice that you are using IIS. Hey @kkrumm… you use IIS as well. Would you kindly check your profile page to see if the button appears on your end?

[stevland]

I see your point, @laroccad.

The color scheme that I’ve used still makes sense to me, and yet I can’t think of any way to justify it. Meanwhile, you have presented a solid case for the red to blue scheme. I see that it is also used in Mexico.

You win. I will update the color scheme at some point. Thanks for the feedback.

[stevland]

Hi Thomas,

osTicket Awesome doesn’t contain any modifications that could be responsible for breaking email piping. However, the fact is that by installing osTicket Awesome you have replaced your osTicket files with new copies.

Therefore, you will likely need to repeat some of the steps that were taken when email piping was first configured on your server.

For example, you will need to set permissions of your /api/pipe.php file to 0755.

I hope this helps.

[stevland]

I’m alive!!!! LOL

Thank you so much for the instructions. I will pass them along to the next IIS user with a permissions issue. IIS is so very different from Apache — I would never have figured out that solution!

[stevland]

Hi guys,

I’m sorry for the delay in responding here.

As you are likely aware, the new version (v1.3) is now available.

district6 thank you for posting your solution. In your case it appears that you must have uploaded the files as another user (perhaps root?), thus the permissions issue.

It is worth mentioning to anyone else who is reading this that the chown -R command that fixes this problem will need to be tailored specifically to each person’s website username and file path to their osTicket installation.

City of Alton did you manage to correct the permissions issue on your IIS server? If you did, I would be very curious to know how you managed to do so! I do not have any experience with IIS. I actually rented an IIS server recently and tried to figure out how to work with permissions, but I failed to learn anything new. 🙁

I’m sorry but osTicket Awesome has not supported IE since version 1.9.12. There are many reasons for this which have already been discussed in this forum (simply search for ‘IE’). 

[stevland]

 Yes that is a perfectly good workaround. 🙂

[stevland]

Hi newox,

Are you still having this issue? 

If yes, is the Theme page the only page that comes up blank?

If this issue persists I would try reuploading the theme files (you may as well us it as an opportunity to upgrade to the latest version); and then I would make sure that the permissions are all correct and that the owner of /include/staff/theme.inc.php is the same as the owner of the other files in the /include/staff/ directory.

Let me know!

 

[stevland]

Hi Stefan,

I hope that it doesn’t sound like a cop-out, but it is definitely worth mentioning that I doubt that this issue is related to osTicket Awesome.

Assuming that your installation is in a directory called support, if you followed the installation instructions then your original osTicket installation will now be in a directory named support-old.

Please visit your original osTicket installation in your web browser and see what happens if you upload/ download attachments from there.

If the issue persists while you are using the original interface, I would recommend seeking help for this issue in the main osTicket Forums.

But if it does turn out that the issue is specific to your osTicket Awesome installation, do let me know and I will give it some more thought.

[stevland]

Are you still having trouble, m.may?

It appears to me from the /volume1/ bit of your error message that you are using a Windows IIS server. I’m afraid that my knowledge of Windows servers is very limited. It does appear that you are having permissions issues. I would try uploading the update again and if the issues persist than focus on permissions.

Another thing to consider: all of files mentioned in the error are unmodified core osTicket files. Therefore, whatever the issue is, I don’t have any reason to believe that it is necessarily related to osTicket Awesome. You may want to keep that in mind if you want to search Google using terms such as ‘osticket’ ‘IIS’ ‘permissions’ etc.

If your trouble persists you should do the following: open your installation in Chrome > open Dev Tools > go to Console tab and then copy/paste any messages into a reply.

[stevland]

Thanks for pointing that out, hogkammen. Doh!

City of Alton‘s tip is exactly correct. Or you can right-click and download this file and upload it to the root directory of your osTicket Awesome installation.

[stevland]

Hi Filippo,

Thank you for your report. I’m not sure how I did not notice this myself. I will look into it.

[stevland]

As I have already stated…

>The top of the System. Logs page is a mess in the demo installation. It is a known issue…

Please stop pointing out the same issue with the demo and making it out to be multiple issues.

You do have multiple issues with your installation, which is very likely because you are trying to run two unrelated themes at the same time.

Maybe you have the very best reason in the world to attempt this. It does not mean that it will work.

The only dependencies that you are missing are

1) a willingness to comprehend and follow instructions
2) the ability to assess facts rationally and
3) the ability to accept the limitations of reality

The next release of osTicket Awesome (v1.3) will not be dramatically different than the current version (v1.2). If you don’t like the Client area now, you won’t like it much better with the new release. 

If you take the opportunity to install the new release according to the instructions, you can eliminate all of the issues that you currently have with your installation. If you try to combine two unreleased themes again, however, you can expect similar results.