Example Any words: php_solr

Example All words: Simple PHP Agenda




absolutengine

Absolut Engine, a news publishing system once, more of content management system (CMS) today, aims to be a simple and flexible PHP framework. With introduction of modules in v1.70 and a rewrite in v1.72 everything seems to be on way to stable and efficient PHP framework. This is CMS with XHTML 1.0 Strict valid output, using PHP/MySQL, clean URLs/friendly URLs, SEO (search engine optimization) enabled CMS.

seo css htaccess xhtml php newspublishing framework mysql cms webstandards

bad-bot-blocker

Block bad, possibly even malicious web crawlers (automated bots) using htaccess.

apache-htaccess-wp

DescriptionIf you are worried about your WordPress blog getting hacked, this can help immensely. It adds a 2nd layer of security to your blog by requiring a username and password to access anything in the /wp-admin/ folder. How it worksThe plugin is simple, you just choose a username and password and you are done. It writes the .htaccess file, without messing it up. It also encrypts your password and creates the .htpasswd file, as well as setting the correct security-enhanced file permissions on both. SettingsThis plugin automatically picks all the right settings for where to save the .htpasswd and .htaccess files, but you can easily change those settings to anything you want. You can change it whenever you want right from your WordPress Admin Panel. Installationpload aa-password-protect.zip to the /wp-content/plugins/ directory nzip into its own folder /wp-content/plugins/aa-password-protect/aa-password-protect.php ctivate the plugin through the Plugins menu in WordPress by clicking "AskApache Password Protect" o to your Options Panel and open the "AskApache Password Protect" submenu. hoose a username and password and hit the "Password Protection" button. Example OutputHere is a sample of the .htpasswd file output by the plugin. # BEGIN AskApache Password Protect askapache:$1$UUNC/Y4z$2HrLVf23pizdtlUXazGbN1 # END AskApache Password Protect/wp-admin/.htaccess # BEGIN AskApache Password Protect AuthName "Authorization Required" AuthUserFile /htdocs/.htpasswd AuthGroupFile /dev/null AuthType Basic Require user askapache # END AskApache Password Protect

plugin php authorization username htpasswd wordpress password security linux htaccess blog apache

psop

Psop - Optimize your web scripts without a cache.Currently optimizing following files: PHP, CSS, XML, JS, PHTML. (Not finished: .htaccess, asp) Why PsopOptimizationNo information available about optimization. CompressionCompress files (remove comments and whitespace) Remove hidden directories (like .svn) LimitationsError messages will not contain the correct line of the error You must have a stable website in order to use psop Benchmarks Description Time before Time after Relative Compiling website with Zend Framework 33s 30s -9% Symfony Sandbox Project 30s 28s -7% phpBB3 with sample database (16mb) 31s 28s -10% Psop benchmarks Psop Version Application/Library Time Compression unreleased Zend Framework < 5s 38% unreleased Symfony Sandbox Project < 5s 43% unreleased phpBB3 < 5s 80%

run optimize css javascript images php smaller scripts faster optimizer html optimization

drupal-intergration-with-other-php-apps

