Strict Standards: Declaration of BB_Walker_Blank::start_lvl() should be compatible with BB_Walker::start_lvl($output) in /webroot/s/2/s2admin/synapp2.org/www/forum/bb-includes/classes.php on line 1127

Strict Standards: Declaration of BB_Walker_Blank::end_lvl() should be compatible with BB_Walker::end_lvl($output) in /webroot/s/2/s2admin/synapp2.org/www/forum/bb-includes/classes.php on line 1127

Strict Standards: Declaration of BB_Walker_Blank::start_el() should be compatible with BB_Walker::start_el($output) in /webroot/s/2/s2admin/synapp2.org/www/forum/bb-includes/classes.php on line 1127

Strict Standards: Declaration of BB_Walker_Blank::end_el() should be compatible with BB_Walker::end_el($output) in /webroot/s/2/s2admin/synapp2.org/www/forum/bb-includes/classes.php on line 1127

Strict Standards: Redefining already defined constructor for class bbdb in /webroot/s/2/s2admin/synapp2.org/www/forum/bb-includes/db-mysql.php on line 12
Can't access tables « Support Forums

Support Forums » Installation
Installation

Can't access tables

(2 posts)
  1. audiosupport
    Member

    Hi there,

    We've been reading this post...
    http://www.synapp2.org/forum/topic.php?id=11

    quite carefully, and thankfully managed to sort out our installation issues. We're all logged in to synapp2 ok, and the ?show_response=1 string is showing us that we are successfully connecting to our web161-synapp2 database. Our problem is that we can't see any table info, it just shows -- no information -- even though we've added a table to the web161-synapp2 DB and put in a couple of fields.

    Is that the right way of doing it, or should we be connecting to a different database which contains all the live data?

    Is it possible to connect to an existing database we have on our server called web161-audiosup? The ?show_response=1 shows us that connection failed. We can't find the option in our myphpadmin to add a new user to this mysql database.

    Thanks in advance,
    Alex

    Posted 9 years ago #

  2. Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /webroot/s/2/s2admin/synapp2.org/www/forum/bb-includes/kses.php on line 440

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /webroot/s/2/s2admin/synapp2.org/www/forum/bb-includes/kses.php on line 510

    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /webroot/s/2/s2admin/synapp2.org/www/forum/bb-includes/kses.php on line 512
    richard

    Administrator

    Hi Alex,

    I think you're close. If I understand your post, the issue may be that you've added your table to the 'synapp2' database. So, to answer one of your questions, yes - your "live data" tables should be should be in any database other than the 'synapp2' database.

    Secondly, you should be able to connect to any number of databases on your server, via the MySQL user 'synapp2' - that's the assumption of the default configuration. If the 'synapp2' user has been granted all MySQL privileges, it should be able to connect to any database that you can access as 'root'.

    The essential idea of the authentication and authorization mechanism is this: You login to SynApp2 with a username and password stored in synapp2.users, and then - behind the scenes, SynApp2 accesses your databases via the MySQL user 'synapp2'.

    In phpMyAdmin, you can add users and grant Global privileges from the 'Privileges' tab, accessed from the phpMyAdmin index/home page. But, if you're successfully logging into SynApp2 (using the default SynApp2 _config_) then you must have somehow added a MySQL user 'synapp2' - perhaps from the command line?

    Send an email to me - richard - at synapp2.org and we can work through the details to get you up and running.

    Richard

    Posted 9 years ago #

RSS feed for this topic

RSS feed for this topic

Reply

You must log in to post.