Forum Replies Created

Viewing 15 replies - 31 through 45 (of 554 total)
  • Plugin Author Peter Booker

    (@peterbooker)

    Hi JulBolt,

    This issue is now resolved, I am sincerely sorry for the length of time that it lasted.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi danes73,

    This issue has now been resolved, I am sincerely sorry for the length of time it lasted.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi techdoncf,

    This issue is now resolved, I am sincerely sorry for the length of time this issue lasted.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi Emily,

    There is currently no inbuilt way to customize the colors, via shortcode or widget. I designed it with the intention of seamlessly matching the users theme, however my opinion on color controls has shifted recently, so I have a task to add control of the colors in the future.

    In the meantime you can add CSS to your theme to easily control it, this will change the link colors to match the heading color at the top of the popup.

    .stb-content a {
        color: #03ADEF;
    }

    Regards,

    Peter

    Plugin Author Peter Booker

    (@peterbooker)

    Thank you for letting me know riasnelli.

    I am now working on a more distributed setup, with automated tests so that I can pickup on errors and or failures much easier. I am very determined to ensure that a repeat of this does not happen again, no matter what my personal situation is.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi I r,

    I don’t believe that is a memory leak, but that line does perform a json_decode on the Tweet data which possibly uses a considerable amount of memory. Looking at that error around 50mb does not appear to be a huge amount, but I have marked the code in question and will see if I can replace it without using such a costly function.

    I appreciate you bringing this up, as I would like to make the code as efficient as possible and there is likely much room for improvement here.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi guys,

    I have just updated the plugin (1.5.8) to use a new URL for linking Twitter accounts to the plugin. It should now work as expected, but please let me know if you have any more problems.

    I am sincerely sorry for the long period of time the plugin was not functioning properly. I took an unexpectedly long time away from work to deal with personal issues and none of my automated service checks picked up on this problem.

    The original service was put together as a test of the theory and not designed for long-term deployment, which left me with a difficult choice. Did I attempt to debug the code and identify where it had broken, or rewrite this particular function into a separate service. I chose the later and in hindsight that was a mistake.

    I don’t plan on getting this behind ever again, but if I do I have learned that I should focus on the most immediate fix.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi Becky,

    I thought this would be a lot easier to troubleshoot. I cannot preproduce this behavior on my test installs, it always properly enqueues the stylesheet on WooCommerce pages.

    I am digging through the WooCommerce code to see if I can find anything which might conflict with how I am enqueuing the files, but this might take a while.

    I will let you know as soon as I find anything.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi Becky,

    Sorry for the slow reply. I have worked out that the problem is caused by the plugin not enqueuing it’s stylesheet on the WooCommerce pages. I have not yet been able to work out why this is happening though.

    None of the obvious things seem to be an issue, so I am going to dig into WooCommerce this afternoon (I don’t use it much personally). I will be back as soon as I work out why the stylesheet doesn’t get enqueued.

    Thank you for letting me know about this, I am sure it has been effecting many other people.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi musicscramble,

    Sorry you are having problems with the plugin. I will have look at reproducing this problem to understand why it might be occurring and get back to you.

    Thank you for letting me know and showing me the error messages, that will help me avoid this happening for you and others in the future.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi BHT Design,

    Thank you for the support, it is great to see the plugin live on a website!

    I am having more teething problems with the next plugin Kebo Social than I had expected. Once I get that plugin stable, I will be able to introduce the second version of the Twitter Feed plugin (which will include multiple accounts). At the moment that looks like it will be around 2-4 weeks time, unless any other large issues crop up during that period.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi tallboy,

    I had a feeling this had come up before. Early on this was an option on the plugins options page. However, it was pointed out that it should be for each instance separately.

    I removed it from the plugin options page, then faced issues about making the Widget options too cluttered and it being difficult to set in Shortcodes.

    I will work this into the Widget/Shortcode soon, thank you for the feedback.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi willc0de4food,

    I wanted to update you here instead of Twitter as 140 characters really isn’t enough.

    I had assumed that my script was incorrectly sending the wrong compression type in some rare cases. What I found was that it was actually always sending the appropriate format of compression, but only when the client server supported ‘deflate’, instead of checking for deflate and gzip.

    My assumption at the moment is that there is either an intermittent bug in the compression support or that it is possible for some servers to display compatibility through the Accept-Encoding headers, but not actually be capable of decompressing the data.

    I have tried switching to PHP (instead of the Web Server) to handle the compression, however this resulted in more problems than before.

    At the moment I am left needing to do a lot more research until I can pin point whether this problem is caused by the compression on my servers or the ability to decompress on client servers.

    I don’t think this is something I will be likely to resolve in the short term, so it is probably better for you to find another solution which works on your current server for now.

    Sorry you have had problems using the plugin, but I will continue to debug this issue until I can resolve it permanently. It will help me to improve this service and others in the future.

    Plugin Author Peter Booker

    (@peterbooker)

    Hi tallboy,

    The plugin currently uses the format set inside WordPress under Settings -> General. Would you prefer to be able to edit is separately?

    Plugin Author Peter Booker

    (@peterbooker)

    Hi aarondub84,

    Thanks for that, I had a look and have some custom CSS which will fix the display issues, I don’t like using !important in CSS but it is the only way to overwrite your themes rules:

    .kebo-tweets p {
        color: #fff !important;
    }
    body .kebo-tweets a {
        color: #fff !important;
    }

    If any of that doesn’t make sense or you have problems let me know. I hope that helps!

Viewing 15 replies - 31 through 45 (of 554 total)