You are not logged in.
Pages: 1
I agree with you that alt tags do little do improve the site experience of a visually impaired user and maybe even make it worse. However, many organizations are required as protocol to comply with the ADA so to not be sued. My understanding of this compliance from an ideological perspective is that we provide equal opportunity for visually impaired users. In practice though, this usually means following dated and ineffective modes of development.
Although we might have qualms with the actual usefulness for blind users, I think for a wider spread adoption of BigTree you may consider adding it to the core.
Hey is there any way to store meta-data about photos within the gallery/photo_uploader? My specific use-case is for having alt-tags on photos included in a template and not adding superfluous fields if possible.
I ended up using BIGTREE_CUSTOM_ADMIN_CLASS and setting a file within /custom/ for the overriding class. We're using LDAP to restrict login to the admin entirely. It looks sorta like this:
class LDAPLogin extends BigTreeAdmin {
function login() {
if ($passes_bigtree_auth) {
BigTreeAdmin::login();
} else {
$this->loginLDAP();
}
}
function loginLDAP() {
// check if user exists and has valid credentials and matches groups specified in $bigtree['config']['ldap']
BigTreeAdmin::createUser();
BigTreeAdmin::login();
}
}It seems to be working well now. Hopefully it's future proof. xD
Thanks for the advice. I'll let you know what implementation we go with.
Ah I see. Thanks for the info!
Nevermind. I figured it out. I had to add global $bigtree; to access it within that scope. Thanks for the advice on the duplication though.
Is it possible to append additional arrays to $bigtree["config"] by adding lines in your /template/config.php and access them in core files like /core/inc/bigtree ? I can't seem to retrieve any of the values added. Perhaps there is a separate configuration for core?
It looks like I can use "BIGTREE_CUSTOM_ADMIN_CLASS_PATH" to subclass BigTreeAdmin create an overriding login method under certain circumstances or just call super. Is LDAP authentication something worth adding to the core of BigTree though?
It looks like I could extend the functionality of BigTreeAdmin#login to check for LDAP configuration with $bigtree["config"] and call an authentication function which would create a new user if the credentials pass/match group and re-call BigTreeAdmin#login with the generated credentials . (Assuming the login form uses the BigTreeAdmin#login method itself. My recursive grep can't find any instances of login(), so I'm not sure if you are xD) Would this extended functionality be something worthwhile in the core or would it need to be re-implemented with each core update?
Probably going into the issue of how to extend the admin functionality of BigTree again.
I'm interesting in making an LDAP plugin for BigTree. Where might I find most of the authentication logic?
Or is there a better way to incorporate this so it doesn't get overwritten in future core updates?
EDIT: It looks like I could use http://www.bigtreecms.org/code-referenc … createUser for the user creation upon authentication with our servers, but I'm just not sure how hook such logic into BigTree.
Just found it too. Thanks! Line 64 GRRR.
I have three tables with modules set up for two. For example:
dogs: name, age (module)
treats: title (module)
dog_x_treat: dog_id, treat_id
If I have 3 treats and set my dog to like all of the treats in the New or Edit form, the MtM input box disappears. If I go and manually remove one of the associations in the database, the form re-appears. It seems that when all rows are associated to the object, it has logic to now show the input. This a problem however, should my dog's treat preferences change, I have no way of editing it as a front-end user.
I'm digging through the /core to try and make a fix. Having trouble finding the right files though. I'll be sure to make a pull request on Github if I patch it.
Pages: 1