Forum Replies Created

Viewing 15 replies - 211 through 225 (of 266 total)
  • Mark

    (@delayedinsanity)

    Glad to hear it’s working! I should have mentioned somewhere in the installation or faq that I was removing that feature; if anyone else mentions it I’ll make sure to upload a new readme.

    Mark

    (@delayedinsanity)

    Do you see a “Get Shortlink” button underneath the title of the post/page? WP Bitly integrates with WordPress and tries to use the built in features where possible, as opposed to adding it’s own GUI elements.

    It used to be in an input field you could copy and paste it, down the right side of your edit posts page, but since there’s now that “Get Shortlink” button it seemed redundant to keep it.

    Mark

    (@delayedinsanity)

    I apologize that it’s not working for you! It seems no matter how many environments you test on, there’s always one more that doesn’t work.

    Sorry to ask a silly question, but did you make sure to update the legacy API key with the newer OAuth token provided by Bitly?

    Mark

    (@delayedinsanity)

    Well we need to get it working for you again!

    I would recommend taking that image down, considering anyone can use your token to authorize their connection.

    Want to know what’s really strange? It validated for me.

    So now we need some other information… what version of WordPress are you running? If you could put up a <?php phpinfo(); ?> page somewhere private and email the URL to mark -at- watero.us, that information would be a huge help as well.

    Mark

    (@delayedinsanity)

    Some major updates are in the works for the plugin, some of which will hopefully make this even more beneficial to your site. For instance our css stylesheet currently overrides a lot of local styles, and it could definitely do from being allowed to integrate with a sites styles a little more.

    In this case, the css is your issue. You’ll find a file called lddbd_style.css in the root folder of the plugin. Open this and navigate to line 105, near where you see the following;

    #lddbd_business_directory{
    	position: relative;
    	overflow: hidden;
    	min-height: 300px;
    	font-size: 16px;
    }

    Remove the line that says overflow: hidden;. There’s one more, now go down to line 261, and find;

    #lddbd_business_directory_body{
    	position: relative;
    	overflow: hidden;
    	/*max-height: 2000px !important;*/
    }

    Remove the same line again, overflow: hidden;

    This is going to overlap the form on top of your footer, but that’s better than before. Let me know if that works for you.

    The reason it still overlaps is that currently all those pages are generated behind the scenes and the browser has no way of understanding how long they’re all going to be. This is another feature we’ll be adding, where each major function is separated on to its own page, improving usability and SEO.

    Mark

    (@delayedinsanity)

    Version 2.0 shouldn’t have any glaring conflicts with the Jetpack module. In fact, it quietly disables the module if it comes into contact with it; I intend to have future versions notify you, but I’m under the impression that if you install WP Bitly, chances are good you intend to use it in place of Jetpack’s module.

    I’m going to mark this resolved unless I hear back from you that there’s any further issues. Feel free to also file new issues at https://github.com/mwaterous/wp-bitly/issues

    Mark

    (@delayedinsanity)

    @hayesmd is correct, thanks for the help!

    Mark

    (@delayedinsanity)

    @hayesmd, that feature was lost in a rewrite, but it can definitely be brought back, and soon. If you notice anything else about the update you’d like to see, just let me know and I’ll most likely add it to the list!

    Mark

    (@delayedinsanity)

    If the field is still red, it didn’t validate the OAuth token (as I’m sure you’re aware). Double check that you pasted the token from Bitly in it’s entirety and that there isn’t a missing character at one end or the other.

    Throwing a random thought out there, check to make sure there aren’t any extra spaces at the end of the token too. If there are, remove them, and let me know if that was the case!

    Mark

    (@delayedinsanity)

    Having the exact same issue. Is everyone here using Chrome? It seems their WordPress.com connect feature worked for me in FireFox but when I attempt to access either Akismet or Gravatar in Chrome it just refreshes the login page.

    Over, and over… and over.

    …and over.

    Mark

    (@delayedinsanity)

    This will be in 2.0.0, everything is being properly coded with i18n in mind. Future releases may have more functionality for directly editing the labels through the admin, but to start language support is being taken into account as a must have feature.

    Mark

    (@delayedinsanity)

    Fixed in the upcoming release. Emails will only be sent when listings are added through the front end!

    Mark

    (@delayedinsanity)

    This is being fixed in the next release. Everything has been migrated to using custom post types and taxonomies, which will permit direct links to all your categories and listings.

    Mark

    (@delayedinsanity)

    This is fixed on my local development trunk. The plugin will be better integrated with the media capabilities already provided by WordPress core in the very next release.

    Keep an eye out for this in the next week or so!

    Mark

    (@delayedinsanity)

    I’m trying to reproduce the issue you’re having, but I haven’t had any luck as of yet. None of my listings are returning 404 errors, and your URL for accessing them is correct. I even tried editing an ID that didn’t exist and it’s still showing the edit screen (which is an issue for a different conversation).

    Out of curiosity, what other plugins are you running? Just to rule out whether or not they’re conflicting somehow.

Viewing 15 replies - 211 through 225 (of 266 total)