The idea is to expose Drupal's commonly generated html output to other php application's template. So it's possible that your users coming from your drupal app going to your other php applications like (magento, sugarcrm, digishop..) will see the similar menus, etc.. This workaround will only exposed Drupal's: 1. Node 2. View 3. Region 4. Menu First install the custom page module. http://drupal.org/project/custompage Make use of the functions available in custompage to output your desired Drupal HTML. http://drupal.org/node/286219 Simple Scenario A stand alone script public_html/standalone_test.php public_html/html/standalone_template.tpl.php Working prototype at: standalone_test.php Simple Scenario A stand alone script that's not in a location where Drupal expects. Solution also based from blog: http://agaric.com/note/access-drupal-functions-and-session-from-a-php-script-a-site-subdirectory Remember to change $base_dir = substr(getcwd(), 0, -6); depending on your current working directory. public_html/script/standalone_test_location.php public_html/html/standalone_location_template.tpl.php Working prototype at: public_html/script/standalone_test_location.php Integration Scenario a. Drupal and other third party php applications would call init_set functions, thus having a problem of duplicate calls of ini_set functions errors. That's why it's remove the ini_set commands from settings.php and move/convert those commands to .htaccess Here are the commands to add in .htaccess php_value session.cache_expire 200000 php_value session.cache_limiter none php_value session.cookie_lifetime 2000000 php_value session.gc_maxlifetime 200000 php_value session.save_handler user php_value session.use_only_cookies 1 php_value session.use_trans_sid 0 Here are the function calls to comment out in settings.php / ini_set('session.cache_expire', 200000); ini_set('session.cache_limiter', 'none'); ini_set('session.cookie_lifetime', 2000000); ini_set('session.gc_maxlifetime', 200000); ini_set('session.save_handler', 'user'); ini_set('session.use_only_cookies', 1); ini_set('session.use_trans_sid', 0); b. Drupal bootstrap switches sql schema. A number of solutions available here: I personally just like to have the two applications to be in the same schema with two different prefixes. 2. Or at the integration function call just switch back the schema to the third party app. Sample file: sample_third_party_template.php

drupalintegration

phprotect

PHProtect is a content protection system coded in PHP. PHProtect works under GNU/Linux, FreeBSD, OpenBSD, NetBSD, OSX, Solaris and NT/2K, they must have a CGI PHP Interpreter or Module installed on the webserver or it won't work, it is "PHProtect", note the PHP . This program will allow you to protect a single web file whether it be PHP, HTML or ASP without having to use .htaccess. Authentication is done by a form which pulls a username and password (EG: PHP with the password ASP) from a configuration file, and if it matches what a user has submitted then it will display the content. You are probably wondering, well why can't users just access the protected file from a directory if they are smart enough to know what it's filename is?, the answer to that is simple using special code it will stop direct access to the file unless someone logs in properly on the login form, that's protection at it's best. An added feature is the ability to retrieve your username/password via a script, if you don't have access to the configuration file. PHProtect also supports the ability to use a MySQL Server for authentication, however it only connects to the server. Future releases will support the ability to change the password using a webform and store usernames and passwords in a MySQL Database.

content authentication php protection authorization

cwsadmin

cwsAdmin offers a command line, menu-driven interface for: Apache: virtual host creation (single conf, or split-configuration) subweb creation enable/disable virtual hosts editing: Apache conf files php.ini htaccess files apachectl (single machine or webfarm) User Management: LDAP search for LDAP object add/remove user from LDAP group add/remove ldap group add/remove ldap organizational unit create new LDAP user create new LDAP object copy/move LDAP objects Htgroup create/delete user add user to existing web change user password list active users report users (by web) Database Management: Mysql add/remove database add/remove users report user access/rights list databases MSSQL add database add user Postgresql add database add user Analog: run stats create new configurations (vhost) Misc: generate random password generate welcome email (customizable message) add/remove user to/from listserv

postgresql apache htgroup email ldap pdf report mysql analog mssql python

phpsyshealth

LAMP??????????????????????????????????????? ????LINUX(CentsOS4????) Apache MYSQL PHP4,5 ??1?????????????????????????? htaccess?????? BASIC???????????

bloghost

IntroductionIf you have a source web site (A), you can create another one website (B) that all pages are same as site (A) except domain name. This project was created by using PHP language. First, you can setup .htaccess file to rewrite all HTTP request into one main.php, then this program will automatically download web page from another website and caching it. Please told me if you using this class. Thank you. FeaturesSupport caching: All data are static HTML. You can setup the expired time. Locking rule: Only one request to source web site when multiple requests happened. These sites was hosting by using bloghost: http://software.sopili.net/ http://official.sopili.net/

php blog host caching

paradiseboard

