Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COI should probably provide a little more background. on my situation so that I may get a better idea of what I need to do. I do agree that it would be much easier to deal with user access on the Drupal system, but I took over this project with a website that was already up and running and databases already in place. So, we already have thousands of users in our Filemaker database with the correct boxes checked for each user to determine access. At this point it would take too long to manually enter the access restrictions for all of the users on the Drupal system. ....
      singulars
    2. COIf there where a simple way to merge databases or transfer some fields over that would be helpful. If not I am still looking for some php code that can help with my problem. I just need to make more specific access. Another quick note. I dont actually enter code as previously shown on the Drupal pages themselves. I usually do something like this <?php include($_SERVER['DOCUMENT_ROOT'].'/folder/filename'); ?> This calls a file on our web-server and thats where I add in php and html. I am still looking for a solution. Please if anybody has any ideas please let me know. Thanks!
      singulars
    3. COI agree with this comment -- if you're using Drupal then you should be using the Drupal user module; if you don't use basic stuff like that then you may as well not use Drupal at all. I'm working on a Drupal system that has to hook into an existing back-end database, including user accounts. We've worked out a mechanism such that our logins use the back-end DB but create dummy user accounts in Drupal that match the one in the back-end. This allows us to login using out back-end DB but still get the benefits of the Drupal Users module.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload