User login

note

A series of updates, ever lates Views dev, causes a Class 'views_handler_field_entity' not found fatal error

The update sequence below - even with a ridiculous amount of cache clears - cannot run over the new Views-3.x-dev code. (Error at bottom.) However i did confirm that registry_rebuild() in a bootstrapped test.php can restore the site at least.

The solution in this place is just to do a deployment, which is due anyway, before beginning on the Continuum branch - the first two updates, anyhow, run fine on the more stable release candidate 1 Views, and then when the code is updated the final update also runs fine. I don't like it but there's nothing blocking about this.

Deleting a branch in git, and deleting that branch from the remote repository

in

git branch -d nameofbranch
git push origin :nameofbranch

You can also use git branch -D nameofbranch for the first command above if you really, really mean it.

And in the second line 'origin' is the name of the remote repository, which can be anything you choose but is usually origin.

Discussion and action

Discussion and planning are essential activities for any project beyond significant size and for any long-term goal. However, so is taking action. As a rule:

People who want to take action should not be held up by people who want to plan.

Access denied on Display Fields settings page for Full view mode

in

Point of everything below: Getting access denied on Display settings pages can be caused by not having a view mode set to custom display settings in a robust enough manner.

Put this code in a test.php file and run it, you can see your lovely giant variable and it can fix you up fine for developing (get access to the settings page again).

Change the text of a tab, such as 'View', for one node type

<?php
/**
 * Implements hook_menu_alter().
 *
 * Use a title callback to replace the text shown on nodes' "View" tab.
 */
function example_menu_alter(&$items) {

Drush and specifying source dump and target dump options

Using temporary files to store and transfer sql-dump. It is recommended that you specify --source-dump and --target-dump options on the command line, or set '%dump' or '%dump-dir' in the path-aliases section of your site alias records. This facilitates fast file transfer via rsync.

What exactly does that mean? Is some random location i make up really better than the temporary directory? Or should i be giving it some specific directory, on different serves or something? Guidance please.

Failure

in drushrc.php

Syndicate content