1. Kern Den Kern des Systems bilden sog. Engines, welche dann auf die Plugins, Module und Komponenten zugreifen. Durch den Einsatz besagter, wird das System sehr flexibel und erweiterungsfähig. Momentan sind folgende Engines geplant: Userengine (Verantwortlich für: Rechte, Login, Registrierung, Profil, Signatur und Avatar.) Templateengine (Verantwortlich für das Aussehen des Forums.) Boardengine (Verantwortlich für Posts, Threads, Foren und Kategorien.) Registryengine (Übernimmt die Verwaltung der Registry, in der z.B. Boardname, News, Einstellungen usw. gespeichert werden.) MCP-Engine (Stellt sämtliche Moderationsfunktionen und das moderative Rechtemanagement zur Verfügung.) ACP-Engine (Stellt die Funktionen des Admin Control Panels zur Verfügung.) 2. Foren Die Foren sind natürlich die wichtigste Funktion im Forum, hierfür sind folgende Funktionen geplant: Genaue Einstellungen für jede Benutzergruppe möglich, welche Informationen sie über einzelne Foren sehen darf. Auch existieren Einstellungen über die Felder die angezeigt werden sollen. 2. Den Administratoren ist es möglich, für jeden einzelnen Thread/Post spezielle Rechte zu vergeben, dies ist jedoch nicht nötig. Auf diese Weise ist es allerdings möglich, z.B. zwei Usern das Schreiben eines gemeinsamen Posts zu ermöglichen. 3. Zum Posten wird ein WYSIWYG-Editor eingesetzt, welcher flexibel erweiterbar sein wird. Dieser WYSIWYG soll später auch Funktionen zum einfachen bearbeiten von Dateianhängen und Bildern bieten. 4. Es soll die Möglichkeit geben, Ankündigungen oder Mitteilungen, nur unter bestimmten Umständen (Useralter ist höher als, User ist in Usergruppe, Usersname enthält, User ist registriert seit, usw...) 5. Neuordnung der Postreihenfolge 6. RSS/Atom 3. User, Gruppen & Profil Verschiedene ?Account?-Aktivierungsmöglichkeiten (z.B. Benachrichtigung per ICQ, Twitter, eMail, PN usw. möglich.) - Ebenfalls sind Einstellungen möglich welche Aktionen der User nach seiner Registrierung durchführen muss (z.B. Profil ausfüllen, Formular ausfüllen usw.) bevor er z.B. in eine Usergruppe kommt, Posten darf, freigeschalten wird usw. Auch sind Einstellungen für ?Ziele? möglich, die z.B. die Benutzergruppe, die Rechte oder ähnliches ändern sollen (Bestimmte Postanzahl, Bestimmte Zeit registriert, usw.) Für das Profil sollte es natürlich möglich sein, eigene, neue Felder zu definieren und deren Anzeigeplätze einzustellen. Für Gruppen können verschiedene Sichtbarkeits- und Beitrittseinstellungen gewählt werden (z.B. nur wenn user bereits in dieser Gruppe ist, oder wenn er mehr als 100 Posts hat o. ä.) Spezielle Gruppenräume mit Dateispeicherplatz, Lesezeichen, Notizblock, Galerien usw. 4. Blog Jeder User soll sein eigenes Userblog haben. (RSS- und Atomfeed). Auch Gruppenblogs sind möglich. Kommentarfunktion mit verschiedenen Einstellungen. Moderative Optionen (Freischalten von Posts, Kommentaren usw.) WYSIWYG-Editor mit Optionen für Bilder, Sounds und Videos. Trackbacks / Pingbacks XML-RPC 5. CMS Grundlegendes erstellen von eigenen Seiten mit WYSIWYG-Editor und den oben genannten Optionen. Erstellen von Navigationen (mit Rechtemanagement usw.). Portalseite. Vordefinierte Blöcke (Statistiken, Wer-Ist-Online, neue Posts, neue Blogs, Team, usw.) möglich. Eigene Blöcke erstellen. 6. Moderation Eigene Oberfläche mit extra Login. ?Teamboard? in dieser Oberfläche. Genaue Rechteeinstellungen. Pruning-Einstellungen Benachrichtigungsoptionen für Melde-Funktion (ICQ, Twitter, eMail, SMS, usw.) 7. Administration Eigene Oberfläche mit extra Login Konfigurator für .htaccess ?Adminmodule?. Normale Adminfunktionen Statistiken Rechte der Administratoren (Beschränkungen, Rootadmin). 8. Entwicklerapplikation (Desktop) Einfaches Erstellen von Templates (auch mit Bildeditor.) Erstellen von Modulen, Plugins, Komponenten. Einsteigerdokumentation. Wizards für Sprachpakete, Templates. Wizards für bestimmte Modul-/Plugin-Typen. Wizard zum erstellen von Anleitungen. 9. XML-RPC-Applikation Ermöglicht das bloggen in der Boardsoftware auch offline. Bildeditor, Soundanpassungen. Uploader 10. Desktopwecker Benachrichtigung bei neuen Beiträgen in bbonnierten Themen.

