Coppermine Issues

[dirtvoyles]

I installed Coppermine at photos.danvoyles.us. I can't seem to view any of the 5 sample images I uploaded though.

 

I have never used this software before, and I don't know a whole lot of anything about being an admin so I would appreciate any help.

 

Edit: And now it won't even let me upload anything. I'm somewhat perplexed.

Edited May 23, 2006 by dirtvoyles

[flashram]

The system in coppermine is set so that you have to login to view the albums, you need to log in and have a good look at the configuration settings, there are little ? marks next to each of the configuration settings and if you move over them you should get a detail hint about what they do and what settings for each of them.

 

Viewing the images is another matter again that has to do with settings in the albums and viewing, it is a permissions thing that they have set up.

[TCH-JimE]

Hello,

 

The images might not be viewable because of many reasons, like above, have you set the permissions to view them? Do they need to be authorised to see them? Have you got the correct settings for GD or imagemagik etc etc?

 

If your still having problems, give us a shout back here and we will suggest some more things for you to try

 

JimE

[TCH-Thomas]

Did you solve this because I can see the images very well.

[dirtvoyles]

Nope, still haven't gotten anywhere. I went to bed shortly after posting this, so it's sat all night.

 

Thomas, I hope I didn't put some images I ddin't mean to up there.

 

I would also like to know how I need to change the file permissions for when I do a bulk add. Do I need to change the permissions for the folders CM adds too AND where it pulls from or just one?

 

A lot of questions I know, but I'm clueless. Please ask what you need to know and I'll check it out and get you details.

[flashram]

I am looking at the gallery at present and upon checking the validation of coppermine it appears that you haven't installed the coppermine correctly as it is reporting all the necessary files to be missing. Which is why when you look at your gallery, or any of most of the other buttons used by Coppermine are said to be missing.

 

How I installed my Coppermine was by using the fantastico installation link but I put it into a seperate folder which I have called gallery.

 

I would suggest that you uninstall Coppermine and reinstall it again, but this time when asked what directory to put it in, make sure you call it either coppermine or gallery.

 

The other thing, you have allow user registrations set to no, which means, unless you are a member already, people will never be able to see you albums, as they aren't able to login. As well as that, you don't allow guests to view either, which amounts to exactly the same thing.

 

Does that all make sense.

 

I have msn on at present and yahoo.

Edited May 23, 2006 by flashram

[flashram]

I've changed your guest permissions to yes, so linking to the gallery now you can at least see the albums not just a log in screen.

 

When you look at the links for the gallery it is showing that the installation is in the root section of your website. It shouldn't be in the root, it should be in one directory lower.

 

When you install the script it allows you to nominate a directory, if you leave it blank it installs into your root directory (public_html) and the structure of coppermine doesn't know where the info is being stored, hence why images etc are missing, although they should display in theory.

 

If you unistall your coppermine installation and then reinstall it using the fantastico install, where it shows the empty box underneath the address line, put in gallery or gallery two if you already have a photos gallery which I think you do with the photos link on your blog website. Or put in Coppermine or gallery 2 what ever you want to call it. So your link will look like http://www.danvoyles.us/gallery2(or what ever you call it)/ and it will then be in the correct installed syntax for the scripts to find the relevant info.

 

Also coppermine is up to version 1.4.6 as well your current install is 1.4.2

Edited May 23, 2006 by flashram

[dirtvoyles]

That's a lot of information, but I think I followed okay.

 

What I was trying to accomplish was installing CM into the root directory of "photos.danvoyles.us" as that is all I want to use that subdomain to do. Can that be done?

 

