Jump to content

Recommended Posts

I am with Nico 100%...

+1 in all that he said.

wiki.processwire.com +1

And I would use MediaWiki, too. I mean this forum doesn't use PW as well so why should wiki? And with the plugin found by SiNNuTs it would perfectly with just one login

Share this post


Link to post
Share on other sites

How 'bout help.processwire.com or docs.processwire.com? :)

Anyway, from those options above guide.processwire.com gets +1 from me.

  • Like 1

Share this post


Link to post
Share on other sites

Now this looks like another great initiative. I'm up for contributing in any way I can.

Share this post


Link to post
Share on other sites

Wiki.processwire.com I think.

There used to be a "bridge" for Mediawiki that integrated the IPB logins but that was a long time ago. I can look into it as that would be useful.

Edit: here it is - works for version 3.2 of the forum software do very likely works for 3.3 too: http://www.ipbwiki.com/

Edit2: I need to upgrade the forums - I hate reading what I think is the last page of a topic on my phone and it's not - I end up repeating other people :P you'll be glad to know the latest version jumps to the last unread post in a topic on the mobile version - I just need to test it before upgrading (hopefully later today).

  • Like 1

Share this post


Link to post
Share on other sites

I've got to put most of my time towards launch a site for the first half of this week, but will plan on getting the account setup in the second half of this week. I'll get it setup for Nico and anyone else that wants to help, just let me know.

Share this post


Link to post
Share on other sites

ryan - MediaWiki does have a lot of initial settings to tweak and there are quite a few recommended addon modules to install to prevent it becoming a spammer's paradise so I'm happy to set this all up.

I'm not sure about the bridge requirements, but it should be fine with being on an isolated subdomain as the database host will still be at the same IP address (depending on servers sometimes using "localhost" in the DB connection on a subdomain doesn't necessarily give you access to the parent domain, which would be required for the bridge to work of course).

If all else fails it could go under processwire.com/wiki (or guide or whichever name we're going with) instead, but I'm pretty sure we can make it work fine on a subdomain.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks Pete! I'll take you up on that because it sounds like you are the only one here that's setup MediaWiki before, so I think it makes the most sense for you to at least get the installation started. That's assuming you have time and are comfortable with doing it? I know you'd originally expressed some reservations about MediaWiki, so if you find something you think might suit us better then that's great too. I'll create an account, subdomain and DB. Let me know what else I can get setup here.

Share this post


Link to post
Share on other sites

That'll be fine - I'm off tomorrow through til Monday to finish decorating the house but I definitely don't want to be doing that all day every day so I'll have time to set this up.

As long as we don't plan on using it forever I'm fine with it - it can become a bit of a resource hog over time and we would need to keep an eye out for spammers but this server should definitely be able to handle it.

My knowledge is reasonably good in terms of setting it up but a bit flakey in terms of day to day operation so if nothing else it'll be a learning experience ;)

  • Like 1

Share this post


Link to post
Share on other sites

I've still got to get the account setup. Sorry for the delay. I ended up working on that datetime fieldtype/inputfield with what extra time I had, because I got fed up with the old one. :) I'll get this account setup within the next day here hopefully.

Share this post


Link to post
Share on other sites

Got it setup here: http://wiki.processwire.com

Nothing there yet but a blank MediaWiki. The access to it should be wide open, so Nico and anyone that wants to experiment, have at it. :) Let me know anything I can do or setup on this end.

Thanks,

Ryan

Share this post


Link to post
Share on other sites

Wahey, snagged User ID 2! :rolleyes:

S'pose that means I ought to get involved...

(Are they going to stay separate logins, or have I just wasted my time?)

Share this post


Link to post
Share on other sites

They will stay separate logins. So congrats on being user id #2 :)

Right now the Wiki is wide-open, so you can make edits without having an account too.

Share this post


Link to post
Share on other sites

I have run a wiki before (different software, so not much help), and they do attract spam like flies to something or other, so I'd recommend battening down the hatches sooner rather than later.

  • Like 1

Share this post


Link to post
Share on other sites

Just in case, I also already reserved my name ;)

Share this post


Link to post
Share on other sites

I thought we want to combine the forum and the wiki? And I would like to experiment on it ;)

Share this post


Link to post
Share on other sites

I thought we want to combine the forum and the wiki? And I would like to experiment on it ;)

I think that is good way to go in longer term - but I guess first we do need some signs that there is enough contributors for the wiki.

Share this post


Link to post
Share on other sites

Great news! Will it be possible to have wiki-articles in different languages?

Share this post


Link to post
Share on other sites
Great news! Will it be possible to have wiki-articles in different languages?

I don't know what the capabilities or limitations of the software are, but I'm all in favor of anything multi language.

  • Like 1

Share this post


Link to post
Share on other sites

I'm happy to write some documentation as I already have to do a little of this for my clients. Is it just a case of getting a login for the wiki until we find something more ideal?

Share this post


Link to post
Share on other sites

Multi language on the wiki software should be possible but I've never got the module for it to work and it was a pain last I checked.

I'd suggest we need a PW based solution since that handles multi language well :) Of course that's honing to require some thought on how to set it up too, plus might need version history first as some way of moderating and rolling back changes.

Share this post


Link to post
Share on other sites
I'm happy to write some documentation as I already have to do a little of this for my clients. Is it just a case of getting a login for the wiki until we find something more ideal?