amigable

Amigable es un mini-framework para programar aplicaciones y sitios web en PHP >= 4.3 Esta diseñado para trabajar con clean_urls fácilmente Contiene un gestor para base de datos, es seguro y flexible Además de librerías básicas: paginado, texto, html, curl, ftp, etc. Como instalar el frameworkLa instalación es muy similar a la de cualquier otra librería para PHP, solo basta descomprimir el archivo del framework en alguna carpeta accesible para nuestros scripts Dicha ubicación puede ser configurada para el entorno de PHP a través de la opción include_path en el php.ini, o bien, usando ini_set() php.ini ; UNIX: "/path1:/path2" ;include_path = ".:/usr/share/php" ; ; Windows: "\path1;\path2" ;include_path = ".;c:\php\includes"test.php En resumen, se recomienda ubicar el framework fuera de nuestro sitio web y configurar el php.ini (tal ves hacerlo vía PHP sea mas sencillo, pero puede resultar inseguro) Modo de usoUna ves podamos incluirlo en nuestros scripts, el siguiente paso es aprender a crear un índice de aplicación o bien, un script controlador /sandbox/test.php __FILE__)); // inicializar el sistema run(array( //'global_permissions' => 0777, 'application_index' => __FILE__, //'temporary_files' => '/tmp', //'allowed_chars' => 'a-zA-Z0-9/.', //'dsn_string' => 'mysql://root@localhost/test', //'timezone' => 'America/Mexico_City', //'charset' => 'UTF-8', //'rewrite' => FALSE, //'suffix' => '.do', //'cache' => 'php' ))); echo link_to('foo'); # /sandbox/test.php/foo/ option('rewrite', TRUE); option('suffix', '.doo'); echo link_to('foo'); # /sandbox/foo.doo ?>Solo basta incluirlo, configurar y ejecutar el framework con la función run() para comenzar a utilizar sus funcionalidades. Además, no es obtrusivo con nuestro propio estilo de programación Todas las opciones, excepto rewrite y suffix, no pueden ser modificadas en tiempo de ejecución Base de datosEl inicializar la librería para manejar nuestra base de datos requiere de la opción dsn_string en la configuración del framework, antes o durante la llamada a la función run() 'scheme=sqlite;path=/tmp/test.db' )); // ejemplos de uso $id = db_insert('tabla', array('columna' => 'valor')); /* INSERT INTO tabla(columna) VALUES('valor') */ $id = db_update('tabla', array('columna' => 'valor')); /* UPDATE tabla SET columna = 'valor' */ $result = db_select('tabla', ALL); /* SELECT * FROM tabla */ $rows = db_fetch_all($result); $one = db_fetch($result, AS_OBJECT); var_dump($result, $rows, $one); ?>Adaptadores disponibles: mysql, mysqli, sqlite, pgsql La conexión se hace de manera automática, siempre y cuando se configure correctamente el DSN de conexión a la base de datos Es importante decir que cada operación hace limpieza automática de las variables, por lo que no es necesario hacerlo manualmente Configurar mod_rewriteSolo tenemos que copiar el archivo htaccess.txt de la carpeta del framework a la ubicación de nuestros documentos web, en el mismo lugar del índice de aplicación Renombramos con un editor el archivo a .htaccess, cambiamos las palabras y por los valores que hagan falta y des comentamos las lineas necesarias, ej. /sandbox/.htaccess ErrorDocument 404 /sandbox/test.php RewriteEngine On RewriteBase /sandbox RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ test.php/$1 [PT,L]También se debe configurar el entorno usando la instrucción option('rewrite') Esto es obligatorio si se quiere hacer uso de urls amigables dentro de nuestra aplicación, aunque se recomienda deshabilitarlo localmente mientras se desarrolla Acerca de clean_urlsEs muy sencillo trabajar con urls amigables, solo necesitamos recordar el concepto de I/O para una aplicación o sitio web, ej. /index.php?foo=bar&does=13 De esta manera ya entendemos la entrada habitual a una parte de nuestra aplicación. Al emplear urls amigables en lugar de variables necesitaremos usar segmentos, ej. /index.php/foo/bar/does/13 __FILE__)); // localmente: off if ( ! is_local()) option('rewrite', TRUE); // ruta principal dispatch('*', 'ejemplo'); function ejemplo($modulo = 'default', $accion = 'index', $id = 0) { // modulo a cargar $mod_file = PATH.'/modules/'.$modulo.EXT; if ( ! is_file($mod_file)) echo 'El modulo no existe: ' . $modulo; else { // lo incluimos include_once $mod_file; // acción a ejecutar $callback = $modulo . '_' . $accion; if ( ! function_exists($callback)) echo 'La acción no existe: ' . $accion; else { // ejecutamos e imprimimos los resultados echo 'Hola mundo!'; echo call_user_func($callback, $id); echo ''; } } } ?>Independientemente de la configuración de mod_rewrite la lógica de los segmentos jamás se ve afectada, inclusive es recomendable utilizar solo segmentos para operaciones visibles e indexables Como se puede observar el framework no ejecuta nada por si cuenta, obviamente hay que implementar la forma en que vamos a ejecutar nuestros scripts DocumentaciónLa mayoría del código viene documentado, se recomienda configurar la carpeta del framework también en algún editor que permita calltips. Adicionalmente se puede obtener una copia personalizada de la documentación utilizando herramientas compatibles con phpdoc (http://www.phpdoc.org/) En un sistema Ubuntu fácilmente se puede conseguir con una instrucción similar: $ sudo phpdoc --directory /usr/share/php/Amigable --target ~/refsNOTAS La única finalidad de usar urls amigables es la de proveer información en forma de segmentos para implementar cualquier tipo de entrada que se plantee para nuestra aplicación El hecho de usar mod_rewrite no hace que nuestras urls cambien mágicamente, para ello siempre hay que generar nuestros enlaces usando la función link_to() Recuerda que utilizar un framework es como emplear una caja de herramientas: no te hace el trabajo, te lo facilita

