I am using SMW with the Semantic Forms extension on my mediawiki instance. I have defined a form that can create a page in a definied namespace.
The form by itself is working very fine. But now I have importet a big set of pages (about 170k). And suddenly the form page isn't available anymore. So if I call it, it loads for a while and then it shows an empty page (even without any mediawiki frame, completely empty).
If I import just a few hundred pages, it does still work.
Now I ask myself, is there any known bug, that Semantic Forms has a problem with big sets of pages?
Thanks, J
Related
Say I have a product website, like Amazon (this is not the case, but it will help me explain my point), and I have a URL for every single product (such as with Amazon)...
Do I need to copy-paste and modify an HTML file for every single individual product page, or is there a way to use a "model" on which I can base all my other pages without recopying the whole code and modifying a few things in each?
I've just started learning HTML and web development, so bare with me if I'm asking a stupid question.
It just seems odd to me that a million-page website should host a million+ individual, nearly identical, HTML files.
Thank you very much in advance.
P.S. I'm using Amazon's brand name as an example here, and am not affiliated with anything related to it. Thank you for understanding.
No, you do not need an HTML file for every single page on your website. While you could do that, it is becomes very infeasible to manage the bigger your site becomes. On most websites you would have the following components:
A front end - consists of HTML code and usually some sort of template engine with placeholders for your data
A backend - consists of your data store (usually a database).
There will also usually be some form of API and/or middleware between your front end and backend.
If you go to https://example.com/myproductid in your browser, your computer will send that request to the web server. The web server will then retrieve your data, load it into the correct template, and serve the page to you.
In traditional HTML and PHP only websites, you would have to reload the entire page each time you went to a new product. However, you can instead use a technique called Ajax to only update certain parts of a web page rather than reloading the entire page. That way you can just update the text, images, and links that are specific to the product, and the rest of the page would stay the same. (Note: Ajax originally used XML, modern implementations usually use JSON).
Ultimately, you will want to learn some JavaScript and then start looking into various web frameworks or libraries such as ReactJS.
Not you Can have only one page for all product, but you have to make it Dynamic.
Yes you need an HTML document for your each webpage, like for Home page, contact us page you need different HTML documents
I want to know if it is possible to hide page(s) in Jekyll when pushed to production. For example, I have a page called crazy-toes that I'm currently developing. But have different edits/changes for other pages that need to be pushed live. Is there a way if someone types in their browser mysite.com/crazy-toes/ they go to a 404? I know there is the published variable for the Front Matters, but for multiple pages, it doesn't seem efficient.
You could store the page in Drafts.
I would like to be able to access a site's HTML in Wordpress in order for fine editing/customization. At the moment, to access the HTML of the page I am going to Chrome Developer tools where I can see all the html for the site in the bottom left-hand window.
But when I try and access it from the Wordpress dashboard, all I can find are files such as 'single.php', which are written using php loops and I cannot seem to trace where the original html elements are.
For example, for changing the number of columns in a contact form 'message' box.
Any ideas?
Wordpress is template-based. As you already mentioned there are templates such as single.php, content.php etc. In order to change the lay-out of the website (or better, the structure) you have to change the corresponding template. If you want to change the style, you have to edit the style.css of your theme.
If you want to change the HTML of individual posts or pages, you can simply click the "edit" button and instead of using the WYSIWYG editor, you can swap to a standard text editor.
Wordpress is very well documented. Here is a guide to get you started on editing files.
WordPress, like pretty much any popular CMS, produces its HTML by combining three basic factors:
The active theme
The enabled plugins
The stored content
While the latter is merely data stored in a database, the other two are responsible for deciding what to pull from the database, how to filter it and how to render it.
So the final HTML your browser receives cannot be a subject of arbitary manipulation. You can change some things by developing your own theme, some others by installing or building extra plugins but not the final, dynamically-produced output.
Consequently, I highly doubt there will ever be a plugin that gives you the opportunity to do what you ask.
I'm actually very new to Web Page Development and would like to have a simple (offline) HTML page displaying in a Control or Browser itself.
Target is to make a log viewer page, which is constantly updating through another application, (which I'm writing in C# plus some Powershell coding).
It might be divided into frames containing different pages, or one page containing different areas.
Main purpose is to update the changes immediately. E.g. If you are viewing the web page, and my application change the Text at some areas of that page, it should detect the change and immediately update that area.
How to achieve this? Is HTML 5 got any such methodologies which are easy to use?
I'm open to any suggestions... And thanks a lot in advance...
You can't do this with HTML5 as far as I know.
To create the Dynamic log viewer page , you can use ajaxticker.js.
It is easy to use..
Ajaxticker Tutorial and Demo
I am newbie to Jquery Mobile, so far what ever examples i searched contains only one html page for whole application, with multipe div tags where each page/screen is defined as div tag with data-role as page with some header and footers optionally. Based on user actions, we are hiding some div's(pages) and showing only expected page. Also, this multi-page template seems to be standard design, as written by some blogs. Are there any other designing ways? what I would like to have is multipe html pages, for ex one for login, one for home, one for contact etc. Other wise it is difficult to understand/code/debug issues, especially people from Java background like me.So, what I want is some kind of MVC design with JQueryMobile, like each view/screen as sepearate html associated with one js (Controller). Can we have multiple html pages in JqueryMobile app? If possible how to pass data/ maintain session between them? Any samples are most welcome. Thanks In Advance.
Note: Also I don't want server side includes, may app contains 10 to 15 screens, each page will make a webservice call and fetch some data and map it to UI.
As jerone mentioned above, the jQuery Mobile documentation clearly says
We strongly recommend building your site or app as a series of separate pages like this because it's cleaner, more lightweight and works better without JavaScript.
See http://jquerymobile.com/demos/1.2.0/docs/pages/page-template.html
Each page (which can be a static HTML file or anything produced by a script (e.g PHP, Python or whatever)) is thus standalone and transitions from one page to another are done using AJAX calls.
There is no such thing as a controller except if you assume that your browser is one!
You can use multiple html files if you want. jQuery Mobile will automatic include these with AJAX: http://jquerymobile.com/demos/1.2.0/docs/pages/page-navmodel.html
Anyways, jQuery Mobile recommends one big html file with multiple pages.
From http://jquerymobile.com/demos/1.2.0/docs/pages/page-template.html
This template is standard HTML document with a single "page" container inside, unlike a multi-page template that has multiple pages within it. We strongly recommend building your site or app as a series of separate pages like this because it's cleaner, more lightweight and works better without JavaScript.