Inserted reference links no longer linking to references

31 views
Skip to first unread message

Alex Turner

unread,
Sep 16, 2012, 4:11:55 PM9/16/12
to ann...@googlegroups.com
In order to solve the known bug with article content disappearing perhaps due to autosave (although changing autosave config didn't fix it) I grabbed the latest 1.02 annotum from github yesterday (commit 40c5e14f4354fa62aa72b823ac39476f3694c9d1).  That problem is fixed in the current code (thanks!!) but there's a new one that's not as much of a deal breaker but still pretty painful:  reference links in articles do not link to the references anymore. This worked in the official version. Here are some snippets from the output code of a test article, viewable via chrome page source:

The reference section:

<h1><span>References</h1></span>
<ul><li data-refid="1" id="ref1">ZxcZXcX</li>

The link, which appears to be seeking an anchor:

<p>ZXcZXc<sup><a class="reflink" href="#1">1</a></sup></p>

I don't see how #1 gets to either data-refid="1" or id="ref1". Entirely possible, I know, but main thing is it doesn't work for me.  Other annotum popups work for me in case it's trying to do a popup, and I do have adblock installed if that might be it. I can supply more info on request. I'm running wordpress/annotum from an ISP account using php version 5.3.16 . I also recently updated wordpress to 3.4.2

Is anyone else experiencing this problem?

Thanks, Alex

Carl Leubsdorf, Jr.

unread,
Sep 16, 2012, 9:37:27 PM9/16/12
to ann...@googlegroups.com
Are you talking about references created prior to installing the new code, or subsequent to it?

It wouldn't surprise me if you have to re-insert all the references (within your articles) after the code upgrade.

--
You received this message because you are subscribed to the Google Groups "annotum" group.
To view this discussion on the web visit https://groups.google.com/d/msg/annotum/-/Un4oSmktTTMJ.
To post to this group, send email to ann...@googlegroups.com.
To unsubscribe from this group, send email to annotum+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/annotum?hl=en.



--
_______________________
Carl Leubsdorf, Jr.
Solvitor ► Problem Solved.
+1 240 389 2255
ca...@solvitor.com


Alex Turner

unread,
Sep 16, 2012, 10:27:10 PM9/16/12
to ann...@googlegroups.com
Thanks for getting back so quick!

I knew I should have mentioned that. Yes, both. I tried creating a fresh test article to see if that would work, but no joy.  I should also mention it's not a "clean install".  I've had other themes on the blog in the past. But I could try that if you aren't seeing the same problem.

Also I'm using a subtheme that's just a pointer to the annotum theme, which I switched to the new version, and yes, I'm sure, because the deleted body problem went away and the appearance of the editor changed. I could try using the annotum theme directly to see if that makes a difference, or try making a fresh subtheme.  But what's the expected behavior for this github commit?

If I'm the only one seeing this I could also try forking it and debugging on my own. I've got PHPStorm. Not volunteering yet though :)

thanks, Alex

Alex Turner

unread,
Sep 16, 2012, 11:40:20 PM9/16/12
to ann...@googlegroups.com
Good news:  I tried a clean install and the reference problem isn't there. I noticed a difference that I *hope* isn't the problem -- the order of entry boxes in the editor is different, presumably because I moved them around the first time.  I tried moving them back to their original arrangement and that didn't fix it. 

A couple more notes about differences: I had work flow turned on, and related settings. Turning it off did not help.

No biggie, since we're just getting started, except our first article has 78 footnotes I'm going to have redo and in the circumstances I'm loathe to ship them over from the old installation via the database ... although I'm very tempted to just edit the content directly in there to spare a million mouse clicks.  As others have requested, a manual mode for editing would be very nice to have, even if with dire warnings.

Thanks again for making such a promising app available. We hope to do great things with it!

best, Alex

Carl Leubsdorf, Jr.

unread,
Sep 16, 2012, 11:52:13 PM9/16/12
to ann...@googlegroups.com
Use Chrome (inspect element, edit HTML) to directly manipulate the content. Consider the dire warning duly given! :)

Also, the meta box placement is stored with your user info. But you can try this to get to the defaults: https://gist.github.com/1186992 (but double-dire warning and use the right userid!!!)


-C

_____________________
Carl Leubsdorf, Jr. 

--
You received this message because you are subscribed to the Google Groups "annotum" group.
To view this discussion on the web visit https://groups.google.com/d/msg/annotum/-/V0EZifecv9YJ.

Alex Turner

unread,
Sep 17, 2012, 12:07:51 AM9/17/12
to ann...@googlegroups.com
I've used inspect element for a number of things, and love it, but it never occurred to me it could do that right in an editor! Great stuff. :)

Thanks again,

Alex
Reply all
Reply to author
Forward
0 new messages