Forum Replies Created

Viewing 15 replies - 226 through 240 (of 266 total)
  • Mark

    (@delayedinsanity)

    I’ve taken note of this request, and added it to my to-do list. I think the best way to address this issue is by ensuring the country list is fully configurable, and making it possible to edit the labels on the address fields (ie, changing zip code to postal code where necessary, etc). It looks like a second address line might be a good idea as well.

    If all you want to edit internally is to change the labels (pardon the current condition of the code!), you can do this starting on line 275 of the file lddbd_display.php.

    Please feel free to let me know if you have any further ideas for consideration!

    Mark

    (@delayedinsanity)

    Currently this isn’t included in the plugin functionality.

    Don’t worry however, this is actually one of a number of updates that are coming to it in the very near future. I’m working on updating the plugins framework right now, watch for the release to come out sometime in the next week or so!

    Mark

    (@delayedinsanity)

    If I’m understanding your question, yes you should be able to use the bit.ly short link in a QR Code as soon as one has been generated. Even if you change the URL in WordPress, a redirect is automatically created so it will continue to forward to the correct page.

    Mark

    (@delayedinsanity)

    I had no idea wp-bitly was in any way associated with Jetpack… I think what may be happening is it’s overriding Jetpack’s short link generator. I’ll have to look more closely at how they’re doing that, because back in the day I included some code to make sure WP Bit.ly didn’t collide with the WordPress.com statistics plugin.

    I am working on rolling out an update right now that will bring it fully current with 3.8.1 – that’s my first goal prior to adding any new features to it.

    Give me a few days! I’m not as fast at addressing issues due to my current employment, but I want to make sure your problem is resolved. I should have an update ready by this weekend.

    Mark

    (@delayedinsanity)

    I don’t see any reason why it shouldn’t be.

    I’m just coming off an extended sabbatical, but I wanted to let you know I have seen this question. As soon as I am back up to speed I will pop back in here with a solution for you.

    Mark

    (@delayedinsanity)

    @wizastudios, my apologies for your lack of response on this subject. I’ve been out of the game for the past two years, pursuing another line of work. I realize this was a mistake now, and I’m returning to pick up where I left off if that’s possible.

    This plugin will be one of my first projects for rehabilitation. Could you expound a little more on what your issue is? Are the two plugins conflicting in a way that causes erratic behavior?

    Thread Starter Mark

    (@delayedinsanity)

    I discovered the problem was with urls that didn’t have the protocol. http://site.com/ would work where site.com would wind up with the blog url prepended and return the expected 404. The fix was a quick SQL query to add the protocol.

    This is a pretty impressive plugin, to say the least. I think the next version could benefit from being able to recognize custom field urls without the protocol and check them appropriately!

    Mark

    (@delayedinsanity)

    Same problem.

    If anybody here needs a temporary fix while the author works it out, open your headspace.php file and look at lines 98 and 99:

    function wp_dashboard_setup() {
                    if ( function_exists ('wp_add_dashboard_widget'))

    Change line 99 to read:

    if ( true == false && function_exists ('wp_add_dashboard_widget'))

    and it will disable the dashboard widget that’s causing the conflict. The next upgrade will automatically overwrite this, so no worries about remembering to remove it! HTH

    Mark

    (@delayedinsanity)

    There are two ways to fix this bug; the first is recommended as it will avoid future conflicts with other plugins as well as provide you with a more secure platform to run your site on.

    1) Upgrade WordPress! Version 3.0.1 is out, and work has begun on 3.1 — you are putting yourself at risk running an older version of WordPress, especially as old as 2.8.6 which was released over a year ago now. This will not only fix the bug you are experiencing with my plugin, but will set you up to receive additional important updates and ensure that you do not run into any problems with other plugins.

    2) There is a little less legacy support than I originally thought built into the plugin. You will have to wait a couple days while I write a few bug fixes, as the conflict extends to the options page as well. If you’re in a rush, option 1 is your best bet.

    Mark

    (@delayedinsanity)

    The easiest method to do this would be the following;

    the_shortlink( wp_get_shortlink() );

    Alternatively if you want to ensure that any occurrence of the_shortlink() will default the text to the actual short link itself, you could do the following;

    add_filter( 'the_shortlink', 'my_shortlink', 10, 4 );
    function my_shortlink( $link, $shortlink, $text, $title )
    {
    	return '<a rel="shortlink" href="' . esc_url( $shortlink ) . '" title="' . $title . '">' . $shortlink . '</a>';
    }

    hth!

    Mark

    (@delayedinsanity)

    Which version of WP Bit.ly are you currently running? There may be a conflict with the way it is written and WP2.9.1 as I just tested it on my local copy of 3.0.1 without encountering this.

    I would suggest upgrading WordPress to 3.0.1 for starters, if you are still encountering the problem after this or for some reason are unable to upgrade I can install a local copy of 2.9.1 and test it to see if we can’t track it down and fix it.

    Mark

    (@delayedinsanity)

    I just took a quick look – I added a deprecated.php file to maintain support for pre-3.0 versions of WordPress but I fudged one of the methods and I’m almost positive this is causing your issue. Is there any reason you haven’t upgraded your copy of WordPress? It’s known to work on 3.0 quite well according to other reports.

    PS: Apologies for the slow response. It’s been a hectic week and I’m traveling a lot right now.

    Mark

    (@delayedinsanity)

    That’s interesting, are you running it alongside CakePHP by any chance? Cake is the only other place, and actually where I got the idea for my pr(), prd() and vrd() debug functions.

    That aside, I apologize for leaving that code in there without wrapping it in function_exists() calls, but if you open the wp-bitly.php main file and scroll down you will see a comment that says // DEBUG, TO BE REMOVED – delete this and everything below it and the plugin should activate for you.

    Thread Starter Mark

    (@delayedinsanity)

    I noticed there are other problems with the media-uploader facility, though none of the items on the list or in other threads (that I’ve found) pertain to thickbox breaking.

    Mark

    (@delayedinsanity)

    This has been fixed and released with 0.7.4. Sorry for the delay!

Viewing 15 replies - 226 through 240 (of 266 total)