Views

You can create VBO actions that can do something for you but for a quick solution and one time actions you can use "Execute arbitrary PHP script" and there you have $entity and $context object that you get one per each line of yout VBO view.

So what I did was copy some text and node reference fields to field collections fields, that have text and entity reference in them. This took a little bit more coding and clever thinking but with google and some help of this page
https://drupal.org/node/1842304

In views there is that part in contextual filters where you can set exception and it is by default set to "all" so if you want to show all the nodes which in a way disables this filter, you can use that. But it also adds itself to default bredcrumbs of your drupal installation. So to remove it from breadcrumb, just use "show page not found" for the "When the filter value is not in the URL:" and this removes it at least from breadcrumbs, but it is still in the system.

Not sure if this is solved in drupal 7, but in drupal 6 you surely need to override
views-view-summary-unformatted.tpl.php with custom code. More on this you can find here
http://drupal.org/node/403012 but I did my own fork that looks best for my needs and think is the best out of those offered on link above. Here it is

Here is another drupal i18n beast. I have nice taxonomy summary for a category of shops. Which is attachment for a view, which passes term to it to filter category and show only shops that are in that category. Looks nice, it is moderately useful and seems it has never been done before. Search for something similar never came up in google, only a rather useful post that deals with similar stuff, only much simpler, people want to translate term title.

However you choose to do a migration from drupal 6 to drupal 7 if you have any complexity in your site it is going to be ugly. Lots of errors and leaps of faith :-).

I choose to do it with drush. So after the drush made what it could do. I tested the site. Not working at all, not even logging in possible. What I did is:

Files: 

icache.zip

I used revisions and almost emidietly regreted. Revisions are just like other nodes. So if you use views to display them, then you will have by default both original nodes and their revisions displayed. What you could probably do is use content revision type of view, but you still get all the nodes there. I tried with some relationships but no luck. Then finally I installed revisioning module and there was one new filter that counted number of revisions. So you add "Content: Revisions (> 1)" and you will get all the new revisions.

As views and even more panels are not perfect when it comes to translations if you need to have some fixed label with translation for some view/panel. You can create custom token for it and then just translate it over translation interface. Token creation is simple, just use this guide

1. Go to Admin > Structure > Custom Token, click on Add Token
2. Enter a Token Name and Description
3. Choose "Custom Tokens" for the Token Type or "Nodes Token" if you want it to be available on for example node panels overide.
4. In the PHP Replacement text area enter something like this:

I recently had a problem with sorting of chars. I have some Eastern Europe chars. like čćžšđ and they didnt sort like I would like to in views. "Đ" would come at the end of the list after "Z" and it should be after "D" so I found the solution and the problem.

Problem is collation of tables in mysql database and solution is changing it. They were all set to "utf8_general_ci" so I just change node table "node" because I was sorting by title and I did this.

People usually set argument and often don't mind about validation. Just leave basic validation thinking most will pass. But that is not the case. For example you can use User ID ad argument and think both UID and User Name would pass, but that is not the case. You have to go and select "User" Validator and use "Allow both numeric UIDs and string usernames" for this to work. Otherwise you could have a view that is showing nothing and left you wondering what is happening.

Most will use views 3.x in future and they should as they are really better, from UI point of view to other parts but for some old sites that are not updated and you want to theme exposed filters differently, you can't from default. You need to change some template as all your filters have the same classes.

Override the exposed form template in your theme -- take a look at /modules/views/theme/views-exposed-form.tpl.php