[stevland]

I have to acknowledge that I hear of this type of issue from time to time, which I find perplexing.

It has never occurred to me that it could be an issue with the process of downloading rather than the file itself.

I’m glad you worked it out, and thanks for sharing how you solved the issue.

[stevland]

Hi @Code54,

Thanks for letting me off the hook. I was already working on this workaround, so I decided to finish it.

You can add the following code to /osta/user-styles.css:

/* Client Portal and Staff Panel */
#header-image img {
display: none !important;
}
#header-image:after {
content: ' ';
display: inline-block;
background: url(https://osticketawesome.com/a/1.12.3-1/osta/uploads/google-white.png); /* change path */
background-size: cover;
height: 34px; /*do not change this value*/
width: 105px; /* adjust this value until the logo looks good*/
}

/*Staff Login page*/
#login-title #header-image img {
display: none !important;
}
#loginBox #header-image:after {
content: ' ';
display: inline-block;
background: url(https://osticketawesome.com/a/1.12.3-1/osta/uploads/google-white.png); /* change path */
background-size: cover;
height: 109px; /* adjust this value until the logo looks good*/
width: 332px; /*do not change this value*/
}

After you add that code your logo will be replaced with a Google logo from my server.

You can then change the path to point to your own logo in the /osta/uploads folder, or elsewhere on your server.

—

After getting all of that ready it occurred to me to ask: how did you upload the osTicket Awesome files?

Did you see the following item from the FAQ page?

Will it work on my Synology NAS?

Yes.

One of our users reported having trouble uploading his osTicket Awesome installation using the File Manager. So if you run into trouble while installing, try using an FTP program (such as the free FileZilla) to copy the files over.

[stevland]

I see it still isn’t fixed in 1.12.3, unfortunately. 

I expect it will be fixed by 1.14, if not sooner!

[stevland]

I can do that. I think I know what you want to change, but rather than wasting time composing code when I may be wrong…

why don’t you help me help you by sending me a screenshot of what you want to change? 

[stevland]

Cool I’ll keep that in mind.

[stevland]

Sorry for the delay. I’m not really sure how to proceed with this issue, other than installing from scratch. In my spare time I’ve been looking for a workaround for you. But I’ve also been very distracted. I’ll get back to you soon.

[stevland]

Sí, eso indica que hay una nueva respuesta esperando. Se elimina cuando un agente responde.

[stevland]

I’m guessing that whatever changes I make are getting over ridden by some of your theme css’s

Yes, that is exactly what is happening. 

For that reason (and also because it will be easier to keep track of when updating to a newer version of osTicket Awesome in the future) the recommended file to add all of your custom CSS to is osta/user-styles.css. It is the last style sheet to load so anything declared there will override any other styles.

[stevland]

Actually one thing that does come to mind is a possible ownership issue.

Make sure the uploads/ directory is owned by the correct user*:

# chown -R thecorrectusername uploads

*(On a regular web server I would suggest that the correct user is the same user account that the main website runs under. Of course, this doesn’t really apply to a Synology NAS so I’m not sure what to suggest in this instance).

I hope that this helps! Let me know.

[stevland]

The fact that you have an attachments/ directory tells me that you are using the Attachments on the Filesystem plugin. Not that this makes any difference to the topic at hand; it is just a note.

I’m not sure why you are ending up with write-protected files. I haven’t heard of anyone running into this before. In fact, a search of this forum for the term protected only turns up one result… this post!

So I believe we’ve found your issue. You seem like you know your way around the Linux command line. As you actually have access to your own installation you are in a better position to figure out a solution. But if you want me to do some research and throw out a couple of suggestions, let me know!

[stevland]

/volume1/web/osticket/

[stevland]

What happens if you delete the two broken Custom Logos and try uploading one from scratch?

[stevland]

Whoa, your permissions look dangerously high.

I recommend setting them properly using these commands:

# find . -type d -print0 | xargs -0 chmod 0755# find . -type f -print0 | xargs -0 chmod 0644

Not that I think this will fix your uploading issue, but let’s make sure your installation is secure.

[stevland]

Just to be clear: are you talking about the Client Portal?

[stevland]

Hi @Code54,

Sorry for the delayed response.

Please confirm that a osta/uploads/ directory exists with 755 permissions.

And are your custom logos present within that directory?