(I'm ignoring the un- and re-installing for a moment to find this out.)

[TCH-Bruce]

If you create the subdomain first called photos when you are installing enter "photos" into the box Peter is referring to above.

 

A subdomain is nothing more than a folder in your webspace. And do not create the "photos" folder manually. Let the subdomain create function create it.

[dirtvoyles]

So, just to be sure, I should NOT choose photos.danvoyles.us as the install domain and leave the directory empty?

 

I SHOULD put CM in danvoyles.us and put the directory as photos?

 

I just want to be sure before I do this again.

[TCH-Bruce]

No, don't install it into your root folder. Create the subdomain called "photos".

 

When installing Coppermine in Fantastico enter "photos" into the box for the folder to install it into.

 

www.dan...us/photos is the same as photos.danvo...us

[dirtvoyles]

Hokay. I was unaware that ....us/photos and photos.danvoyles.us were the same thing.

[TCH-Bruce]

They are the same as long as you create the subdomain without creating the folder first. The subdomain function will create the folder of the same name.

 

If the folder is created first when you go to the link photos.whatever.ext it will change in the browser to whatever.ext/photos

[dirtvoyles]

Hokay, I think I'm making progress. CM is there, I used bulk add to put up a FEW test photos (4), but the thumbnails aren't showing. Neither are the pictures.

 

If this is getting too annoying, just say so and I'll go to the CM support forums.

[flashram]

Coppermine needs to be installed into a direcotry under the domain name not before the domain name like sub domain.

 

You need to let it install into http://www.danvoyles.us/ when you are installing Coppermine, it has a box under the domain address which is blank, in there you put the name you want for the directory e.g. gallery, photos, coppermine, what ever you want.

 

Don't try and install into www.photos.danvoyles.us, it won't work as the scripts aren't resolving properly to where they think coppermine is installed.

 

It is alright to install the content Management into the root directory as your front end, but Coppermine sits below the root directory in a sub directory of your choice but you have to remain within the norms of it's own set structure.

 

When you have it installed you can imbed it into the CM but I would suggest not doing that, just make a link to the gallery as a sperately opening window, otherwise the displaying of Coppermine will just suck big time, from what I have been looking at, as I am on a similar track that you are on as well, redesigning my own websites to use a Content Mangement Systems scripts like Joomla.

 

As I said in a post above, the photos are on your system, but the syntax of the scripts is looking in the wrong directory for images etc, as you have confused Coppermine with it's location being wrong.

 

I have messenger open at present if you want to chat.

[flashram]

Bruce,

 

DanVoyales has confused the installation of Coppermine and he needs to uninstall it and follow the normal install into a sub direcory under his domain name. You know that I know that but he hasn't picked up on that, hopefully he will after my last post.

Edited May 24, 2006 by flashram

[dirtvoyles]

Hokay, as I have it now Coppermine is installed in danvoyles.us/photos. In Fantastico I installed to danvoyles.us then photos as the folder. Did I at least get that part correct?

 

I'm not going to use a content management system with it, I am just planning on using it as it's own frontend. Kind of like photobucket.

 

photos.danvoyles.us resolves to the Coppermine install, but the photos aren't showing.

 

Perhaps I'm not getting it and it needs to be drawn out in crayon.

[flashram]

I just went to the website and I can see the images in the website now. So I think you have got it now.

 

If you log in to Administrator and see the button Admin Tools select that and then scroll towards the bottom and click on Version Check, it will show there are some little problems, which have to do with folders that need to be CHMOD to allow the scripts to write to certain directories. There is also one file missing which isn't a huge problem but should be uploaded.

 

I would also suggest that you update to the current version which is 1.4.6, when you have that done, you will be set and then can do what ever you want with the themes. Have a look on sourceforge coppermine website and you will find quite a number of themes that others have put up for people to download and install, I personally use the Digital Flow theme over the others, I just like the way it is displayed.

Edited May 24, 2006 by flashram

[TCH-Bruce]

DanVoyales has confused the installation of Coppermine and he needs to uninstall it and follow the normal install into a sub direcory under his domain name. You know that I know that but he hasn't picked up on that, hopefully he will after my last post.

Yes, I assumed that. I was trying to clarify that a subdomain is nothing more than a folder within the domain space.

 

To access a gallery, blog or what ever else you want as a subdomain you should do the following:

 

1. Create a subdomain in cPanel - cPanel will create the folder (ie: photo, blog, gallery, etc...)

2. Install the gallery or blog software into the "folder" created in the subdomain function

 

You can then access your install using yourdomain.ext/folder or folder.yourdomain.ext

 

I don't know if that clears it up either.

[dirtvoyles]

First, thank you all for your help.

 

Second, am I the only one who can't see the images? I have tried from home on my Kubuntu box using FF and can't see even the frame for them.

 

When I try from work using IE6 I can see the frames, but not the actual images. I get the joyous red X. Does this make sense?

 

Finally, how do I go about updating the install? I'm not a command line pro or anything, and definitely not when it comes to servers. I would like to clean everything up and have it running properly. Not to mention this is all about experience for me.

Edited May 24, 2006 by dirtvoyles

[TCH-Bruce]

I can see the images using /photos but not photos.dan...us

[dirtvoyles]

So much for using photos.danvoyles.us. That kinda ticks me off.

[TCH-Bruce]

Dan, I am not familiar with Coppermine but I am sure that it's possible. I just don't know what you need to change in the configuration or .htaccess file for it to function that way.

[dirtvoyles]

Well, I'll let this sit for a bit (I made a funny) and see if anyone has any ideas.

 

Again, thanks to everyone for your help.

[abinidi]

Mine works: photoalbum.pehrsonfamily.net

 

However, I can't find any configuration settings that make it work. With my WP blog, I can modify the install directory in the settings. I can't find any such option with Coppermine.

 

I wonder if it was set by the install script?

[Redeagle]

I may be way off base here, but I know the 2 times I've changed servers (and the DNS) I was always able to access subdomains using www.sitename.com/subfolder/ way before I was able to access it from subfolder.sitename.com.

maybe that has something to do with it? how long ago did you set up your subdomain?

[TCH-Don]

Did you by chance create the folder photos first

then the sub-domain

[flashram]

Well, I'll let this sit for a bit (I made a funny) and see if anyone has any ideas.

 

Again, thanks to everyone for your help.

 

 

 

Dan,

 

I just tried what you have been doing, putting it in the root directory and need to know if you can see it.

 

Tell me if you can see this. http://photos.testing.flashram.com.au

Edited May 24, 2006 by flashram

[flashram]

Ok what the problem has been is a two fold problem.

 

One making a subdomain called photos.xxx.xxx.xxx and also having a folder under the domain xxx.xxx.xxx the same and trying to install coppermine.

 

If you make a subdomain called photos it will show up in the syntax as photos.xxx.xxx.xxx but will in actual fact be stored in the domain as a folder so xxx.xxx.xxx/photos

 

So installing to the subdomains root directory in actual fact installs to the directory under the domain name and is fooled by the cpanel software thinking it is a subdomain.

 

If you already had/have a folder in there called photos and installed coppermine into that, then there is where the problem occurs.

 

So moral of the story, don't name the subdomain as a name of a directory you already have in the structure.

 

Call it Gallery.

[flashram]

Addendum to the above post.

 

After reviewing the file structure in cPanel for Dirtvoyels it would appear that there might be confilicting html pages at the root and public_html areas of the website.

 

I think there is an inherent problem with the way that installations have been done and it has stired the pot too much.

 

I have noticed that with Fantastico scripts that even though you tell it to uninstall packages it in fact leaves some stuff behind in cPanel filemanger and that can cause problems down the track especially with naming conventions of directories (read future installations).

 

Will post more as time goes on.

 

Just to sum up.

 

I created a sub directory exactly as the intial user did in my test domain and installed coppermine into the root of that subdomain and it worked.

 

But if you have a folder that is the same as the domain name i.e. photos then I think there is a confusion on the installation that is then not easily resolved. Well it is, you delete the domain and start again.

 

Probably post some more about this later on today.

[TCH-Bruce]

That's why I said to create a subdomain and not create the folder first. Creating a subdomain will create the folder.

[flashram]

I know Bruce saw that but that had already been done.

 

I noticed that like me that he had done the same thing and installed a lot of the scripts to look at them and deleted them.

 

But there was still stuff from the installs hanging around, like databases, files etc and addon script info.

 

But I also noticed that there is info in the root directory at the level where public_html directory is showing and I think that the installation of the domain name is now confused about about where files are as they are in sevel places.

 

I think it needs to be looked at by helpdesk and cleaned up to a near fresh domain install and starting again, doing it as I first suggested as have you, installing into a directory below the main domain and not doing a subdomain install, makes it much cleaner, tidier and easier to fix up as well.

 

I do know the subdomain creates the folder, but it seems that he elected to try both ways and used the name the same and that has confused then installation and it is still maintined somewhere in the files on the domain.

 

Make sense.

[dirtvoyles]

Sounds like I fouled some stuff up. Eh, that's why I'm doing this - to learn from my mistakes.

[TCH-Bruce]

I think it needs to be looked at by helpdesk and cleaned up to a near fresh domain install and starting again

The only thing the help desk can do is reprovision the account. Taking it back to a brand spanking new account. They have no idea what files are required for what you have installed. And the help desk does not support third party programs.

 

If Fantastico is not properly uninstalling things, that is a problem with Fantastico and up to them to clean it up.

[dirtvoyles]

To that end, I think I might just be better off dealing with /xxxxx instead of worrying about it.

 

Granted, I might have issues further down the road, but for now it's just something for me to play with. If I should ever get to the point where I'm running my site in a commercial manner (doubtful) I could start over with a better-designed site.

 

I'll allow a bit of time for people to respond with input, but I'm afraid I'll just have to deal with some quirks.