Wordpress twitter plugin - twitter

I was using a wordpress plugin "Twitter for Wordpress" located in wordpress plugins directory then it seems to suddenly stopped fetching my tweets showing "No public Twitter messages".
I went to the plugin url and find that the demo showing the same error message and I tried to contact the developer for code update as this plugin hasn't been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress with no success.
As being not familiar with PHP I am asking anyone who may assist me with code modifying so that the plugin could back to work.

First of all, can you look at plugin configurations or inside PHP code for Twitter resource URLs? Since Twitter has dropped version "0", legacy code is probably the issue.
See https://dev.twitter.com/docs/api/1.1
Else, you should look at another plugin solution. Twitter is always improving, you need a plugin that follows updates

Related

Aspnetzero - Publishing .NET Core 2.0 version question

I just published my Aspnetzero solution to my hosting provider site.
I have multiple apps setup on my website. They are located in the example.com/apps/app1 folder structure.
So my aspnetzero site is on example.com/apps/aspnetzeroapp folder.
As I expected, this is breaking all of the URL references (Images, nav menu links etc.) on my published app.
I have updated the appsettings.json files with the URLs as shown below.
"App": {
"WebSiteRootAddress": "https://example.com/apps/aspnetzeroapp/",
"RedirectAllowedExternalWebSites":"https://example.com/apps/aspnetzeroapp/"},
Question: Can someone tell me all the changes, within the aspnetzero template code, that I need to make in order for my app to work given the above folder structure?
Update: I found this thread on the ABP support forum. I am having all the same issues with images and API endpoints. In that thread there is a link to a GIT code repo for a fix that was implemented by the ABP team. I cannot see it as I don't have an active license. Could that solution apply to my issue?
I decided on the easier option. I setup a new domain and deployed my app at root of the new domain. Its all working fine now!

How to do restful search in Apache Sling

i am evaluating Apache Sling as a potential backend CMS. I like how easy it is to push / get new content via rest. However, I also need to be able to search the content via REST. I compiled all the source code and am running their standalone jar. There are like 100 bundles installed, but I can't find a single rest query.
Some old documentation says you can do /content/mynode.query.json?
But this is not working, and there is no help on whether its supported or not. Honestly the only search option I found was in the console via /.explore.search.html/ which returns web pages.
How can you do restful search using sling?
The JsonQueryServlet, which provides an HTTP search interface was moved to a separate bundle as part of SLING-2226. See that issue's page for how to use it, and there's a related blog post at http://in-the-sling.blogspot.ch/2008/09/how-to-use-json-query-servlet.html

Recaptcha for .NET MVC having more trouble with SSL

I'm attempting to get Recaptcha for .NET working with ASP.NET MVC 4.0 on an https site that is using SSL. I've been reading up on it and the problem seems prolific, but I'm having a hard time finding a solution.
I've seen this related topic here Stackoverflow Question and it did not solve the problem. I am following the documentation here : RecaptchaNET Documentation
I have made an ad-hoc solution work by running the page in non HTTPS and just copying and pasting the raw HTML code, and changing the various URLS. But I'd like to make this work with the actual HTML helper. Can anyone help? Has this changed since that original topic?
There are a few posts about this out there for the change google made to the api. Basically, RecaptchaNET wasn't supporting google's latest api endpoints for this.
If you check your version, this is fixed in version 1.3.
Try downloading the latest version from CodePlex and using that dll.
or the nuget here.

My Twitter api is not working suddenly

I have a web application which uses twitter api. It was working fine.But suddenly it stopped work. I started googling & came to know about that twitter upgraded their api. So I need to use the library which supports v1.1
Have anybody worked with v1.1 library please help me
Thanks in advance.
Take a look at this project on GitHub. Don't be confused by the title - it has been updated since Twitter's API update to 1.1.
The jQuery plugin on the page has been re-purposed to be a Rendering engine, i.e. it helps with rendering your feeds.
The important part, however is in the "Server-Side Examples and Setup" directory. Go there, read and follow the directions in the SETUP_INSTRUCTIONS document. When you are done, if you are using PHP, use the file in the "Plug_And_Play" directory as a start point. If you are using C#, you can use this library. It is still under development, but it is updated regularly and mimics the Twitter API's specifications as closely as possible.
P.S. I am the author of both of those projects, so if you need any help, let me know. Good luck! :)

Pins on Pinterest link to 404 - yet link is valid

this is a really strange one.
I've set up a bunch of pins on Pinterest linking through to our services which all work fine. Then I decided to do the same on our blog articles (we use Wordpress), yet everytime I click the link (and I've done this on different computers) the link goes to a 404 page on our site. However the link is valid and if you right click the pin and open in new window it opens fine: pinterest.com/pin/105342078755648946
I have contacted Pinterest who are next to useless. I have also tried different browsers, different computers and different Pinterest accounts.
I can't see any weirdness in my htaccess files causing this so I'm a little stumped. Any suggestions?
I found this when I was searching for the same issue - so though it's an old question I thought I'd answer for anyone else who is searching!
My client was using a really old version of WordPress, when I upgraded to the latest version it fixed the issue. After a bit of digging it turns out you have to be on WordPress 1.5.2 and beyond in order to fix it - as they applied the fix in that update.

Resources