netcarver

Hi tinacious, Glad you got that working thanks to MakeMyDay's post.

Hello tinacious, This is taken from the .htaccess file; Did you copy the .htaccess file up into the root of your live site? If not, upload it and try again. If that doesn't help, you will need to speak to your hosting provider and ask if mod_rewrite is installed and enabled or if it can be installed and enabled.

@Pete, Good call, thanks for the update. @Michael, I use several classes regularly from Flourish and, as I just added a contact form to my first PW, I used the fValidation class for form validation & the fSMTP and fEmail classes to send things out via my SMTP server on successful form submission.

I've been asked how to integrate Will Bond's Flourish library with ProcessWire so I thought I'd post the code I use. I downloaded the Flourish classes (not the whole flourish project) and put them into /site/.flourish. I then pasted the following into the top of my head.inc file. function flourish_loader( $class_name ) { // Customize this to your root Flourish directory $flourish_root = wire('config')->paths->root . 'site/.flourish/'; $file = $flourish_root . $class_name . '.php'; if (file_exists($file)) { include $file; } } spl_autoload_register( 'flourish_loader', true ); After that, you should be able to use flourish classes anywhere in your templates. NB, if you do download the whole flourish project into .flourish, then read Alan's post on how to adapt the above to your layout.

Hi Alan, saw you in there briefly. Planning on coming back?

Congratulations to Antti Peisa for being the first to join me on #processwire!

Hi Pete, Thanks for the positive feedback. I wouldn't count on it being an overnight success but hopefully it can reach critical mass eventually if a few of the more experienced PW users decide to frequent it.

Hi Carlos, Sorry, I don't know. As I am often logged into several IRC channels on Freenode, I thought I'd look into extending the options for fans of PW.

In case anyone is interested in using IRC to chat about ProcessWire, and having consulted with Ryan about it, I have registered #processwire on irc.freenode.net for that purpose. If you are a regular on freenode, just pop into #processwire. If you are not then the fastest way to get online is probably via the webchat interface at http://webchat.freenode.net/?channels=processwire&uio=d4 Hope to meet a few of you in there sometime.

Hi Ben, Glad to hear that the LAMP stack worked out for you. BTW, which distro did you use for that? FWIW, the official PHP docs do not recommend using threaded MPM & Apache2.

I did try this module for a while but found it of limited use. Ah, I like the sound of that. Gives you the options you need, right where you need them.

Apologies for the slow reply, was up near you last two days and offline. I'm down in South Gloucestershire. Ah, so that was you. I guess there could be a convention for locating 3rd party libraries but, as mentioned, versioning would need to be handled and here's another variable to mi into the pot: I like to keep my code outside the site root where possible. I haven't tried this yet with a PW install but I presume it is possible to do. Whatever the scheme/convention (if) introduced, I'd like to see it be able to handle easy relocation outside of site roots and also handle multi-site installations.

Ooooooooo, nice!

Ben, I doubt this will help you directly, but just bookmarking this post as it has an interesting use of ProcMon to track down the same exception code in php5ts.dll. Edited to add: Thinking aloud from this idea. Perhaps PHP is writing to an error log file and there is some contention over that?

Hi Ben, Thanks for posting that. Back to your original question re: slicing and dicing to find out what's going on. Some thoughts, incomplete and in no particular order... If you have access to a Linux box I'd try running your ap stress test there to see if it is isolated to Windows. If I only had a Windows box, I'd now try verifying that each of the bundled php modules (especially MySQLi) is also compiled thread-safe. Can you identify any components that PW is exercising that the other CMS systems aren't (ie. are they using the MySQL module instead of PWs MySQLi?) Although it's from a while back, there is a report here of a similar looking issue.

Tom, Re: release as a module -- I don't know yet. I only started playing with PW a few days ago so I'm learning my way around it too. I doubt I can come up with something as flexible as that right now. What I do have a simple contact form class working right now from my glue.php include. However, it uses classes from another fantastic PHP project called flourish, so an install of this solution is not a one-stop shop. It's reusable for me 'cause I'm used to flourish but might not be reusable to everyone. BTW, I highly recommend looking at flourish, i.m.o it is a PHP project par-excellence & the documentation is fantastic.

Hi Pete, I think yours was a more explicit way of doing it though. BTW, how's sunny Chester? You're not far from my parents there.

Yeah, I'm working on some reusable bits here too -- think zem_contact_reborn for PW.

Ok, out of interest, what worker module is your Apache install using? --- Ben, sorry but a follow-up Q: is your apache2 executable compiled with multi-threaded support by any chance? On linux I can get at this with apache2ctl -V but don't know how on Windows .

Tom, try this (untested)... <? $image = $profile->images->first(); $alt = ($image->description) ? $image->description : $image->name; echo "<img src='{$image->url}' height='{$image->height}' width='{$image->width}' alt='{$alt}' />"; ?>

Hi Ben, Welcome to the PW forum & thanks for posting this. I'm new to ProcessWire myself but want to ask if this problem shows up if you run ap with just a single thread?

Great topic! Thanks for posting Tom and good to see you in a forum again. I used to use something similar to Ryan's tools.inc back in Textpattern but called it glue.php and had it live in the plugin cache directory.

+1 for this.

Ryan, You might want to think about adding the target doctype to the constructor call now that textile can target HTML5. Not sure how you'd want to have the user indicate their preferred output type though. Presumably, if a site is targeting HTML5 then some kind of site-wide setting, or config option would do it. $textile = new Textile('html5'); Currently this causes textile to output <abbr> instead of <acronym> and drops the invalid align attribute on images, instead inserting classes to allow CSS to do the alignment.

I committed some updates to PHP textile today. Added since post #28 above were... Support for HTML5 output. Support for symbols as backref link characters for note lists. Support for raw urlencoding of unicode characters in URLs. Simpler forms of "$" style links. More robust support for n-dash characters. If I can, I'd like to add better support for Japanese-wikipedia style links (info here) and close a problem with line breaks in table cells; and that should get PHP Textile to version 2.4.