Zenphoto
The simpler media website CMS
ZenphotoThe simpler media website CMS
Forum search only. You might also want to search on the main site's user guide.
Your support helps pay for this server, and helps development of zenphoto. Thank you!
Visit the donations page
Comments
I think the dynamic album way is the best and most flexible. That way you can "pick" the images via a specific tag without having to create duplicates.
The uploaded folder is not really a good way IMHO because it is outside the general management and image processing is way more complicated.
Hi @kuzzzma,
thanks a lot for your answer. In the meantime I finished my work on restructuring my webpage and came to the final design.
Also, now my page has a logo and and favicon.ico.
The second option looks perfect to my. I created myself an auxilary folder, that contains pictures, I use in blogs and docu pages like this one: https://spottair.de/gallery/pages/About-me/ Of course, I don't want those picture to show up in any album. So - your second option would fit best. Would be great if you could enable this option.
Thanks again for your great work.
But if the album is unpublished, it wil not show up for any normal visitor.
@ChristianS
yes, I use images from uploaded folder in the same way - sometimes you need images for pages/blog posts that just make no sense in the main gallery, so I think that option to populate slideshow from uploaded folder can be useful - for example, to create promo-pictures for events or slides akin to presentation, this opens up possibilities..
You can unpublish them so they are not in the "main gallery". Using a specific album has lots of benefits as you have ways to enter titles, descriptions and also ordering them (unless you use a dynamic album of course).
We generally consider the albums as a kind of "media library" and will do so in the future. That just to note ;-)
But of course do as it fits your purpose!
Hi @acrylian,
let's step back for one moment. The paradigm theme is able to show images from every album you select in the setup. Unfortunately, and there is no config option to do different, the theme always shows images aligned top/left. Or lets say, starting at pixel 0. On the other hand, the area, that show the image has a diffenrent ratio, a little bit like 32:9. Therefore, and of course it is because of my motives, the planes are cut, or only parts are shown. Must of the slideshow images will show the sky :-( That does look professional.
Because of that, I created a series of pictures, that can be used by the slide show, to work around that alignment topic. But those pictures are just a few special ones, I want to hide from my gallery. At that moment, I figured out, that images from unpublished folders can't be shown.
At the moment, I help myself here, with burrying down the special folder in my Gallery ;-)
Sure, but what you describe is a matter of the theme and slideshow setup – respectively the CSS setup – and not really if the images are from an album or not. More flexibility you always have with custom made stuff, themes are always a litte general naturally.
Anyways, whatever works for you!
@ChristianS
If presentation is your major concern - it can be easily adjusted via custom CSS rules for the slideshow.
How-to:
In /css folder of Paradigm theme files there is a file "! rename-to-custom.css", it's empty out of the box.
You add custom CSS rules to override current CSS, then rename it to "custom.css" and upload to Paradigm theme /css folder on your server
To adjust height of your slideshow to better suit aspect ratio of your photos you need to specify height for 2 classes:
.carousel-inner {
height: 200px;
}
.carousel-inner > .item {
height: 200px;
}
You might have to play around with actual number for height, to find a right fit.
This file "custom.css" is already linked in the theme and won't be overwritten by future theme updates, so it can be used to completely change theme look and feel.
@kuzzzma: Still the file is in danger on upgrade if FTP clients may overwrite the whole theme folder content on upload. You could implement a "real" custom.css file within and outside the theme easily:
Plain draft is this:
$theme = getCurrentTheme(); $css = SERVERPATH . '/' . THEMEFOLDER . '/' . internalToFilesystem($theme) . '/custom.css'; if (file_exists($css)) { $css = WEBPATH . '/' . THEMEFOLDER . '/' . $theme . '/custom.css'; } else { $css = WEBPATH . '/' . ZENFOLDER . '/' . PLUGIN_FOLDER . '/yourthemename/custom.css'; } // load the custom.css after the standard cssSome plugins use similar but actually we have an simple API for that:
$customcss_filepath = getPlugin('custom.css', true, true); // load the custom.css here after the standard csshttps://docs.zenphoto.org/1.6.2/namespaces/default.html#function_getPlugin
The name
getPlugin()is quite misleading as it actually meansgetPluginFile- just realized that and will rename it with the next release – and refers to any file within a plugin or the current theme (2nd parameter) as themes are technically a special kind of plugin.@acrylian
Paradigm theme has no file "custom.css" amongst distributed files, only "! rename-to-custom.css".
This way if user uploads whole folder with theme upon upgrade, their custom.css won't be affected, they will only upload empty "! rename-to-custom.css" to their css folder and it's not hooked into head section of the theme, only "custom.css" is (with address specific to Paradigm theme).
I consider this way to be pretty safe in regards to potential mistakes.
Still there is the danger of overwriting. My FTP client usually either updates/adds files not existing or overwrites the folder content with all contents.
Anyway, I just guided to the "offiical" way to do this ;-)
A big update to my fork of Paradigm theme: current version is 1.5 .
Link to latest version is always available here: https://www.blog.private-universe.net/web-and-tech/zenphoto-theme-paradigm/
Changes:
Great, you frequently update it. We will update it on our demo. The no indexing of the archive and tags pages I think this should indeed be part of the official html_meta_tags plugin. I will put that on the list therefore.
If I look at the head file I wonder why the theme does what the html_meta_tags plugin actually also does/providees incl OpenGrap and such. As far as I see it does not disable the plugin so you might get things duplicated.
@acrylian
Some of it is just legacy features, as original creator added them, so I keep them too, fixing and updating as I find stuff lacking.
To ensure no duplication occurs, in my installation notes I list stuff that users need to disable/enable if they use html_meta_tags or other plugins.
As far as meta tags go - I've got some ideas for html_meta_tags plugin, will write some suggestions on github, when I get some time.
Okay, I see. You could force disable the plugin, too. But not all meta elements do duplicate as it provides a few more I think.
Me too ;-) I plan to extend it but some of it will depend on some changes planned for later releases only…
PARADIGM ver 1.6
MAJOR WORK on Theme Options
Reworked descriptions for Options.
Cleaned up Contact Form, fixed errors/warnings
Support for Related Items plugin:
Extended Featured Images plugin support:
Support for User Login-Out and Register User plugins.
(?) Added support for Default Codeblocks plugin [work in progress]
Download here:
https://www.blog.private-universe.net/web-and-tech/zenphoto-theme-paradigm/
Demo site with screenshots and theme in action: https://demo.private-universe.net
Paradigm on GitHub + Version 2.0
Compatible with Zenphoto 1.6.3 (official release) and above due to changes to comment_form and contact_form.
I've created a repository for Paradigm on GitHub, so users can get snapshots with fixes between releases.
Past releases were added there too, for those who need them.
To coincide, I gave Paradigm a version bump to 2.0 - as I should have done it for v1.6 due to breaking changes to Options.
Changelog:
Links
Download Paradigm on Github: https://github.com/kuz-z-zma/paradigm
Demo site with screenshots and theme in action: https://demo.private-universe.net
Main Theme page was updated with instructions and how-to;
blog post and final package to follow soon.