clean_urls php mini mod_rewrite mvc framework

bashsp

Aboutmod_bashsp is primarily a joke but also a fully functional Apache 2.2 module to execute "Bash Server Pages", that are dynamic generated web pages using Bash. InstructionsUsageTo activate mod_bashsp module, include a block similar to the following in your httpd.conf file: SetHandler bashsp-handler As an alternative, you can put the following into a .htaccess file and then request files with ".bsp" extension from that location: AddHandler bashsp-handler .bspAfter reloading/restarting your server, you should be able to see your Bash Server Pages working. InstallationCheck out INSTRUCTIONS.txt in the source code. Hope to have a compiled version very soon :)

bash apache

panoye-f

Panoye-fPanoye-f is a lighweight php framework used for the panoye (panoramic) photosharing site HOWTOYou must have php5 and command line php5 installed (php5-cli) on your computer before starting with panoye-f. You would probably need mysql database also. After unpackig the archive - go to the place where you want to create your panoye-f application. Type the following command in shell: php -q app_tools/create_app.php This will create the basic php scripts and directories for your web application: app/ app/lib/ -> the place for all your classes app/objects/ -> ORM classes generated by the framework (you can edit them later) app/pages/ -> Page classes (one class for page) app/templates/ -> HTML/PHP templates used in the application app/test/ -> unit tests (you can delete existing and create your own, of course) app/Application.class.php -> configuration cache/ -> temporary cache data (you must empty it when you add new classes) index.php -> ... .htaccess -> ... When you create new pages and/or classes in your application, you must clear your application's cache: php -q app_tools/clear_cache.php If you need to change any configuration settings - edit the app/Application.class.php. Every class must be saved in a ClassName.class.php file somewhere in app/lib or app/objects (but app/objects should contain only ORM classes). DATABASETables used with panoye-f ORM system must have these three columns: ID - auto increment indeger CREATED - timestamp (updated once on insert) UPDATED - timestamp (updated on every $object->update() or $object->save()) If you want your pages to have "search engine friendly" links you must add also SEF_LINK column (VARCHAR). SEF links will bi created automatically on $object->insert(). CRUD pagesAfter installed - go to http://localhost/your_app/application. You can create ORM objects and CRUD pages there. Of course - do look at their source and change what you need. DEPLOYMENTWhen you deploy your application be sure to delete the app_tools directory, and set const DEBUG = false; in your app/Application.class.php! QUESTIONSIf you have any questions - please ask them on the blog.

