Admin Problem

[mehdi4689]

hi
I installed oscmax and now i can't login to admin
when i type user and password admin panel:

/shop/admin/login.php?osCAdminID=bd0f536c261b93ae6de65c2ae9930 b7b

is open:
/shop/admin/index.php?osCAdminID=bd0f536c261b93ae6de65c2ae9930 b7b

but whet click in item, for example:
/shop/admin/admin_members.php?selected_box=administrator

back to admin login:

/shop/admin/login.php?osCAdminID=0c5a8544766544ab61596528be23e 3c0

and i can not change items information...

Please Help ME
Thanks

[michael_s]

This is a sessions problem. osCmax looks like it is unable to keep the session. Usually incorrect session save path or cookie domain settings in configure.php. You can overcome both by editing your configure.php to store sessions in mysql and set the cookie domain to .yourdomain.com (make sure you change it to your actual domain name and the '.' needs to be there too).

[tdwuk]

I just tried the Beta 3 and could not get into admin. I checked the session and it is set to mysql already.
I just added mydomain.com to:
includes/configure.php lines 17 and 18

define('HTTP_COOKIE_DOMAIN', 'http://www.mydomain.com/store/');
define('HTTPS_COOKIE_DOMAIN', 'https://www.mydomain.com/store/');

Not sure about lines 19 and 20:

define('HTTP_COOKIE_PATH', '/dev_oscmax/catalog/');
  define('HTTPS_COOKIE_PATH', '/dev_oscmax/catalog/');

Trial and error

[tdwuk]

I seem to be stuck, I changed the domain settings to my domain the the configure.php file.
I get stuck after installation, I get:
Congratulations! Your admin folder has been renamed to .

When I click on Admin tool I get:
http://www.mydomain.com/store//index.php

When I enter my actual admin directory name it says cannot connect to database.
Can someone please advise where I am going wrong. I am going to change some more things in the configure.php file and see how I go.

Thanks

[met00]

Congratulations! Your admin folder has been renamed to .

I consider this an installation defect (and have reported it as such). This is my procedure for an install (and I've done a lot of them lately). It is on a linux box (your mileage on whatever type of box other than that that you use may vary). This install method uses the directory root, not /catalog.

1 ) upload files with FTP (putting the files in the directory root, not /catalog)
2 ) make the database in phpmyadmin
3 ) on the server go to the directory root and
4 ) chmod 777 admin
5 ) chmod 777 admin/includes
6 ) chmod 777 includes
7 ) chmod 777 ../httpdocs [required because I don't use catalog subdirectory]
8 ) run osCmax install in the browser
9 ) chmod 755 admin
10) chmod 755 admin/includes
11) chmod 755 includes
12) chmod 755 ../httpdocs [don't forget this step or you have a very unsecure server]
13) chmod 755 includes/configure.php
14) chmod 755 {your admin name}/includes/configure.php
15) mv install __install
16) open up all the image directories to allow apache to write to them (you are gong to have to do it anyhow after you log into the admin and attempt to upload an image for a category or a product, might as well get it over with now)

At this point you have a problem still. The configure.php files created by the install process are owned by the webserver. That has to be fixed or you will get an error that you can write to them. You could set them with a chmod 555 rather than 755, but the better thing to do is make the account the owner of them.

17) chown {usernamle} includes/configure.php
18 ) chgrp {groupname} includes/configure.php
19) chown {username} {your admin name}/includes/configure.php
20) chgrp {groupname} {your admin name}/includes/configure.php

[ridexbuilder]

1 ) upload files with FTP (putting the files in the directory root, not /catalog)

Upload a tar.bz2 of the catalog directory and expand on the server - far quicker and more reliable, in my experience.
1a ) rename the htaccess and configure files, as stated in the wiki.
Those extensive permission changes as mentioned, are very much dependant on the server environment and are often not required where suphp/fastcgi/mod_php is used. All that is required is to make the config files writeable, prior to install, reverting when completed.

Just another side to the coin.
EJ

[met00]

not everyone uses tar, I was doing it the simple way.

If you are not using /catalog, apache needs to be able to write at the root or it can't change the admin directory (not everyone has suphp - I know for a fact that at least two major hosting companies do not load that as an apache module).

for example

core prefork http_core mod_so mod_auth_basic mod_auth_digest mod_authn_file mod_authn_alias mod_authn_anon mod_authn_dbm mod_authn_default mod_authz_host mod_authz_user mod_authz_owner mod_authz_groupfile mod_authz_dbm mod_authz_default util_ldap mod_authnz_ldap mod_include mod_log_config mod_logio mod_env mod_ext_filter mod_mime_magic mod_expires mod_deflate mod_headers mod_usertrack mod_setenvif mod_mime mod_dav mod_status mod_autoindex mod_info mod_dav_fs mod_vhost_alias mod_negotiation mod_dir mod_actions mod_speling mod_userdir mod_alias mod_rewrite mod_proxy mod_proxy_balancer mod_proxy_ftp mod_proxy_http mod_proxy_connect mod_cache mod_suexec mod_disk_cache mod_file_cache mod_mem_cache mod_cgi mod_version mod_bw mod_fcgid mod_perl mod_php5 mod_proxy_ajp mod_ssl

notice "mod_php5"

Please note, that running mod_suphp and mod_php concurrently can be
*VERY DANGEROUS* and should be avoided. The same applies to CGI
scripts which are run with webserver privileges.

[michael_s]

This is wrong:

define('HTTP_COOKIE_DOMAIN', 'http://www.mydomain.com/store/');
define('HTTPS_COOKIE_DOMAIN', 'https://www.mydomain.com/store/');

The cookie domain should never be a full url, just a host name like this:

define('HTTP_COOKIE_DOMAIN', '.mydomain.com');
define('HTTPS_COOKIE_DOMAIN', '.mydomain.com');

[ridexbuilder]

Good old Boss, back to the point in hand.
I'm interested in the dot prefix - presumably to allow subdomains to be detected/separated, in terms of cookies. I've never found the need to change from the defaults, post installation.

[michael_s]

The . dot prefix covers the top level domain and any subdomains. It makes it valid for any subdomain and the tld. Just the least restrictive setting.