Search options (Page 1 of 39)

I've updated the patch (see here for details) to include the fix for the Open Graph tags scheme (http:// vs https://).

Digging into the Showkase source, it looks like the Open Graph tags use hard-coded "http://" paths.
This is not ideal by any means but it should be easy to change them to "https://".
Change "http://" to "https://" for the og:url and og:image entries in the following files:

• _themes\base\pagetypes\basetheme.tpl

• _themes\manager\pagetypes\juicebox.tpl

• _themes\maribo\pagetypes\simpleviewer.tpl

• _themes\base\pagetypes\simpleviewer.tpl

Don't forget to re-publish your site after making the changes.
I'll see if I can figure out a way to get Showkase to use the current protocol rather than hard-coding "http://" (disclaimer: I'm not the author of Showkase) but, in the meantime, this might hopefully be a suitable workaround.

That's really good to hear. Thank you for letting me know. I hope things run smoothly for you from now on.
However, if you run into any further difficulties, just post back in the forum and I'll do my best to help you out.

I don't think you're missing anything. If you are missing something, I'm missing it, too.

I've just used your modified ckeditorconfig.js file in my test site (Showkase-Pro v1.7.6 with latest patch) and the attribute is added to the <iframe> code each time the site is published (and my test YouTube video is displayed in the site).

The one thing I find to be odd is when you say "When I go back to Showkase, remove the sandbox references and re-publish, it does show correctly.".
With the new code in place (at the foot of the ckeditorconfig.js file), each time you publish the site, the editor will add the sandbox="allow-scripts allow-same-origin" attribute to all iframes.

• If an iframe has no sandbox attribute, publishing should ensure that it has the sandbox="allow-scripts allow-same-origin" attribute.

• If an iframe has a pre-existing sandbox attribute with any value (even empty ""), publishing should ensure that the sandbox attribute changes to "allow-scripts allow-same-origin".

Therefore, every time you publish, (even after removing the sandbox attributes), each and every iframe should have the sandbox="allow-scripts allow-same-origin" attribute and the videos should display.
This seems to be working as expected in my test site.

If I can think of anything that might be causing this process to not work in your own site, I'll be sure to post back.