Thanks Stephen! I've created you an account on the wiki. Username is the same as your username here, and password is your email address. Go ahead and change the password once you login.

I see the wiki as a place to post documentation that will be eventually moved to the main site, and I think it's pretty good for this purpose. I agree with Pete that we'll eventually have a PW-based solution to replace the Wiki too, but now that we've gotten the spammers out of the Wiki it seems to work pretty well.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By ksymmons
      Hey guys,
      As the question says, I'd really like to learn about your initial client communication workflows. In other words, what's your process like from the moment you get a request to provide a quote for a website to the moment you actually send the quote?
      My current workflow:
      A client fills out the contact form on my site to request a quote. I review the information provided and send them a Word document questionnaire with a list of questions. I ask for things like project scope, features needed, desired timeline, allocated budget, etc. They fill out the document and send it back to me. I review the information provided and make sure I've got everything I need. I write and send the quote to the client. Client accepts the quote. I send them a contract, get it signed and collect 50% of total payment. I gather some extra information from them, usually just by asking questions via email or by sending them another Word document questionnaire. I start building their site. Lately, I've been thinking about changing this workflow a bit. Currently, my online contact form has three fields: name, email and message. What I'm thinking is, what if I provide a select toggle above my form so that clients can choose between a simple, general enquiries form and a larger form (with all the questions I've got in my Word document) to request a quote? This would allow me to do away with the Word document, and would make this a one-step process.
      The reason why I haven't done this so far is because I'm not sure how good of an idea it is to have a long contact form with say, 10-15 questions. What's your take on this?
      Another thing I'm not entirely happy with is having to send them two questionnaires (steps 2 and 8). The reason why I do this is because I don't want to overwhelm them with lots of questions at the beginning, and also because, to be honest, the questions I ask in the 2nd questionnaire do not really influence pricing, as they have more to do with the nature of their business, their goals with the new site, possible corporate colours they may have, things like that.
      What do you guys think? Does my workflow seem sensible to you? Is it similar to what you do? What would you change?
      Thanks, and sorry for the brick!
      P.S. If some of you guys are willing to share your client questionnaires I would certainly appreciate it.
    • By eangulo
      Hello everyone,
      Usually in many CMS database tables prefixed or suffixed with "cache" can be manually cleared without a problem because the system will populate them on the "next page request". Actually in Processwire I am expecting this behaviour:
      [On PW 3.x]
      Manually clear table "caches" in database Go to "client" side (not in the admin panel) All references to my "/site/modules" in my template files does not work : wire("modules")->get(""), $modules->get("") and modules()->get("") PHP error:  Fatal error: Uncaught TypeError: Return value... My _init.php file are not able to find the references to my /site/modules/  The client side not working because this PHP fatal error. If I go to the admin panel "Admin -> Modules" and I trigger the action "Check for New Modules" in the top-right corner in the page, it populates the caches table with the required information and them the client side works.
      It is normal? Or I am doing something wrong ?
      A solution could be to manually call the script that the button "Check for New Modules" calls, but I want to know if  I am doing something wrong here.
      Thank you in advance guys ! 
    • By MrSnoozles
      Hello,
      this feature wish came up while I was working on my first bigger project with ProcessWire. While almost all of the CMS is very well thought out there was one thing that always kept me thinking "where should I put this?": simple page actions.
      What I mean is code snippets that belong to a page and should be run when a certain action is taken. E.g. when a user submits the form on my contact page (that has the contact template) I somewhere have to validate the form and then send it somewhere. So far I see two options to do that.
      Write a module that hooks into some methods and checks if the post data is set and if the page is my contact page
      This aproach is clean but it's usually a lot of overhead to write a module just for that Write the code in my contact.php template
      This aproach is fast but feels really dirty. It does not help to separate the logic from the design which I fear in a long term could lead to some Wordpressish code structure  
      Now since I don't have so much experience with ProcessWire there might be a chance I missed something, but then it's probably not documented obvious enough. So I thought how you improve on this problem and came to a solution, that's again really close to the syntax that jQuery provides. If we had some kind of routing system we could register those actions in any file, for example the templates _func.php
      <?php // execute this action when a post request is sent to /contact // the parameters given to the callback function probably should be different wire('request')->on('post', '/contact', function($request, $input) { // do an action } // do the action for any post request wire('request')->on('post', function($request, $input) { // do an action } // do the action for get requests on contact pages wire('request')->on('get', 'template=contact', function($request, $input) { // do an action } // do the action on ajax-GET requests wire('request')->on('get.ajax', '/contact', function($request, $input) { // do an action }  
      Is that something that could improve the work with ProcessWire? What's your honest opinion about it? If that's a useful suggestion I would like to help with the implementation.
       
      Regards
      Alex
    • By cosmicsafari
      Hi all,
      Just wondering if its safe to delete the content of the cache table manually within the database?
    • By Chris
      short story:
      think of a radio button mechanic in the background, but ui-wise you present images with captions as "buttons".
      for instance i whant to be able to let admins change some visual themes of a single page, with different background and formating for each, i could place screenshots thumbs with a short caption. so the admins are able to se a preview image and know better what this setting does.
      therefore it would be needed to define images for an input field, during the field creation. maybe someone likes the idea and is able to do it? 
×
×
  • Create New...