I thought using Finder in OS X would allow me to view the path but it seems Cyberduck is truly needed.
Currently I have some issues with it actually showing any content in TV/Movies/Music..
I can get the categories, but whenever I click one I get "Please Wait" and then nothing happens.
Any help will be appreciated :)
Apparently you have modified your post since KnightOrc replied to it.
I will first address your original problem, as I have no clue to what you mean by the new post content. (What does 'Cyberduck' have to do with anything?)
Judging from the file list you linked to in your original post I believe that you were merely inspecting the SMB fileshares of RasPlex, rather than the real filesystem content as seen locally in the RPi itself. The SMB fileshares do NOT originally include the folder structure needed to access the custom skin location at "/storage/.plexht/addons/", and even if you use RPi command line through SSH, you need to realize that ".plexht" is a hidden folder (set so by the initial period in its name) so you'll need to use extra parameters to the "ls" command to list it inside "/storage".
Personally I prefer to fix this access problem by adding the "/storage/.plexht" folder as a new SMB fileshare, so I can access it conveniently.
This can easily be done without any commandline usage as follows:
01: Use your normal fileshare browser (OSX Finder I guess), to get the same folder list you posted earlier (in your original post).
02: Also open another file browser window to any local folder on your computer (another Finder window I guess).
03: In this listing window, open the share named "Configfiles".
04: Drag-drop the file named "samba.conf.sample" from the RPi window to your local folder window.
05: In the local folder window, rename that file to "samba.conf.txt".
06: Double-click the renamed file to open it in your normal text editor.
07: In this text note that definition blocks have headers enveloped in square brackets like: "[global]"
08: Skip past the [global] block (as it has special purposes) to reach one of the others that follow it.
09: At the start of the first next header, insert the following text block:
path = /storage/.plexht
available = yes
browsable = yes
public = yes
writable = yes
root preexec = mkdir -p /storage/.plexht
NB: The header text in the brackets is what will be visible as the fileshare name. You can change it, but I like that form as it sorts the name to the top in most cases.
10: After inserting the text block above (not removing any original content but just inserting it), save the modified text file and exit from the editor.
11: Rename the edited text file so that its new name is just "samba.conf"
12: Drag-drop the new "samba.conf" file back to the RPi Finder window (assuming it still shows contents of "Configfiles" folder).
NB: That RPi folder will now have both "samba.conf.sample" and the new "samba.conf" which overrides the former.
13: Close the RPi Finder window.
14: Go to the RPi and use the side menu to restart it.
15: After full restart of RPi, go to the OSX system again.
16: Open a new Finder window to the RPi, which should now include the fileshare named "-_storage_plexht", which accesses the real "/storage/.plexht" folder.
17: If you open that folder you should see the "addons" subfolder, inside which you can place your custom PHT skins.
NB: If you save the edited "samba.conf" file you can reuse it for future RasPlex installs.
For those future installs you simply use the same guide as above, but go directly from step 02 to step 12.
Similar methods can be used for accessing most RasPlex folders from GUI filebrowser windows in any OS capable of using SMB fileshares.
I do it mostly from Windows, though it works equally well from OSX or Linux.
There is one exception though, in that some OpenELEC/RasPlex files/folders are write-protected.
Modifying those will require commandline methods through SSH protocol.
----- Now as to the new content of your post -----
If it's true as you say that your RasPlex can not show any content at all in TV/Movies etc, then I think the installation must be botched and you need to start over.
I'm not sure if you've succeeded in installing any custom skins yet, but faulty skin installation could very well lead to non-working results.
There are lots of skins around that will not work at all with current PHT, some of them even crashing the program directly on launch.
Best regards: dlanor