There are options to specify the CSS class of the whole UL tag. If you specify CSS of a menu item (“firstNav” in my example), it’s added to to the A tag, not the LI tag as required by sliced design I have.
Googling shows that people are trying to work-around that by jQuery fixes.
It seems there is a proper way to solve this; you just need to add this option:
It’s seems Google tries to find a silver bullet to split high quality content from shit. The way they chose is to distinguish an author of this or that article. This fact means the text is better than an anonymous staff.
The new way to distinguish the authorship is called Google Authorship. Simply put, you can tell Google “Hey, I am the author of this content”.
There are 2 roles of “authors”: authors and publishers. A site usually usually represents a single publisher, but can have multiple authors. For example, New York Times or developers.org.ua is a publisher. Every article on those resources has its own author.
Both roles are setup via Gooogle+ profile. It’s a must, otherwise nothing works.
There are two and half ways to tell to Google who you are.
Way #1. Email on the same domain
Prove your relation to the website via an email address on the same domain. You can read Google guide on it first.
Way #2.1. A HYPER-link to Google+ profile
Add a usual hyperlink to your Google+ page with “?rel=author” at the end of the URL. Disadvantage is that you need to have a hyper link to an externtal resource which is not always a good idea.
Way #2.2. A link to Google+ profile
Just add a link, not “hyper”, just add this tag anywhere on the page:
Often Assembla makes me remember these wise words — “any fool can make things bigger and more complex” (I started this topic in a previous article “10 reasons not to use Assembla” where I even got reply from their guy, but seems things don’t change fast).
In general project is one of the best on the market, but the devil is in details, and those details just make me crazy at times.
The project is not stuck, development is active, but it seems that the focus of the Assembla development is 2 things:
where to put a sidebar of ticket details page — left or right? (it jumps every 6 months)
tiny CSS changes of menu and buttons.
All in all, the project is a decade mature, but still feels amateur at times. No offense.
Here is a list of things that irritate me the most.
My piece of code called “CSV import with visual mapping” is quite popular — people download it (from Assembla repository), ask questions, request support. I don’t develop new features, people just use it as it is.
At the same time, Assembla thinks, that due to the fact that I didn’t visit the space and don’t commit new code, space is not used. They marked it as inactive. There is now way to reactivate it apart from either buy a credit (no, thanks, it’s open source and you allow free spaces) or spend some time to recreate a new free space, recommit the code and update the links (that’s what I gonna do when they finally kill the old one).
Assembla spaces fail #2: cannot remove a space
Wanna kill a space? Maybe you want to switch to a cheaper plan this way? All you get clicking a “Delete this space” button is a “Space was successfully queued to be deleted” message and the space remaining forever.
Tickets fail #1: Parent story is NOT a parent ticket
This feature announced not so much time ago made me remember those words regarding making things bigger and more complex.
You have to choose either relations between tickets are “parent — child” or “parent story — child story”. A bit confusing, ha? Stories are made for Agile guys, the other option is for the rest.
To make it easier to distinguish a difference, child stories have a special icon =)
Behavior is different too — closing a parent story will also silently close all children tickets.
Having stories doesn’t help since…
…you cannot see tickets hierarchy (tickets fail #2)
Even if you spent some time defining tickets relations, it not possible to make a tickets filter sort stories so that their children are still shown under the parent story. All tickets are equal!
Your filter becomes a mess of parents and different children. Agile.
Tickets fail #3: the details editor
Make a list (numbered or not) out of a few lines, make a hyperlink out of a URL — just not possible. You get a template of a hyperlink and you are supposed to edit it in order to form the proper hyperlink. These things work for decades on other sites — making a hyperlink in Gmail is just sexy.
Take me right. It’s kind of ok if it doesn’t work in a free plug-in, but the tickets are the heart of Assembla as project management tool, these guys charge money for it — and it simply doesn’t work.
Tickets fail #4: the filter totals – NO WAY
You have a filter of tickets. Do you want to quickly find out the total estimated / spent time? Open tickets one by one and use your calculator.
Wiki fail #1: Editor
WISWIG editor adds a lot of crappy tags. Many times I experienced that after changes are saved (something complex like a big table with hyperlinks and new lines) what you get is a mess.
No preview button is available (anymore), but there is a half of the screen of Wiki format reference text, so you cannot just go down to the page bottom and click Save — scroll carefully not to miss it!
Wiki fail #2: Never change the format!
OK, you realized that in Assembla world what you see is not what you get. Yes, they allow to change the format of Wiki pages from WISWIG to something more reliable like Textile or Markdown, but get ready — it applies to existing pages as well!
Yes, your pages are not readable anymore after that.
Subversion fail: No care about old customers
If you are stuck with Assembla and old-school SVN+Trak repository (like we do), you cannot add a new nice Subversion repository — you are supposed to kill the old one first. You cannot do that without having your code gone.
One work around is to stop development for a few hours, export the old repository to a file, cross the fingers, kill the old one, add a new Subversion feature, then import the repo file.
Another way is to start with a new fresh space, although, might be not an option for those who has a simple plan.
Time feature fail #1: Date filter
Filter by one date (starts and ends the same day), and as result you’ll see time tracked for a day before that. Very “useful” when you half way finishing to make a report in a spreadsheet and realize that dates are wrong.
So, to check what you did today so far, you have to set dates in the future (so called “tomorrow”). If you set the dates wrong, you get this self-explanatory error message:
Time feature fail #1: edit a time entry
Filter your time entries, then edit or delete a time entry — and voila, your filter is lost! Nice how this application “cares” about your time.
The main question I would ask Assembla dev team — do you guys use your own tool for the project management?
I am becoming a fan of Domain Driven Design (DDD).
Here is a fun idea how DDD could look if you come to a pub to play a billiards game.
You are asked which game exactly you are going to play; so you say “pool”. As result you get a pool table and a pool rules agreement. This is an abstract factory.
The balls are numbered and colored. Black ball has a custom behavior. Since they all have an identity, they are entities.
As for the billiard cue — it’s a bit trickier. If the cues have different size, and you prefer to play by your own one, it’s an entity. Although, if you are drunk and don’t care about the stick you are playing with, it’s a value object.
A small pieces of chalk is a value object — any one works. The adjustment triangle is a value object too.
The rules of pool is a domain service.
The kick, the chalk break, the balls setup — all these form a infrastructure service.
--enable-id64 mean you want to support really long integers as document IDs, depends on your application needs
--with-mysql – fix the path to the file
5. Run this command:
Check the response, there must be no errors. Mine ends like this:
...[scary looking C commands]...
Making all in test
make: Nothing to be done for `all'.
Making all in doc
All docs are already pre-built by developer.
If you want to rebuild them, install docbook-xsl
and xsltproc and then run 'make docs' instead of simple 'make'.
make: Nothing to be done for `all-am'.
6. Run this:
sudo make install
7. Test if all is OK. If you run this, you must get a list of parameters of this tool:
You can always have the player visible in 3 easy steps.
1. Create a bookmark of current page in your browser (Google Chrome in my example, but it doesn’t really matter).
2. Right-click on the bookmark and choose “Edit…” menu item.
3. Replace the bookmark URL with this snippet of code and click Save:
Default values — how trivial this hint might seem…
Although, simple things make life easier. If you have a huge amount of SQL updates in your system, having correct default values helps to build smaller queries.
Also, when playing with data in your PhpMyAdmin, you can afford to focus on what is really important, not on repeating the boring staff. Every time when you have a big table and need to paste a couple of new records manually, you or the pear developer will be thankful that the majority the fields can be just ommited in order to have the proper and meaningful value.
It can be zero for numeric types, current date and time value for timestamp, a most frequent and meaningful value for the ENUM field or a “magic constant” of default value if you have to use one in your application.
You might be surprised, but a right choise of the project text encoding can affect the project file size and amount of bugs.
To avoid bugs of wrong presentation of text on your page, make sure that all database entities and the application server (PHP) use the same encoding. That helps to forget about issues connected with text presentation.
On database side, make sure you set the correct encoding to:
import-export tools parameters (a big source of wrong encoding bugs),
corresponding SQL server variables
On application server it’s usually just one query –
SET NAMES utf8
Pay attention, that utf8 might be not the best choise for your project: every non-English character needs 2-6 bytes of memory, so if you built a one-language (local) project with lots of database data, consider using a 1 byte encoding like windows-1251 and save about half of the space on server file system.