[stevland]

Did that work? It’s been a couple of weeks so I will mark this as resolved, but feel free to post an update at any time.

[stevland]

After updating the plugin, did you clear Safari’s browser cache?

Unfortunately I do not have access to a Mac right now, so I can’t test MacOS Safari.

But I did try it on an iPhone and a PDF did preview in iOS Safari, although the preview sometimes did not load right away until I refreshed the page.

If clearing Safari’s cache doesn’t help, try the SHIFT + O keyboard combination to view the same ticket in vanilla osTicket. Does the PDF preview display as expected over there?

(BTW I highly recommend using Chrome on MacOS anyway. I think it is a crime that Apple keep promoting Safari. Either they should accelerate its development, or they should abandon it. But that’s my personal opinion, ymmv)

[stevland]

Obviously there isn’t anything I can do to help you right now.

I know I said this:

Search this forum for the terms ‘white’ and ‘blank’. I know this type of thing has come up once or twice in the past.

But I also searched the forum and the incidents I was thinking of where totally different and unrelated to your issue.

So to answer your question: “Has this been reported elsewhere?”  Sorry, no.

It seems to me that you must be doing something wrong during the installation process.

My advice is to create a copy of your current database, install 1.15.x in a different directory and using the copied db, and let it upgrade the db.

That way you can have a testing installation while keeping your production installation running.

Then fill out the Assistance Request Form again with the info on your testing installation and I will take a look (section 3 of the form would be really helpful, if possible, so that I can look at your error logs as you did not report back on that when I asked).

I will mark this resolved for now but feel free to report back at any time.

[stevland]

Hi Oliver,

This is a great idea. It will be added in all future 1.15.x releases.

In the meantime you can open /osta/js/mousetrap.js, add the following…

// shift + e
Mousetrap.bind('shift+e', function(e) {

var loc = location.href;
loc += loc.indexOf("?") === -1 ? "?" : "&";
location.href = loc + '&a=edit';

});

…and then have at ‘er.

[stevland]

Sorry for the late reply.

Please fill out this form (at least sections 1 and 2) and I will take a look.

[stevland]

I’m very surprised that anyone who is running a recent release is seeing this issue.

But here is a nuclear fix.

Copy / paste the following to Admin Panel > Theme > Custom CSS:

.Icon.apiTicket {
background: none;
margin-left: 0;
}
a.Icon.apiTicket.preview {
margin: 0 0 0 12px;
margin: 0;
}
a.Icon.apiTicket.preview b {
font-weight: normal;
font-size: 10px;
font-family: 'Open Sans', sans-serif;
}
table.list.queue.tickets a.Icon.apiTicket.preview {
font-weight: 400;
border: .5px solid #128dbe;
border-radius: 2px;
padding: 2px 3px 2px 3px;
background: #ffffff7a;
margin: 0;
font-size: 10px;
}

If it doesn’t work, let me know!

[stevland]

Thank you for the report.

Please replace <span style="color: #008000;">/include/plugins/attachment_preview.phar</span> with this version.

You may need to then go to Admin Panel > Manage > Plugins and re-enable the Attachment Inline Plugin.

But either way, after that you should be good-to-go.

[stevland]

Hmmm. Please try clearing your browser cache.

If that doesn’t fix this glitch, let me know.

[stevland]

Hi @NIcholasjansen,

Just a quick note to let you know that I have received your form submission and I will look into this soon.

[stevland]

Hi guys, 

Please see this for the cause and a couple of solutions:

https://osticketawesome.com/forums/topic/footer-showing-text/

[stevland]

Thank you for the report, @Shimo. We are looking into this.

[stevland]

Thank you for sharing this, @james!

[stevland]

Oh, that’s weird.

It is definitely not happening on this end, at least in Chrome. I don’t have access to Safari at the moment, but I’ll check later.

Let’s make sure I am understanding you correctly. You are on the Ticket Queue page, you click to go into a Ticket View page, and then use the browser’s back button to go back to the Ticket View page…. is that right?

And are you eventually able to make the extra arrows go away. If so, how? For example, do they go away when you clear the browser’s cache?

[stevland]

I am not seeing that on this end. Can you please send a screenshot?

[stevland]

Hmmm I can’t reproduce that on my end.

What happens when you switch over to vanilla osTicket (by pressing SHIFT + O)?

Are the fields populated over there?