I am following the qooxdoo tweets tutorial and in the part 3 it's seem the public timeline url is dead.
Is there another url or we can retrieve the data to perform the tests
It seems that this location got lost when we migrated the website from 1&1 infrastructure, BUT you can find the respective file here ...
https://github.com/qooxdoo/qooxdoo/blob/branch_5_0_x/component/tutorials/tweets/step4.5/source/resource/tweets/service.js
I will fix the tutorial.
Related
Im currently working on my backend for my website and Ive found that I need an index html. As I've done my front end in react (on Vscode) do I just copy and paste the exact same index html code I've already done in react in spring boot?
On my index page there is a search bar where users will enter text and I will pass it through to my algorithm that I've created in spring boot on eclipse and then the result will be returned on a new page. I've searched how to do this but a lot of the examples are more to do with saving items entered into a database. Im assuming I will need a controller which I have made that will link to the index page? But I don't know what else comes after that This may seem trivial but I am a complete beginner. Thanks in advance!
The class named review.java is my algorithm. I read that I probably need an entity, repo and service but I am unsure what goes in them. Ive attached my package explorer. Sorry if this a very basic question.
package explorer
I am working on integrating a 2sxc content WebAPI feed into a ReactJS application.
I have managed to get a JSON feed of data into the application, and am in the process of mapping out the data.
I'm wondering what the best practice would be to "resolve" a URL which is coming through as a DNN Page/ Tab ID.
Below I will showcase the various points this is referenced...
First the Setup of the entity / data types...
Then this is an example entry with the data filled out... The page link / URL is set up to point to another internal page on the DNN website:
Finally you can see this data item come through as a JSON feed via the 2sxc API:
What is the best way to convert this piece of data into a URL which can be used in a SPA type application?
There isn't any "server-side" code going on, just reading a JSON feed on the client side...
My initial idea would be to parse this piece of data in JS, to extract the number then use something like this:
http://www.dotnetnuke.com/tabid/85/default.aspx
http://www.dotnetnuke.com/default.aspx?tabid=85
I was hoping someone with more experience would be able to suggest a better / cleaner approach.
Thanks in advance
If you were server-side in Razor you'd be doing something like this:
#using DotNetNuke.Common
View List
XXXX = Dnn.Tab.TabID or define a string with the tab id you want
I seem to have a vague memory that I saw somewhere that Daniel (2sxc) has a way to use Globals.NavigateUrl() or similar on the client side, but I have no idea where or if I did see that.
The Default.aspx?tabid=xx format will certainly work, as it's the oldest DNN convention and is still used in fallbacks. The urls aren't nice, but it's ok.
The reason you're seeing this is because the query doesn't perform the automatic lookup with the AsDynamic(...) does for you. There is an endpoint to look them up, but they are not official, so they could change and therefor I don't want to suggest that you use them.
So if you really want a nicer url, you should either see if DNN has a REST API for this, or you could create a small own 2sxc-api endpoint (in the api folder) just to look that up, then using the NavigateURL. Would be cool if you shared your work.
I am migrating an existing ASP.NET Web API 2 project to ASP.NET Core. While migrating I am unable to find this.Request object. Can anyone help me solve out this issue?
This question was asked here, but since ASP.NET Core was still probably in an RC state then, I figured I'd answer here instead of referring to there because there is some stuff that's obsolete or completely gone from the official release.
Assuming your controller class inherits from Controller (or more specifically, ControllerBase) then it does have a this.Request property as you can see here and here. As Pawel noted, you can also access it from the this.HttpContext property.
The request's URL is broken up into several properties on HttpRequest. You can access the URL in a friendlier API by adding using Microsoft.AspNetCore.Http.Extensions; which gets you access to the following extension methods:
GetDisplayUrl()
GetEncodedUrl()
As far as the query string, HttpRequest provides QueryString and Query properties for you to interact with.
Side note: I just created an app from scratch targeting ASP.NET Core on .NET Core for the first time on this laptop, and it took a while for the Intellisense to work for the Request property, so I'm wondering if that could have been your issue.
You need to override your class like this to get this.Request
public partial class _Default : System.Web.UI.Page
I don't see any updated answer on similar topics (hopefully something has changed with last crawl releases), that's why I come up with a specific question.
I have an AngularJS website, which lists products that can be added or removed (the links are clearly updated). URLs have the following format:
http://example.com/#/product/564b9fd3010000bf091e0bf7/published
http://example.com/#/product/6937219vfeg9920gd903bg03/published
The product's ID (6937219vfeg9920gd903bg03) is retrieved by our back-end.
My problem is that Google doesn't list them, probably because I don't have a sitemap.xml file in my server..
In a day a page can be added (therefore a new url to add) or removed..
How can I manage this?
Do I have to manually (or by batch) edit the file each time?
Is there a smart way to tell Google: "Hey my friend, look at this page"?!
Generally you can create a JavaScript - AngularJS sitemap, and according to this guidance from google :
https://webmasters.googleblog.com/2015/10/deprecating-our-ajax-crawling-scheme.html
They Will crawl it.
you can also use Fetch as Google To validate that the pages rendered correctly
.
There is another study about google execution of JavaScript,
http://searchengineland.com/tested-googlebot-crawls-javascript-heres-learned-220157
Im migrating a wicket webapplication from wicket 1.4 to wicket 6.8.
Im having some problems with the bookmarkable/non bookmarkable implementation introduced in wicket 1.5.
The application now adds wicket/bookmarkable to "bookmarkable" pages when setresponsepage is called. it does not matter if i provide a class or an instance of a page. My applications keeps adding wicket/bookmarkable.
I dont want to have the wicket/bookmarkable prefix in the url. I have tried to make a new implementation of imappercontext to override these prefixes. But i dont want them at all. Actually i dont bookmarkable pages in my application at all, besides some mounted pages.
Any ideas about how to remove this prefix?
You must mount page to remove wicket/bookmarkable in the url. Override the init method and configure on your WebApplication.
#Override
public void init() {
super.init();
...
mountPage(your_url, YOUR_PAGE.class);
}
I took a look at my code (we somewhat recently updated to Wicket 6.x) and did not notice it before, but I am also getting the 'bookmarkable' string in my url when I call
setResponsePage(SomePage.class);
however, in other places the link is set up as
setResponsePage(new SomePage());
and the 'bookmarkable' string is not included in the URL.
Hope this helps...