Trouble logging in with admin / test after install on version 8.1
6 views
Skip to first unread message
KenWall
Apr 1, 2009, 3:24:44 PM4/1/09
to phpShop
I was looking for a very simple (free) on-line cart and this looks
like it will fit my needs nicely. I followed all the steps in the
instructions and after the Database set-up and changing the
etc.config.php, I went to view the shop as instructed. Well the shop
came up just fine however I tried to log-in using the provided info
and it does not bring up the admin panel, returns to the shop. I also
tried to use the store demo and same thing. The not so funny part is I
can add an item in the cart and it WILL bring up the checkout process
meaning asking for my info as a quest etc.
Any thoughts as I need to get this working quickly for a client?
like it will fit my needs nicely. I followed all the steps in the
instructions and after the Database set-up and changing the
etc.config.php, I went to view the shop as instructed. Well the shop
came up just fine however I tried to log-in using the provided info
and it does not bring up the admin panel, returns to the shop. I also
tried to use the store demo and same thing. The not so funny part is I
can add an item in the cart and it WILL bring up the checkout process
meaning asking for my info as a quest etc.
Any thoughts as I need to get this working quickly for a client?
jnewman67
Apr 2, 2009, 8:56:30 AM4/2/09
to phpShop
did you get my personal response to this? just making sure you got
it.
it.
KenWall
Apr 2, 2009, 10:40:46 AM4/2/09
to phpShop
Just sent an email with screen shots. Still no go!
KGW Mail Comcast
Apr 2, 2009, 10:56:47 AM4/2/09
to php...@googlegroups.com
I just noticed something and am not certain it is/was supposed to be
installed. I imported into MY_SQL as the instructions stated to the letter
the phpshop.sql file and looked at all the tables and structure and it looks
fine. I now noticed there is a db_mysql.inc file. This is not
shown/mentioned if I recall in the instructions. Is this the part I am
missing? If so, what do I do with it?
Ken
installed. I imported into MY_SQL as the instructions stated to the letter
the phpshop.sql file and looked at all the tables and structure and it looks
fine. I now noticed there is a db_mysql.inc file. This is not
shown/mentioned if I recall in the instructions. Is this the part I am
missing? If so, what do I do with it?
Ken
Jeff Newman
Apr 2, 2009, 3:07:46 PM4/2/09
to php...@googlegroups.com
no, that's actualy the db functions that phpshop uses to interface with the
database. hence the .inc(lude) extension.
i didn't see an attachment with your last email
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.11.38/2037 - Release Date: 04/02/09
06:09:00
database. hence the .inc(lude) extension.
i didn't see an attachment with your last email
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.11.38/2037 - Release Date: 04/02/09
06:09:00
KenWall
Apr 2, 2009, 5:57:37 PM4/2/09
to phpShop
To All:
Found and fixed the problem. It was on my end but may be an issues
with others that do the same as I do for SEO purposes. I use
an .htaccess file to control BOT's from reading the root directory
(mysite.com) and the public_html directory (wwww.mysite.com) and have
it direct all to (www.mysite.com). This way for those unaware (and I
know this sounds funky but it is very true), Google and others do see
and read two (2) websites without this. They see the main mysite.com
and the www.mysite.com if this method s NOT used. I picked this up in
the W3C School and it does make a HUGE difference in rankings! Google
especially does not like to see duplicate content on websites. They
will and do see the 2-versions if you do not instruct your website
either with a Robots Text File (which some search engines ignore) or
to ensure it is read just once you add the following code to
the .htaccess file it guarantees it only sees 1-website:
Options -Indexes
RewriteEngine on
RewriteCond %{HTTP_HOST} ^mysite.com
RewriteRule ^(.*)$ http://www.mysite.com/$1 [R=permanent,L]
This is mainly for those using a shared server as there you are most
likely under a "root" and a public_html. That is the problem. Both the
root AND public_html are scanned by search engines. Not as much an
issue for a VPS or Dedicated server as internally, the root IS hidden
as added protection that a VPS or Dedicated server already provides.
So take it for what it is worth. It has worked very well in my 15+
years in IT and web design.
What happens in the end is no matter how it is typed in a web browser
(with or without the www) it will always come up showing the www
version. Google and ALL search engines will now only see the www
version and thus 1-website and index accordingly with NO duplicates. I
have used Google Analytics for years and within 1-week of me doing
this (and after I saw the google.bot come through), my ranking went up
10-places. I have used this now on all my sites and same thing, BOOM,
the rankings went up dramatically for all and later I found many
additional search engines picked these websites up gaining me even
better rankings for my clients. It also brought the other main search
engines dramatically up.
How it relates here: Well in the config file, you have to specify the
website path. In the instructions and in the file it uses no www.. So
as my website was directing to a www one through the .htaccess file,
the shop came up but it would not allow a login. Solution was just to
add the www in front of the path in the config file. All set now and
thanks for the quick replies and that is what made me look again as it
seemed VERY straight forward and I was missing something.
> --------------------------------------------------------------------------------
>
> - Show quoted text -
Found and fixed the problem. It was on my end but may be an issues
with others that do the same as I do for SEO purposes. I use
an .htaccess file to control BOT's from reading the root directory
(mysite.com) and the public_html directory (wwww.mysite.com) and have
it direct all to (www.mysite.com). This way for those unaware (and I
know this sounds funky but it is very true), Google and others do see
and read two (2) websites without this. They see the main mysite.com
and the www.mysite.com if this method s NOT used. I picked this up in
the W3C School and it does make a HUGE difference in rankings! Google
especially does not like to see duplicate content on websites. They
will and do see the 2-versions if you do not instruct your website
either with a Robots Text File (which some search engines ignore) or
to ensure it is read just once you add the following code to
the .htaccess file it guarantees it only sees 1-website:
Options -Indexes
RewriteEngine on
RewriteCond %{HTTP_HOST} ^mysite.com
RewriteRule ^(.*)$ http://www.mysite.com/$1 [R=permanent,L]
This is mainly for those using a shared server as there you are most
likely under a "root" and a public_html. That is the problem. Both the
root AND public_html are scanned by search engines. Not as much an
issue for a VPS or Dedicated server as internally, the root IS hidden
as added protection that a VPS or Dedicated server already provides.
So take it for what it is worth. It has worked very well in my 15+
years in IT and web design.
What happens in the end is no matter how it is typed in a web browser
(with or without the www) it will always come up showing the www
version. Google and ALL search engines will now only see the www
version and thus 1-website and index accordingly with NO duplicates. I
have used Google Analytics for years and within 1-week of me doing
this (and after I saw the google.bot come through), my ranking went up
10-places. I have used this now on all my sites and same thing, BOOM,
the rankings went up dramatically for all and later I found many
additional search engines picked these websites up gaining me even
better rankings for my clients. It also brought the other main search
engines dramatically up.
How it relates here: Well in the config file, you have to specify the
website path. In the instructions and in the file it uses no www.. So
as my website was directing to a www one through the .htaccess file,
the shop came up but it would not allow a login. Solution was just to
add the www in front of the path in the config file. All set now and
thanks for the quick replies and that is what made me look again as it
seemed VERY straight forward and I was missing something.
>
> No virus found in this incoming message.
> Checked by AVG -www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.38/2037 - Release Date: 04/02/09
> 06:09:00- Hide quoted text -
> No virus found in this incoming message.
> Checked by AVG -www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.38/2037 - Release Date: 04/02/09
>
> - Show quoted text -
Reply all
Reply to author
Forward
0 new messages