PHP flat file CMS

Imam zalju da napravim jednostavni flat file cms (npr. pluck ili ecoCMS) sa PHP-om. Napravio sam vec jednu verziju ali glavni su mu problemi sto ne mogu dodavati stranice, ne mogu im mjenjati redosljed i tesko se mjenja dizajn zato sto se svaki put CMS mora podesiti na neku novu temu. Samo mogu mjenjati sadrzaj mojih stranica i ineke osnovne konfiguracije ali to u obliku WYSIWYG kao google sites.

Mislio sam da pocnem iz pocetka ali nemam dovoljno znanja iz php-a da napravim ono sto bi zelio. Kupio sam jednu dobru knjigu “PHP i MySQL Razvoj aplikacija za web” od Luke Welling i Laura Thomson (800 strana) ali se boim da kad je procitam opet necu znati ono sto mi treba. Da li neko zna neku manju i bolju knjigu ili TUT za ovo sto meni treba u php-u.

Unaprjed hvala.:slight_smile:

Treba ti znanje mysql-a i php-a, pročitaj knjigu :smiley: više manje sve knjige pokrivaju takve stvari, ne direktno, ali ako imaš nešto u glavi brzo ćeš skužiti sam kako što napraviti. Inače pitanje zbog čega flat file? zašto ne koristiti bazu?

Problem je ako koristim knjigu ona kao vec napisano uci o kombinaciji PHP i MySQL-a.
Bazu podataka ne koristim zato sto je to previse komplikovano za mali CMS i zato sto je BEZVEZE. Ja ne kazem da baze podataka nisu dobra stvar ali kad je u pitanju mala aplikacija koja se treba brzo premjestati sa servera na server onda je komplikovano dodavati novu bazu i etc.

Prije nego se baciš na knjižurine, možda ti ovakvi primjeri koda više pomognu.

HVALA, ovo mi je jako pomoglo, ali ovo je vise file meneger a ne cms iako u njemu ima zanimljivih skripti.

YouTube ti ima dosta tutoriala kako napraviti CMS module, osnove PHP-a i naprednije stvari. Meni je najbolji “phpacademy” na YouTube-u, a ako bas hoces detaljna uputstva kako napraviti CMS od A do Z za to je najbolje skinuti video lekcije “Lynda.com.PHP.With.MySQL.Essential.Training.DVD”.

Kao sto naslov vec kaze cilj mi je napraviti FLAT FILE CMS a ne sa mysql-om ili nekom drugom DB. Ali opet hvala za tip.

Preporučam da koristiš SQLite. Cijela baza je sadržana u jednoj datoteci, nema nikakve konfiguracije, prenosiva je, podržana u PHP5 itd. itd.

Nađi na internetu priručnik “Using SQLite 2010”.

The “Lite” in SQLite does not refer to its capabilities. Rather, SQLite is lightweight when it comes to setup complexity, administrative overhead, and resource usage.
SQLite is defined by the following features:

Serverless
SQLite does not require a separate server process or system to operate. The SQLitelibrary accesses its storage files directly.

Zero Configuration
No server means no setup. Creating an SQLite database instance is as easy as opening a file.

Cross-Platform
The entire database instance resides in a single cross-platform file, requiring no administration.

Self-Contained
A single library contains the entire database system, which integrates directly into a host application.

Small Runtime Footprint
The default build is less than a megabyte of code and requires only a few megabytes of memory. With some adjustments, both the library size and memory use can be significantly reduced.

Transactional
SQLite transactions are fully ACID-compliant, allowing safe access from multiple processes or threads.

Full-Featured
SQLite supports most of the query language features found in the SQL92 (SQL2) standard.

Highly Reliable
The SQLite development team takes code testing and verification very seriously.
Overall, SQLite provides a very functional and flexible relational database environment that consumes minimal resources and creates minimal hassle for developers and users.

SQLite is a in-process library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. The code for SQLite is in the public domain and is thus free for use for any purpose, commercial or private. SQLite is currently found in more applications than we can count, including several high-profile projects.

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file. The database file format is cross-platform - you can freely copy a database between 32-bit and 64-bit systems or between big-endian and little-endian architectures. These features make SQLite a popular choice as an Application File Format. Think of SQLite not as a replacement for Oracle but as a replacement for fopen()

SQLite is a compact library. With all features enabled, the library size can be less than 300KiB, depending on compiler optimization settings. (Some compiler optimizations such as aggressive function inlining and loop unrolling can cause the object code to be much larger.) If optional features are omitted, the size of the SQLite library can be reduced below 180KiB. SQLite can also be made to run in minimal stack space (4KiB) and very little heap (100KiB), making SQLite a popular database engine choice on memory constrained gadgets such as cellphones, PDAs, and MP3 players. There is a tradeoff between memory usage and speed. SQLite generally runs faster the more memory you give it. Nevertheless, performance is usually quite good even in low-memory environments.

[quote=“iwwwek”]Preporučam da koristiš SQLite. Cijela baza je sadržana u jednoj datoteci, nema nikakve konfiguracije, prenosiva je, podržana u PHP5 itd. itd.

Nađi na internetu priručnik “Using SQLite 2010”.

The “Lite” in SQLite does not refer to its capabilities. Rather, SQLite is lightweight when it comes to setup complexity, administrative overhead, and resource usage.
SQLite is defined by the following features:

Serverless
SQLite does not require a separate server process or system to operate. The SQLitelibrary accesses its storage files directly.

Zero Configuration
No server means no setup. Creating an SQLite database instance is as easy as opening a file.

Cross-Platform
The entire database instance resides in a single cross-platform file, requiring no administration.

Self-Contained
A single library contains the entire database system, which integrates directly into a host application.

Small Runtime Footprint
The default build is less than a megabyte of code and requires only a few megabytes of memory. With some adjustments, both the library size and memory use can be significantly reduced.

Transactional
SQLite transactions are fully ACID-compliant, allowing safe access from multiple processes or threads.

Full-Featured
SQLite supports most of the query language features found in the SQL92 (SQL2) standard.

Highly Reliable
The SQLite development team takes code testing and verification very seriously.
Overall, SQLite provides a very functional and flexible relational database environment that consumes minimal resources and creates minimal hassle for developers and users.

SQLite is a in-process library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. The code for SQLite is in the public domain and is thus free for use for any purpose, commercial or private. SQLite is currently found in more applications than we can count, including several high-profile projects.

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file. The database file format is cross-platform - you can freely copy a database between 32-bit and 64-bit systems or between big-endian and little-endian architectures. These features make SQLite a popular choice as an Application File Format. Think of SQLite not as a replacement for Oracle but as a replacement for fopen()

SQLite is a compact library. With all features enabled, the library size can be less than 300KiB, depending on compiler optimization settings. (Some compiler optimizations such as aggressive function inlining and loop unrolling can cause the object code to be much larger.) If optional features are omitted, the size of the SQLite library can be reduced below 180KiB. SQLite can also be made to run in minimal stack space (4KiB) and very little heap (100KiB), making SQLite a popular database engine choice on memory constrained gadgets such as cellphones, PDAs, and MP3 players. There is a tradeoff between memory usage and speed. SQLite generally runs faster the more memory you give it. Nevertheless, performance is usually quite good even in low-memory environments.[/quote]

E ovo sam trazio, puno hvala. krecem sa radom 1.1.2011 godine i bice brzo gotov a stavi cu prvu beta verziju na WM forum da je prvi isprobate. :smije:

Nice temu
Hvala vam na dijeljenje


Copyright © 2020 WM Forum - AboutContact - Sponsored by: Mydataknox & Webmaster.Ninja