PHP Backend Interface
$30-100 USD
착불
I am looking for a simple PHP-based backend system. It should have user authentication but there's no need for an admin system to control the users -- I can do that manually in phpmyadmin. Here is the db schema of the content it will be managing.
CREATE TABLE `pages` (
`page_id` int(5) NOT NULL auto_increment,
`page_slug` varchar(85) NOT NULL,
`page_title` varchar(85) NOT NULL,
`page_h1` varchar(85) NOT NULL,
`page_metadesc` varchar(180) NOT NULL,
`page_metakey` varchar(160) NOT NULL,
`page_content` longtext NOT NULL,
PRIMARY KEY (`page_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
Please see below for additional information and details.
## Deliverables
Here are the additional details...
1. There needs to be a listing page which allows authors to choose which page to edit. The top of the listing page should have some forms which allow authors to search through fields to find pages. A form button should narrow the pages listed on the listing page. In addition, there should be a reset button which removes any search. The listing page should be paginated.
2. There needs to be a way to add new pages. This script should be the same script as the edit script.
3. The edit script needs to be able to populate all of the fields by pulling in information from the database. There should not be any escaping of quotes or any other change done to the data when the edit script re-populates the database. In other words, it should appear exactly the same on the page in the backend as it does in the database.
The page_content field should utilize the CodePress system that the latest version of WordPress uses in their Theme Editor section. That system is a web-based code highlight system that allows for easier code-writing than your typical online form text box. Note that the page_content field does have PHP in it along with PHP opening and closing tags (multiple times)! This would obviously need to be accounted for.
Lastly, the page_slug field should only allow lowercase characters and the page_metadesc field should only allow 160 characters (outside of the database limitation, it should tell the author how many characters are left inside of the 160 character limit). Errors should be handled intelligently -- in other words, changes should be populated into the fields after an attempt at saving the changes and the error should be reported to the user in a clear manner. Changes should not be wiped out if an error occurs. All of the character limitations are made clear by the schema.
프로젝트 ID: #2858834