php panoye php5 framework

phptact

TACT is a relatively simple MVC framework that is driven by Components. I havn't yet moved it to google codes svn servers, so you can view the repository here: svn co http://svn.asdfjkl.com.au/tact/trunkCheck out the Quick Start Guide to see what you can do, and get started RequirementsLinux (Not yet tested in Windows) PHP Version => 5.1.6 (5.2.5 Recommended) Modules: php-pdo, php-json Note: json is strongly recommended, however if its not found it will fall-back to its own implementation of json. Recommended: php-cli, if you want to run the command line scripts Note: magic_quotes_gpc must be off, either by .htaccess or in the php.ini file DatabasesThe included PDB class which controls connectivity to the database supports (In order of tested installs) MySQL via PDO (Easily) Oracle via PDO (Yes it does work! As long as you've compiled your PDO w/ Oracle) SQL Server via PDO (Nothing in production that I know of) However, you don't even need to use PDB and can use whatever else you wish, but some Components require the PDB Class Structure to work correctly BackgroundThe following frameworks had some influence on the initial direction of tact, you could say TACT is a mixture of these: Oracle HTMLDB / Application Express PHP Prado Framework .NET Java Common-Controls Tiles from Java Struts (Not Struts itself!) ActiveRecord It started in about mid-2007, and is mainly focused, but not limited to more complex data-driven applications.

rad commoncontrols mvc php prado activerecord components

barebonesmvc-php

