Page 1 of 1
Still unsolved: Album 0.9.2 problem
Posted: Sat Aug 18, 2007 11:36 am
by margo
First, I hope you understand me correctly, my English is not very good...
I use CMS Made Simple 1.1 and problematic modules are:
Album 0.9.2
CustomContent 1.4.6
FCKeditorX 1.0.3
1. Module Album problem. How to make and/or assign thumbinails? My procedure for adding new album:
Add an album -> Name: -> Submit -> Add pictures -> Select all (from certain folder) -> Save...
And now what? How do I build thumbinails for those added images? I can see so called thumbinails, but those are actually original size-images, just made smaller by simply using img width/height-attribute...
The following issues are now more ore less OK, but Album problem remains...
2. CustomContent problem. Perhaps not (only) CustomContent is the one to blame... If I understand correctly, when I use tags such as these:
Code: Select all
{if $customcontent_loggedin}
{cms_module module=FrontEndUsers}
{content}
{else}
{cms_module module=FrontEndUsers}
{/if}
Following things should happen:
a) if user is logged in, then the logout form AND the content will be displayed
b) if user is not logged in, then only the login form will be displayed.
But I get very strange behaviour. At first, I managed to log in and see the logout-part, BUT NO content-part...
Then I messed with those tags (put those into the templates, not to content-page) and eventually I managed to create a situation where I'm not logged in, but I still see the content that should be protected.
How to create (minumum) one page, where you have to be logged in to see the content?
Btw... does CMS Made Simple 1.1 has set smarty to cache and how to I disable it???
3. FCKeditorX 1.0.3. I installed FCK, because I don't like TinyMCE. Then I made a change in User Prefrences to use FCK and now I get 404 Not found in that place where FCK should appear:
/modules/FCKeditorX/FCKeditor/editor/fckeditor.html?InstanceName=content_en&Toolbar=Default
I have spent some time with those problems and haven't get anywhere...
Re: Many problems with modules: Album, CustomContent, FCKeditorX
Posted: Sun Aug 19, 2007 5:51 am
by kneehigh
Just had a similar problem today with the comments module always being included regardless of logged in state. I fixed it by using the 'other' syntax for using the module (see the comments for frontendusersmiodule)
try...
{cms_module module=CustomContent}
{cms_module module=FrontEndUsers}
{content}
{cms_module module=FrontEndUsers}
regards
Kim
Re: Many problems with modules: Album, CustomContent, FCKeditorX
Posted: Sun Aug 19, 2007 4:04 pm
by Dr.CSS
FCKEditor may not work in the latest CMSMS 1.1 it hasn't been updated since 12/19/06...
Re: Many problems with modules: Album, CustomContent, FCKeditorX
Posted: Mon Aug 20, 2007 10:28 am
by Deblus
So which editor would you suggest should be used with 1.1 Mark?
Re: Many problems with modules: Album, CustomContent, FCKeditorX
Posted: Mon Aug 20, 2007 2:39 pm
by Dr.CSS
If you don't like tinyMCE that comes with CMSMS 1.1, maybe due to it being basic, you could uninstall it and try the full version of tiny, I quit using fck. a long time ago...
Re: Many problems with modules: Album, CustomContent, FCKeditorX
Posted: Mon Aug 20, 2007 3:14 pm
by margo
kneehigh wrote:
{cms_module module=CustomContent}
{cms_module module=FrontEndUsers}
{content}
{cms_module module=FrontEndUsers}
OK, I hope that solved the most important problem... For now at least it seems to work...
It's a long story why I pref. FCK... Actually I don't like such editors at all, but unfortunatelly I'm not going to maintain this site myself and that's why I need some HTML-editor. So there's no reasonable solution for FCK-problem then? Too bad, but I'll survive
So, that leaves just this album-stuff... what is it that I'm doing wrong there?
Re: Many problems with modules: Album, CustomContent, FCKeditorX
Posted: Mon Aug 20, 2007 3:18 pm
by calguy1000
{if isset($customcontent_loggedin)} would've worked.
Re: Many problems with modules: Album, CustomContent, FCKeditorX
Posted: Tue Aug 21, 2007 8:26 am
by chrisl
Margo I agree with you I don't like or use WYSIWYG editors but they are a necessary evil for inexperienced users.
I install both Tiny and FCK, Tiny because it's lite and FCK because it has, for some users essential standard features such as templates (the most important feature), Word paste and a better image browser although it is relatively easy to put ImageManager on both editors.
Yesterday I installed a system using CMSMS v1.1 and the standard cms FCK module and it worked fine even before modifications. So it maybe some files were not properly installed or omitted from your set up and would suggest uploading again and it may be better to use the zip file rather than the xml and install it manually.
Re: Still unsolved: Album 0.9.2 problem
Posted: Mon Aug 27, 2007 8:30 am
by margo
Up!
I've changed the title and first post to point out, that Album-problem still remains. FE/CustomContent problem works now with those HTML comment-tags, but calguy1000 version didn't work also... And I've changed the editor to XStandard

Hope it provides enough functions

Re: Still unsolved: Album 0.9.2 problem
Posted: Mon Aug 27, 2007 4:16 pm
by Dr.CSS
The first time you look at images to use in an album do you notice the images have a blank spot then it starts showing images, blink, blink, they show up, this is album making thumbs out of images, if you go to site, FTP, and look in folder you should see thumb_imagename.jpg or whatever ext. it has, they don't show in Image Manager by default...
And if you have an album and want to change the main thumb, first one at top for showing in album list mode on page, try changing it and you will see all the images with, on the right, 2 picture icons big one is image second small one is thumb, I tried to change thumb and clicked the larger image icon and it used the large one, that's how I found out...
Re: Still unsolved: Album 0.9.2 problem
Posted: Fri Aug 31, 2007 10:58 am
by margo
mark wrote:
The first time you look at images to use in an album do you notice the images have a blank spot then it starts showing images, blink, blink, they show up, this is album making thumbs out of images, if you go to site, FTP, and look in folder you should see thumb_imagename.jpg or whatever ext. it has, they don't show in Image Manager by default...
First time I go to see added images from admin-panel, system should generate thumbs, that will be placed in the same dir. where original ones are, right?
But I don't get that behaviour. When I go to see images from admin side I only see the large images being wrapped up by the img width and height attributes...
When I try to see images from "outside", I see also only the large files. And I can't see any thumb-files from FTP either...
Re: Still unsolved: Album 0.9.2 problem
Posted: Fri Aug 31, 2007 1:06 pm
by Dr.CSS
I uploaded some images to a cmsms site and made an album, w/o looking at the images in Image Manager which will generate thumbs from looking at the large images also, then I went to site via FTP and this is what I see...
As you can see they are in a subfolder in uploads/images, but if they were in any folder in images or the uploads/images folder, which is the folder Album looks for images in, it would still work...
http://multiintech.com/webshots/thumb.png FTP screen shot...
The site is
http://cmsmsdemo.multiintech.com/ login info on home page...
ps. what does your config.php say about image settings? something like this...
pss. what is your "File Creation Mask (umask):" set to? mine is 002 or 000 or blank on some of the sites I work on...
#--------------
#Image Settings
#--------------
#Which program should be used for handling thumbnails in the image manager.
#See
http://wiki.cmsmadesimple.org/index.php ... ge_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = '/usr/bin/ImageMagick/';
#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = '/homepages/24/d151200904/htdocs/uploads/images';
$config['image_uploads_url'] = 'http://
yoursite.com/uploads/images';