Forum Replies Created

Viewing 15 replies - 91 through 105 (of 380 total)
  • Forum: Plugins
    In reply to: [Shashin] javascript error
    Plugin Author Mike Toppa

    (@toppa)

    I posted a message here a minute ago that I thought was the answer, but it wasn’t (I mis-read the jQuery version being loaded on your site). The forum doesn’t let me delete the message, so I’m putting this message here instead of leaving a blank post.

    Plugin Author Mike Toppa

    (@toppa)

    chule024: in the new version of Shashin I changed it so it loads its javascript in the page footer (instead of the head), which is better for performance reasons.

    Plugin Author Mike Toppa

    (@toppa)

    xemilix: Now that you’ve removed the other version of prettyPhoto, the javascript error message has changed, and I see what the problem is now. Your site is loading an old version of jQuery. It’s loading version 1.4.2, and Shashin requires version 1.7 or higher.

    I don’t know if it’s your own custom theme or not. The theme is loading jQuery from Google (and it’s pointing to an old version), which is not considered best practice for WordPress. There’s a lengthy essay on why here:

    http://pippinsplugins.com/why-loading-your-own-jquery-is-irresponsible/

    If you’re not a programmer yourself I recommend contacting your theme author, and ask him/her to change how the theme is loading jquery.

    Plugin Author Mike Toppa

    (@toppa)

    chule024: I think your theme is missing a wp_footer() call. This is an important WordPress hook that many plugins (including Shashin) rely on:

    http://codex.wordpress.org/Function_Reference/wp_footer

    xemiilx: this is not the problem with your site. Please answer my previous question and then I’ll check into further.

    Plugin Author Mike Toppa

    (@toppa)

    Were either of you using prettyPhoto with Shashin before I released version 3.4, and did you have another plugin that provided prettyPhoto on your site? Please let me know, as that will be a helpful clue.

    Plugin Author Mike Toppa

    (@toppa)

    So I’ve installed Yoast’s SEO (which is what I’m assuming you’re using to generate the Open Graph tags), and I still can’t re-create the problem.

    1.The Yoast plugin is providing an og:description tag on all my posts, and Facebook is using it. Your pages don’t have og:description tags – probably because of whatever you’ve done to turn off excerpts.

    2. I tried leaving the description blank for my home page in the Yoast settings (to force my home page to not have an og:description tag) and even then I can’t re-create the problem (Facebook is grabbing “Mike Toppa’s blog” from my masthead div as the description).

    It seems to me this is happening because your site isn’t fully setup to use Open Graph. You should have an og:description tag (as the Facebook debugger is advising you to do), or a meta description tag.

    Without those things, Facebook is scanning through the page content looking for something it thinks might be the page description. I don’t know what their algorithm is, but there must be something about the names of the shashin classes that it’s latching on to. Without being able to re-create your problem, I would be guessing blindly at renaming my shashin classes (and I’m not using “description” as a name anywhere).

    It seems to me that if you want to use Open Graph, you should supply it properly with the fields it’s expecting. Otherwise there’s really no predicting what it will try to use as the page description.

    Plugin Author Mike Toppa

    (@toppa)

    Did you switch themes? It looks like it’s not Oxygen currently. If you don’t mind temporarily switching back to Oxygen, I can take a look today and try to debug the issue.

    Plugin Author Mike Toppa

    (@toppa)

    Thanks for the debug link – that’s helpful. I did some Googling, and it seems that if you don’t provide an og:description tag (your site has other og tags, but not the description), Facebook goes looking for other tags on the page it thinks might have what it wants.

    Could you try temporarily switching to Fancybox on the Shashin settings page, and try it again? From what I read you may need to load the page in the debugger again in order to clear Facebook’s cache of your page. I ask because prettyPhoto has a div with a “pp_description” class, and the “view at Picasa” link is the only link inside that div. I’m wondering if Facebook is latching on to any tags with the word “description” in them. Fancybox does not have this div.

    Plugin Author Mike Toppa

    (@toppa)

    Thanks for checking into the feeds. Shashin is built around reading feeds, so unfortunately, if it’s not a feed, it can’t be added to Shashin.

    Plugin Author Mike Toppa

    (@toppa)

    You’re site isn’t loading the custom version of prettyPhoto that comes with Shashin. It’s loading a standard version that you have installed from a different plugin.

    Did you upgrade Shashin from an older version? Let me know. If so, there may be a bug I need to fix.

    Plugin Author Mike Toppa

    (@toppa)

    Sorry about that. I have an upgrade hook that runs on “admin_init”, which basically means that data property should get added the first time you load an admin page after upgrading the plugin. If you only went to a public facing page, then you would see that error message (it would be overkill to check for plugin updates every time a public facing page is loaded).

    The upgrade process is tricky because there’s hooks for plugin activation, hooks for upgrading though the automatic upgrade process, and (understandably) no hooks at all if you’re upgrading by installing files from a zip download (which is why I use the admin_init hook – it catches all cases).

    If you still see that error message after going to an admin page more than once after upgrading, let me know.

    Plugin Author Mike Toppa

    (@toppa)

    What you’re seeing is normal behavior for WordPress excerpts. They are designed to not run shortcodes. I did a search online and found a couple suggestions you may want to review (I have not tried these myself)

    http://www.cyberciti.biz/faq/howto-wordpress-3-adding-shortcodes-to-excerpts/

    http://www.visualserendipity.com/2013/05/how-to-enable-short-codes-in-post-excerpts-on-wordpress/

    Forum: Plugins
    In reply to: [Shashin] Album Title
    Plugin Author Mike Toppa

    (@toppa)

    Thank you for the details. I’ve found and fixed what I think is the problem. But I have not uploaded the change to wordpress.org yet. There are a couple other issues I’d like to look into first, before pushing another update (I don’t want to give people update fatigue). I’ll push the update probably this weekend or early next week.

    Forum: Plugins
    In reply to: [Shashin] Album Title
    Plugin Author Mike Toppa

    (@toppa)

    I just spent some time reviewing it, and I’m not sure what’s causing the problem with that album’s caption. The HTML for it is getting garbled on your page for some reason. When I add that same album on my computer, the caption for it appears fine and the HTML is fine.

    Could you let me know the exact shortcode you are using, so I can try that? Also, please try temporarily displaying them in a different order – I’m curious if it’s something to do with that album, or if it’s just whichever one is last.

    Plugin Author Mike Toppa

    (@toppa)

    What the validator is showing as errors are valid HTML 5 data attributes. They are showing as errors because your site is set to XHTML 1.0 Strict, which is a 13 year old standard. You’re asking me to not use any HTML 5 features. I’m sorry but I’m not willing to do that.

    I’ve tested it with IE 8 on an HTML 5 site and it works.

Viewing 15 replies - 91 through 105 (of 380 total)