Edit:
If you are able to remove the sandbox attributes by removing them in the editor and republishing (and they don't reappear with the "allow-scripts allow-same-origin" value), then your editor does not seem to working in the same way that mine does.
Maybe try re-applying the patch to make sure your site is using exactly the same files as mine. (Link in this post.) I've updated the patch a couple of times since it was first released and the latest version includes the new sandbox attribute (in the ckeditorconfig.js file) so, after applying the patch, there are no files to manually edit/update.

Thank you for the additional information. I think that might be the root of the problem.
My tests were done on a stock Showkase v1.7.6 installation (without the patch in place).
My patch updates CKEditor (the Showkase editor) and I've done some digging and found the following in the CKEditor changelog:

That's all well and good, in theory, but, as we've discovered, this prevents Vimeo and YouTube videos from displaying.
Here's something to try. Open the showkase/admin/settings/ckeditorconfig.js file (from your patched installation) and add the following to the foot of the file (before the closing };).

config.iframe_attributes = {
    sandbox: 'allow-scripts allow-same-origin'
}

This should add the sandbox="allow-scripts allow-same-origin" attribute to your iframes (instead of sandbox="") allowing your videos to display.
Hopefully this'll fix the problem.

I notice your YouTube embedding code looks like:

<iframe allowfullscreen="" frameborder="0" height="236" sandbox="" src="https://www.youtube.com/embed/xxxxxxxxxxx?rel=0&amp;fs=0" width="420"></iframe>

Having run a quick test, it looks like the video will show up in the page if you remove the sandbox="" attribute.

(Also, your second YouTube embed src attribute has a space immediately after the opening double-quote. I don't think this is actually causing a problem but it shouldn't really be there.)

I'll keep my fingers crossed that removing the sandbox="" attributes resolves your problem.

Just in case this does not work (although it does work in my own test), here is the current YouTube embed code (taken from a video on the YouTube site a couple of minutes ago). You could try using the same format and attributes as this:

<iframe width="560" height="315" src="https://www.youtube.com/embed/xxxxxxxxxxx?si=xxxxxxxxxxxxxxxx" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

(I think the ?si=xxxxxxxxxxxxxxxx query string is a tracking id which can probably be omitted.)

The permissions for 'showkase2' look fine (the leading zeros are OK).
The 777 permissions for '_showkase' should also work (they are less restrictive than 755 so should not be causing a problem).

I do not know why the patch does not work on your original '_showkase' site or why you are unable to set up a new fresh site.
Both should be quick and easy and I guess the answer lies somewhere on your web server.
Maybe you could contact your web host and ask if they have made any changes to your hosting account since you first set up Showkase which might somehow be contributing to your problem.

It's hard to tell from a screenshot if everything is OK or not.
The screenshot shows what looks like a Showkase root folder but some files are missing (apple-touch-icon.png, favicon.ico, index.php, readme.html and any/all page folders) and I'm not sure about the user.php file (I don't think it's part of the Showkase installation... maybe it contains PHP settings for your site).

Please try my suggestion above (try uploading images in a fresh Showkase v1.7.6 installation with patch in place) and let me know how you get on.
Thank you.

Hi.

I'm sorry to hear you are still having trouble.
I've split your posts into a separate thread as it looks like your problem is not exactly the same as the original poster's (or, at the very least, requires more troubleshooting).

Could you please confirm which version of Showkase you applied the patch to? You say you were using v1.7.7 but the latest version is v1.7.6. (The patch should be applied to v1.7.6.)

The dynamic property error you reported was due to a deprecation introduced in PHP 8.2 (which you are currently using) but the patch should completely fix this issue.
There is no 'themes.php' within Showkase (as noted in the error message you reported) but there is a file named 'themeset.php' which does, indeed, contain a problem at line 60 which the patch addresses.
It sounds very much like the patch has not been applied correctly.
I'd recommend you try to apply the patch again (no harm in doing it more than once) and make sure that all pre-existing files are overwritten. (Check the date on the 'themeset.php' file afterwards, specifically, with regard to the error you reported.)
The patch does fix the error you reported so, after successfully applying the patch, if the error still occurs, then maybe your web server employs a method of server-side caching whereby older files are still used for a period of time instead of newly uploaded ones. It might be worth checking in with your web host to ask if they have server-side caching active on your web hosting account (and ask if they can disable it).

For reference, here is the link to the post containing the information about the patch: https://showkase.net/forum/viewtopic.php?pid=2368#p2368
... and here is the post containing more information about applying the patch: https://showkase.net/forum/viewtopic.php?pid=2376#p2376

I hope this points you in the right direction.

Agreed (but I'm not the original author of Showkase and I don't make the decisions around here!).

Please try upgrading your site to the latest version of Showkase v1.7.6.

There was a fix in v1.7.1:

Even if the upload still fails, at least we should now get a description of the error which should hopefully point us in the right direction.

The upload module itself was updated in v1.7.4:

Also, after you have installed v1.7.6, please apply the patch I created as I fixed a couple of upload module problems (caused by PHP 8.1 and PHP 8.2 deprecations) and updated the upload module once again.

You can find instructions to upgrade Showkase here.
I've reactivated your download link and you should receive an email containing the link so that you can download the latest version of Showkase v1.7.6.

The patch I created can be found in this forum post.
More information about applying the patch can be found here.

Hopefully, updating your site to Showkase v1.7.6 + patch will resolve your problem without any further action.
However, if you continue to experience difficulties, please let me know and I'll try to help further.
Thank you.

Note:
Please be sure to make a complete backup of your existing site before upgrading. You should not experience any problems during the upgrade process but it would be wise to have a backup in case anything goes wrong and you need to reinstate your original files at a later date.

The upload module within Showkase is for images only.

You'd need to upload your text document outside Showkase using FTP (or your web hosting account's online file manager) and then provide a link to the file in your page's body content, e.g:

Click <a href="http://www.example.com/files/text_file.docx" download>here</a> to download the document.

When entering HTML code into the Showkase editor, make sure that the editor is in 'Source' mode.