I'm using some templates to work around some use cases in mediawiki and if an untrained user edits these templates my site functionality breaks in some places.
I want the users to be able to edit some sites with this extension, but if they edit the source code of the template the functionality breaks.
Is there a way to disallow users or disable the source code editing for mediawiki entries or set rules for user groups to disallow source editing? Is it still possible for the users to edit the pages with the form editor?
You could attempt to modify the edit page via a hook like https://www.mediawiki.org/wiki/Manual:Hooks/EditPage::showEditForm:fields
By removing inputs or making fields readonly and adding a notification to use the form, you should be able to get a situation where pages are not editable vie the edit page directly. I'm not sure if that would affect form editing though.
Related
Background:
I need to allow users to create web pages for various products, with each page having a standard overall appearance. So basically, I will have a template, and based on the input data I need the HTML page to be generated for each product. The input data will be submitted via a web form, following which the data should be merged with the template to produce the output.
I initially considered using a pure templating approach such as Nunjucks, but moved to ReactJS as I have prior experience with the latter.
Problem:
Once I display the output page (by adding the user input to the template file with placeholders), I am getting the desired output page displayed in the browser. But how can I now obtain the HTML code for this specific page?
When I tried to view the source code of the page, I see the contents of 'public/index.html' stating:
This HTML file is a template.
If you open it directly in the browser, you will see an empty page.
Expectedly, the same happens when I try to save (Save As...) the html page via the browser. I understand why the above happens.
But I cannot find a solution to my requirement. Can anyone tell me how I can download/save the static source code for the output page displayed on the browser.
I have read possible solutions such as installing 'React/Redux Development Extension' etc... but these would not work as a solution for external users (who cannot be expected to install these extensions to use my tool). I need a way to do this on production environment.
p.s. Having read the "background" info of my task, do let me know if you can think of any better ways of approaching this.
Edit note:
My app is currently actually just a single page, that accepts user data via a form and displays the output (in a full screen dialog). I don't wish to have these output pages 'published' on the website, and these are simply to be saved/downloaded for internal use. So simply being able to get the "source code" for the dislayed view/page on the browser and saving this to a file would solve my problem. But I am not sure if there is a way to do this?
Its recommended that you use a well-known site generator such as Gatsby or Next for your static sites since "npx create-react-app my-app" is for single page apps.
(ref: https://reactjs.org/docs/create-a-new-react-app.html#recommended-toolchains)
If I'm understanding correctly, you need to generate a new page link for each user. Each of your users will have their own link (http/https) to share with their users.
For example, a scheduling tool will need each user to create their own "booking page", which is a generated link (could be on your domain --> www.yourdomain.com/bookinguser1).
You'll need user profiles to store each user's custom page, a database, and such. If you're not comfortable, I'll use something like an e-commerce tool that will do it for you.
You can turn on the debugger (f12) and go to "Elements"
Then right-click on the HTML tag and press edit as HTML
And then copy everything (ctrl + a)
Where can I put custom input form code in media wiki homepage?
This is so I can modify it into fewer steps for a user to create a new page. The input form will be for entering the title of the new page.
Currently, when adding a page, the user has to search for a page, and if it doesn't exist, it redirects to another page with a link to add the new page. After that it will load the built-in Wiki editor(will also modify this to default to the Visual Editor extension I integrated instead of Wiki editor).
Any input would be greatly appreciated.
There are a number of extensions that can do what you want:
InputBox, is bundled with recent versions of MediaWiki. It is used with Wikimedia wikis, and thus probably very stable.
CreateBox, specifically for letting users create pages
Create Page, more general aproach
Semantic Forms The most fulfledged, but also the most complex, and requires the Semantic MediaWiki extension
You might also want to combine this with some biolerplate extension, e.g. Preloader
As you are posting on SO, I assume that developing your own extension would also be an option. In that case, have a look at the parser functions manual: https://www.mediawiki.org/wiki/Manual:Parser_functions
The file in which i can add/modify a custom input form in the media wiki homepage would be the /rootWikiDir/skins/Vector.php
I have a mailchip signup form in the footer of my site. I've noticed recently that after trying to signup, the user is greeted with a 404:page not found error reading:
MailChimp It seems the page you were looking for has disappeared We’ve
recorded this vanishing act and our team of chimp magicians will find
the missing link.
The form worked perfectly on my old site, I'm not quite sure why it's suddenly stopped- I didn't change anything but the styling.
When you create your MailChimp subscribe form, you have the option to specify your own Thank You page that users are sent to after they subscribe:
http://kb.mailchimp.com/article/can-i-design-and-host-my-own-thank-you-pages-instead-of-using-mailchimps/
Are you sure that MailChimp isn't trying to redirect your users back to a Thank You page of your own... that no longer exists on your end?
Regardless, I'd recommend going through the steps on that page to create a new subscribe form from scratch, specify the options including the Thank You page that you want to use, and place the new embed code in the footer of your website. That should fix whatever is currently broken.
your question is broad,It may have multiple reasons:
1: Compare your old code and new code and see difference if any malicious code is written (includes other pages or script that leads to errors)
2: Check if the Signup page (abc.html etc) file is present on the server and not deleted/Renamed during deployment. Also check nested pages that are included as headers/ footers
3: Some times files are placed in the wrong directory. Make sure particular file is placed at the required location.
please specify what type of page is it and called from which source (JSP/simple html etc).
I am frequently changing code in a Dreamweaver template, and every time I do so, the "Update Template Files" dialog box appears, followed by the "Update Pages" dialog box which I have to manually close. Is there any way to have my inheriting HTML documents automatically update, without having to deal with the 2 dialog boxes, every time I save the Template?
I am coming from developing ASP.NET in Visual Studio, which only requires a quick save, and a reload on the browser. This may seem like a petty problem, but the frequency of it is getting to me quickly...
No, you must go through the Update Pages dialogs if you are using Dreamweaver Templates. The only way to truly get rid of it is to switch out of Templates entirely and use some form of include call to handle the "templated" areas of your site. Editing the called include file and saving it will update all pages that use that file. Just like Templates without the slow dialogs and occasional bugs
Have a wiki installed in our organization, and want to start using it.
Failed to find the answers for the next 2 basic questions:
How do I configure the entry page to show a list of all existing pages
How do I create a new page (!). Only succeeded doing it by typing a url of an non existing page. Guess there are nicer methods for this
Thanks
Gidi
For how to show a list of all pages, look at DynamicPageList, which is part of MediaWiki. (There's a more advanced third-party version, but it's not needed for such a simple task.)
Creating a new page really is exactly as you said: Type a URL and save some edits. Most beginning editors will edit a link into a page, and then use that link to browse to the page, so that they don't accidentally forget the spelling and lose the page to the Ether. (Of course it would show up in the recently edited and other special pages.)
This is more of a webapps.stackexchange.com question though.