display posts shortcode broken

  • Unknown's avatar

    No you’re right. You are just making me very angry and upset. As I said before thank you for your help. You can stop replying now.

  • Unknown's avatar

    I am here to help and try my best to do that. I have been a Volunteer here for nearly 9 years and I predate all Support Staff members being on Staff except one and I even predate the support docs.

    I know that no one can make another person angry or upset, because that is a decision that is made between the ears. Maybe all you need to do is take a break and wait for Staff to respond to you.

    Staff work through all forum threads tagged for their attention and through all email support tickets in chronological order based on datestamps and timestamps – first posted first served, as would be expected.

    How long it takes to clear the threads and support tickets depends on how many Happiness Engineers are working on them at any given point in time. It also depends on how complex the issues in each thread and ticket are are.

    Please don’t bump your thread here by posting into it again because it’s not in your best interest to do that. Doing that moves the timestamps forward and it takes longer to get a response.

  • Unknown's avatar

    I could give a crap about the time stamp – what I am not willing to put up is being treated like crap when i am right to be upset about the problems I am experiencing and PS you are not always that nice to people who request support here. Your answers are sometimes rude and condescending and I said thank you for you help. You know all you have to do is make people feel like their concern is justified and not be argumentative because that is what helpful customer service actually is, and deterring people away by telling them to go somewhere else is a terrible answer, doesn’t solve the problem, and loses customers. I, like many people, am happy to be patient and nice in return for legitimate help, which actually addresses my concern. I appreciate your help but I’ve volunteered here too and I am not new and I am not gonna let you bully me for being rightly upset. And btw you are the one who keeps replying. I started this thread so stop battling me about this. People here deserve helpful support – not to be made to feel like it doesn’t matter. It does matter and it needs to be a concern to WP not just me, so if the people here aren’t going to act like its a problem when I had my entire site content stolen from me – you bet your ass I am going to make a huge deal out of it.

  • Unknown's avatar

    Maybe you did not understand me. Encryption is not yet available for domain mapped WordPress.COM blogs, but If you have a WordPress.ORG software install then this would not be an issue.

  • Unknown's avatar

    @timethief – listen to me… in no way am I not understanding you . What I do understand is that WP.com blogs are vulnerable to theft and attacks and this IS NOT OK. Most users don’t realize that they do not recieve the same encryption they would if they had bought their domain elsewhere because that is not disclosed in the support doc which says “want your own domain – absolutely!” – like myself I was not aware of this until after I had already established my site and domain and the real point is that if the servers where everything is kept for us bloggers is not secure that is not freaking acceptable. My entire site has been duplicated and these security issues are not just a problem but threatening to wp.com users so I don’t care what you are saying about the encryption blah blah blah IT IS NOT ACCEPTABLE – period and someone needs to do something about it. WP has been saying they are working on it for years now (I know because I have searched the threads). When looking at the console for the site that has stolen my content – it appears to be some kind of wp remote login but who knows exactly how they have stolen it. I’ve changed my login, etc. the point is WP is vulnerable to attacks and theft and there is nothing acceptable about that – so someone has to do something, not in another year – NOW. And I am going to continue to raise hell about this until it is rectified.

  • Unknown's avatar

    Telling me to go to wp.org is not a solution to this problem. If WP.com can’t make the services secure then they should not offer them in the first place.

  • Unknown's avatar

    Hi there,

    We’re now discussing a couple of different items, one of which was from your other post. It’s important to realize that the interface that you found was someone’s proxy. A proxy is a means by which users (usually in places which have severe internet restrictions) can view other sites online. It isn’t a matter of them copying your site. Instead, they have set up a system which allows them to view the entire internet from one webpage.

    As an example, they can view the popular tech news website, The Verge (hosted on WordPress.com)
    http://quia.cf/orange/pooxy4/nph-poxy.pl/es/30/http/www.theverge.com/

    Or they can view Reddit (most definitely NOT hosted on WordPress.com):
    http://quia.cf/orange/pooxy4/nph-poxy.pl/es/30/https/www.reddit.com/

    This has nothing to do with whether or not your site has an SSL, as clearly even reddit can be viewed with their SSL in place (note the https in the url).

    At present, I am unable to find any part of your site which is throwing security errors or links which are incorrectly linking to https version of your custom domain (all links to snappingtwig.com should link to http. If you did not have an SSL, then all links would go to https://snappingtwig.wordpress.com).

    While I agree that we have certainly been saying that we’re working on implementing SSL coverage for domains for a long while now, it also does happen to be true. I’m afraid I’m not able to go in to details, but the immensity of implementing stand-alone SSLs for millions of different sites in a multi-datacenter and load-balanced environment is somewhat mind-boggling. We want to make sure it is done right and so that users and viewers have the most positive experience possible when it does go live. As things are now, the base of your site is fully encrypted. If you’d like, you can set snappingtwig.wordpress.com as your primary domain and allow snappingtwig.com to point to it. That way absolutely all interface on your site will be encrypted. Sadly, until we are done rolling out custom-domain SSL encryption that is my only suggestion.

  • The topic ‘display posts shortcode broken’ is closed to new replies.