BareBones: a one-file, no-configuration, MVC framework for PHP5.Update: "CuspOf1000Downloads" Weighing in at just 60 lines of code (excluding comments), the BareBones MVC framework for PHP5 is perfect for: small-to-medium websites; in other words, the vast majority, i.e. shared hosting sites without htaccess and/or mod_rewrite capabilities as a foundation for PHP software such as CMS, weblog and/or wiki software as a foundation for a "full stack" framework; e.g with (request) dispatching 1, object-relational mapping (ORM) 2, etcetera (see footnotes at bottom) BareBones' sole goal is proper separation of concerns between the Model, View and Controller layers; this is achieved through just two abstractions, the controller itself and a "ModelTransferObject" (MTO), and is exemplified through the source for the following "template method": static function sendResponse(IBareBonesController $controller) { $controller->setMto($controller->applyInputToModel()); $controller->mto->applyModelToView(); }Using BareBones can be succinctly summarized as requiring just 2 steps: implementing applyInputToModel() calling sendResponse() Or, in more detail, from the source comments: * require('barebones.lib.php'); // 1) require * * class DemoController extends AbstractBareBonesController {// 2) extend * function applyInputToModel() { // 3) implement * $mto = new BareBonesMTO('barebones.tpl.php'); // 4) instantiate * $mto->setModelValue('message', 'bare bones demo'); // 5) assign * session_start(); $_SESSION['preserved'] = 1; // 6) preserve (optional) * return $mto; // 7) return * } * } * * DemoController::sendResponse(new DemoController()); // 8) sendNote that despite being static, because sendResponse() accepts a new object instance, thread safety is maintained through "stack confinement" Notes on the inspiration for BareBones, as well as observations on some patterns besides MVC, can be found at http://docs.google.com/Doc?id=dcdwmnq5_22fpsbjr Direct inquiries to jemptymethod at gmail dot com "A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away." (Antoine de Saint-Exupery) Because AbstractBareBonesController::sendResponse() is static, if htaccess and mod_rewrite functionality is exposed to your website, it is an easy matter to add dispatching, without relying on reflection.By not coupling itself to a specific ORM implementation, BareBones' avoids bloat that would be unnecessary should database access not be necessary, and might even encourage a more orthogonal design and/or best-of-breed approach when ORM is deemed necessary

mvc oo web php5 php

webtoftp

webtoftpWelcome on the official website of webtoftp. This tool is designed for users that wish to upload, download and update files on their FTP server without using the FTP protocol. How does it work? webtoftp only uses the HTTP protocol to transfer files, thus you can manage your website even if you are at work (or anywhere else) and that the firewall blocks FTP connections. What you will need however is a PHP engine installed on your server with permissions to write/read/... well, actually all the permissions that you would need if you wanted to manage your files with the FTP protocol! How do you use it? It is simple and easy: just upload this tool on your server, protect it by an .htaccess and you're done! OverviewList the fileswebtoftp has a very simple interface and is designed to be used by everyone. Its usage is very similar to what you would do in Windows, Mac or Linux, although you do not have the right-click menu to help you. But it isn't a problem as you will see. General interface: list folders and files, display their size, browse through the hierarchy, ... If you click on a folder name, you will display its contents. If you click on a file name, you will be redirected to it, such as a normal user would do by typing the file location in the address bar of his web browser. UploadYou can easily upload some files in the current folder by clicking the "upload" link on top of the page. It is possible to send 20 files per upload (limited in size, depending on your server configuration). Upload page: select up to 20 files and upload them in the folder you last visited. Download, rename, deleteAfter you have uploaded the files on your server, you can easily download, rename or delete them by using the links on the right of the page. Note that you directly download the source code of all the pages, so you will get the .php files without any compilation/interpretation. Upload page: select up to 20 files and upload them in the folder you last visited. DownloadYou can get the latest release of webtoftp here: releases. LicenseThis software is provided under the GNU General Public License (v3). Copyright 2006, pb_ee1

server fileupload php management ftp http administration

slightphp

