ANNOUNCE: Krang v2.100
Krang v2.100 is now available (the source release is up now and binary builds should be up soon). Notable changes in this release: * Numerous bugs were fixed in Krang's most intensive QA cycle in years. * Krang now includes methods to integrate with dynamic front-end applications by publishing CGI::Application instance scripts and templates. New methods were added to Krang::ElementClass::TopLevel to facilitate this: publish_frontend_app_template() and publish_frontend_app_stub(). [Jesse Erlbaum] * Modified Site Server configuration to support CGI applications and Apache::Registry apps. This will permit the site server to host interactive applications. [Jesse Erlbaum] * Added new parameter "mode" to additional_content_block() method in the publisher. This new parameter permits the permission of the file to be set, which is particularly useful for publishing executable files. [Jesse Erlbaum] * Added new options to Krang::HTMLPager to allow paging of data from external sources. [Michael Peters] * Krang now sends no-cache HTTP headers for all Krang::CGI requests. This will fix some problems when logging in as a different user with the same browser session in IE. [Michael Peters] * Upgraded to HTML::Template v2.9, fixing several bugs. [Sam] * Added a new configuration variable, PreviewSSL, which controls whether links to preview use SSL. This behavior was previously the default when EnableSSL was set, but now it is available independently and can be turned off even when Krang itself is using SSL. [Sam] * During DB creation, addon SQL files now come after core Krang. This allows addons to change existing Krang data/tables. [Michael Peters] * Stricter enforcement of asset permissions. [Michael Peters] Detailed change-log here: http://krang.sf.net/docs/changelog.html Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for website editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team
ANNOUNCE: HTML::Template v2.9
CHANGES - New Feature: the force_untaint option makes sure you do not pass tainted values to param(). [Sven Neuhaus] - New Feature: Added ESCAPE="none" as a synonym for ESCAPE="0". Fixed both to work with default_escape. [EMAIL PROTECTED] - Bug Fix: DEFAULT didn't work with URL and JS escaping. - Bug Fix: Long-standing bug where variables set in a loop weren't available inside inner loops under global_vars if the variable wasn't actually used in the outer loop. (Thanks to Richard Fein for help debugging the fix.) - Doc Fix: Changed references to CVS in the docs to Subversion now that the switch is complete. - Test Fix: At long last, the work from the Phalanx project has been merged! The tests are now more complete and easier to work on. Thanks Phalanx guys! DESCRIPTION This module attempts to make using HTML templates simple and natural. It extends standard HTML with a few new HTML-esque tags - , , , , and . The file written with HTML and these new tags is called a template. It is usually saved separate from your script - possibly even created by someone else! Using this module you fill in the values for the variables, loops and branches declared in the template. This allows you to separate design - the HTML - from the data, which you generate in the Perl script. This module is licensed under the same license as Perl. See the LICENSE section of the docs for more details. TUTORIAL If you're new to HTML::Template, I suggest you start with the introductory article available on the HTML::Template website: http://html-template.sourceforge.net AVAILABILITY This module is available on SourceForge. Download it at: http://html-template.sourceforge.net The module is also available on CPAN. You can get it using CPAN.pm or go to: http://www.cpan.org/authors/id/S/SA/SAMTREGAR/
[ANNOUNCE] Krang v2.008 Released
Krang v2.008 is now available (the source release is up now and binary builds should be up soon). Notable changes in this release: * Improved password security. Password policy is now configurable and extensible by addons. [Michael Peters] * Added several new configuration options which allow Krang instances to run on separate IPs and have different SSL configurations. [Sam] * Added a new option for addons, DataSetClasses. This allows addons to extend Krang::DataSet and include new objects in KDS files. [Sam] * Implemented a system of universally-unique identifiers (UUIDs) for Krang objects. This allows updates between machines to propagate changes correctly even when keys have changed. [Sam] * Several bugs were fixed. Detailed change-log here: http://krang.sf.net/docs/changelog.html Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for website editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team
[ANNOUNCE] Krang v2.007
Krang v2.007 is now available (the source release is up now and binary builds should be up soon). Notable changes in this release and in v2.006, which never received a proper announcement: * Improvements to the list-data management system, command-line tools and associated element classes. [Jesse Erlbaum] * Added support for Konqueror and fixed Krang to deny access to Mac IE, which was never supported. [Michael Peters] * Krang now automatically deletes any alerts tied to a desk when that desk is deleted, fixing a long-standing import/export bug. [Michael Peters] * Added --clean option to bin/krang_addon_installer. [Michael Peters] * Added new index to element table. This index will greatly speed complex publishing logic. Thanks to James Reidy for identifying the bottleneck. [Jesse Erlbaum] * Allow users whose page-size preference is 100, to be able to toggle between 100 and 20, instead of 100 and 100. [Michael Peters] * SiteServer configuration now does server-side includes by default. SSI is very common for sites managed by Krang. This will make development use of the SiteServer more useful and easier. [Jesse Erlbaum] * Added new --grep option to krang_upload_media. This option permits you to use a regex to filter what you want media to upload. [Jesse Erlbaum] * Binary distributions now include src/ allowing for rebuilding installed copies of Krang. [Sam] * Fixed krang_install --FromBackup issues when the backups contain addons. [Michael Peters] * Fixed bug where KDS import would trigger delete_hook calls when updating elements for stories and categories. [Sam] * Fixed bulk-edit to allow white-space on the blank line separating paragraphs. [Sam] * Modified krang_schedulectl to skip scheduler start-up if SchedulerMaxChildren parameter is set to 0 in krang.conf. This is useful in development when you do not want the scheduler to run. [Jesse Erlbaum] * Fixed several bin/ scripts to always load Krang::Conf via Krang::ClassLoader before using it. This fixes problems overriding Krang::Conf in an addon. [Sam] * Changed krang_upload_templates script to now handle "global" templates (those without categories). [Jesse Erlbaum] * Numerous other bug fixes. Detailed change-log here: http://krang.sf.net/docs/changelog.html Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for website editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team
ANNOUNCE: Krang v2.005 Released
Krang v2.005 is now available. Notable changes in this release and in v2.004, which never received a proper announcement: * Added enforcement of permissions at the application and run-mode level rather than just at the UI level. [Michael Peters] * Fixed Xinha link-munging so that you can now use the WYSIWYG editor to create links and images. Full-screen mode now works properly. [Jesse Erlbaum] * Added a new configuration parameter, Charset. This may be used to control the character set for the Krang user-interface. [Sam] * Numerous improvements to the addon system. [Bodo Schulze] * Upgraded to HTML::Template::Expr v0.07, providing a better expression syntax and some bug-fixes. [Sam and Michael Peters] * Added new primitive, Krang::ElementClass::CheckBoxGroup, which integrates with Krang's lists system, in addition to permitting simple values. [Jesse Erlbaum] * Added new option "--makecats" to krang_upload_media and krang_upload_templates. When specified, missing categories will be created in the CMS. [Jesse Erlbaum] * Many bugs are now fixed. Detailed change-log here: http://krang.sf.net/docs/changelog.html Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for website editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team
Re: Why is err_header_out needed to set cookies when redirecting?
On Wed, 15 Feb 2006, Geoffrey Young wrote: in short, because anything other than 200 is considered an error. so REDIRECT (302) forces apache to use the err_headers_out table instead of the headers_out table. why does Location work in headers_out, then, you ask? well, it's an exception to the rule - see http_protocol.c :) Thanks Geoff. I guess I don't feel so bad that it doesn't make sense then! -sam
Re: Why is err_header_out needed to set cookies when redirecting?
On Wed, 15 Feb 2006, Michael Peters wrote: Now, we all know that second line has to be err_header_out not header_out, or Apache will silently ignore the Set-Cookie directive. I knew it as soon as I saw it, although I couldn't explain why and thus didn't trust my intuition. I looked through the list archives and the guide without finding an explaination that made sense. Would anyone mind explaining this to me? Anything that does not return an OK is considered an 'error', so it won't send the normal header_out() stuff. How does Location get through then? It's set using header_out() and works... -sam
Why is err_header_out needed to set cookies when redirecting?
Hello all. Check out this bug: my $r = Apache->request; $r->header_out(Set-Cookie => '...cookie here...' ); $r->header_out(Location => '...url here...'); return REDIRECT; Now, we all know that second line has to be err_header_out not header_out, or Apache will silently ignore the Set-Cookie directive. I knew it as soon as I saw it, although I couldn't explain why and thus didn't trust my intuition. I looked through the list archives and the guide without finding an explaination that made sense. Would anyone mind explaining this to me? Thanks, -sam PS: This is Apache v1.3.33 with mod_perl v1.29, in case it matters.
ANNOUNCE: HTML::Template::JIT v0.05
CHANGES - Fixed param() to allow for blessed hash-refs. [Alex Kapranoff] - Fixed url-escaping to work with UTF-8 characters. [Alex Kapranoff] - Added support for JS escaping. [Alex Kapranoff] - Fixed a compatibility problem with HTML::Template v2.8, which is now a prerequisite. DESCRIPTION This module provides a just-in-time compiler for HTML::Template. Templates are compiled into native machine code using Inline::C. The compiled code is then stored to disk and reused on subsequent calls. HTML::Template::JIT is up to 8 times as fast as HTML::Template using caching. NOTE This module is not feature-complete. Be sure to read the CAVEATS section in the documentation before using! AVAILABILITY The module is available on CPAN. You can get it using CPAN.pm or go to: http://www.cpan.org/authors/id/S/SA/SAMTREGAR/ CONTACT INFO This module was written by Sam Tregar ([EMAIL PROTECTED]). You can join the HTML::Template mailing-list by visiting: http://lists.sourceforge.net/lists/listinfo/html-template-users --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Html-template-users mailing list Html-template-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/html-template-users
ANNOUNCE: HTML::Template v2.8
ANNOUNCEMENT: HTML::Template 2.8 CHANGES - New Feature: the new default_escape option allows you to apply escaping to all variables in a template. [Alex Kapranoff] - Bug Fix: ESCAPE wasn't working on variables containing code-refs. - Bug Fix: Changed HTML::Template to help sub-classes by called _new_from_loop() via ref($self) rather than hard-coding the package name. [Mark Stosberg] - Bug Fix: Including more than one tag in or now dies with an error message, instead of silently ignoring one of the clauses. [Mitar and Mark Stosberg] - Bug Fix: Fixed HTML::Template to re-evaluate conditions to handle . This bug could cause HTML::Template to take both branches of a conditional if a code-ref parameter returned a different value when called a second time. [Emanuele Zeppieri] DESCRIPTION This module attempts to make using HTML templates simple and natural. It extends standard HTML with a few new HTML-esque tags - , , , , and . The file written with HTML and these new tags is called a template. It is usually saved separate from your script - possibly even created by someone else! Using this module you fill in the values for the variables, loops and branches declared in the template. This allows you to separate design - the HTML - from the data, which you generate in the Perl script. This module is licensed under the same license as Perl. See the LICENSE section below for more details. TUTORIAL If you're new to HTML::Template, I suggest you start with the introductory article available on the HTML::Template website: http://html-template.sourceforge.net AVAILABILITY This module is available on SourceForge. Download it at: http://html-template.sourceforge.net The module is also available on CPAN. You can get it using CPAN.pm or go to: http://www.cpan.org/authors/id/S/SA/SAMTREGAR/ CONTACT INFO This module was written by Sam Tregar ([EMAIL PROTECTED]). You can join the HTML::Template mailing-list by visiting: http://lists.sourceforge.net/lists/listinfo/html-template-users --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Html-template-users mailing list Html-template-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/html-template-users
Re: HTML::Template::Compiled
On Tue, 30 Aug 2005, Jonathan Vanasco wrote: > are there any worries for security overflows / memory leaks, having compiled > that stuff into c or xs (its one of those, right?) under mod_perl Sure, it's worth worrying about. Anything written in C can potentially have a buffer-overflow bug or a memory leak, include Perl itself. One way to mitigate against a bug like this is to use taint checking. If you carefully check all input from the user then exploiting a buffer-overflow becomes much harder, ideally impossible. > under regular perl, that stuff would just die at the end of the script/post > execution - under mod_perl does it die after execution and then is respawned > or is it still running? You might want to read about buffer-overflow vulnerabilities. If one did actually exist and was remotely exploitable then the Apache process would actually run code written by the attacker. This isn't just about crashing the server, it's a break-in scenario. This goes for buffer-overflows in XS modules like HTML::Template::JIT as well as one that might exist in Perl itself. -sam
Re: HTML::Template::Compiled
On Tue, 30 Aug 2005, jonathan vanasco wrote: > 2- even the slowest templating option - petal - was a fraction of > the speed of my business logic and db connectivity This is an important point, and it's the main reason I've never actually used HTML::Template::JIT. My ego demanded that I create the fastest templating system possible, but that doesn't mean it's actually needed. Performance optimization should be about addressing bottlenecks and it's a pretty rare web-app that actually has a templating bottleneck. Similarly, I still use CGI.pm all the time. Despite all kinds of evidence about how "slow" it is, it's never shown up on a single profile run I've ever done. Now my ego is telling me to disect HTML::Template::Compiled and figure out how it manages to beat HTML::Template::JIT in some tests. Help! -sam
Re: [PATCH] DBI::ProfileDumper::Apache ported to mp2 RC5+
On Sun, 21 Aug 2005, Philip M. Gollucci wrote:
> I wasn't doing it for speed, more of consitency's sake with
> perl.apache.org docs and other modules like Apache::DBI, Apache::DB
> (+friends), and etc. I have however changed it to a user var ($MP2)
> per you request.
Cool, thanks. One question (which you may perfectly reasonably ask me
to check for myself): won't this cause a warning when
MOD_PERL_API_VERSION is undefined?
$MP2 = $ENV{MOD_PERL_API_VERSION} == 2 ? 1 : 0;
Perhaps this would be better:
$MP2 = (($ENV{MOD_PERL_API_VERSION} || 0) == 2);
-sam
Re: [PATCH] DBI::ProfileDumper::Apache ported to mp2 RC5+
On Sun, 21 Aug 2005, Philip M. Gollucci wrote: > Hi all, > > Nuff said! Very cool! One comment: don't bother with 'use constant' here. The tiny amount of time saved by using a constant will be overwhelmed by the time used loading constant.pm and calling import(). > P.S. > I believe its a side effect, but you need to enable > PerlOptions +GlobalRequest or you get errors in the on_destory() method. Can you confirm this and add it to the documentation? I'd check it out myself but I don't have an Apache2/mod_perl setup at the moment. -sam
[JOB] Perl Programmer for large-scale Apache/mod_perl development
NEW YORK CITY AREA ONLY Plus Three is looking for an experienced Perl programmer to join our team. You will join a large-scale, high-visibility project with the potential to positively affect the future of the Democratic party during the next election cycle. We're looking for someone who enjoys programming as much as we do and is always interested in learning more. Our team conducts weekly code reviews and is involved in the Perl community. Required skills: * Significant development experience in a professional environment. * Solid programming experience with Perl, including extensive use of object-oriented features, code testing and CPAN modules. * Apache/mod_perl development experience * Working knowledge of SQL * Working knowledge of e-mail * Communication - ability to discuss requirements clearly with non-technical users Desired skills: * Experience with our toolset: Class::DBI, CGI::Application, HTML::Template, and Krang. * MySQL development experience * Linux programming experience * E-mail campaign experience * Open source development experience (CPAN authors preferred!) * Test-driven Developemnt * Advanced database tuning Send resume and code samples to [EMAIL PROTECTED]
Re: Newline and tab escaping in Apache's error_log
On Fri, 3 Jun 2005, Michael Peters wrote: > It's a fairly recent change to apache since some characters could cause > problems for some text viewers thus creating a security hole (if your > text reader isnt smart enough). > > You can turn it off by building apache like so: > > CFLAGS="-DAP_UNSAFE_ERROR_LOG_UNESCAPED" ./configure > make ... Thanks, that worked perfectly. -sam
Newline and tab escaping in Apache's error_log
Hello all. Does anyone know why Apache (v1.3.33) is escaping newlines
and tabs in my error logs? I'm seeing stuff like:
[Thu Jun 2 18:54:18 2005] [error] Error executing run mode 'process':
Unable to find message named 'city_missing' in messages.conf. at
/home/sam/projectx/lib/Projectx/Message.pm line
131\n\tProjectx::Message::add_message('city_missing') called at
/home/sam/projectx/lib/Projectx/Form.pm line
183\n\tProjectx::Form::_errs_to_messages('Arc..
That can get pretty unreadable for dead stack traces. Any idea how to
turn it off?
-sam
Re: Debugging memory allocation
On Mon, 9 May 2005, Igor Chudov wrote: > I would like to at least have a log that lists pid, > page requested, parameters, starting memory and memory > after the request was processed. O rsome other ideas > like that. Any thoughts? Check out GTop.pm. You should be able to write a LogHandler which produces the stats you want. -sam
Re: Graphics / Pie Charts
On Fri, 6 May 2005, David Hofmann wrote: > Someone recommend that I use GDGraph-1.43. Looking at it there > hasn't been an update since 2003. So before I go play with it I > figure I ask here if anyone has done and graph stuff, and if there a > better module to use under mod perl. I asked a similar question on PerlMonks recently: http://perlmonks.org/?node_id=452166 I ended up settling on GD::Graph3D but I'll be interested to see if someone here has a better idea. -ssam
Re: [Slightly OT] Standardizing image uploads/making thumbnails
On Sat, 5 Mar 2005, jonathan vanasco wrote: > What have people here found good to use (a2/mp2)? > As far as CPAN mods/interfaces go > GD seems to be faster , but it looks awful > ImageMagick looks better, more stress on the server > Imager looks simple, but even more stress Krang (http://krang.sf.net) uses Imager to do thumbnailing, not because it's any better than the other two but because it's much easier to compile and install. I've often had problems getting GD and ImageMagick installed but Imager has been very easy to support. -sam
Re: Has anyone successfully used Devel::Profiler::Apache under modperl?
On Fri, 18 Feb 2005, Geoffrey Young wrote: > sam is the real expert here, so I would follow his advice more than mine :) That said, most of the new code in CVS is Geoff's. So don't blame me if it roasts your cat. ;) -sam
Re: Has anyone successfully used Devel::Profiler::Apache under modperl?
On Fri, 18 Feb 2005, Richard Chen wrote: >Most importantly, after the server process is shutdown and dprofpp > is applied to the tmon.out file, it always complains about garbled profile. > The -F option for dprofpp does not help. So basically I cannot use any data > inside the tmon.out file. > > Has anyone successfully used Devel::Profiler::Apache? Yes. But that said, your experience seems to be increasingly common. I suspect a popular module (DBI? mod_perl?) has started playing nasty XS tricks that are confusing Devel::Profiler. One thing you can try is adding modules to bad_pkgs until the problem goes away. Start with anything written in C. Alternately, write a package_filter which only tries to profile the modules you're interested in. For example, on the Krang project I used a package_filter that only instrumented modules in the Krang:: namespace. -sam
Re: Segfault with Apache::Request->param method
On Thu, 2 Dec 2004, Chris Brown wrote: > Right now I'm running Apache 1.3.31 with mod_perl 1.29. Perl is 5.8.3 on > Fedora FC1 Well, I don't know anything about your specific problem but judging by the lack of responses neither does anyone else. So here's what I'd do: - Download the latest Perl, 5.8.6. - Compile it without thread support. Thread support is still pretty rough and it slows down your Perl anyway. - Re-compile Apache/mod_perl. Make sure you've got mod_perl compiled in static, not loaded as a DSO. DSO and mod_perl are famous for seg-faulting. - Recompile Apache::Registry and any other non pure-Perl modules you might be using. - Say your prayers and give it a try! -sam -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: mod_perlservice? Heck Yeah!
On Fri, 26 Nov 2004 [EMAIL PROTECTED] wrote: > XML-RPC is a standalone system (except for the Java-Apache extension). If > you need to run your webservices system on port 80, for firewalling issues > for instance, you can't also run Apache. That's not ideal. With > mod_perlservice, you can host RPC webservices AND webpages all on one > server! Wow. > > ... > > Also mod_perlservice's configuration system allows you to host MANY RPC > applications on a single Apache server. Try hosting 25 different remote > apps using XML-RPC; there is no native functionality that enables XML-RPC > to accomplish such feats. How about SOAP? I'm sure the problem you identify with XML-RPC don't apply to SOAP. I've created SOAP apps which share space with web-apps and offer multiple modules in a single server. > Well, why not just use mod_perl? > > Well that's a silly question. mod_perlservice is an RPC system, not a CGI > system. You just lost me. Clearly mod_perl is not a CGI system. It's a Perl binding to (nearly) all of Apache, of which an emulated CGI environment is just a small piece. > mod_perl CGI doesn't provide support for marshaling and unmarshaling > aggregates; try passing an array of hashes of arrays of integers > efficiently using CGI, it's improbable. Application functionality like marshaling and unmarshaling can be added by modules on top of mod_perl. Take SOAP::Lite, for example. > It's all Free and GPL. It was developed by me and I decided to share it > with all of you. I don't understand why some of you might snark at my > work. If you'd ever launched a GPL project of your own, I believe you'd > stop short of criticizing before you know the whole story. I've spent > hundreds of hours contributing something useful to the community that I've > received so much from. Every submission should be welcomed. I'm sorry your feelings were hurt. The free software world has never been a very friendly place. I suppose the best we can hope for is that every project is judged fairly on its merits. -sam -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: mod_perlservice? what the heck?
On Wed, 24 Nov 2004, Perrin Harkins wrote: > Did everyone see this on perl.com today? > > http://www.perl.com/pub/a/2004/11/18/mod_perlservice.html > > I just skimmed it quickly, but I can't understand why this is not just a > simple mod_perl module, or even what it solves that XML-RPC didn't. On > the face of it, writing a new embedded-Perl module for apache sounds > like a terrible idea, so I wonder if anyone knows what the story is > here. Wow, that's not just reinventing the wheel, that's reinventing the road too. Even if you can somehow convince yourself that the world needs yet another RPC mechanism, I can't understand why that would require a new Apache Perl module. But, uh, there's a Flash client library. What the heck? -sam -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: Protecting against Cookie copying
On Mon, 8 Nov 2004, Martin Moss wrote: > I'm looking into ways of uniquely identifying a > computer. Intel tried to implement this a while back with a unique ID in the CPU. The public was not ammused. If you do find a way, please tell us so we can find a workaround. > What I wish to do is prevent another user copying the > session cookie, from one computer to another, and then > gaining access. You can get close by using a very short session timeout, tying the IP to the cookie and putting a serial number on each form. I believe this is what my bank does. Sure, the IP can be spoofed or shared, and hackers can automate systems to defeat the timeouts and serial numbers, but it definitely raises the bar. As an added bonus, the serial numbers also help with the ubiquitous catastrophe which is the back button. -sam -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ANNOUNCE: Krang v1.021
Krang v1.021 is now available. Notable changes in this release: - Krang Data Set (KDS) files may now include any number of Media objects. The previous limit was 32,000. - The new DBHost option allows MySQL to run on a separate machine. - Category templates can be turned off per story type. - Several List and Story searches are now much faster. - More bugs are now fixed. Detailed change-log here: http://krang.sf.net/docs/changelog.html Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for magazine editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ANNOUNCE: Krang BricLoader v1.11 Released
The first Krang add-on, Krang-BricLoader v1.11, is now available. With this add-on Krang can load data from Bricolage. If you've been looking for a way to go from Bricolage to Krang without losing data then your search is over! Download this, and someday many more, add-ons from the Krang add-on repository on the Krang website: http://krang.sourceforge.net/ - the Krang team -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ANNOUNCE: Krang v1.020 Released
Krang v1.020 is now available. Notable changes in this release: - Added support for Fedora Core 2. - Upgraded to HTML::Template v2.7, fixing a bug in the handling of cached templates. - More bugs are now fixed. Detailed change-log here: http://krang.sf.net/docs/changelog.html Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for magazine editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ANNOUNCE: HTML::Template 2.7
HTML::Template - a Perl module to use HTML Templates CHANGES - New Feature: Added javascript escaping with ESCAPE=JS. (Craig Manley) - Bug Fix: Improved cache keying to be sensitive to options which alter the compilation of templates (path, search_path, loop_context_vars and global_vars). Calls to new() with different settings for any of these options will no longer pull incorrect cached objects. - Bug Fix: Added code to detect broken Perl 5.8.0 installs during installation (i.e. Redhat 8 and 9). - Bug Fix: Fixed parsing of ESCAPE='URL' (Paul Baker) - Bug Fix: Added check for empty filename passed to new(). - Test Fix: Migrated tests to Test::More. This will allow the easier introduction of new tests and the use of Devel::Cover. (Gabor Szabo) DESCRIPTION This module attempts to make using HTML templates simple and natural. It extends standard HTML with a few new HTML-esque tags - , , , , and . The file written with HTML and these new tags is called a template. It is usually saved separate from your script - possibly even created by someone else! Using this module you fill in the values for the variables, loops and branches declared in the template. This allows you to separate design - the HTML - from the data, which you generate in the Perl script. This module is licensed under the GPL. See the LICENSE section below for more details. TUTORIAL If you're new to HTML::Template, I suggest you start with the introductory article available on the HTML::Template website: http://html-template.sourceforge.net AVAILABILITY This module is available on SourceForge. Download it at: http://html-template.sourceforge.net The module is also available on CPAN. You can get it using CPAN.pm or go to: http://www.cpan.org/authors/id/S/SA/SAMTREGAR/ CONTACT INFO This module was written by Sam Tregar ([EMAIL PROTECTED]). You can join the HTML::Template mailing-list by visiting: http://lists.sourceforge.net/lists/listinfo/html-template-users -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
RE: newbie confused, documentation seems contradictory and/or inc omplete.
On Thu, 24 Jun 2004 [EMAIL PROTECTED] wrote: > I also get the feeling that module development seems to have more > activity around 2 in other areas. I'm sure you're right. There's a lot of work to be re-done! How much fun is it to work on Apache 1.3 where everything important already works? > Obviously MP is allot different, but one day I think we would want MP to be > a better choice on 2 than 1, and I get the impression the HTTP developers > are moving on to 2, and view 1 as legacy. That might be true. I wouldn't know, since I'm not a core Apache or mod_perl developer. I'm just a mod_perl user, and I pick my technologies based on my perception of their suitability to the task at hand and their maturity. As far as I can tell Apache 1.3 is still the best platform for production mod_perl usage, and will probably remain so for some time to come. -sam -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: newbie confused, documentation seems contradictory and/or incomplete.
On Wed, 23 Jun 2004, Steven Scotten wrote: > Am I clear here that you're suggesting that I scrap the idea of working > with Apache2 and just go back to 1.3? Yes. > I'm concerned that six (or eighteen) months down the line if I have > questions they'll be answered by "you should be running the most > current version, stop pestering with obsolete Apache 1.3" Setting up > a new server has been enough of a pain without doing it again in a > few months. I suppose that's possible, but I find it unlikely. Apache 1.3 is very stable and I don't expect to see a mass shift to Apache 2 in production usage any time soon, particularly in mod_perl programming where the porting costs are non-zero. Actually, considering the relative pace of Apache 2 versus Apache 1.3 development, I think you're more likely to encounter the situation you fear with Apache 2. The chances of a major new release altering significant functionality in Apache 1.3 is quite low. -sam -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: newbie confused, documentation seems contradictory and/or incomplete.
On Wed, 16 Jun 2004, Steven Scotten wrote: > My problem is that I'm trying to pick up mod_perl2 without ever having > used mod_perl before. I agree. I think you should back up a step and get comfortable with mod_perl 1. Unless you're doing this just for the thrill of learning something new and difficult I think you'll get better results faster from mod_perl 1. -sam -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ANNOUNCE: Krang v1.019 Released
Krang v1.019 is now available. Notable changes in this release: - Upgrades can now be re-run even if they failed part-way through previously. Several bugs are now fixed which should make failure less likely than before. - Krang::DataSet, and as a result krang_import, is now much faster when loading large KDS files. - Krang::Site no longer requires a site's preview URL and publishing paths to be unique. Only the publish URL is required to be unique now. - Many bugs are now fixed. Detailed change-log here: http://krang.sf.net/docs/changelog.html Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for magazine editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ANNOUNCE: Krang v1.018 Released
Krang v1.018 is now available. Notable changes in this release: - Krang will keep working if you to delete the 'admin' user. A new hidden 'system' account is now used by automated tasks. - The permissions system is now applied throughout the UI. - The publish_check() method is working again after getting left behind in the Krang::Schedule rewrite. This routine allows an element class to inhibit scheduled publishing. - Numerous bugs have been exterminated. Detailed change-log here: http://krang.sf.net/docs/changelog.html Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for magazine editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ANNOUNCE: Krang v1.017 Released
Krang v1.017 is now available. Notable changes in this release: - A major performance speedup for previewing and publishing is now in place. Links to stories and media which are unchanged since their last publish will no longer trigger publishing. - The category chooser now respects permissions settings. - More bugs are fixed. Detailed change-log here: http://krang.sf.net/docs/changelog.html Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for magazine editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ANN: Krang v1.016 Released
Krang v1.016 in now available. Changes in this release: - Added support for FreeBSD 4.9 and Debian Linux. - Fixed bugs. Detailed change-log here: http://krang.sf.net/docs/changelog.html Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for magazine editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ANN: Krang v1.015 Released
Krang v1.015 in now available. Changes in this release: - Added support for Gentoo Linux, Fedora Core and FreeBSD. - Upgraded Apache and mod_perl to their latest releases. - Fixed numerous bugs and portability problems. - Improved documentation. Detailed change-log here: http://krang.sf.net/docs/changelog.html Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for magazine editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
ANN: Krang v1.014 Released
Krang v1.014, the first public release, is now available. Krang is an Open Source web-publisher / content-management system designed for large-scale magazine-style websites. It is a 100% Perl application using Apache/mod_perl and MySQL, as well as numerous CPAN modules. Krang provides a powerful and easy to use story and media editing environment for magazine editors, as well as a complete template development environment for web designers. On the back-end, Perl programmers can customize Krang to control the data entered in the story editor and add code to drive the templates to build output. Krang can be enhanced with add-ons containing new skins and other new features. Krang easily handles large data sets and can manage multiple websites in a single installation. For more information about Krang, visit the Krang website: http://krang.sourceforge.net/ There you can download Krang, view screenshots, read documentation, join our mailing-lists and access the CVS tree. - the Krang team -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
