JoeGermuska

If you created the spreadsheet, you should be able to find it using Google drive. If you can’t turn it up, the iframe code should include either the URL to a form of the spreadsheet, or a string of letters and numbers that is the Spreadsheet’s identifier.

If you just have the string of letters and numbers, you can plug it into this:

https://docs.google.com/spreadsheet/ccc?key=%5Bput it here]

and at least get a readable view. Whether or not you can edit it depends on which Google user created the spreadsheet.

This will work: https://docs.google.com/spreadsheet/pub?key=0AgIA0Cg1XUhUdFdOZzgxemN5WW9mR3VXQTY0cVlkMGc&output=html

The “source” attribute in the short code should be a link to a Google Spreadsheet, not to a finished timeline.

In your case, something more like
[timeline src=”https://docs.google.com/spreadsheet/pub?key=0AgIA0Cg1XUhUdFdOZzgxemN5WW9mR3VXQTY0cVlkMGc&output=html” width=”100%” height=”650″ font=”Bevan-PotanoSans” maptype=”toner” lang=”en” ]

?(I didn’t check the non src attributes

Can you send a link to the actual page where your timeline is not working?

Can you post a link to a page where we can see this issue? If the timeline is blank, that alone could have something to do with the formatting. But also, there are plenty of CSS things that may be unique to your site which our plugin may just not be able to do anything about.

I answered this by email, but that tracks down to a rule in your stylesheet creating a 1 px wide grey div before any div.container

Acknowledging that in the future we should choose CSS class names that are less likely to conflict with other people’s existing sites, in this case, you could make your rule more specific, or I believe you can make a rule like

#storyjs .container:before { background-color: inherit }

and solve this problem.

Your language file is 404: https://cl.ly/image/093z0t183W2F

I’ve traced this back to a bug which you can work around by changing the name of your plugin directory to not end with ‘js/’.

We’ve had some trouble keeping up with issues but it turns out someone reported this a while ago. I’ll probably implement the suggested fix, but in the meantime, renaming your plugin directory from “knight-lab-timelinejs” to “knight-lab-timeline” will get you going.

sorry, i misread your code — didn’t see it had both next and previous. So things are working for you?

you can use style selectors that don’t otherwise appear in the CSS. There may not be anything with what I wrote. I verified those values using the inspector tool in my browser.

.date is a child of .nav-container, so my rule changes the date and the title, while yours only changes the date. If it works for you, it works for you!

#storyjs-timeline is the outermost CSS selector. The ones you use are fine, although do you also want to control the .nav-previous ?

Jeff:

All the text on the timeline seems a bit larger than normal—almost like someone had used the browser’s “zoom in” feature a few times and hadn’t reset it for that domain. On a mac, that’s cmd-+ and sometimes pressing cmd-0 resets things correctly.

If the problem is just that your host page has an overall CSS rule that sets all of the type on the page larger, then you should be able to overcome that with a selector addressing “#storyjs-timeline” or if all you want is for the text in the nav buttons, then you can use “#storyjs-timeline .nav-container”

Yes, thank you. We’re considering this feature. StoryMap was designed very strongly with an eye towards storytelling, and it seems that in many cases collections of blog posts don’t actually group into a narrative in the way that StoryMap does best, but you’re not the only person to request it.

I’m not sure what you mean by wp-post integration.

The forum thread you reference was related to a third-party effort that wasn’t an official part of the TimelineJS project. I’m sorry, but we do not intend to support using Timeline as a WordPress post navigation tool in the foreseeable future.

I get these errors as well; and yet the plugin seems to work just exactly as it should. I’m using Sociable 2.0 and WordPress 2.2. I was able to customize it just as I wanted.

Give the developer a break. He probably has a job, and maybe even a life.

Are other people who are having this error finding that the plugin simply doesn’t work? For the person who didn’t see the share section, did you see that you can control which kinds of pages show it? By default, it doesn’t show on your home page, only on individual post pages.