SlightPHP???????PHP?????PHP5?????? ????1 ????????????????????pecl?????? 2 ?????????? 3 ??Apache?Rewrite???URL 4 ??Sphinx? 5 ?????????6K???????????????? 6 ??Hello, world!??? ??index.php ??? ??index.php???????zone????zone?????page.page.php ??? ??????????index.php?? http://localhost/index.php ????zone ????????????"zone" page ??????????.page.php????????"page" entry ????????Page??????????"entry" appDir ??????????"."??????? splitFlag ???????"/" inPath entry???????????????????????????? http://localhost/index.php ???? http://localhost/index.php/zone/page/entry ?? ????? appDir/zone/page.page.php??pageEntry?? ?????????? SlightPHP::setDefaultZone("user"); SlightPHP::setDefaultPage("profile"); SlightPHP::setDefaultEntry("update");??? http://localhost/index.php ?????? appDir/user/profile.page.php??pageUpdate??????? http://localhost/index.php/user/profile/update ??URL ????????-????????? SlightPHP::setZoneAlias("user","u");??????? http://localhost/index.php/u/profile/update ? http://localhost/index.php/user/profile/update ??????? ???????user????u ?????(splitFlag)zone,page,entry???????/???????????????? SlightPHP::setSplitFlag(".")???????? http://localhost/index.php/user.profile.update ????????.html http://localhost/index.php/user.profile.update.html ????? ??????,?????? SlightPHP::setSplitFlag("-.") http://localhost/index.php/user-profile-update.html ??????? ??Apache Rewrite???.htaccess???apache???????????? RewriteEngine on RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ index.php/$1 [L]??????????? http://localhost/user/profile/update ??????? SlightPHP::setSplitFlag(".");??????????? http://localhost/user.profile.update ?????????????????? http://localhost/profile/update ??apache??????????????? RewriteRule ^(/profile/.*)$ /index.php/user/profile/update/$1 [E=PATH_INFO:$1,L]????$inPath$inPath[0] ????? zone??? $inPath[1] ????? page??? $inPath[2] ????? entry??? $inPath[...] ????????????????html? http://localhost/index.php/user/profile/update/other1/other2/... inPath???? $inPath=array("user","profile","update","other1","other2","...")??appDir??????????????????? SlightPHP::setAppDir("/home/www/myAppdir");?http://localhost/index.php/user/profile/update ???? /home/www/myAppdir/user/profile.page.php??pageUpdate?? ????appDir?????????? ??????????samples????

framework php slightphp

transporrent

The Sourceforge project has more documentation and gets updated a bit more often. Transporrent is a collection of simple technologies. In a nutshell, it should work this way: A browser extension adds a new HTTP Header to normal file requests, asking if the server supports Transporrent. If the server does, it will respond with the normal file, plus a special header pointing to a .torrent file which contains the originally requested file. The browser extension will download the file normally, unless it is slow or very large, at which point it will download the .torrent file and start it by calling one of several existing BitTorrent extensions (Foxtorrent, Bitfox, etc.). Transporrent is aimed at resolving a subset of the 'Slashdot effect' problem, the subset in which the BitTorrent protocol is most effective. BitTorrent is designed to be especially effective at times of high peak load, but can be slower than standard http with just a few peers. Transporrent will only kick in if it detects the server is slow. Also, BitTorrent is more effective with larger files. So Transporrent won't try to get standard .html files. It will only target file types that are typically larger (initial implementations will likely focus on media files). I am starting simply with documentation and planning. This will lead to 2 file groups: the afore-mentioned browser extension, and a server-side php script or Apache mod (in the form of .htaccess) which sets up the server for Transporrent.

downloads firefox extensions bittorrent apache

odminko

????????? ????????????? ?????? CMS ????????? Parser 3.2.2 ? MySQL 5. ??? ??????????? ?????????, ? ???? ???????? ?????? FCKeditor, ????? php. ??????????????????????? odminko.zip ???, ????? ?????????? ?????????? www ???? ? ????? ???-????????????. ???????? ???? ?????? (?????????? ?????? ? MySQL). ???????????? ? ??? ?????? ?? odminko.sql. ?????? ?????? ???? ? UTF8. ? ??????? sites ??????? ?????, ?? ??????? ????? ???????? CMS. ??????? ????????? ?????????? ? ?? ? ???????? auto.p. ????????, ???????? ???????? ????????? ????????? ? ???????? .htaccess. ????????, ?????????????? ?????????? www ? ????? ?????? (? ?????? ??? ??????? ????????? ?????? ? ????????? www): RewriteCond %{HTTP_HOST} ^odminko.ya$ [NC] RewriteRule ^(.*)$ http://www.odminko.ya/$1 [R=301,QSA,L]??????? ????? ???????? ?? ?????? htt?://???_?????.nu/admin/edit/ ??????? ??? ? ???? ?? ?????????. ??????, ??? ?????? ???????????????? ??????? ???????? ?? ????????? ???????? ? ????? ????????????, ? ?? ????????????.

web extjs parser3 cms