I have my own mediawiki (running on a LAMP stack on an Ubuntu machine).
Some pages constitute my own scratchpad / diary. I don't want other people to edit them.
Other pages I would like to allow and encourage community editing.
However I don't want to have to crank up another webserver Machine instance to run another MediaWiki.
Is it possible to get both within the same mediaWiki installation?
Sure. You could use $wgNamespaceProtection, or plain page protection. More generally, see Manual:Preventing access.
Related
We have a site running to drupal and migrated it to Squarespace. I have to retrieve some pages of drupal site but I can no longer view the site. Do you know any way to get the old content of website on drupal? Please know that we still have access to the drupal box. Any suggestions will be a big help.
Easiest way would be to make the old Drupal site available again through the browser running on a different domain like old.example.com, login into the admin panel and start copy/pasting content.
If you know your way around your computer, know the IP address the old server is running on you could for the time being change the host file of your machine to send requests for your site to the old server and get access to the site that way.
Migrating content by automating the process is also an option, but it is not only time consuming, it requires in depth knowledge of both platforms so is mostly a very expensive solution if you are not able to do this yourself.
But if I read your question, I think the first option is the easiest option. Get a hold of the technical person/party of the server the site is running on and get them to make the site accessible on a different domain.
I wanted to create a website that would be like a dropbox of sort, which just has files that me and my organization can access. I wanted to password protect the website, just a simple username and password. I have my own domain. I have been looking all over the web to find how to do this(I am a beginner) and found that using httaccess and htpasswd would be used to secure a website similar to what is shown here: http://www.htaccesstools.com/articles/password-protection/
But I cannot seem to get it to work. I am using the s3 bucket and putting the httaccess and htpasswd file in the same folder as the index.html file. Do you know how I would get my site to have a simple password protection(thats not seen in the source code or by typing in the html)? I am not sure if I am finding the directory correctly or not to implement this password protection correctly. Thank you for taking the time to read this and hopefully this makes sense!
Anyone else had this issue?
Amazon AWS alone won't do it. htaccess and htpasswd are also not the right tools for what you want to do.
Get yourself a cheap hosting account with a company like hostgator or godaddy or namecheap or any other that will host your web page and give you PHP and MySQL.
You cannot accomplish what you want just using javascript/jQuery. Those languages run on the browser, but you want to store your files on a server. Therefore, you need the language that controls the server - that is usually PHP. (The other popular solution is ASP, which is by Microsoft and runs on costly and complex Microsoft servers -- PHP is free and runs on (free) Linux and is therefore what ALL of the cheap web hosting companies provide. MySQL is the (free) database that is analogous to Microsoft SQL)
Next, watch a video tutorial on creating a PHP / MySQL login system, such as the ones over at:
phpAcademy (now called codecourse, apparently)
theNewBoston.com
You need to learn more about:
PHP sessions
Ajax
jQuery
MySQL (possibly)
On a basic website, you can stick your files into directories and control who can access those directories by whether or not they are logged in.
You can determine if a visitor is "logged-in" or not by asking for a username/password and setting a session variable. Session variables are just variables that are stored on the server, rather than on a user's own computer (of course, that wouldn't work since every visitor has his own computer and your files are stored on a central server -- so that is where the security (variables) must reside, right?)
Anyway, in a weekend of video watching and trial-and-error you can probably get something cobbled together that will do what you want.
I administer a MediaWiki wiki that has been hit by a ton of spam. I've managed to get rid of the spam pages that have been added to the wiki by using an extension, but the pages' data is still present in the wiki's MySQL database. This is bloating the database to over 3GB.
Is there a way to permanently delete the spam pages from the wiki, so that they are completely removed from the database?
Run the maintenance script named deleteArchivedRevisions.php.
Note that running MediaWiki maintenance scripts normally requires shell access to the server you're running MediaWiki on. If you don't have that (which might be the case on some cheap shared hosting setups), you can try using the MaintenanceShell extension instead.
i have registered a project at ourproject.org and requested a mysql dp,they answered at my email and said that i can acces relative information at home/users/my_user_name/dp.txt but it just directs me to my use page.
first:how can i access the dp ?
second:i want to install mediawiki on it but they say that i should install it to the web space of the project ,by web space do they mean the ftp server ?
third:i want to enable interwiki's(eg: en.wiki , es.wiki, ...etc) should this be configured during or after the installation of media wiki.
On you third (second) question. Interwiki means between wiki's, meaning that it link from one wiki to the other. You can set up your other wiki's after you set up the first one.
Also when your wikis are basically the same, except for the fact that they are in different languages, you should refer to the interwiki links as interlanguage links.
About setting up the MediaWiki. You first need to set up a MySQL DB (I assume that is what you mean with dp?). Then you upload the MediaWiki files to your FTP server (it is recommended to do this to the /w folder). After this you can just visit your wiki (at ourproject.org/w) and set it up (including giving it the MySQL DB information).
I am trying to configure Apache2 so I can use MySQL for authenticating users to access certain pages. Also authorization needs to work so different groups can reach differen pages.
Now, I have googled a lot but can't find out how to do this. At least not for the configuration I am having. There doesn't seem to be any version of mod_auth_mysql that supports my configuration.
OSX 10.6.4
Apache 2.2
Now, how do I achieve this not creating my own login-application in php but using the built in support of Apache2? I'm totally stuck on this one...
Thanks in advance!
Regards,
Niklas
I also would like to use a taylormade login page, not pop-up
....
how do I achieve this not creating my own login-application in php but using the built in support of Apache2
Short answer is that you can't. Unless you rewrite the Apache source code or create your own module, you can't mix HTTP based authentication with non-pop-up login prompts.
However if you are using PHP then a relatively low impact solution would be to use auto-prepend to prefix every protected page with a check on the users session. Obviously this would need a bit more thought if it is to be applied to files other than PHP source files (it'll work perfectly well if you tell Apache to apply the php engine to, say .gif files, but your script will need to detect and return the appropriate mime type).
A simpler solution might be to put a tool like squid in front of the webserver as a reverse proxy, then make the session handling data available to the squid url-rewriter.
You can build mod_auth_mysql from the source. Have a look at this post.
I you want your own log-in page, you cannot use Apache to do authentication.
Apache authentication uses the Authentication portion of the HTTP standard, and as a result you're reliant on the browser to handle the interaction with the user. There are plugins (like mod_auth_mysql) to use a database as the backend for this, but Apache can't ask the user for their credentials any other way.
The fastest approach might well be to set up Drupal or Joomla, which will get you user and group management as well as full content editing, in a way that will let you control who can edit what.