-- MySQL dump 10.13 Distrib 5.7.23-23, for Linux (x86_64)
--
-- Host: localhost Database: softwax3_cropMap
-- ------------------------------------------------------
-- Server version 5.7.23-23
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
/*!50717 SELECT COUNT(*) INTO @rocksdb_has_p_s_session_variables FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA = 'performance_schema' AND TABLE_NAME = 'session_variables' */;
/*!50717 SET @rocksdb_get_is_supported = IF (@rocksdb_has_p_s_session_variables, 'SELECT COUNT(*) INTO @rocksdb_is_supported FROM performance_schema.session_variables WHERE VARIABLE_NAME=\'rocksdb_bulk_load\'', 'SELECT 0') */;
/*!50717 PREPARE s FROM @rocksdb_get_is_supported */;
/*!50717 EXECUTE s */;
/*!50717 DEALLOCATE PREPARE s */;
/*!50717 SET @rocksdb_enable_bulk_load = IF (@rocksdb_is_supported, 'SET SESSION rocksdb_bulk_load = 1', 'SET @rocksdb_dummy_bulk_load = 0') */;
/*!50717 PREPARE s FROM @rocksdb_enable_bulk_load */;
/*!50717 EXECUTE s */;
/*!50717 DEALLOCATE PREPARE s */;
--
-- Table structure for table `categories`
--
DROP TABLE IF EXISTS `categories`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `categories` (
`categoryid` smallint(6) NOT NULL AUTO_INCREMENT,
`category` varchar(25) NOT NULL,
`archive` tinyint(4) NOT NULL,
`keywords` varchar(250) NOT NULL,
PRIMARY KEY (`categoryid`)
) ENGINE=MyISAM AUTO_INCREMENT=14 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `categories`
--
LOCK TABLES `categories` WRITE;
/*!40000 ALTER TABLE `categories` DISABLE KEYS */;
INSERT INTO `categories` VALUES (1,'Location',0,'gps coordinates'),(2,'Soil Tests',0,'field'),(3,'Yield Results',0,''),(4,'Acreage',0,'crop acres'),(5,'Farm Service',0,'usda'),(6,'Seed',0,'pioneer, dekalb'),(7,'Misc',0,''),(8,'Repairs',0,'highway 257'),(9,'Plow',0,''),(10,'Hp Pivot piplines',0,''),(11,'Planting',0,'gated pipe and corner'),(12,'Map',0,'farm images'),(13,'Hemp',0,'Maps location variety');
/*!40000 ALTER TABLE `categories` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `chemical_used`
--
DROP TABLE IF EXISTS `chemical_used`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `chemical_used` (
`chemicalid` mediumint(9) NOT NULL AUTO_INCREMENT,
`mapid` smallint(6) NOT NULL,
`product1` smallint(6) NOT NULL,
`amount1` decimal(6,2) NOT NULL,
`product2` smallint(6) NOT NULL,
`amount2` decimal(6,2) NOT NULL,
`product3` smallint(6) NOT NULL,
`amount3` decimal(6,2) NOT NULL,
`product4` smallint(6) NOT NULL,
`amount4` decimal(6,2) NOT NULL,
`product5` smallint(6) NOT NULL,
`amount5` decimal(6,2) NOT NULL,
`date` datetime NOT NULL,
`hour` tinyint(4) NOT NULL,
`notes` varchar(200) NOT NULL,
`gps` varchar(40) NOT NULL,
`crop_year` smallint(6) NOT NULL,
PRIMARY KEY (`chemicalid`)
) ENGINE=MyISAM AUTO_INCREMENT=38 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `chemical_used`
--
LOCK TABLES `chemical_used` WRITE;
/*!40000 ALTER TABLE `chemical_used` DISABLE KEYS */;
INSERT INTO `chemical_used` VALUES (1,4,1,20.00,4,4.00,2,2.00,3,25.00,0,0.00,'2011-06-02 06:18:14',0,'hay in corn needs to be sprayed. 2 rounds short of completing lake field also.','',2011),(3,18,1,20.00,4,4.00,2,1.50,3,25.00,0,0.00,'2011-06-01 13:13:20',0,'Alfalfa in corn. Did outside of field with some from yard spray. Tank empty at end of field.\r\n\r\nRoundup in quarts, banvel quarts, amonium lbs, adwet quarts','',2011),(4,3,1,20.00,4,4.00,2,2.00,3,25.00,0,0.00,'2011-06-02 09:39:14',0,'2 rounds in lake field.','',2011),(5,7,1,10.00,4,2.00,2,1.00,3,12.00,0,0.00,'2011-06-02 10:32:08',0,'2 rounds in lake field.','',2011),(6,1,1,10.00,4,2.00,2,1.00,3,12.00,0,0.00,'2011-06-04 06:14:48',0,'90 gal from hpsw to finish.','',2011),(7,8,1,20.00,4,4.00,2,2.00,3,25.00,0,0.00,'2011-06-05 07:32:42',0,'Empty tank.','',2011),(8,6,1,20.00,4,4.00,2,2.00,3,25.00,0,0.00,'2011-06-05 07:32:53',0,'Empty tank. Some went to finish hpsheep.','',2011),(9,2,1,20.00,4,4.00,2,2.00,3,25.00,0,0.00,'2011-06-06 08:50:42',0,'Empty tank. Some will be needed to finish hptopmid.','',2011),(10,10,1,10.00,4,2.00,2,1.00,3,12.00,0,0.00,'2011-06-06 18:52:13',0,'3 rounds in hpnorth finished with load. Most used to do ends.','',2011),(11,10,1,20.00,5,4.00,2,2.00,3,25.00,0,0.00,'2011-06-07 06:06:06',0,'10 gal','',2011),(12,12,1,20.00,5,4.00,2,2.00,3,25.00,0,0.00,'2011-06-07 07:30:16',0,'0 gal','',2011),(13,11,1,20.00,5,4.00,2,2.00,3,25.00,0,0.00,'2011-06-08 06:26:21',0,'0 gal finish up sev09','',2011),(14,11,1,20.00,5,4.00,2,2.00,3,25.00,0,0.00,'2011-06-08 07:20:00',0,'10 gal','',2011),(15,10,1,20.00,5,4.00,2,2.00,3,25.00,0,0.00,'2011-06-08 08:46:20',0,'0 gal','',2011),(16,13,1,20.00,5,4.00,2,2.00,3,25.00,0,0.00,'2011-06-08 10:09:10',0,'10 gal 1 rounds sev5 and sev10','',2011),(17,13,1,20.00,5,4.00,2,2.00,3,25.00,0,0.00,'2011-06-08 11:45:06',0,'10 gal','',2011),(18,13,1,10.00,5,2.00,2,1.00,3,12.00,0,0.00,'2011-06-08 13:33:47',0,'Finish up last load','',2011),(19,8,1,20.00,5,4.00,2,2.00,3,25.00,0,0.00,'2012-05-22 06:01:01',0,'I just sprayed the big weeds on the top of the field','',2012),(20,1,1,20.00,5,4.00,2,2.00,3,25.00,0,0.00,'2012-05-26 06:01:01',0,'Sprayed everything except last round on short rows.','',2012),(21,18,1,20.00,5,4.00,2,1.75,3,25.00,0,0.00,'2012-05-29 06:01:01',0,'Sprayed everything except last 2 round on short rows.','',2012),(22,11,1,20.00,5,4.00,2,1.75,3,25.00,0,0.00,'2012-05-30 08:13:26',0,'Sprayed some on sev09 perimeter','',2012),(23,11,1,20.00,5,4.00,2,1.75,3,25.00,0,0.00,'2012-05-30 09:35:39',0,'Finished field except for pass accross top','',2012),(24,12,1,20.00,5,4.00,2,1.75,3,25.00,0,0.00,'2012-05-31 06:08:23',1,'perimiter sprayed from previous load.','',2012),(25,10,1,20.00,5,4.00,2,1.50,3,25.00,0,0.00,'2012-05-31 08:32:25',0,'part of load used to finish sev09','',2012),(26,10,1,20.00,5,4.00,2,1.50,3,25.00,0,0.00,'2012-05-31 09:34:53',0,'2nd part to finish field','',2012),(27,15,1,20.00,5,4.00,2,1.50,3,25.00,0,0.00,'2012-05-31 10:55:07',0,'3nd part to finish field','',2012),(28,15,1,20.00,5,4.00,2,1.50,3,25.00,0,0.00,'2012-05-31 12:55:27',0,'3nd part to finish field','',2012),(29,13,1,20.00,5,4.00,2,1.50,3,25.00,0,0.00,'2012-06-01 06:43:35',0,'Part of load used to finish last field','',2012),(30,13,1,20.00,5,4.00,2,1.50,3,25.00,0,0.00,'2012-06-01 20:38:40',0,'2nd load','',2012),(31,7,1,20.00,5,4.00,2,1.50,3,25.00,0,0.00,'2012-06-01 20:39:52',0,'South 2/3rds of field','',2012),(32,3,1,10.00,5,2.00,2,0.75,3,12.00,0,0.00,'2012-06-02 08:25:29',0,'south half the field','',2012),(33,4,1,20.00,5,4.00,2,1.50,3,25.00,0,0.00,'2012-06-11 09:31:40',0,'finished up that load on hp take. Did make 1 round on hp sheep','',2012),(34,2,1,20.00,5,4.00,2,1.50,3,25.00,0,0.00,'2012-06-12 09:34:02',0,'','',2012),(35,2,1,20.00,5,4.00,2,1.50,3,25.00,0,0.00,'2012-06-14 10:10:54',0,'finished up hp top mid an h p s w','',2012),(36,8,1,20.00,5,4.00,2,1.50,3,25.00,0,0.00,'2012-06-14 12:12:15',0,'spray for the second time','',2012),(37,8,1,11.00,5,2.00,2,0.75,3,12.00,0,0.00,'2012-06-16 06:12:13',0,'spray for the second time. Batch 2','',2012);
/*!40000 ALTER TABLE `chemical_used` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `chemicals`
--
DROP TABLE IF EXISTS `chemicals`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `chemicals` (
`chemicalid` smallint(6) NOT NULL AUTO_INCREMENT,
`product` varchar(50) NOT NULL,
`manufactured` varchar(25) NOT NULL,
`technology` varchar(200) NOT NULL,
`notes` text NOT NULL,
`number` smallint(6) NOT NULL,
`archive` tinyint(6) NOT NULL,
PRIMARY KEY (`chemicalid`)
) ENGINE=MyISAM AUTO_INCREMENT=12 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `chemicals`
--
LOCK TABLES `chemicals` WRITE;
/*!40000 ALTER TABLE `chemicals` DISABLE KEYS */;
INSERT INTO `chemicals` VALUES (1,'Bacanneer Plus','Monsanto','plus','1qt per acre. 1.2 works great. Sprayer dumps 11 gal acre.\r\n\r\nunits in quarts\r\n\r\n51.230 gal 5/27/11\r\n51.25 gal 6/6/11',409,0),(2,'Ad Wet','Ad Max 90','soap scum\r\n$33 gal 5/22/18','1 qt per 100 gals measured quarts',15,0),(3,'Amonium Sulfate','','fertilizer solid\r\n$0.60 a pound','25 lbs per 200 gals. Units of measure LBS\r\n\r\n306 LBS 6/1/11\r\n51 LBS 6/6/11',408,0),(4,'Banvel','ARYSTA','molucule ripper','1/3 pt per acre. 1 gal per 200 gal water. Units used quarts\r\n\r\n10 gal 5/27',40,0),(5,'Detonate','','Banvel equivalent\r\n$70 a gallon','noticed book had the 8 oz rate',60,0),(6,'Prowel 3.3','','$51 gallon','.875 gal 5/11',5,0),(7,'Balance Pro','','','8 OZ 5/11',8,0),(8,'WIDEMATCH','','stinger','units in quarts',4,0),(9,'Option','Bayer','Formasulfuron','1.5 ounces per acre .\r\nmust be mixed with methylated or ethalated seed oil at 1.5 pints per acre. also 2 pounds per acre of ammonium sulfate.\r\n\r\ncan be mixed with banvel herbicide.',0,0),(10,'Methylated Seed Oil','Pierce','Vegetable oil,alkylphenol ethoxlate, polysiloxane.','this is use with option\r\n1.5 pints per acre .',3,0),(11,'Glystar Plus','','Round up\r\n$14.10','',100,0);
/*!40000 ALTER TABLE `chemicals` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `contacts`
--
DROP TABLE IF EXISTS `contacts`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `contacts` (
`contactid` smallint(6) NOT NULL AUTO_INCREMENT,
`contact` varchar(60) NOT NULL,
`text` tinyint(4) NOT NULL,
`name` varchar(50) NOT NULL,
PRIMARY KEY (`contactid`)
) ENGINE=MyISAM AUTO_INCREMENT=10 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `contacts`
--
LOCK TABLES `contacts` WRITE;
/*!40000 ALTER TABLE `contacts` DISABLE KEYS */;
INSERT INTO `contacts` VALUES (1,'steve@softwarewebdesign.com',0,'Steve Winter'),(2,'9702315854@vtext.com',0,'Steve Winter Cell'),(3,'9706920034@vtext.com',1,'Davids Cell'),(4,'kklatt@agfinityinc.com',0,'Kevin Klatt'),(5,'9702315855@vtext.com',1,'Calebs Cell'),(6,'steve@sjwfarms.com',0,'Steve Farm'),(7,'Sons@sjwfarms.com',0,'Caleb Winter'),(8,'softwarewebdesign@gmail.com',0,'Steve Winter Gmail'),(9,'paul.hahn1@chsinc.com',0,'Paul HAHN');
/*!40000 ALTER TABLE `contacts` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `farmNotes`
--
DROP TABLE IF EXISTS `farmNotes`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `farmNotes` (
`noteid` mediumint(9) NOT NULL AUTO_INCREMENT,
`farmid` smallint(6) NOT NULL,
`categoryid` smallint(6) NOT NULL,
`year` smallint(6) NOT NULL,
`note` text NOT NULL,
`pdf` varchar(12) NOT NULL,
PRIMARY KEY (`noteid`),
KEY `farmid` (`farmid`,`year`)
) ENGINE=MyISAM AUTO_INCREMENT=131 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `farmNotes`
--
LOCK TABLES `farmNotes` WRITE;
/*!40000 ALTER TABLE `farmNotes` DISABLE KEYS */;
INSERT INTO `farmNotes` VALUES (1,1,4,2011,'Severance Alfalfa 78.0 \r\nSeverance Desert 10.0 \r\nSeverance whole corn 144.5 \r\n\r\nFirst descent rain 5/1/2011\r\nFirst frost date 10/20/2011','1.pdf'),(2,2,4,2011,'Acerage by Farm\r\nFARM Crop Acres \r\nHome Alfalfa 25.0 \r\nHome Desert 10.0 \r\nHome whole corn 109.0 \r\nTotal \r\n--------------------------------------------------------------------------------\r\n\r\nFirst frost 10/19/2011','2.pdf'),(3,1,1,2014,'Pipeline covered from sump \r\nlat 40 32 31.38\r\nlong -104 51 42.238','3.pdf'),(6,2,7,2015,'Fertilizer Prices via email\r\n\r\nSteve,\r\n\r\nWe have you down for seed prepay at $13,928.54, but I didn’t see any fertilizer prepay. This is what the fertilizer pricing would be for Feb 2015:\r\n\r\n46-0-0-$525\r\n11-52-0-$590\r\n00-00-60-$630\r\nMN-32% -$1.20/lb\r\n\r\nI think these cover most of your needs. We will have the air max available tomorrow to spread, if that works. We do also have the spinner truck as well.\r\n\r\nThanks,\r\n\r\ndavid\r\nTimnath SGS','6.pdf'),(7,1,2,2015,'
\r\n
LAB NUMBER
SAMPLE ID
ORGANIC
PHOS P1
PHOS P2
PHOS BiCarb
POTASSIUM
MAGNESIUM
CALCIUM
SODIUM
PH Soil
EXCHANGE
%K
%MG
%CA
%H
%NA
LAB NUMBER
Nitrate ppm
Nitrate lb/A
Nitrate depth
Nitrate total
Sulfur s
ZINC Zn
MANGANESE Mn
IRON Fe
COPPER Cu
BORON B
lime rate
SOLUBLE SALTS\r\n
06329
1SEV04
2.1_L
57_VH
115_VH
33_VH
392_VH
683_VH
3782_H
36
8.0
25.8
3.9
22.1
73.4
0.0
0.6
06329
30
108
0-12
108
31_VH
3.6_H
3_VL
12_M
1.0_M
1.7_H
_H
0.5_L\r\n
06330
2SEV05
1.7_L
59_VH
140_VH
26_VH
366_VH
540_VH
3373_H
43
8.1
22.5
4.2
20.0
75.0
0.0
0.8
06330
25
90
0-12
90
35_VH
3.0_M
2_VL
7_L
0.9_M
1.3_H
_H
0.5_L\r\n
06331
3HPSWEST
1.7_L
60_VH
127_VH
27_VH
288_VH
422_VH
2808_H
35
8.1
18.4
4.0
19.1
76.1
0.0
0.8
06331
9
32
0-12
32
26_VH
3.0_M
2_VL
10_L
1.0_M
1.1_M
_M
0.5_L\r\n
06332
4HPNORTH
1.9_L
8_L
52_H
15_M
285_VH
607_VH
3502_H
46
8.2
23.5
3.1
21.5
74.5
0.0
0.9
06332
10
36
0-12
36
30_VH
2.1_M
2_VL
9_L
1.0_M
1.1_M
_H
0.5_L\r\n
','7.pdf'),(8,1,2,2014,'
\r\n
LAB NUMBER
SAMPLE ID
ORGANIC
PHOS P1
PHOS P2
PHOS BiCarb
POTASSIUM
MAGNESIUM
CALCIUM
SODIUM
PH Soil
EXCHANGE
%K
%MG
%CA
%H
%NA
LAB NUMBER
Nitrate ppm
Nitrate lb/A
Nitrate depth
Nitrate total
Sulfur s
ZINC Zn
MANGANESE Mn
IRON Fe
COPPER Cu
BORON B
lime rate
SOLUBLE SALTS\r\n
77843
1HECKMAN
1.6_L
45_VH
109_VH
39_VH
170_M
806_VH
2993_M
284VH
8.2
23.4
1.9
28.7
64.1
0.0
5.3
77843
7
4
10-12
4
172_VH
3.9_H
2_VL
30_VH
1.3_H
2.4_VH
_L
1.1_M\r\n
77845
2SEV7
1.6_L
8_L
46_H
10_L
234_H
595_VH
3144_H
70
8.2
21.6
2.8
23.0
72.8
0.0
1.4
77845
17
10
10-12
10
59_VH
2.3_M
3_VL
19_H
1.1_M
1.0_M
_M
0.6_L\r\n
77846
35B
1.8_L
5_VL
58_H
16_H
212_H
786_VH
2926_M
155VH
8.2
22.4
2.4
29.2
65.4
0.0
3.0
77846
24
14
10-12
14
169_VH
1.9_M
3_VL
14_M
1.0_M
1.9_VH
_M
0.8_L\r\n
77847
4SHEPCORRA
1.9_L
83_VH
129_VH
45_VH
342_VH
535_VH
2789_H
57
7.9
19.5
4.5
22.9
71.3
0.0
1.3
77847
21
13
10-12
13
34_VH
3.4_H
3_VL
13_M
1.1_M
1.6_H
_L
0.4_L\r\n
','8.pdf'),(11,1,2,2012,'- 20- - 190 - 19 - 11 - . - 207 - 14 - 165 - 14 - 26 - 280 - VI - 0-10 - 0-10 - 0-10 - 0-10 - 0-10 - Midwest - %iof - Laboratories, Inc.\' - 13611 \"B\" Street - • Omaha, Nebraska 68144-3693 (402) 334-7770 FAX (402) 334-9121 - www.midwestlabs.com - IDENTIFICATION - STEVE WINTER - SIMPLOT SOIL SOLUTIONS - WINDSOR COLORADO - P0 BOX 63 - TIMNATH CO 80547 - SOIL ANALYSIS REPORT - NLUTAI. AMMQMIUM ATATEEXCFANGEAELE) - MAGNESIUM - PAGE 1/1 - INFO SHEET: 447259 - :.PERCENTI.BASE.SATURATION - .(COMPIJTEP) - REPORT NUMBER - 12-030-0019 - REPORT DATE - ACCOUNT - Jan 3l,2012 - 8149 - RECEIVED DATE - Jan 30, 2012 - 2.1 - 58973 - 58974 - 58975 - 58976 - 58977 - 1 SEV 10 - 2 SEV 6W - 3HP LAKE - 4HP NORTH - 5HP SWEST - 652v - 514..i. - 597v - 539 - 445vH - 3310 - 3548 - 3482..:: - 3388 - 321 - 22.7 - 22.7 - 23.0 - 22.2 - 20.7 - 23.9 - 18.9 - 21.6 - 20.2 - 17.9 - 72.8 - 78.2 - 75.7 - 76.4 - 77.8 - 1 .9 - 1.9 - 1.8 - 1.8 - 61 - 33. - 50 - 39 - 39 - 8.1 - 8.2 - 8.2 - 8.2 - 8.1 - 2.1 - 2.3 - 1.8 - 2.6 - 3.5 - 0.0 - 0.0 - 0.0 - 0.0 - 0.0 - 1.2 - 0.6 - 0.9 - 0.8 - 0.8 - 58973 - 58974 - 58975 - 58976 - 58977 - 39 - 33 - 45 - 18 - 21 - RATE-N (Fl) - S - . - 0LU01- - : - SALTS - 0.6... - 0.4 - 0.4 - 0.4 - 0.4 - 13 - 11 - 15 - 6 - 7 - MANE ANtS - 39 - 33 - 45 - 18 - 21 - 9 - 15 - 22 - 19 - 29 - H - H - 2.9 - 2.9 - 4.7 - 2.3 - 2.5 - 3 - 3 - 2 - 3 - 2 - L - 17 - 16 - 13 - 14 - 12 - 1.0 - 1.1 - 0.8 - 0.9 - 0.9 - 1.0 - 1.0 - M - M - M - M - L - L - L - REV. 12/03 - Our reports and letters are - br - the exclusive and conticleuitial use ot our clients and may not be reproduced in whole or in part, nor may any reterence be made - to the work, the results, or the company in any advertising, news release, or other public announcements without obtaining our prior written authorization. - The abpve analvficl results app/v - poly - to the sample(s) ubmitte/. Samples re retained maximum 0130 days. - \r\n\r\nRECEIVED DATE - Jan 30, 2012 - 13611 \"B\" Street• - Omaha, Nebraska 68144-3693 (402) 334-7770 FAX (402) 334-9121 - www.midwestlabs.com - IDENTIFICATION - STEVE WINTER - SIMPLOT SOIL SOLUTIONS - WINDSOR COLORADO - P0 BOX 63 - TIMNATH Co 80547 - SOIL FERTILITY RECOMMENDATIONS (POUNDS PER ACRE) - 1 SEV 10 - CORN - bu - 200.0 - CORN - bu - 0.7 - 5.5 - 70 - 35 - 205 - ELEMENTAL - SULFUR. - LBSIA - GYPSUM - IONS/A - YOUR - SAMPLE - NUMBER - (LAB NUMBER) - 1NTENDED - CR - • - sO1LAMEND.MENTS: - YIELD - .11 - GOAL - p. - FHOSPHAT - Cu - COPE - B - BORON, - (23658977) - (23658973) - CORN - bu - 200.0 - CORN - bu - 200 - 1.1 - 6.1 - 6.1 - 90 - 75 - RE\'!. 12103 - 0.9 - 6.1 - 225 - CORN - bu - 200.0 - CORN - bu - (23658975) - 4HP NORTH - • - (23658916) - 5HP SWEST - REPORT NUMBER - 12-030-0019 - REPORT DATE - ACCOUNT - Jan 31, 2012 - 8149 - Midwest, - 440 - \'I/ Laboratories, lncm\' - PAGE 1/1 - The alove analvticpl resets ajplv.oply to the stnple(s) submitter!. Samples aie reta!I7ed.a maximum of 30 deys. - Our reports and letters are tor me exClusive and conlideñtial use ot our clients and may not be reproduced in wflole or in part, nor may any reterence be made - to the work, the results, or the company in any advertising, news release, or other public announcements without obtaining our prior written authorization. - Midwest - 13611 “B” Street - x - Omaha, Nebraska 68144-3693 - x - (402) 334-7770 - x - FAX (402 334-9121 - www.midwestlabs.com - Our reports and letters are for the exclusive and confidential use of our - clients and may not be reproduced in whole or in part, nor may any refere - nce be made - to the work, the results, or the company in any advertising, news release, or other public announcements without obtaining our prior written au - thorization. - Laborator - ies - Inc. - ® -NITRATE-N (FIA) - ORGANIC - MATTER - PHOSPHORUS - PERCENT BASE SATURATION (COMPUTED) - P - 1 - (WEAK BRAY) - P - 2 - (STRONG BRAY) - LAB - NUMBER - SAMPLE - IDENTIFICATION - CATION - EXCHANGE - CAPACITY - C.E.C. - meq/100g - SOIL - pH - 1:1 - OLSEN - P - K - POTASSIUM - MAGNESIUM - Mg - CALCIUM - Ca - SODIUM - Na - pH - NEUTRAL AMMONIUM ACETATE (EXCHANGEABLE) - % - Mg - % - Ca - % - H - % - Na - % - K - BUFFER - INDEX - RATE - ppm - RATE - ppm - RATE - ppm - RATE - ppm - RATE - ppm - RATE - ppm - RATE - percent - SOIL ANA - LYSIS REPO - RT - REV. 12/03 - ppm - ppm - ppm - lbs/A - lbs/A - depth - (in) - depth - (in) - depth - (in) - lbs/A - Total - lbs/A - RATE - ppm - EXCESS - LIME - RATE - SULFUR - S - ZINC - Zn - MANGANESE - Mn - IRON - Fe - COPPER - Cu - BORON - B - SOLUBLE - SALTS - 1:1 - RATE - mmhos/ - cm - RATE - ppm - RATE - ppm - RATE - ppm - RATE - ppm - RATE - ppm - RATE - ppm - ICAP - LAB - NUMBER - SURFACE - SUBSOIL 1 - SUBSOIL 2 - L - . - O - . I. - BICARBONATE - 12-338-0258 - Dec 5, 2012 - Dec 3, 2012 - STEVE WINTER - 8149 - SIMPLOT SOIL SOLUTIONS - PO BOX 63 - TIMNATH CO 80547 - The above analytical results apply only to the sample(s) sub - mitted. Samples are retained a maximum of 30 days. - REPORT NUMBER - REPORT DATE - RECEIVED DATE - ACCOUNT - IDENTIFICATION - DTPA - DTPA - DTPA - DTPA - SORB. DTPA - 1:7 - 1:7 - INFO SHEET: 523472 - *248* - *248* - PAGE 1/1 - 98711 - 1HPTOPMID - 1.8 33 69 17 214 448 3233 - 39 8.2 - 20.6 2.7 18.1 78.4 0.0 0.8 - L - VH - VH - H - H - VH - H - 98711 13 8 - 8 47 3.6 - 3 - 31 1.3 - 1.0 - 0.5 - H - VH - H - VL - VH - H - M - L - 10-12 - 98712 - 2SEV 06E - 1.7 43 91 28 201 550 3533 - 33 8.2 - 22.9 2.3 20.0 77.1 0.0 0.6 - L - VH - VH - VH - H - VH - H - 98712 24 14 - 14 30 3.9 - 3 - 13 1.0 - 1.0 - 0.5 - H - VH - H - VL - M - M - M - L - 10-12 - 98713 - 3SEV 09 - 2.0 18 47 29 298 922 3630 - 52 8.2 - 26.8 2.9 28.7 67.6 0.0 0.8 - L - M - H - VH - VH - VH - H - 98713 26 16 - 16 56 2.8 - 3 - 11 1.1 - 1.7 - 0.7 - M - VH - M - VL - M - M - H - L - 10-12 - Midwest - 13611 “B” Street - x - Omaha, Nebraska 68144-3693 - x - (402) 334-7770 - x - FAX (402 334-9121 - www.midwestlabs.com - Our reports and letters are for the exclusive and confidential use of our - clients and may not be reproduced in whole or in part, nor may any refere - nce be made - to the work, the results, or the company in any advertising, news release, or other public announcements without obtaining our prior written au - thorization. - Laborator - ies - Inc. - ® - - - - - - - YOUR - SAMPLE - NUMBER - (LAB NUMBER) - YIELD - GOAL - NP - 2 - O - 5 - K - 2 - OMg S ZnMnFeCuB - INTENDED - CROP - SOIL AMENDMENTS - NITROGEN - PHOSPHATE - POTASH - MAGNE- - SIUM - SULFUR - ZINC - MANGA- - NESE - IRON - COPPER - BORON - LIME - LBS/A OF - LIME TON - GYPSUM - TONS/A - ELEMENTAL - SULFUR - LBS/A - SOIL FERTILITY RECOMMENDATIONS (POUNDS PER ACRE) - REV. 12/03 - PREVIOUS - CROP - 12-338-0258 - Dec 5, 2012 - Dec 3, 2012 - STEVE WINTER - 8149 - SIMPLOT SOIL SOLUTIONS - PO BOX 63 - TIMNATH CO 80547 - The above analytical results apply only to the sample(s) sub - mitted. Samples are retained a maximum of 30 days. - REPORT NUMBER - REPORT DATE - RECEIVED DATE - ACCOUNT - IDENTIFICATION - PAGE 1/1 - 1HPTOPMID - CORN - bu - 200.0 CORN - bu - 235 - 30 - 55 - -- - -- - -- - 5.5 -- - -- - -- - (24898711) - 2SEV 06E CORN - bu - 200.0 CORN - bu - 230 - -- - 65 - -- - -- - -- - 5.5 -- 0.7 -- - (24898712) - 3SEV 09 - CORN - bu - 200.0 CORN - bu - 225 - 30 - -- - -- - -- - -- - 5.5 -- - -- - -- - (24898713) -','11.pdf'),(12,1,1,2015,'GPS the old pre-pivot road from old sump to drain tile\r\n\r\n40.53800, 104.86238\r\n40.53835, 104.86260\r\n40.53874, 104.86284\r\n40.53904, 104.86302\r\n40.53929, 104.86317\r\n40.53941, 104.86326\r\n40.53964, 104.86350\r\n40.53989, 104.86391\r\n40.54024, 104.86440\r\n40.54045, 104.86464\r\n40.54084, 104.86492 This marks drain tile 2 feet south','12.jpg'),(13,1,5,2015,'Acre report sign up','13.pdf'),(14,2,5,2015,'Producer Farm Data Report\r\nDate: 2/2/15 10:21 AM\r\nCrop Year: 2015 \r\n\r\nContains Farm numbers and tracts','14.pdf'),(15,2,3,2017,'Plot data in raw form.','15.jpg'),(16,2,7,2015,'Electric meter number by lake _ PVREA 99429','16.jpg'),(17,2,7,2015,'crop insurance quote and sign up information.','17.pdf'),(18,2,7,2015,'TEMPORARY BANK STUFF','18.pdf'),(19,1,7,2015,'Corn contract from west plains. Include fall harvest $4.32, $4.08, $4.28, $4.45\r\nsummer bin $3.95','19.pdf'),(21,1,6,2015,'Pioneer invoice for 2016 in 2015','21.pdf'),(22,2,3,2015,'Yield check on home farm','22.pdf'),(23,1,6,2016,'Pioneer seed delivery for plot.\r\nPioneer Delivery Ticket 4_25_2016 3_51_29 PM.pdf','23.pdf'),(24,1,7,2016,'Severance Pivot electrical hookup info:\r\nNema L16 - 20 -R 20 amps 480 volts than 30','24.jpg'),(25,1,7,2016,'Walking your fields planting notes','25.pdf'),(26,1,7,2017,'crop contracts from west plains. Grain sold in bins in accounting record','26.pdf'),(62,1,7,2017,'
Liquid N
\r\n131 acres under pivot or 262 under both\r\n$280 ton \r\n750 x 4 x 11 x0.32= 11000 lbs N or 42 lb N/acre\r\n\r\nDate: 06/02/2017 Invoice No: 740023274 Product Unit of Measure Qty Price Ext. Price\r\nTotals: $2,983.40\r\n32-00-00 TRI-N-32 [T] Tons 10.655 $280.000 $2,983.40\r\n\r\nDate: 06/28/2017 Invoice No: 740023505 Product Unit of Measure Qty Price Ext. Price\r\nTotals: $1,104.60\r\n32-00-00 TRI-N-32 [T] Tons 3.945 $280.000 $1,104.60\r\n\r\nDate: 07/11/2017 Invoice No: 740023599 Product Unit of Measure Qty Price Ext. Price\r\nTotals: $2,164.40\r\n32-00-00 TRI-N-32 [T] Tons 7.730 $280.000 $2,164.40\r\nDate: 07/20/2017 Invoice No: 740023658\r\n\r\n22 tons= 53 lb N/acre','62.jpg'),(28,2,4,2016,'this is the yield reports on the home place that was done on November 9th 2016\r\nAcerage by crop\r\n\r\nCrop Acres\r\nalfalfa 91.0\r\nDesert 20.0\r\nwhole corn 269.0\r\ntotal \r\n380\r\nAcerage by Farm\r\n\r\nFARM Crop Acres\r\nHome 9504 alfalfa 38.0\r\nHome 9504 Desert 10.0\r\nHome 9504 whole corn 96.0\r\nSeverance 7847 Alfalfa 53.0\r\nSeverance 7847 Desert 10.0\r\nSeverance 7847 whole corn 173.0\r\nTotal \r\n380','28.pdf'),(29,2,10,2017,'Pump hookup\r\n\r\n
40.55077 - 104.90948 west couple\r\n40.55075- 104.90945 east couple\r\n45 degree elbow 40.55075 - 104.90949\r\nEast of pump General pipe layout. 40.55067 - 104.90948 5ft west of actual pipe.\r\n
Pic of the Curve 40.55026 -104.90942 5ft west\r\n
Electric hookup measure 5 foot to the West again 40.55050 - 104.90945\r\n
Where the pipe straightens out going to the pond 40.55005 104.90926\r\n
Just remember that the electric line is on the downhill side or east side of the pipe and due to the size of the trench with the bucket he could be up to 2 feet away from the existing pipeline if you ever decide to dig. Because most of my measurements were done on my GPS device with the trench open I got it standing on the uphill side or the west side of the pipeline trench unless noted in the thing by the measurements are all at least five feet to the downhill side or east side of the Trench. I did climb in the trench where the initial hookup was the ground was frozen I could stand next to the pipe.\r\n
Angle change in the pipe going to the pond. 40.54967 Dash 104.90888\r\n
Right on top the electric line where it makes a curve. 40.54928 - 104.90884','29.jpg'),(30,2,10,2017,'Hook up 2\r\n\r\n
40.55077 - 104.90948 west couple\r\n40.55075- 104.90945 east couple\r\n45 degree elbow 40.55075 - 104.90949\r\nEast of pump General pipe layout. 40.55067 - 104.90948 5ft west of actual pipe.\r\n
Pic of the Curve 40.55026 -104.90942 5ft west\r\n
Electric hookup measure 5 foot to the West again 40.55050 - 104.90945\r\n
Where the pipe straightens out going to the pond 40.55005 104.90926\r\n
Just remember that the electric line is on the downhill side or east side of the pipe and due to the size of the trench with the bucket he could be up to 2 feet away from the existing pipeline if you ever decide to dig. Because most of my measurements were done on my GPS device with the trench open I got it standing on the uphill side or the west side of the pipeline trench unless noted in the thing by the measurements are all at least five feet to the downhill side or east side of the Trench. I did climb in the trench where the initial hookup was the ground was frozen I could stand next to the pipe.\r\n
Angle change in the pipe going to the pond. 40.54967 Dash 104.90888\r\n
Right on top the electric line where it makes a curve. 40.54928 - 104.90884','30.jpg'),(31,2,10,2017,'Pipe location\r\n
Pic of the Curve 40.55026 -104.90942 5ft west','31.jpg'),(32,2,10,2017,'Electric hook up\r\n\r\n
Electric hookup measure 5 foot to the West again 40.55050 - 104.90945','32.jpg'),(33,1,11,2019,'Planting coordinates\r\nSEVERANCE top of hill split gps coordinates\r\nI use the multi Point GPS in the tractor the starting points are latitude 40.5 37989 what longitude is -104.86 1 3 3 5\r\nNew coordinates for the gated pipe. Walking south to north\r\n40.53812 104.86128 00\r\n40.53838 104.86130 40\r\n40.53867 104.86131 40\r\n40.53888 104.86131 25\r\n40.53908 104.86129 25\r\n40.53954 104.86123 65 steps\r\n\r\n-104.861261,40.538042\r\n-104.861301,40.538348\r\n-104.861314,40.538621\r\n-104.861311,40.538888\r\n-104.861286,40.539168\r\n-104.861244,40.539428\r\n\r\n\r\n\r\n\r\n\r\n\r\nH 145.879 degrees planting\r\n\r\nSouth track -104.865153,40.538072\r\n\r\nGoogle maps 2016 view North to south\r\n-104.861209,40.539456 just south of atv path\r\n-104.861219,40.539365 -104.861239,40.539276 -104.861251,40.539211 -104.861259,40.539159 -104.861270,40.539077 -104.861288,40.539012 -104.861296,40.538966 -104.861304,40.538918 -104.861308,40.538869 -104.861307,40.538841 -104.861303,40.538796 -104.861304,40.538751 -104.861300,40.538697 -104.861291,40.538630 -104.861288,40.538567 -104.861288,40.538503 -104.861288,40.538438 -104.861279,40.538304 -104.861268,40.538232 -104.861268,40.538160 -104.861264,40.538105 -104.861257,40.538049 -104.861253,40.538002 -104.861257,40.537931','33.jpg'),(34,2,2,2017,'
\r\n
LAB NUMBER
SAMPLE ID
ORGANIC
PHOS P1
PHOS P2
PHOS BiCarb
POTASSIUM
MAGNESIUM
CALCIUM
SODIUM
PH Soil
EXCHANGE
%K
%MG
%CA
%H
%NA
LAB NUMBER
Nitrate ppm
Nitrate lb/A
Nitrate depth
Nitrate total
Sulfur s
ZINC Zn
MANGANESE Mn
IRON Fe
COPPER Cu
BORON B
lime rate
SOLUBLE SALTS\r\n
24621
1HPUPMID
1.8_L
23_H
52_H
13_M
298_VH
478_VH
3533_H
42
7.7
22.6
3.4
17.6
78.2
0.0
0.8
24621
45
135
0-10
135
30_VH
2.4_M
3_VL
10_L
1.0_M
1.0_M
_H
0.6_L\r\n
24622
2HPCATTLE
2.2_L
73_VH
115_VH
46_VH
397_VH
714_VH
3328_H
98_M
7.6
24.0
4.2
24.8
69.2
0.0
1.8
24622
75
225
0-10
225
148_VH
3.5_H
4_VL
11_M
1.0_M
1.7_H
_H
1.0_L\r\n
','34.pdf'),(35,1,9,2018,'
Plow Schedule 2021
\r\nSev\r\nPivot field S to N\r\nsev08 N to S East end up or W to E\r\nfall South of pivot field S to E until West crossing\r\n\r\n
Plow Schedule 2019
\r\nStarted north of hp pivot tower fall 2018 plowing S to N\r\nHPHILL N to S\r\n\r\nSev\r\nsev08 N to S East end up or W to E\r\nfall South of pivot field S to E until West crossing\r\n\r\n
Plow Schedule 2018
\r\nSEVPivNW West to East\r\nSev08 South to north. East end down both long and short rows. Waited on west end in case of ditch replacement.\r\n\r\nHP\r\nFall North to South\r\nHill- East to West Ends plowed toward field.\r\n\r\n\r\n
Plow Schedule 2017
No fall plowing done\r\nSev07 S to N, E end down 2016\r\n\r\nSEVPivNW - N to S, old alfalfa west end to east else west end west 1 round 2016\r\n\r\n
Plow Schedule 2014-2015
Sev07 N to S E end down\r\nSev 09 S to N stopped at pivot center.\r\n\r\nFirst year with pivot.\r\nThe year hail hit 3 times at the knee high length. North side worse than south. Was pretty good rains later in season. Got pivot stuck in south draw near abandoned sump.\r\n
\r\nIn the field that by the modular house the distance from the end of the cement cut ditch to the road is 270 feet. This equates to 9 sections of gated pipe.','37.jpg'),(38,1,5,2017,'LDP sign up at USDA office 3/29/2017','38.pdf'),(39,1,6,2017,'DELIVERY TICKET RETURN ALFALFA Spring 2017\r\nApril 7, 2017 - Operation: Winter; Steve - Pioneer Hi‐Bred International, Inc.\r\n Current Delivery - Product Segment Sub‐Product Description Account Description - Units this\r\nDelivery/Return - 55VR05 Muscle GEN RR N221 50# BAG FST\r\n Winter; Steve ‐2.0 - Alfalfa Total ‐2.0 - Product Total ‐2.0\r\nThank you for using Pioneer® brand products. All disclaimers and warranties will be provided and will also be printed on the product - container. The above products invoiced are subject to availability at delivery.\r\nDiscounted price includes the value of the regular ﴾excludes replant and sample﴿ invoiced seed and any associated seed treatments - listed on this invoice, while assuming the use of all applicable discounts based on meeting qualifications for each period, or the - customer´s locked discount rate, and no other price changes.\r\nYou may pay electronically via the Pioneer.com website or make checks payable to PIONEER HI‐BRED INTERNATIONAL, INC. To - qualify for the Early Pay Savings shown above, full payment must be in Pioneer\'s possession via a cash payment, an electronic - payment that is scheduled for payment by the date shown or a Deferred Payment receipt must be created. If you are a Deferred - Payment ﴾DP﴿ Loan customer, your 2016 DP Loan must be paid in full by December 1, 2016 and you must be approved with adequate - credit available for a 2017 DP Loan with PHI Financial Services, Inc. by January 6, 2017 in order to retain the Early Pay Savings discount - above.\r\n\r\nWhen you provide a check as payment, you authorize us either to use information from your check to make an electronic fund - transfer from your account or to process the payment as a check transaction. By authorizing an electronic fund transfer you also agree - to be bound by the NACHA Operating Rules. - Terms of sale are cash PAYMENT DUE UPON DELIVERY of goods. Any unpaid account balances will accrue a finance charge at the rate - of 1.5% per month ﴾18% or at the maximum rate allowed by your state law, if less than 1.5%﴿. If you are an approved Deferred Payment - Loan customer of PHI Financial Services, Inc. under their Deferred Payment Program, then the terms of your agreement with PHI - Financial Services, Inc. shall govern this sales transaction. Except as noted above, Pioneer has a no return policy; however, Pioneer may - in its sole discretion, allow for a return of product﴾s﴿ in limited circumstances. - By the purchasing of the products listed on this invoice, you hereby consent to the jurisdiction of the state or federal courts in Polk - County, Iowa in the event of litigation concerning this purchase. If binding arbitration is required ﴾see bag﴿, the place of the arbitration - will be Des Moines, Iowa. - If you have not signed a Pioneer Technology Use Agreement, then this document is not an offer or acceptance of an offer for sale of - the products listed and any purported sale of such products is void. If you have received products without signing a Pioneer - Technology Use Agreement, your use of those products is unauthorized and unlicensed, and you must, either ﴾i﴿ return such products - to Pioneer, or ﴾ii﴿ sign a Pioneer Technology Use Agreement for such products. - EXPORT APPROVAL NOTICE: This product is fully approved in the United States and Canada. Traits included in these products may or - may not be approved in all global markets; therefore, the combination of these traits and the grain and certain by‐products ﴾including - oil, dried distillers grain, cobs, and husks﴿ from THESE PRODUCTS MAY NOT BE APPROVED for all markets. Growers that use this - product are required and agree to adhere to the stewardship requirements as outlined in the Pioneer Product Use Guide and product - specific Stewardship Requirements for this product, which include specific grain disposition requirements. For questions regarding - product stewardship and biotech traits please contact your sales representative or refer to www.pioneer.com/stewardship. Growers are - required to discuss trait acceptance and grain channeling policies with their local grain handler prior to delivering grain containing - biotech traits. - THE FOLLOWING STATEMENT APPLIES TO CORN PRODUCTS P0157AMX, P0157R, P9188AMX, P9789AMXT. By entering into this - transaction, you affirm that you are contractually obligated to comply with Insect Resistance Management ﴾IRM﴿ requirements for - growing Pioneer® brand hybrids containing any of the following traits: the Herculex® I insect protection trait, the Herculex RW - rootworm protection trait, the Herculex XTRA traits, the Agrisure® RW, Agrisure Viptera®, and/or the YieldGard®Corn Borer gene. - Consult the Product Use Guide for refuge management requirements at www.pioneer.com/IRM. Herculex® Insect Protection - technology by Dow AgroSciences and Pioneer Hi‐Bred. ® Herculex and the HX logo are registered trademarks of Dow AgroSciences - LLC. YieldGard® and the YieldGard Corn Borer design and Roundup Ready are registered trademarks used under license from - Monsanto Company. Liberty®, LibertyLink® and the Water Droplet Design are trademarks of Bayer. Agrisure® and Agrisure Viptera® - are trademarks of, and used under license from, a Syngenta Group Company. Agrisure® technology incorporated into these seeds is - commercialized under a license from Syngenta Crop Protection AG. - Refuge seed in Optimum® AcreMax® Xtra insect protection products are treated with Poncho® 1250/Votivo® “insecticide” to deliver - protection against below ground pests and disease. Some Optimum® AcreMax® , Optimum® AcreMax® RW and Optimum® - AcreMax® Xtra Insect Protection products are not resistant to Liberty® herbicide. Please check the seed label or contact your sales - professional for more information. - Refuge Optimum® AcreMax® Xtreme insect protection products are treated with Poncho® 1250/Votivo® “insecticide” to help - deliver protection against below ground pests and disease. - Refuge seed in Optimum® AcreMax® Xtra insect protection products are treated with Poncho® 1250/Votivo® “insecticide” to help - deliver protection against below ground pests and disease. - Bakel Farms - 2726 E State Highway 60 - Loveland, CO 80537 - ﴾970﴿ 669‐1275 Customer Signature - For internal use only: [ T: CDA S: 1250994 ]','39.pdf'),(40,2,6,2017,'PIONEER CORN SEED DELEIVERED\r\n\r\nProduct - Segment - Sub‐Product Description - Account Description - Units this - Delivery/Return - P0157AMX - AMX/LL/RR2/AQ - NWP9 40 PKP H IST R VO - Winter; Steve - 2.0-\r\n- P0157R - RR2/AQ - NW02 PDF 80 H IST V R - Winter; Steve - 23.0-\r\n- P9188AMX - AMX/LL/RR2 - NWP9 40 PKP H IST R VO - Winter; Steve - 2.0-\r\n- P9608AM - AM/LL/RR2 - NWP9 40 PKP H IST R VO - Winter; Steve - 2.0-\r\n- P9789AMXT - AMXT/LL/RR2 - NM04 MR 80K MD IST - Winter; Steve - 43.0-\r\n- P9789AMXT - AMXT/LL/RR2 - NVP9 40K PKP HI IST VO - Winter; Steve - 2.0-\r\n- P9998AMXT - AMXT/LL/RR2/AQ - NJP9 40K PKP MD LR - Winter; Steve - 2.0-\r\n- Corn Total - 76.0-\r\n- Product Total - 76.0','40.pdf'),(41,1,1,2021,'Pivot\r\nPond location 40°32\'41.36\"N, 104°51\'43.20\"W SEV\r\n\r\n
Pivot Severance
\r\nLarge gun as of 07/17/25\r\n20 - 61\r\n85 - 160 [opt 130 - 160 to keep gated pipe road dry]\r\n201 - 251\r\n287 - 321\r\n327 - 339\r\n\r\nsmall gun as of 07/17/25\r\n10 - 72\r\n76 - 170\r\n191 - 256\r\n280 - 346\r\n\r\n\r\n\r\nWater\r\n0 - 61 1.5\r\n61 - 80 1.5\r\n80 - 95 1.5\r\n95 - 270 1.5\r\n271 - 290 .7 draw in alfalfa field\r\n290 - 359 1.5\r\n\r\nSeverance Pivot info:40°32\'29.53\"N, 104°51\'54.38\"W\r\ntower 40.541544, -104.865101 - -104.865099,40.541545 from maps\r\ngoogle earth: \r\nPivot length 1294 feet 1268 to outside wheels \r\npivot road length 1511.54 feet\r\npivot pump 40.544655, -104.861962\r\n\r\nChemical hook up valve first center pivot','41.jpg'),(42,2,10,2017,'XTR midstream new electrical wire GPS points where the wire crosses over our existing pipe structures.\r\nBy the lake pump on the west side 40.55079 104.90970\r\nPivot pipe west side electric line 2ft south. 40.54919 104.90957\r\nHill field:\r\nPvc pipe top 104.908095 40.55234\r\nCrossover pt Pvc 104.90901 40.55135\r\nCrossover steel 40.55128 104.90895\r\nLake field old clay tile 104.90954 40.55062\r\nHpsheep drain tile 104.90813 --. 40.54590 estimated','42.jpg'),(43,2,8,2005,'The guy is installing the clamps and the things around the drain tile is in the progress of fixing the drain tile these pictures are out of order of course.\r\n\r\nNotice the depth of the guy sitting in the hole fixing the pipe. That will estimate approximately how deep the pipe is. it could be down at the four foot mark but that should be the maximum.','43.JPG'),(44,2,8,2005,'The section that he was putting together has now been connected to the drain tile underneath the water line.\r\n\r\nSince the sun was in the East the bright spot on the right hand side should be where the Sun was shining on the dirt so I am assuming that is the west side of the hole.\r\n\r\nAgain remember that the drain tile is headinging off at an angle. The actual water pipe above it is parallel to the highway. so make sure you notes this when trying to locate the drain tile in the field. \r\n\r\nGPS coordinates:','44.JPG'),(45,2,8,2005,'How the repair looks like','45.JPG'),(46,2,8,2005,'This is the most important picture. It shows the hole in reference to the telephone box in the field by the Sheep Corral. Note that the guy is assembling the section to repair the drain tile. \r\n\r\nNote the direction of the shadow on the phone box since it is facing towards the cornfield that means the sun had to be in the East so this picture was taking in the morning.\r\n\r\nIn an upcoming picture it will show you that where this hole is that the drain tile is going off at an angle to the Northwest so we will proceed to the next picture so you can see what\'s happening.\r\n\r\nGPS coordinates:','46.JPG'),(47,2,8,2005,'Original Damage\r\nKnow this image shows the water pipe over the top of our drain tile. Where I was standing with the camera the drain tile is at an angle to the Northwest. The water line is actually parallel to the highways so it is not the water pipe at an angle it\'s the drain tile. More detail in coming pictures.','47.JPG'),(48,1,11,2018,'When planning the field by the modular house I am going to try in 2017 to plant a square or rectangular field here instead of going around the curve. The GPS coordinates of the bottom I\'m going to measure the latitude which is 40.54 338. The next thing I will do is will be measuring the longitude at the east corner of the field and this will be 104.86 764. Try moving south border to the south past the drainage area.','48.jpg'),(49,2,7,2017,'valve- Renter shutoff\r\nThis is a picture of the shut off valve for shutting off the water down at the North renters house. The valve is located west and Slightly North of the main water main cover. The distance is approximately three and a half feet West Northwest. Remove the cap top and turn the valve deep into the ground. Get the smaller valve rod. the bigger one does not fit Down in the Hole.','49.jpg'),(50,1,1,2026,'Transfer line only 4 ft from fence looking at barn grain tank\r\n\r\n
Severance waterline
\r\nPuma 185 gps screen\r\nE elevation midstream repair point N break 40.54216741, -104.86047145 == South break 40.53778987, -104.85959957 === Head 171.360\r\n\r\nHand held gps\r\nThese are the coordinates Jarrod water line going from his house to the lumber guys building of reference. \r\n40.542635, 104.860525 at the lumber guy. off 15ft tp east \r\n40.53374, 104.85894 \r\n at the hole at his house.\r\nor\r\n-104.86128740.542635,-104.860525; 3274.6284883864473 feet -> 172.2874289054938 degrees; 40.53374, -104.85894\r\n\r\nStart water line 40.542567, -104.860479\r\nend water line 40.533712, -104.858868\r\n\r\nwaste ditch crossing 40.537870 -104.859622 ////-104.859797\r\nfence line at waste ditch 40.537937, -104.858699 259 feet or 264 feet to crossing\r\n\r\n the 1.5 inch pvc water line is at least four feet deep at this point.\r\n\r\nOld road from lumber business [-104.860425,40.542600][-104.864909,40.540871] 1393.9837275096925 feet, Heading ->243.09801787971094 DIRECTION CHANGE [-104.869008,40.543187][-104.864931,40.540871] 1411.1652115503011 feet, HEADING 126.7776384205655','50.jpg'),(51,1,1,2025,'
\r\n\r\nDistances of various things on severance place\r\nNWest corner\r\ncut dittch\r\n -104.868815,40.544544 -104.867600,40.544550 336.8312346603658feet E - W part\r\n-104.867600,40.544550 -104.867375,40.545086 205.24701615019873feet SW - NE part\r\ndirt ditch\r\n-104.868839,40.544544 -104.869595,40.544501 210.16579171503423 feet -\r\n-104.869595,40.544501 -104.869762,40.544399 59.39676818205368 feet curve piece\r\ncut ditch\r\n\r\nNORTH DITCH 1566.844814044374 feet \r\n-104.867375,40.545086 -104.866224,40.545092 319.0868721336482feet west entrance\r\n-104.866224,40.545092 -104.863746,40.545090 686.9496849247827feet east entrance\r\n-104.863746,40.545090 -104.862595,40.545086 319.0827059616948feet to pivot pond\r\n-104.862595,40.545086 -104.861707,40.545084 246.1717958751622feet to NE wide ditch crossing\r\n\r\nWest ditch \r\n-104.869512,40.538031 -104.869743,40.539654 new cement 595.5446673367852 feet\r\n-104.869743,40.539654 -104.869719,40.540893 old cement before curve 452.05196981853453 feet\r\n -104.869823,40.541197 before 2nd curve 114.58973741790405 feet\r\n -104.869832,40.543033 old cement north side 669.8008589283704 feet\r\n -104.869842,40.543288 dirt part to valley\r\n 93.06855020976086 feet','51.jpg'),(52,2,10,2017,'Lake field\r\n\r\n-104.911411,40.551851 top pipe break oil company\r\n-104.910081,40.551098 2nd pipe break\r\n-104.909861,40.550937, could be the 2nd also','52.jpg'),(53,2,4,2017,'2017 Acreage Reports & Maps & CCC-633 LDP request form','53.pdf'),(54,2,5,2017,'2018 Alfalfa Hay Report\r\n\r\nSteve,\r\n\r\nHere is your 2018 Alfalfa Acreage Report. This is just in case you don\'t make it back to the office by the Alfalfa reporting deadline - November 15, 2017.\r\n\r\nPlease See Attached\r\n\r\nCall or email if questions.\r\n\r\nThanks\r\n\r\n\r\nJerrie White\r\nWeld County FSA Office\r\n4302 W 9th Street Road\r\nGreeley, CO 80634\r\nPh# 970-356-8097 Ext 2\r\nFax # 844-332-7505\r\nUSDA is an equal opportunity provider, employer, and lender Stay Connected with USDA:','54.pdf'),(55,2,6,2018,'Pioneer Seed Invoice\r\nP9621AMXT AMXT/LL/RR2 NJ02 PDF 80K MD IST LR Regular 1.0 $368.00 $368.00 $331.20\r\nP9697AM AM/LL/RR2/AQ NW02 PDF 80 H IST V R Regular 1.0 $343.00 $343.00 $308.70\r\nP9789AMXT AMXT/LL/RR2 NS02 PDF 80 M IST R Regular 22.0 $324.00 $7,128.00 $291.60\r\nP9998AMXT AMXT/LL/RR2/AQ NJ02 PDF 80K MD IST LR Regular 22.0 $367.00 $8,074.00 $330.30\r\nCorn Total 46.0\r\n$345.93 $15,913.00\r\n$311.34 \r\n55VR05\r\nMuscle GEN RR\r\nN221 50# BAG FST\r\nRegular\r\n6.0\r\n$320.00\r\n$1,920.00\r\n$288.00\r\nAlfalfa Total\r\n6.0\r\n$320.00\r\n$1,920.00\r\n$288.00\r\nGross Invoice Value\r\n$17,83','55.pdf'),(56,2,6,2017,'Grower: - Address: - City, State, Zip: - Soil Texture: - Tillage: - Previous Crop: - Comments: - Plot - No. - Brand - RM - Hybrid - Traits - Treatment - Plot Weight - (lbs.) - Harvest - Moisture (%) - Row - Width - Row - Length - No. - Rows - 15% Corn - Yield Bu/Ac. - Test Weight - Rank - 1\r\n\r\nPioneer - 101 - P0157 - R - 4,370 - 14.20 - 30.0 - 657.0 - 8.0 - 261.13 - 58.50 - 2 - 2 \r\n\r\nChannel - 103 - 203-01 - STXRIB - Poncho/VoTiVO - 3,840 - 13.60 - 30.0 - 657.0 - 7.0 - 264.07 - 57.20 - 1 - 3\r\n\r\nDeKalb - 96 - 46-36 - STXRIB - Poncho/VoTiVO - 6,092 - 13.00 - 30.0 - 657.0 - 12.0 - 246.08 - 56.50 - 6 - 4 \r\n\r\nPioneer - 97 - P9789 - AMXT - 6,050 - 13.30 - 30.0 - 657.0 - 12.0 - 243.54 - 56.70 - 7 - 5\r\n\r\nChannel - 97 - 197-68 - STXRIB - Poncho/VoTiVO - 6,282 - 13.30 - 30.0 - 657.0 - 12.0 - 252.88 - 57.80 - 3 - 6\r\n\r\nPioneer - 101 - P0157 - AMX - 6,266 - 14.90 - 30.0 - 657.0 - 12.0 - 247.58 - 57.80 - 5 - 7 \r\n\r\nPioneer - 99 - P9989 - AMXT - 5,946 - 14.70 - 30.0 - 657.0 - 12.0 - 235.49 - 58.60 - 8 - 8 - \r\n\r\nPioneer - 96 - P9608 - AM - 6,238 - 13.40 - 30.0 - 657.0 - 12.0 - 250.82 - 58.80 - 4 - 9 -\r\n\r\nPioneer - 91 - P9188 - AMX - 5,544 - 13.00 - 30.0 - 657.0 - 12.0 - 223.94 - 58.20 - 10 - 10 - \r\n\r\nPioneer - 91 - P9120 - AM - 5,826 - 13.40 - 30.0 - 657.0 - 12.0 - 234.25 - 57.90 - 9 - 11\r\n\r\nPioneer - 87 - P8761 - AMXT - 5,502 - 13.10 - 30.0 - 657.0 - 12.0 - 221.99 - 58.60 - 11 - 12','56.pdf'),(57,1,2,2017,'
\r\n
LAB NUMBER
SAMPLE ID
ORGANIC
PHOS P1
PHOS P2
PHOS BiCarb
POTASSIUM
MAGNESIUM
CALCIUM
SODIUM
PH Soil
EXCHANGE
%K
%MG
%CA
%H
%NA
LAB NUMBER
Nitrate ppm
Nitrate lb/A
Nitrate depth
Nitrate total
Sulfur s
ZINC Zn
MANGANESE Mn
IRON Fe
COPPER Cu
BORON B
lime rate
SOLUBLE SALTS\r\n
62591
1SWEST1/4P
1.6_L
4_VL
27_M
5_VL
168_M
657_VH
3047_H
39
8.3
21.3
2.0
25.7
71.5
0.0
0.8
62591
6
18
0-10
18
35_VH
1.0_L
1_VL
11_M
0.9_M
0.9_M
_H
0.4_L\r\n
62592
2SEAST1/4P
1.5VL
8_L
64_VH
16_H
245_VH
575_VH
3505_H
51
8.2
23.2
2.7
20.7
75.6
0.0
1.0
62592
9
27
0-10
27
119_VH
1.7_M
1_VL
11_M
0.9_M
1.0_M
_H
0.5_L\r\n
62593
3LOWERFARE
1.6_L
21_M
78_VH
14_M
202_H
340_VH
2925_H
30
8.2
18.1
2.9
15.7
80.7
0.0
0.7
62593
11
33
0-10
33
25_VH
1.9_M
1_VL
8_L
0.8_L
0.8_M
_M
0.3_L\r\n
','57.pdf'),(130,2,10,2026,'
HP waterline
\r\n12/12/25 Water leak\r\n\r\nby cattle loading chute\r\n\r\nLocation from light pole by chute 11 ft\r\nLine off site north hinges of grain bin\r\nSw post 7.5 ft','130.jpg'),(58,2,3,2017,'
\r\nNew hay field using gps map 1380 ft N-S & 1079 ft E-W at 34.5 acres\r\n\r\nat 13 lbs per acre makes 9 + 1 extra 10 bags @$292 = $2920 hay seed\r\n\r\nalfalfa 68.0\r\nDesert 23.0\r\nwhole corn 298.6\r\nalfalfa left $32760\r\n38000 bu * $3.30 = $125400\r\ntotal : $158160\r\n\r\nfertilizer/herbicide: $150*290=$43500\r\nrepairs :$25*290=$7250 ($13500.00 2017)\r\nseed: $120*290=$34800 + $2920 (alfalfa)\r\ninsurance (crop & liability): $66*290=$19140\r\nfuel : $40*290=$11600\r\nlabor: $40*366=$14640\r\ntotal $133850\r\n\r\nadditional:\r\ncomite $40*300=$12000\r\nwevil $30*35=$1050\r\ntotal $13050','59.jpg'),(60,2,7,2018,'Pivot electric rates from pouder Valley are EA of 08065 dollars per kilowatt-hour','60.jpg'),(61,2,7,2017,'Weed resistance by state map','61.jpg'),(63,2,4,2018,'
6140 combine paper work','65.pdf'),(66,2,6,2018,'PIONEER CORN SEED DELEIVERED','66.pdf'),(67,2,5,2018,'Reports\r\nREPORT OF COMMODITIES FARM AND TRACT DETAIL LISTING\r\nFSA\r\nUSDA\r\ngovernment program','67.pdf'),(68,2,7,2018,'Pivot breaker box \r\nThe two square buttons are what reset the heaters on the box if they are trip there will be some resistance when you push the button down if they\'re not tripped they will be loose and easy to push down.','68.jpg'),(69,1,7,2018,'Picture image of the 10 inch gated pipe that we have going around the severance pivot pond','69.jpg'),(70,1,7,2018,'This is the gated pipe that\'s on the North End of the farm by The Woodworking Shop','70.jpg'),(71,2,6,2018,'Channel seed Invoice\r\n - Description - Order - Quantity - Return - Quantity - Net - Quantity - Retail - Price/Unit - Amount* - Net Dlvd - Quantity\r\n Corn - 203 - 01STXRIB 80M BAG BAS500 B - 18 - 18 - $366.00 - $6,588.00 - 18 - 2018\r\n Channel Advantage - $ - 630.00 - Corn Total - 18 - 18 - $5,958.00 - 18 - Order Summary Total - $5,958.00 - *The totals, including all disco -','71.pdf'),(72,2,3,2018,'Yield plot. DeKalb corn seed starts at the South edge of the large pile of gated pipe','72.jpg'),(73,1,11,2019,'Planting corners\r\nSeverance Pivot info:\r\ntower 40.541544, -104.865101\r\nPivot length 1294 feet 1268 to outside wheels \r\n\r\nseverance farm field Southwest corner\r\n40.542551 -104.866208 1800Ft\r\n\r\nhomeplace farm Northwest corner\r\n40.550076 -104.912814 1082Ft.','73.jpg'),(74,2,2,2018,'
\r\n
LAB NUMBER
SAMPLE ID
ORGANIC
PHOS P1
PHOS P2
PHOS BiCarb
POTASSIUM
MAGNESIUM
CALCIUM
SODIUM
PH Soil
EXCHANGE
%K
%MG
%CA
%H
%NA
LAB NUMBER
Nitrate ppm
Nitrate lb/A
Nitrate depth
Nitrate total
Sulfur s
ZINC Zn
MANGANESE Mn
IRON Fe
COPPER Cu
BORON B
lime rate
SOLUBLE SALTS\r\n
09271
NE1/4pivot
2.3_L
42_VH
116_VH
13_M
335_VH
415_VH
3289_H
36
7.9
20.9
4.1
16.5
78.7
0.0
0.7
09271
24
86
0-12
86
39_VH
2.8_M
4_VL
23_H
1.6_H
1.1_M
_L
0.6_L\r\n
09272
Sevsouth
2.0_L
10_L
73_VH
23_VH
191_H
448_VH
3265_H
32
8.0
20.7
2.4
18.0
78.9
0.0
0.7
09272
28
101
0-12
101
26_VH
3.0_M
3_VL
16_M
1.3_H
1.0_M
_M
0.5_L\r\n
09273
_HPHILL
2.1_L
16_M
40_H
7_L
187_H
792_VH
2784_M
79_M
8.0
21.3
2.3
31.0
65.1
0.0
1.6
09273
42
151
0-12
151
60_VH
2.1_M
4_VL
15_M
1.0_M
1.4_H
_M
0.7_L\r\n
09274
_HPSHEEP
2.4_L
65_VH
125_VH
38_VH
339_VH
702_VH
3194_H
62
8.0
23.0
3.8
25.4
69.6
0.0
1.2
09274
34
122
0-12
122
52_VH
3.4_H
4_VL
26_VH
3.2_VH
1.7_H
_M
0.7_L\r\n\r\n
','74.pdf'),(75,2,3,2018,'Channel weigh wagon harvest results','75.pdf'),(76,2,3,2018,'Pionner comprehensive yield results','76.pdf'),(77,2,6,2019,'GP\r\nPioneer seed invoice padding or locking in off seed','77.pdf'),(78,1,7,2018,'July 12 severance septic tank 1000 gal pump','78.jpg'),(79,2,6,2019,'GP\r\nChannel seed','79.pdf'),(80,1,12,2019,'Severance pivot','80.jpg'),(81,1,12,2019,'South Severance farm image map','81.jpg'),(82,2,12,2019,'Home place image map','82.jpg'),(83,2,5,2019,'Reports\r\nREPORT OF Crop acres and program\r\nFSA\r\nUSDA\r\ngovernment program','83.pdf'),(127,3,7,2025,'Sample Recomendation\r\n\r\nSAMPLE\r\nCROP\r\nYIELD\r\nPREV CROP\r\nN\r\nP205\r\nK2O\r\nMg\r\nSULFUR\r\nZn\r\nMn\r\nFE\r\nCu\r\nB\r\n\r\nHOME EAST\r\nCORN bu\r\n250.0\r\nCORN bu\r\n230 \r\n--\r\n--\r\n--\r\n--\r\n--\r\n6.8\r\n1.2\r\n--\r\n--\r\n\r\nHOME West\r\nCORN bu\r\n250.0\r\nCORN bu\r\n230 \r\n70\r\n90\r\n--\r\n--\r\n--\r\n7.6\r\n2.4\r\n1.1\r\n--\r\n\r\nHOME Alfalfa\r\nAlfalfa\r\n5 ton\r\nAlfalfa\r\n0\r\n30\r\n35\r\n--\r\n-10\r\n--\r\n3.5\r\n--\r\n0.9\r\n--\r\n2023\r\nLab Number\r\nSample ID\r\nSample Depth\r\nSoil pH\r\nBuffer pH\r\nSol. Salts\r\nExcess Lime\r\n%Organic Matter\r\nNitrate-ppm\r\nNitrate-lb.N/A\r\nPhos ppm P\r\nPotassium ppm K\r\nSulfur ppm\r\nSulfur lb/A\r\nCalcium ppm Ca\r\nMagnesium Mg\r\nSodium ppm Na\r\nZinc ppm Zn\r\n
','89.pdf'),(90,1,5,2020,'Agriculture Risk Coverage CCC-866','90.pdf'),(91,2,5,2020,'dEFINITIONS TO above REPORT','91.pdf'),(92,1,1,2020,'Hemp location map','92.jpeg'),(93,2,6,2020,'Pioneer invoice 5/4/20 seed pick up','93.pdf'),(94,2,6,2020,'5/4/20 current pioneer invoice','94.pdf'),(95,2,6,2020,'GP\r\nPioneer seed bought 5/4/20','95.pdf'),(96,1,12,2020,'pivoot end gun settings\r\n\r\n11 and 66 end gun 2','96.jpg'),(97,1,12,2020,'pivot vri table information','97.jpg'),(98,2,12,2020,'home place pivot end gun locations','98.jpg'),(99,2,12,2020,'pivot vri table medium','99.jpg'),(100,1,5,2020,'Weld, Colorado 2020 - GREELEY, CO 80634-2132 - JACK E WINTER - DATE: - REPORT OF COMMODITIES - FARM AND TRACT DETAIL LISTING - FSA - 578 (09-13-16) - 1 - PROGRAM YEAR: - 07/30/2020 - 5207 W 13TH STREET RD - Farm Number: 7847 - Original: - Revision: - Cropland: - Farmland: - PAGE: - DB - 252.91 - 228.93 - C/C - Stat - End - Date - Int - Use - Crop - Land - Var/ - Type - Planting - Period - Rpt - Unit - Det - Qty - Crop/ - Commodity - Planting - Date - Rpt - Qty - Irr. - Pr. - Act - Use - Tract - Number - CLU/ - Field - Org - Stat - Nat. - Sod - Field - ID - Official/ - Measured - Producer JACK E WINTER Share 50.00 FSA Physical Location Weld, Colorado NAP Unit 2421 Signature Date - STEVEN J WINTER 50.00 Weld, Colorado - 7793 3 ALFAL FG I C N I A 34.77 Yes N 4/7/2016 01 2026 - Producer JACK E WINTER Share 50.00 FSA Physical Location Weld, Colorado NAP Unit 2421 Signature Date - STEVEN J WINTER 50.00 Weld, Colorado - 5A CORN YEL GR I C N I A 30.46 Yes N 4/27/2020 01 - Producer JACK E WINTER Share 50.00 FSA Physical Location Weld, Colorado NAP Unit 2421 Signature Date - STEVEN J WINTER 50.00 Weld, Colorado - 5B HEMP SD I C N I A 2.00 Yes N 6/10/2020 01 - PP Cr/Co Var/Type Int Use Irr Pr Rpt Unit Rpt Qty PP Cr/Co Var/Type Int Use Irr Pr Rpt Unit Rpt Qty PP Cr/Co Var/Type Int Use Irr Pr Rpt Unit Rpt Qty - 01 ALFAL FG I A 34.77 01 HEMP SD I A 2.00 01 CORN YEL GR I A 30.46 - Photo Number/Legal Description: - 67.23 - PT E & W OF D IN N2 35-7-67 - Cropland: Reported on Cropland:67.23 Difference:0.00 Reported on Non-Cropland:0.00 - Tract 7793 Summary - Producer JACK E WINTER Share 50.00 FSA Physical Location Weld, Colorado NAP Unit 2421 Signature Date - STEVEN J WINTER 50.00 Weld, Colorado - 15479 1A CORN YEL GR I C N I A 156.70 Yes N 4/28/2020 01 - Producer JACK E WINTER Share 50.00 FSA Physical Location Weld, Colorado NAP Unit 2421 Signature Date - STEVEN J WINTER 50.00 Weld, Colorado - 1B HEMP SD I C N I A 5.00 Yes N 6/10/2020 01 - PP Cr/Co Var/Type Int Use Irr Pr Rpt Unit Rpt Qty PP Cr/Co Var/Type Int Use Irr Pr Rpt Unit Rpt Qty PP Cr/Co Var/Type Int Use Irr Pr Rpt Unit Rpt Qty - 01 HEMP SD I A 5.00 01 CORN YEL GR I A 156.70 - Photo Number/Legal Description: - 161.70 - PT S2 26-7-67 - Cropland: Reported on Cropland:161.70 Difference:0.00 Reported on Non-Cropland:0.00\r\n\r\nWeld, Colorado 2020 - GREELEY, CO 80634-2132 - JACK E WINTER - DATE: - REPORT OF COMMODITIES - FARM SUMMARY - FSA - 578 (09-13-16) - 2 - PROGRAM YEAR: - 07/30/2020 - 5207 W 13TH STREET RD - Farm Number: 9504 - Original: - Revision: - Cropland: - Farmland: - PAGE: - DB - 159.79 - 141.10 - NOTE: The following statement is made in accordance with the Privacy Act of 1974 (5 USC 552a – as amended). The authority for requesting the information identified on this form is 7 CFR Part 718, the Farm - Security and Rural Investment Act of 2002 (Pub L. 107-171), and the Agricultural Act of 2014 (Pub. L. 113-79). The information will be used to collect producer certification of the report of acreage of - crops/commodities and land use data which is needed in order to determine producer eligibility to participate in and receive benefits under FSA programs. The information collected on the form may be - disclosed to other Federal, State, Local government agencies, Tribal agencies, and nongovernmental entities that have been authorized access to the information by statute or regulation and/or as described in - applicable Routine Uses identified in the System of Records Notice for USDA/FSA-2, Farm Records File (Automated) and USDA/FSA-14, Applicant/Borrower. Providing the requested information is voluntary. - However, failure to furnish the requested information may result in a denial of the producer’s request to participate in and receive benefits under FSA programs. According to the Paperwork Reduction Act of - 1995, an agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid OMB control number. The valid OMB control number for this - information collection is 0560-0175. The time required to complete this information collection is estimated to average 30 minutes per response, including the time for reviewing instructions, searching existing - data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. The provisions of criminal and civil fraud, privacy, and other statutes may be applicable to - the information provided. RETURN THIS COMPLETED FORM TO YOUR COUNTY FSA OFFICE. - Variety/ - Type - Crop/ - Commodity - Share Crop/ - Commodity - Variety/ - Type - Share Crop/ - Commodity - Variety/ - Type - Share Crop/ - Commodity - Variety/ - Type - Share - STEVEN J WINTER ALFAL 50.00 CORN YEL 50.00 - JACK E WINTER ALFAL 50.00 CORN YEL 50.00 - Variety/ - Type - Crop/ - Commodity - Irrigation - Practice - Intended - Use - Planting - Period - Reported - Quantity - Determined - Quantity - Reporting - Unit - Determined - Quantity - Reported - Quantity - Reporting - Unit - Irrigation - Practice - Planting - Period - Intended - Use - Crop/ - Commodity - Variety/ - Type - 01 CORN YEL GR I A 104.30 01 ALFAL FG I A 36.80 - CERTIFICATION: I certify to the best of my knowledge and belief that the acreage of crops/commodities and land uses listed herein are true and correct and that','100.pdf'),(101,1,13,2020,'Hemp plot map considers the plots from 1 through 14. This is a hemp plot map','101.pdf'),(102,2,3,2020,'Corn yield PDF\r\n\r\not \r\nNo. Brand RM Hybrid Traits Treatment\r\nPlot Weight \r\n(lbs.)\r\nHarvest \r\nMoisture (%)\r\nRow \r\nWidth\r\nRow \r\nLength\r\nNo. \r\nRows\r\n15% Corn \r\nYield Bu/Ac. Test Weight Rank\r\n1 Dekalb 101 51-91 STXRIB STXRIB 30.0 925.0 8.0 0.00\r\n2 Pioneer 100 P0046 AM AM 4,606 17.00 30.0 925.0 8.0 189.11 59.40 9\r\n3 Pioneer 100 P0075 AM AM 4,818 17.10 30.0 925.0 8.0 197.57 58.00 4\r\n4 Channel 99 199-11 STXRIB STXRIB 4,622 16.90 30.0 925.0 8.0 189.99 58.50 8\r\n5 Pioneer 99 P9880 AM AM 4,444 17.20 30.0 925.0 8.0 182.02 58.30 10\r\n6 Dekalb 97 47-54 STXRIB STXRIB 4,340 15.90 30.0 925.0 8.0 180.55 58.30 12\r\n7 Pioneer 97 P9789 AMXT AMXT 4,526 14.50 30.0 925.0 8.0 191.42 58.20 7\r\n8 Channel 97 197-90 STXRIB STXRIB 4,782 15.70 30.0 925.0 8.0 199.41 57.80 3\r\n9 Dekalb 96 46-36 STXRIB STXRIB 4,656 14.90 30.0 925.0 8.0 196.00 59.60 5\r\n10 Dekalb 95 45-65 STXRIB STXRIB 4,638 15.40 30.0 925.0 8.0 194.09 59.90 6\r\n11 Channel 94 194-75 STXRIB STXRIB 4,256 13.70 30.0 925.0 8.0 181.69 59.90 11\r\n12 Channel 94 194-49 VT2PRIB VT2PRIB 5,080 15.10 30.0 925.0 8.0 213.34 59.50 1\r\n13 Channel 99 199-60 TRERIB TRERIB 5,006 15.40 30.0 925.0 8.0 209.49 60.60 2\r\n14 #DIV/0!\r\n15','102.pdf'),(103,2,3,2020,'This is the home placed yield results taken by the channel grain wagon.','103.pdf'),(104,2,3,2020,'combine yield maps','104.pdf'),(105,2,12,2020,'Home place image map 2nd','105.jpg'),(106,1,12,2020,'Severance pivot only II','106.jpg'),(107,2,2,2020,'
\r\n
LAB NUMBER
SAMPLE ID
ORGANIC
PHOS P1
PHOS P2
PHOS BiCarb
POTASSIUM
MAGNESIUM
CALCIUM
SODIUM
PH Soil
EXCHANGE
%K
%MG
%CA
%H
%NA
LAB NUMBER
Nitrate ppm
Nitrate lb/A
Nitrate depth
Nitrate total
Sulfur s
ZINC Zn
MANGANESE Mn
IRON Fe
COPPER Cu
BORON B
lime rate
SOLUBLE SALTS\r\n
04842
HPPIVNW
2.0_L
8_L
41_H
13_M
217_VH
450_VH
3177_H
52
7.6
20.4
2.7
18.4
77.8
0.0
1.1
04842
47
169
0-12
169
65_VH
1.6_M
4_VL
10_L
0.9_M
0.8_M
_M
0.9_L\r\n
04843
SEVPIVSW
2.2_L
37_VH
118_VH
44_VH
318_VH
489_VH
3275_H
42
7.7
21.4
3.8
19.0
76.3
0.0
0.9
04843
36
130
0-12
130
50_VH
3.1_H
3_VL
9_L
0.9_M
0.9_M
_M
0.8_L\r\n
\r\n\r\n
SAMPLE
GOAL
CROP
Prev_CROP
\r\nN NITROGEN
P2O5 PHOSPHATE
K2O POTASH
Mg MAGNESIUM
S SULFUR
Zn ZINC
Mn MANGANESE
Fe IRON
Cu COPPER
B BORON\r\n\r\n
HPPIVNW
CORN-bu
250.0
CORN-bu
135
110
65
--
--
2.4
6.1
--
1.1
0.9\r\n
SEVPIVSW
CORN-bu
250.0
CORN-bu
175
--
--
--
--
--
6.8
--
1.1
0.6\r\n
','107.pdf'),(108,2,11,2021,'2021 corn plot','108.pdf'),(109,2,7,2021,'Sequence 3.5 pints acre\r\nClass Act 2.5 gal per 100 gal\r\nSterling blue 4 oz actre\r\n\r\n300 gal\r\n13.125 gal sequence \r\n7.5 gal class act\r\n120 oz sterling blue','109.jpg'),(110,2,3,2021,'Yield plots corn for the year 2021','110.pdf'),(111,2,2,2021,'SOIL TEST fall 2021\r\n
\r\n
LAB NUMBER
SAMPLE ID
ORGANIC
PHOS P1
PHOS P2
PHOS BiCarb
POTASSIUM
MAGNESIUM
CALCIUM
SODIUM
PH Soil
EXCHANGE
%K
%MG
%CA
%H
%NA
LAB NUMBER
Nitrate ppm
Nitrate lb/A
Nitrate depth
Nitrate total
Sulfur s
ZINC Zn
MANGANESE Mn
IRON Fe
COPPER Cu
BORON B
lime rate
SOLUBLE SALTS\r\n
27477
HPplot
2.8_M
60_VH
139_VH
76_VH
511_VH
625_VH
2838_M
100_M
7.8
21.1
6.2
24.7
67.0
0.0
2.1
27477
28
101
0-12
101
85_VH
3.2_H
3_VL
10_L
1.1_M
2.0_VH
_M
0.8_L\r\n
27478
HPHeckRidg
2.7_M
3_VL
37_M
14_M
215_H
567_VH
3132_H
85_M
8.1
21.3
2.6
22.2
73.5
0.0
1.7
27478
34
122
0-12
122
66_VH
1.4_M
3_VL
8_L
0.8_L
1.4_H
_H
0.6_L\r\n
27479
HPSEast
2.8_M
51_VH
110_VH
44_VH
377_VH
631_VH
3086_H
61
7.9
21.9
4.4
24.0
70.4
0.0
1.2
27479
16
58
0-12
58
62_VH
2.6_M
2_VL
10_L
0.9_M
1.2_M
_M
0.6_L\r\n
27480
SEV06
2.0_L
13_L
76_VH
19_H
249_VH
368_VH
3135_H
29
8.1
19.5
3.3
15.7
80.4
0.0
0.6
27480
20
72
0-12
72
21_H
1.8_M
2_VL
6_L
0.8_L
0.8_M
_H
0.4_L\r\n
\r\n
SAMPLE
HPplot
HPHeckRidg
HPSEast
SEV06\r\n
CROP
CORN-bu
CORN-bu
CORN-bu
CORN-bu\r\n
YIELD
245.0
245.0
245.0
245.0\r\n
PREV CROP
CORN-bu
CORN-bu
CORN-bu
CORN-bu\r\n
N
195
175
235
230\r\n
P205
--
105
--
45\r\n
K2O
--
65
--
40\r\n
--
--
--
--\r\n
SULFUR
--
--
--
5\r\n
Zn
--
3.5
--
1.1\r\n
Mn
6.7
6.7
7.4
7.4\r\n
FE
--
1.2
--
2.4\r\n
Cu
--
1.3
1.1
1.3\r\n
B
--
--
--
0.9\r\n
\r\n','111.pdf'),(129,1,2,2025,'
\r\n
LAB NUMBER
SAMPLE ID
ORGANIC
PHOS P1
PHOS P2
PHOS BiCarb
POTASSIUM
MAGNESIUM
CALCIUM
SODIUM
PH Soil
EXCHANGE
%K
%MG
%CA
%H
%NA
LAB NUMBER
Nitrate ppm
Nitrate lb/A
Nitrate depth
Nitrate total
Sulfur s
ZINC Zn
MANGANESE Mn
IRON Fe
COPPER Cu
BORON B
lime rate
SOLUBLE SALTS\r\n
26199
sev_east
2.5_L
69_VH
130_VH
60_VH
504_VH
513_VH
3351_H
80
7.8
22.7
5.7
18.8
74.0
0.0
1.5
26199
82
148
0-6
148
35_VH
5.0_H
10_M
15_M
1.6_H
1.3_H
_M
0.9_L\r\n
\r\n\r\n
SAMPLE
GOAL
CROP
Prev_CROP
\r\nN NITROGEN
P2O5 PHOSPHATE
K2O POTASH
Mg MAGNESIUM
S SULFUR
Zn ZINC
Mn MANGANESE
Fe IRON
Cu COPPER
B BORON\r\n
sev_east
CORN-bu
240.0
CORN-bu
145
--
--
--
--
--
1.5
--
--
--\r\n
','129.pdf'),(114,1,2,2021,'SOIL TEST fall 2021 sev06\r\n\r\n
\r\n
LAB NUMBER
SAMPLE ID
ORGANIC
PHOS P1
PHOS P2
PHOS BiCarb
POTASSIUM
MAGNESIUM
CALCIUM
SODIUM
PH Soil
EXCHANGE
%K
%MG
%CA
%H
%NA
LAB NUMBER
Nitrate ppm
Nitrate lb/A
Nitrate depth
Nitrate total
Sulfur s
ZINC Zn
MANGANESE Mn
IRON Fe
COPPER Cu
BORON B
lime rate
SOLUBLE SALTS\r\n
53545
SEV8-north
2.4_L
36_VH
130_VH
26_VH
261_VH
469_VH
2953_H
26
7.9
19.5
3.4
20.0
76.0
0.0
0.6
53545
10
36
0-12
36
15_M
3.0_M
3_VL
9_L
0.9_M
0.9_M
_M
0.4_L\r\n
53546
SEV8-south
2.4_L
37_VH
150_VH
28_VH
278_VH
567_VH
3290_H
26
8.1
22.0
3.2
21.5
74.8
0.0
0.5
53546
8
29
0-12
29
14_M
2.8_M
3_VL
11_M
0.9_M
0.9_M
_M
0.4_L\r\n
\r\n\r\n
SAMPLE
GOAL
CROP
Prev_CROP
\r\nN NITROGEN
P2O5 PHOSPHATE
K2O POTASH
Mg MAGNESIUM
S SULFUR
Zn ZINC
Mn MANGANESE
Fe IRON
Cu COPPER
B BORON\r\n
SEV8-north
CORN-bu
260.0
ALFALFA-ton
230
30
30
--
16
--
7.1
--
1.2
0.6\r\n
SEV8-south
CORN-bu
260.0
ALFALFA-ton
240
30
--
--
17
--
7.1
--
1.2
0.6\r\n
','114.pdf'),(115,2,4,2021,'Acerage by crop\r\nCrop Acres\r\nalfalfa 105.0\r\nCORN 0.0\r\nDesert 23.0\r\nwhole corn 251.1\r\ntotal 379.1\r\n\r\nAcerage by Farm\r\nFARM Crop Acres\r\nARCHIVE CORN 0.0\r\nHome 9504 alfalfa 38.0\r\nHome 9504 CORN 0.0\r\nHome 9504 Desert 13.0\r\nHome 9504 whole corn 97.5\r\nSeverance 7847 Alfalfa 67.0\r\nSeverance 7847 CORN 0.0\r\nSeverance 7847 Desert 10.0\r\nSeverance 7847 whole corn 153.6\r\nTotal 379.1','115.jpg'),(117,2,7,2022,'Measured sprayer output just under 11 gal acre\r\n\r\nUsed 30 gal per acre to round up\r\n\r\nCredit----------64oz \r\nSequence -- 13.5 gallons ->4.5 - 2.5 gal \r\nClass act -----7.5 gallons -> 3 - 2.5\r\n\r\nSystem 5 ---- 7.5 gallons -> 3 - 2.5\r\n*Clash -------- 1.8 gallon\r\n\r\n*Banvel equivalent\r\n\r\nRates per acre\r\nSequence 3.5 pints acre\r\nClass Act 2.5 gal per 100 gal\r\nSterling blue 4 oz acre\r\nsystem 5.0 1 qt per acre','117.jpg'),(119,2,12,2022,'Mcginn heading 300.411\r\nSeverance ridge heading 3.00','119.jpg'),(123,2,2,2024,'Map of 2024 fertilizer spread and test locations\r\n\r\nAlfalfaFertilize-soilTestWinterFarm.pdf\r\n\r\nOnedrive/documents','123.pdf'),(124,2,2,2024,'soil tests taken fall 2024\r\nHill require elemental sulfur\r\n
'),(3,'hp hill','2025-04-25','map - Field 1\r\n\r\n1 Spread fertilizer north and south.\r\n2. Keep spreader pattern 20 ft from north fence.\r\n3. Keep spreader pattern 10 ft from east cement ditch\r\n4. Keep spreader pattern 20 ft from creek \r\n\r\n\r\ncorn on corn 2025 crop year',4.0,2025,220,80,80,0,0,2,3,0,1,0.5,0,10,'3.png',0,0,278.82,1092.32,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
134
534
$144.18
11-52-0
154
616
$255.64
46-0-0
442
1766
$467.99
Boron
4
14
$28.00
Copper
5
17
$63.07
Elemental Sulfur
12
45
$13.50
Manganese Sulfate
10
38
$71.06
Zinc 360
6
23
$48.88
'),(4,'hpsheep','2025-04-25','map - Field 2\r\n1. Spread fertilizer east and west.\r\n2. Stay 20 ft from south fence & east road\r\n\r\n\r\ncorn on corn 2025 crop year',36.5,2025,210,40,40,0,0,0,6,0,0,0,0,0,'4.png',0,0,201.91,7341.33,'
'),(6,'hpMcGinn','2025-04-25','map - Field 4\r\n\r\n1. start south end\r\n2. Run truck parallel with south embankment\r\n3. Keep spreader pattern 20 ft from east fence.\r\n4. Keep spreader pattern 20 ft from north cement ditch\r\n5. Keep spreader pattern 20 ft from west cement ditch\r\n6. Stay out of SE corner swamp land',29.0,2025,240,50,40,0,0,0,3,0,0,0,0,0,'6.jpg',0,0,209.28,6021.22,'
',15.0,2025,240,30,0,0,17,0,7.1,0,1.2,0.6,0,0,'11.png',0,1,0.00,0.00,''),(23,'sev07','2025-04-25','map - Field 7\r\n\r\n1. start North end\r\n2. Run truck parallel (west to east) with North Ditch\r\n3. Spread pattern border - 16 ft away from west ditch and Creek border\r\n\r\ncorn on corn\r\nspring application',35.0,2025,220,40,40,0,10,0,3,0,1,0.5,0,0,'11.png',0,0,218.79,7562.58,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
67
2334
$630.18
11-52-0
77
2693
$1,117.60
21-0-0-24
36
1254
$332.31
46-0-0
444
15524
$4,113.86
Boron
4
117
$234.00
Copper
4
140
$519.40
Manganese Sulfate
10
329
$615.23
'),(24,'sev08','2024-11-11','map - Field 8\r\n\r\n1. start South end\r\n2. Run truck parallel (west to east) with North fence\r\n3. Spread pattern border - 16 ft away from west border, south fence and east rode\r\n\r\ncorn on corn 2025\r\nspring application',20.0,2025,225,70,60,0,0,0.5,3,0,1,0.5,0,0,'24.png',0,0,249.92,4923.42,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
100
2000
$540.00
11-52-0
135
2693
$1,117.60
46-0-0
457
9139
$2,421.84
Boron
4
67
$134.00
Copper
4
80
$296.80
Manganese Sulfate
10
188
$351.56
Zinc 360
2
29
$61.63
'),(25,'SEV06','2025-04-25','map - Field 6\r\n\r\n1. Line up with south orange post and north shed\r\n2. Spread pattern border - 16 ft away from west ditch and Creek border\r\n\r\ncorn on corn',20.7,2025,230,40,40,0,5,1,3,0,1,0,0,0,'25.png',0,0,219.55,4512.40,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
67
1381
$372.87
11-52-0
77
1593
$661.10
21-0-0-24
13
267
$70.76
46-0-0
476
9848
$2,609.72
Copper
4
83
$307.93
Manganese Sulfate
10
195
$364.65
Zinc 360
3
59
$125.38
'),(33,'hpPivotNorth67','2025-11-11','Spread field 67 acres\r\n\r\n1. Use pivot tracks to spread\r\n2. Stay 5ft from all field borders',67.0,2026,0,60,60,0,0,0,0,0,0,0,0,0,'33.png',0,0,99.27,6633.27,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
101
6701
$1,809.27
12-40-0-10-1
150
10050
$4,824.00
'),(26,'sevPivCorn','2025-04-25','map - Field 5\r\n\r\n1. Spread SEV06 or Field 6 FIRST to mark east border \r\n2. Start spreading on north end\r\n3. Run spreader East and West\r\n4. Spread pattern border - 16 ft away from existing east road, existing south road, and west cement ditch. 0 ft. everywhere else.',105.0,2025,230,50,40,0,0,0,3,0,0,0,0,0,'26.png',0,0,203.72,21195.27,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
67
7001
$1,890.27
11-52-0
97
10097
$4,190.26
46-0-0
478
50086
$13,272.79
Manganese Sulfate
10
985
$1,841.95
'),(34,'Cover map SEV','2025-11-08','Cover map',92.0,2025,0,60,60,0,0,0,0,0,0,0,0,0,'34.png',1,0,0.00,0.00,''),(35,'Cover map HP','2025-11-10','Cover map',67.0,2026,0,60,60,0,0,0,0,0,0,0,0,0,'35.png',0,1,0.00,0.00,''),(30,'sevPivSWcorner','2025-11-09','map - Field 47 acre\r\n\r\n1.Start Mark 151-degree line 40 ft west pivot tower. Make east boundary \r\n2. Start spreading on west end\r\n3. Run spreader North & South\r\n4. Spread pattern border - 16 ft away from existing south road & existing north pivot road',47.0,2026,0,60,60,0,0,0,0,0,0,0,0,0,'30.png',0,0,99.27,4653.27,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
101
4701
$1,269.27
12-40-0-10-1
150
7050
$3,384.00
'),(27,'sevPivNe','2025-01-24','1. start N end\r\n2. Run truck parallel (west to east) with North fence\r\n3. Spread pattern border - 16 ft away from west border, south fence and east rode',34.0,2025,220,30,30,0,0,0,3,0,0,0,0,0,'15.png',1,1,178.05,6053.92,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
51
1701
$459.27
11-52-0
58
1962
$814.23
46-0-0
465
15792
$4,184.88
Manganese Sulfate
10
319
$596.53
'),(31,'sevPivNWcorner','2025-11-09','map - Field 35 acre\r\n\r\nSpread with pivot racks\r\n4. Spread pattern border - 10 ft away from north cement ditch & existing east & south pivot roads',34.5,2026,0,60,60,0,0,0,0,0,0,0,0,0,'31.png',0,0,99.27,3415.77,'
'),(29,'McGinn/hp Farms Fields 1-4','2025-04-25','west farm map',146.0,2025,0,0,0,0,0,0,0,0,0,0,0,0,'29.png',0,0,0.00,0.00,''),(36,'HPPivot','2025-11-06','HPPivot corn NW, NE and alfalfa midway',0.0,2025,0,0,0,0,0,0,0,0,0,0,0.128,0,'36.jpg',0,1,0.00,0.00,''),(37,'HP 3 plots','2024-11-12','HPPivot corn W, below gated pipe and Hill',100.0,2024,0,0,0,0,0,0,0,0,0,0,0.124,0,'37.pdf',0,1,0.00,0.00,''),(45,'SevPivotNE','2026-01-06','map - Field 3\r\n\r\n1. Spread fertilizer north and south.\r\n2. Stay 20 ft from south fence & west fence \r\n\r\ncorn on corn',57.5,2026,200,20,20,0,0,0,6,0,1,0,1,0,'45.jpg',1,0,237.83,12943.87,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
34
1917
$555.93
12-40-0-6.5-1
50
2875
$1,473.44
46-0-0
422
24250
$7,881.25
Copper
5
231
$857.01
Manganese Sulfate
19
1079
$1,683.24
sperader
2
58
$493.00
'),(38,'hpSwest (hp_sw)','2026-01-05','map - Field 3\r\n\r\n1. Spread fertilizer north and south.\r\n2. Stay 20 ft from south fence & west fence\r\n \r\n\r\ncorn on corn',34.0,2026,210,70,70,0,0,0,6,2,1,0,1,0,'1.png',1,0,324.83,10618.11,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
117
3967
$1,150.43
12-40-0-6.5-1
175
5950
$3,049.38
46-0-0
411
13970
$4,540.25
Copper
5
137
$508.27
Iron Sulfate
7
220
$77.00
Manganese Sulfate
19
638
$995.28
sperader
2
35
$297.50
'),(39,'hp hill','2026-01-05','map - Field 1\r\n\r\n1 Spread fertilizer north and south.\r\n2. Keep spreader pattern 20 ft from north fence.\r\n3. Keep spreader pattern 10 ft from east cement ditch\r\n4. Keep spreader pattern 20 ft from creek \r\n\r\n\r\ncorn on corn 2025 crop year',4.0,2026,240,80,80,0,0,2,6,0,1,0,0,10,'3.png',0,0,278.82,1092.32,''),(40,'hpsheep','2026-01-05','map - Field 2\r\n1. Spread fertilizer east and west.\r\n2. Stay 20 ft from south fence & east road\r\n\r\n\r\ncorn on corn 2025 crop year',36.5,2026,210,20,20,6,0,0,6,1,0,0,1,0,'4.png',1,0,227.83,7973.42,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
34
1217
$352.93
12-40-0-6.5-1
50
1825
$935.31
46-0-0
444
16187
$5,260.78
Iron Sulfate
4
118
$41.30
Manganese Sulfate
19
685
$1,068.60
sperader
2
37
$314.50
'),(41,'hpMcGinn','2026-01-05','map - Field 4\r\n\r\n1. start south end\r\n2. Run truck parallel with south embankment\r\n3. Keep spreader pattern 20 ft from east fence.\r\n4. Keep spreader pattern 20 ft from north cement ditch\r\n5. Keep spreader pattern 20 ft from west cement ditch\r\n6. Stay out of SE corner swamp land',29.0,2026,230,50,40,0,0,0,6,0,0,0,1,0,'6.jpg',1,0,282.23,7927.69,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
67
1934
$560.86
12-40-0-6.5-1
125
3625
$1,857.81
46-0-0
468
13555
$4,405.38
Manganese Sulfate
19
544
$848.64
sperader
2
30
$255.00
'),(42,'SEV06','2026-01-05','map - Field 6\r\n1. Line up with south orange post and north shed\r\n2. Spread pattern border - 16 ft away from west ditch and Creek border\r\ncorn on corn',20.7,2026,230,40,40,0,5,1,3,0,1,0,1,0,'25.png',1,0,275.88,5440.25,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
67
1381
$400.49
12-40-0-6.5-1
100
2070
$1,060.88
46-0-0
474
9810
$3,188.25
Copper
5
83
$307.93
Manganese Sulfate
10
195
$304.20
sperader
2
21
$178.50
'),(43,'sev07','2026-01-05','map - Field 7\r\n1. start North end\r\n2. Run truck parallel (west to east) with North Ditch\r\n3. Spread pattern border - 16 ft away from west ditch and Creek border\r\ncorn on corn\r\nspring application',35.0,2026,220,40,40,0,10,0,3,0,1,0.5,1,0,'11.png',1,0,278.01,9220.04,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
67
2334
$676.86
12-40-0-6.5-1
100
3500
$1,793.75
21-0-0-24
7
233
$64.08
46-0-0
450
15720
$5,109.00
Boron
4
117
$234.00
Copper
5
141
$523.11
Manganese Sulfate
10
329
$513.24
sperader
2
36
$306.00
'),(44,'sev08','2026-01-05','map - Field 8\r\n1. start South end\r\n2. Run truck parallel (west to east) with North fence\r\n3. Spread pattern border - 16 ft away from west border, south fence and east rode\r\ncorn on corn 2025\r\nspring application',20.0,2026,225,70,60,0,0,0.5,3,0,1,0.5,1,0,'24.png',1,0,322.43,6163.08,'
Product
LBS/ACRE
POUNDS
Cost
0-0-60
101
2001
$580.29
12-40-0-6.5-1
175
3500
$1,793.75
46-0-0
444
8870
$2,882.75
Boron
4
67
$134.00
Copper
5
81
$300.51
Manganese Sulfate
10
188
$293.28
sperader
2
21
$178.50
');
/*!40000 ALTER TABLE `fertilizer_applied` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `inventory`
--
DROP TABLE IF EXISTS `inventory`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `inventory` (
`inventoryid` mediumint(9) NOT NULL AUTO_INCREMENT,
`productid` smallint(6) NOT NULL,
`mapid` smallint(6) NOT NULL,
`amount` tinyint(11) NOT NULL,
`date` datetime NOT NULL,
`harvest_date` date NOT NULL,
`notes` text NOT NULL,
`gps` varchar(60) NOT NULL,
`crop_year` smallint(6) NOT NULL,
PRIMARY KEY (`inventoryid`),
KEY `date` (`date`,`harvest_date`)
) ENGINE=MyISAM AUTO_INCREMENT=259 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `inventory`
--
LOCK TABLES `inventory` WRITE;
/*!40000 ALTER TABLE `inventory` DISABLE KEYS */;
INSERT INTO `inventory` VALUES (1,1,10,15,'2010-04-20 00:00:00','0000-00-00','planted 1/3 on the 20th. rest on the 21st. There might be some dekalb at east end.\r\n\r\nSprayed on jun 1. Noticed skips where sandy soil. The weeds are also gone. Cold spring may be the problem.\r\n\r\nReceived hail damage on this field especially north end. Yielded good. Hit dry down the earliest.\r\n\r\nHarvested Oct 16','',2010),(2,2,11,2,'2010-04-21 00:00:00','0000-00-00','4 of the seed buckets filled.','',2010),(3,3,11,1,'2010-04-21 00:00:00','0000-00-00','Refuge planted in buckets 5&6','',2010),(4,4,11,9,'2010-04-21 00:00:00','0000-00-00','Mark seed change at west 2nd telephone from south. Stopped 4 rounds new hayfield.','',2010),(5,4,11,2,'2010-05-03 00:00:00','0000-00-00','West silver shed filled. Seed carried over to sev 09.\r\n\r\nThe north corn was slightly drier but both varieties are close in moisture in this field. Both varieties yielding high. Best corn so far.','',2010),(6,7,12,9,'2010-05-03 00:00:00','0000-00-00','3 rounds into field start fill. 2 rounds into sev 07 with seed left over.\r\n\r\nAs of Oct 29 this was at 17 plus moisture by the tester. Seems to be the wettest corn.','',2010),(7,3,13,3,'2010-05-04 00:00:00','0000-00-00','Start at 3rd round\r\n\r\nHarvested Nov 1\r\nYield 228.29 bu/acre 17%. beats Pioneer in the yield test\r\n\r\nHavested Nov 4-5 moisture 15%','',2010),(8,10,13,9,'2010-05-04 00:00:00','0000-00-00','2nd drop from north\r\n\r\nChecked Moisture Oct 30, I was surprised to see 16.5 moisture that was the wettest at 22% a week earlier.\r\n\r\nHarversted Nov 1\r\n198.91 busshel/acre the Dekalb variety is much better.\r\n\r\nFinished Harvest Nov 4 moisture 15%','',2010),(9,11,13,3,'2010-05-04 00:00:00','0000-00-00','Telephone pole by cement pit.\r\nCarried seed to south sev 08.\r\n\r\nBoth varieties showed a drop in yield because of the large seep spot at the bottom.\r\n\r\nHarvest Nov 1 140 bu/acre. The P0125AM1 next to it was 151.67 bu/acre','',2010),(10,6,14,11,'2010-05-04 00:00:00','0000-00-00','Started north of the lane culvert.\r\nAdded 2 bags toward evening shown in total. Kept some for pat plot\r\n\r\nHarvested Oct 26. This was the second driest but close to the 38H72.\r\nIt did stand better then the PO125R which was on the south end of field','',2010),(11,7,1,3,'2010-05-05 00:00:00','0000-00-00','Planter Units 1 & 2\r\nharvest nov 6\r\ndriest varity at 14 moisture','',2010),(12,8,1,6,'2010-05-05 00:00:00','0000-00-00','Planter units 3 - 6. Carried over to hpswest.\r\nHarvested there nov 7','',2010),(13,5,7,7,'2010-05-05 00:00:00','0000-00-00','Mule 3000 switched at colonial house east and betwwen two small trees west.','',2010),(14,4,8,6,'2010-05-05 00:00:00','0000-00-00','Placed bags in hopper for am plant. Colonial house to east variety switch.','',2010),(15,4,8,3,'2010-05-06 00:00:00','0000-00-00','harvested nov 7\r\nmoisture 16%\r\nNear end long rows','',2010),(16,5,6,5,'2010-05-06 00:00:00','0000-00-00','Some 45-79 in units','',2010),(17,3,6,1,'2010-05-06 00:00:00','0000-00-00','Added at the 14 section north of lower cement ditch drop.','',2010),(18,14,2,1,'2010-05-06 00:00:00','0000-00-00','Plot\r\nDEKALB DKC52-62 24 rows\r\nPioneer P9512XR 18 rows planted rest at east plot','',2010),(19,12,2,1,'2010-05-06 00:00:00','0000-00-00','12 rows in plot. PAT plot starts here and goes till the next SAMPLE and planted rest to east','',2010),(20,13,2,1,'2010-05-06 17:00:00','0000-00-00','planted whole bag. Planted samples after this sample to the east.','',2010),(21,15,7,5,'2010-05-10 00:00:00','0000-00-00','Q2 pass starting E to W\r\nDouble delicious 2 bgs unit4\r\nGot to have it unit 5\r\nThat\\\'s delicious unit 6\r\nStarted back down\r\nAmbrosia unit 2\r\nDouble delicious unit 3\r\nAmbosia 1/2 down unit 6\r\nLower fiel','',2010),(25,20,10,7,'2011-04-28 08:53:53','2011-11-08','Switched at deans house telephone pole. Saved some seed for plot.\r\nharvest: 10/24/11\r\nmoisture top from rummers house\r\n16% 10/19/2011\r\n15% 10/24/2011\r\nHarvest: 11/8/11','',2011),(26,1,11,9,'2011-04-29 08:39:22','2011-11-17','Switch between North schlagel house and south of telephone pole.\r\n\r\nmoisture bottom check by y 22% 10/14/11\r\n20% 10/22/11\r\n16.8% 11/8/11\r\nHarvest: 11/17/11','',2011),(27,4,10,8,'2011-04-27 16:12:57','2011-11-08','Some seed left from six\r\n\r\nmoisture field bottom 21% 10/14/11\r\n14.5% 10/22/11\r\ntop check 20% 10/19/11\r\n17.5% 10/22/11\r\n17.5% 10/31/11\r\n14.5% 11/8/11\r\nHarvest: 11/8/11','',2011),(28,20,13,5,'2011-04-29 17:04:02','2011-11-10','Silver shed north side\r\n18.5% moist 10/14/11\r\nkilling frost 10/20/2011\r\n17.5% 10/20/2011\r\n16.5% 10/31/11\r\n14.5% 11/8/11\r\nHarvest: 11/10/11','',2011),(46,8,2,0,'2011-05-03 13:49:12','2011-11-25','','',2011),(30,5,12,7,'2011-04-28 15:42:32','2011-11-16','Switched at 1st telephone pole north of pump house.\r\n\r\nmoist test bottom near telepole 2\r\n25% 10/19/2011\r\n22% 10/22/11\r\n18% 11/8/11\r\n15% 11/14/11\r\nHarvest: 11/16/11','',2011),(31,2,12,5,'2011-04-28 13:04:21','2011-11-16','1 round in 05b\r\nMoist 17.5% in 5b 10/23/11\r\n14.0% 11/14/11\r\nHarvest: 11/16/11','',2011),(32,8,18,7,'2011-04-27 10:12:45','0000-00-00','First field acre 1423 monitor. Had monitor problems.\r\nEmerged out of ground the quickest.','',2011),(33,5,8,5,'2011-04-30 13:02:44','2011-11-21','June 19 leader in height and color.\r\n\r\n2 rounds north past hole. 2nd hole from north. See \r\npicture\r\nHarvest: 11/21/11.','',2011),(34,2,8,4,'2011-04-30 10:23:44','2011-11-21','Continued From top field.\r\nHarvest: 11/21/11','',2011),(35,2,7,8,'2011-04-30 08:01:22','2011-11-22','3 rounds of 9512 @ 11% 11/20/11\r\n\r\n14.5% 11/20/11\r\nHarvest: 11/22/11','',2011),(36,25,6,2,'2011-05-01 13:18:03','2011-11-22','13% 11/20/11','',2011),(37,25,3,6,'2011-04-30 15:02:35','2011-11-12','started 37K11. Made six rounds before filling. Finished Sunday morning\r\nmoisture garden 23% 10/20/11\r\n13.0% 11/8/11\r\n13% 11/12/11\r\nK11 was 15.5% 11/13/11','',2011),(38,25,4,2,'2011-05-01 08:15:00','2011-11-12','From lake field.\r\nmoisture 17% 10/20/11\r\n12% 11/8/11\r\nHarvest: 11/12/11','',2011),(39,2,2,0,'2011-05-03 10:15:36','2011-11-25','','',2011),(40,5,2,0,'2011-05-03 10:01:27','2011-11-25','Placed post in fence where this variety starts','',2011),(41,14,2,1,'2011-05-03 14:38:39','2011-11-25','','',2011),(42,1,2,0,'2011-05-03 14:01:52','2011-11-25','','',2011),(43,21,2,1,'2011-05-03 13:38:55','2011-11-25','Only 1 bag. Next big after plot. Started where water dumps into ditch.','',2011),(44,2,13,8,'2011-04-29 13:59:03','2011-11-18','Switch middle 1st drop. Decreased population 500 seeds per acre because of small seed\r\n\r\n26% 10/19/2011\r\n23.5% 10/22/11\r\n15.8% 11/8/11\r\n16% 11/14/11\r\nHarvest: 11/18/11','',2011),(45,9,14,2,'2011-04-11 10:37:12','2011-09-02','first entry later','',2011),(47,22,14,5,'2011-04-11 11:51:29','2011-09-01','','',2011),(48,9,14,2,'2011-04-11 11:48:41','2011-09-01','','',2011),(53,2,6,1,'2011-05-01 15:20:40','2011-11-23','Added looking at panels east.','',2011),(49,9,14,2,'2011-04-11 14:22:33','2011-09-01','','',2011),(50,22,14,3,'2011-04-11 14:23:27','2011-09-01','Testing 12345 the conditions were sunny with a temperature of 75 degrees','',2011),(51,9,14,2,'2011-04-11 16:07:44','2011-09-01','The alfalfa has been planted with a Tv 6070 tractor','',2011),(52,22,14,2,'2011-04-12 08:53:02','2011-09-01','5 bags in planter at start','',2011),(54,5,1,6,'2011-05-02 13:30:30','2011-11-23','15.5% 11/20/11','',2011),(55,24,2,1,'2011-05-03 14:29:51','2011-11-25','After 0231 where pump water comes out. Mixed all the samples to finish off the corner','',2011),(56,28,2,1,'2011-05-03 14:20:32','2011-11-25','','',2011),(57,23,2,1,'2011-05-03 15:07:39','2011-11-25','Triumph 32 before this variety. Added the whole bag. Finished of the other big bags after this variety as mentioned by the bags profile.','',2011),(58,27,2,1,'2011-05-03 14:10:46','2011-11-25','','',2011),(59,8,18,1,'2011-04-27 15:19:28','2011-11-18','moist test bottom 50 yard from clean out\r\n27% 10/190/2011\r\n23% 10/22/2011\r\n20.5% 11/08/11\r\nHarvest: 11/18/11','',2011),(60,1,11,3,'2011-04-29 11:09:16','0000-00-00','Some left over for BF07\r\nmoist 21.5% 10/31/11','',2011),(61,4,6,2,'2011-05-01 14:28:20','2011-11-23','Added between new shed and grain bin.\r\n14.5% 11/20/11','',2011),(62,30,2,1,'2011-05-03 09:51:04','2011-11-25','First variety 2.5 rounds','',2011),(63,29,6,1,'2011-05-02 09:52:19','2011-11-23','to end of field','',2011),(64,29,2,0,'2011-05-03 14:47:22','2011-11-25','Some of the early variety was mixed in since I was short. Placed post in fence to separate the varieties.','',2011),(65,15,8,0,'2011-05-05 08:53:51','2011-11-25','Planting from east to west.\r\n\r\n1 ambrosia, 2 gotta have it, 3 that\\\'s delicious, 4 gotta have it, 5 that\\\'s delicious,6 double delicious\r\nMoved up to 3 rows top field.\r\n\r\n4 that\\\'s delicious 1/2 up field. 6 also had some ambrosia added to finish.','',2011),(68,37,7,6,'2012-04-25 07:51:13','2011-12-31','17 percent moisture on November 1st 2012','',2012),(69,39,13,12,'2012-04-20 09:15:55','2011-12-31','22 percent moisture as of 10 Dash 8 - 2012','',2012),(70,33,8,9,'2012-04-23 19:26:27','2011-12-31','No iNsecticide applied','',2012),(71,34,1,3,'2012-04-26 08:12:20','2011-12-31','East side of heckmans white barn.','',2012),(72,37,6,1,'2012-04-25 13:24:32','2011-12-31','center of pasture','',2012),(73,31,10,1,'2012-04-23 09:19:00','2011-12-31','2 rounds start 37K11 for field\r\nSeed changed at the pump outlet.\r\n 16 percent moisture as as of 10 - 7 - 2012','',2012),(74,32,6,5,'2012-04-25 11:16:27','2011-12-31','18 percent moisture on November 1st 2012','',2012),(75,32,7,1,'2012-04-25 10:53:11','2011-12-31','3 rounds of seed north end','',2012),(76,35,10,12,'2012-04-22 19:13:45','2011-12-31','1st round K11 for testing\r\n12 of 12 needed\r\n\r\n 16 percent moisture as of 10 - 12 2012','',2012),(77,36,15,10,'2012-04-23 10:37:54','2011-12-31','9 of. 12 bags','',2012),(79,33,3,6,'2012-04-24 14:08:33','2011-12-31','NO INSECTICIDE','',2012),(80,33,4,1,'2012-04-25 06:25:51','2011-12-31','','',2012),(81,37,2,0,'2012-04-25 14:01:34','2011-12-31','test plot TEST PLOT VARIETY 2','',2012),(82,38,12,8,'2012-04-20 13:54:11','2011-12-31','','',2012),(83,36,18,2,'2012-04-23 10:36:37','2011-12-31','the seed has been added for the lane comes down through the two fields','',2012),(84,34,12,2,'2012-04-20 17:33:44','2011-12-31','halfway between second and third telephone phone','',2012),(85,33,2,0,'2012-04-26 09:42:19','2011-12-31','test plot variety 4','',2012),(86,40,1,2,'2012-04-26 08:16:58','2011-12-31','','',2012),(87,40,12,3,'2012-04-20 17:34:45','2011-12-31','','',2012),(88,40,6,2,'2012-04-25 13:26:04','2011-12-31','','',2012),(89,40,7,3,'2012-04-25 06:26:56','2011-12-31','','',2012),(90,40,11,3,'2012-04-21 10:23:15','2011-12-31','partial bag left','',2012),(91,40,2,2,'2012-04-26 22:00:18','2011-12-31','Sweet corn hpsw\r\nstarting from the inside of the outfield \r\nRow 1: gotta have it\r\nRow2: that\\\'s delicious\r\nRow3: gotta have it\r\nR ow 4: double delicious\r\nRow 5: gotta have it.\r\nRow 6: double delicious','',2012),(92,40,10,4,'2012-04-21 20:37:46','2011-12-31','4 of 4 needed record open bag on next field','',2012),(94,38,13,2,'2012-04-20 13:09:31','2012-12-31','telephone pole 5 yellow water tank cattle corral\r\n 19 percent moisture as of 10 Dash 8 - 2012','',2012),(95,34,11,12,'2012-04-21 10:21:13','2012-12-31','island telephone pole. en route 2 bags by the hay field\r\n 18 percent moisture as of 10 - 7 - 2012','',2012),(96,32,2,0,'2012-04-25 12:49:07','2012-12-31','Started planting at bottom of field. Loaded plots at bottom of field.\r\n3 rounds TEST PLOT VARIETY 1','',2012),(97,31,18,5,'2012-04-23 09:19:54','2012-12-31','started planning field by the lane\r\n 21 percent moisture as of 10 Dash 8 - 2012','',2012),(98,37,4,1,'2012-04-25 07:09:00','2012-12-31','variety starts at the west edge of the red white shed. started spreading the aztec here too','',2012),(99,37,1,4,'2012-04-26 07:14:54','2012-12-31','center of pasture','',2012),(100,34,2,0,'2012-04-26 09:31:39','2012-12-31','Plot variety 3','',2012),(101,41,2,1,'2012-04-26 09:54:47','2012-12-31','test plot variety 5','',2012),(102,36,2,0,'2012-04-26 10:05:38','2012-12-31','test plot variety 6','',2012),(103,39,2,0,'2012-04-26 10:26:17','2012-12-31','test plot variety 7','',2012),(104,45,2,1,'2012-04-26 10:45:00','2012-12-31','test plot variety 8','',2012),(105,42,2,1,'2012-04-26 10:55:30','2012-12-31','test plot variety 9','',2012),(106,35,2,1,'2012-04-26 11:08:20','2012-12-31','test plot variety 10','',2012),(107,44,2,1,'2012-04-26 11:15:22','2012-12-31','test plot variety 11','',2012),(108,26,2,1,'2012-04-26 11:25:36','2012-12-31','test plot variety 12\r\npost marks end of plot unlike first which splits variety 1 and 2','',2012),(109,46,12,12,'2013-05-14 14:59:41','2013-12-31','Variety switched north of the telephone pole','',2013),(111,39,13,12,'2013-05-13 21:17:20','2013-12-31','North side 3212 triumph near the first drop\r\n10/25/13 15%','',2013),(112,39,7,6,'2013-05-15 17:08:58','2013-12-31','5 rounnds from north end\r\n11/7/13 14%','',2013),(117,37,2,0,'2013-05-16 18:25:09','2013-12-31','No 8','',2013),(113,41,8,9,'2013-05-15 09:50:11','2013-12-31','3 rounds south with 9946 triumph from sev 1o\r\n18.5% 11/7/13\r\nvariety sucks in alkali','',2013),(114,51,7,6,'2013-05-15 13:17:50','2013-12-31','4 rounds south with 08\r\n11/7/13 19%','',2013),(115,52,6,3,'2013-05-16 18:10:26','2013-12-31','finished this field and started the next one the first variety in the plot.\r\n11/7/13 15%','',2013),(116,37,12,6,'2013-05-14 10:55:20','2013-12-31','3 rounds on 7','',2013),(118,39,18,6,'2013-05-17 09:47:49','2013-12-31','F','',2013),(119,34,10,12,'2013-05-13 15:05:29','2013-12-31','10/25/13 18.5%','',2013),(120,47,2,1,'2013-05-16 18:19:02','2013-12-31','No 2','',2013),(121,48,2,1,'2013-05-16 18:19:46','2013-12-31','No 3','',2013),(122,49,2,1,'2013-05-16 18:20:27','2013-12-31','No 4','',2013),(123,50,2,1,'2013-05-16 18:21:11','2013-12-31','No 5','',2013),(124,53,18,1,'2013-05-17 09:46:50','2013-12-31','','',2013),(125,52,1,4,'2013-05-17 05:39:14','2013-12-31','Could be 3 bags','',2013),(126,51,13,3,'2013-05-14 19:45:37','2013-12-31','10/25/13 19.5% moisture','',2013),(127,51,10,3,'2013-05-14 06:01:01','2013-12-31','switched variety seed by rumor Hals place','',2013),(128,54,11,6,'2013-05-15 07:07:17','2013-12-31','Variety switch east corner hay \r\n11/4/13 - 17% moisture the corn is yielding good','',2013),(129,52,2,0,'2013-05-16 18:17:39','2013-12-31','first variety. Planted 24 rows. All varities have 0.57 acres per plot via tractor monitor','',2013),(130,54,2,0,'2013-05-16 18:21:38','2013-12-31','No 6','',2013),(131,46,2,0,'2013-05-16 18:22:38','2013-12-31','No 7.\r\nThis variety only complete 6 of 12 rows','',2013),(132,39,2,0,'2013-05-16 18:25:28','2013-12-31','No 9','',2013),(133,41,2,0,'2013-05-16 18:26:25','2013-12-31','No 10','',2013),(134,53,2,1,'2013-05-16 18:27:55','2013-12-31','No 11\r\nPkanted full bag','',2013),(135,55,3,17,'2013-09-30 06:01:01','2014-08-08','field had excellent moisture','',2014),(136,56,13,15,'2014-04-19 10:36:11','2014-10-21','added more seed after drop 1. added two more bags the next morning','',2014),(138,62,12,4,'2014-04-21 16:33:28','2014-10-22','#3\r\nE 40.54195 - -104.86041\r\nthis variety of corn Good','40.54200 To 40.54173',2014),(150,62,2,0,'2014-04-23 14:05:36','2014-12-31','5th','-104.914052',2014),(140,60,12,12,'2014-04-21 08:18:37','2014-11-01','#1\r\nStart variety parallel north cement ditch.\r\ngps readings east of field or on gated pipe road.','40.54508 To 40.54323',2014),(142,59,2,0,'2014-04-23 14:06:36','2014-12-31','6th','-104.913938',2014),(143,56,8,8,'2014-04-23 19:22:23','2014-12-31','1. double delicious\r\n2. Goto have it.\r\n3. Thats delicious\r\n4. Miracle\r\n5. Ambrosia\r\n6. Rr from triumph\r\n\r\nPlant bottom totop','',2014),(144,58,6,5,'2014-04-25 07:56:37','2014-12-31','P0231 planted to the variety to the south\r\nproximity to the new white shed.','40.54817 -104.91415',2014),(146,57,2,0,'2014-04-23 14:02:36','2014-12-31','2nd','-104.914370',2014),(147,58,2,0,'2014-04-23 14:01:36','2014-12-31','1st variety','-104.914469\r\n40.552497 Start Latitude North Side',2014),(148,61,12,6,'2014-04-22 06:01:01','2014-10-22','#4\r\nthis variety is good\r\ntwo Rounds North Of The Pivot Tower','40.54173 to 40.54122\r\n',2014),(149,59,12,12,'2014-04-21 13:30:24','2014-10-30','#2\r\nrows run east and west','40.54323 To 40.54200 End',2014),(151,58,12,21,'2014-04-22 14:42:39','2014-10-22','#5','40.54122 To 40.53938',2014),(152,60,2,0,'2014-04-23 14:04:36','2014-12-31','4th','-104.914160',2014),(153,56,2,0,'2014-04-23 14:03:36','2014-11-01','3rd','-104.914273',2014),(154,64,1,4,'2014-04-07 06:01:01','2014-12-31','ROUNDUP READY alfalfa.\r\n\r\nThe right hand side planted heavier then west','',2014),(156,63,12,7,'2014-04-23 12:09:30','2014-10-22','#6\r\ntwo rounds south of the telephone pole by the crossing.','40.53938 To 40.53871',2014),(157,59,12,6,'2014-04-23 13:17:44','2014-10-22','#7\r\nSouth of 2nd telepole and finished field to south lane\r\nThis variety fails hail','40.53871 To 40.53800',2014),(158,57,8,12,'2014-04-24 12:13:57','2014-12-31','Short rows by shed','',2014),(159,65,2,1,'2014-04-23 16:01:01','2014-12-31','8th','-104.913740',2014),(160,66,2,1,'2014-04-23 16:50:30','2014-12-31','9th','-104.913631',2014),(161,67,2,1,'2014-04-23 16:51:12','2014-12-31','10th','-104.913513',2014),(162,68,2,1,'2014-04-23 16:52:47','2014-12-31','11th','-104.913398',2014),(163,69,2,1,'2014-04-23 16:53:57','2014-12-31','12th','-104.913280\r\n40.552497 end latitude north side',2014),(164,70,13,15,'2015-04-25 11:08:48','2015-12-31','Estimated 22% 10/27','',2015),(165,70,8,9,'2015-05-01 09:05:19','2015-12-31','Estimated',' ',2015),(166,70,7,8,'2015-05-01 09:15:37','2015-12-31','Estimated\r\n24% 11/2','',2015),(167,72,19,30,'2015-04-29 12:04:17','2015-12-31','North pivot circle 28%\r\n11 first fill, 12 2nd dill','40.54162 S End',2015),(168,71,9,2,'2015-04-07 08:10:31','2015-12-31','Bottom of the pivot circle','',2015),(169,71,12,9,'2015-04-30 05:51:30','2015-12-31','South of the pivot circle','',2015),(170,74,12,5,'2015-04-30 09:59:46','2015-12-31','2ND South of the pivot circle 18% 10/28','40.54008 N End',2015),(171,76,6,4,'2015-05-02 09:15:09','2015-12-31','Switch at white shed grain tank','',2015),(172,75,12,21,'2015-04-30 11:42:06','2015-12-31','3rd from south 19.5% 10/28','Cement Ditch Crossing Start',2015),(173,70,20,8,'2015-05-01 07:35:45','2015-12-31','9067 to east\r\n17% 11/2','104.91045 Variety Started',2015),(174,72,15,3,'2015-04-29 19:00:36','2015-12-31','North pivot circle','40.54097 S End',2015),(175,76,2,1,'2015-05-02 07:32:32','2015-12-31','1st variety in plot. 2 rounds','',2015),(176,76,2,1,'2015-05-02 20:10:49','2015-12-31','1st Variety',' ',2015),(177,71,2,1,'2015-05-02 20:12:18','2015-12-31','2nd Variety',' ',2015),(178,70,2,0,'2015-05-02 20:13:17','2015-12-31','3rd Variety',' ',2015),(179,77,2,1,'2015-05-02 20:21:24','2015-12-31','4th Variety',' ',2015),(180,75,2,1,'2015-05-02 20:22:33','2015-12-31','5th Variety',' ',2015),(181,78,2,1,'2015-05-02 20:23:14','2015-12-31','6th Variety',' ',2015),(182,79,2,1,'2015-05-02 20:23:42','2015-12-31','7th Variety',' ',2015),(183,72,2,1,'2015-05-02 20:24:34','2015-12-31','8th Variety. whole bag put in. Made 3 round before variety mixing occurs.','Steel Fence Post Between Variety 7 & 8',2015),(184,81,21,6,'2016-04-25 08:39:39','2016-10-24','A. Large seed planted first','',2016),(186,81,7,6,'2016-05-04 16:52:05','2016-11-08','Filled actually in sheep field','',2016),(187,82,5,5,'2016-05-04 10:18:42','2016-11-05','End variety by ditch gate opening west of first big drop. Start Dekalb here.','',2016),(188,83,19,14,'2016-04-26 16:20:55','2016-10-24','C. South p9789AMXT North DK52-04\r\nRain Monday Night dried by 4pm Tuesday because of wind 50 degree temp\r\nswitch varieties at road sign at the end of the big cement ditch\r\n6 BAGS added on Tuesday 6:30pm\r\n6 bags Wednesday 7am\r\nWent to Severance06 after reaching the pivot tower to allow pivot to move back west.\r\n\r\nCHANGED 20 TO 14 BAGS. ADDED 6 TO SEV06','',2016),(189,81,19,10,'2016-04-25 13:35:55','2016-10-28','B. Started planning in the NW corner. Planted some north rows then finished NE corner after pivot moved far enough. Temperature warm &0 degree mostly cloudy in afternoon.','',2016),(190,82,12,18,'2016-04-27 14:50:21','2016-11-03','End of sev06 also 7 rounds from circle. start after pivot tower.\r\n6 bags Wednesday 6pm','',2016),(191,83,6,5,'2016-05-05 08:38:23','2016-11-08','Same Variety in HP Southwest. Ron bakel delivered us 10 more bags of the pioneer 9789 am XT','',2016),(194,83,15,6,'2016-04-27 13:52:02','2016-10-24','C1. Added one bag of 9811 on top Triumph\r\nMoisture range between 14% And 15 and a half percent on 10/26/16','',2016),(195,85,13,6,'2016-04-11 06:45:33','2016-10-07','Planted at 13 lb. per acre','',2016),(196,81,19,6,'2016-04-26 16:20:14','2016-10-28','B1. DeKalb has 2 seed sizes. Started with large seed first\r\nSeeds size switch\r\n\r\ncHANGED COUNT FROM 7 TO 6','',2016),(197,86,12,9,'2016-04-28 14:18:21','2016-11-03','D. P0157 North 2nd pole (just south of crossing).Robseed south of telephone pole near the old crossing\r\nEnd of sev06 also 7 rounds from circle. start after pivot tower.\r\n9 bags thursday 8 a.m','',2016),(198,81,5,12,'2016-05-04 10:18:59','2016-11-05','Start variety by ditch gate opening west of first big drop. End pioneer here.','',2016),(199,83,7,5,'2016-05-04 16:52:59','2016-11-08','Dekalb south pioneer north. Looking east variety switches 2 round north of 2nd telephone pole at 1/3 of field done','',2016),(200,83,2,1,'2016-05-05 12:38:18','2016-11-09','v1','',2016),(201,82,2,0,'2016-05-05 12:48:18','2016-11-09','V2','',2016),(202,86,2,1,'2016-05-05 12:53:18','2016-11-09','V3','',2016),(203,81,2,0,'2016-05-05 12:58:18','2016-11-09','V4','',2016),(204,88,2,1,'2016-05-05 13:03:18','2016-11-09','V5','',2016),(205,89,2,1,'2016-05-05 13:09:18','2016-11-09','V6','',2016),(206,87,2,1,'2016-05-05 13:19:18','2016-11-09','V7\r\nPlanted the whole bag. Added the last 2 pioneer varieties on top. Planted them then added the robs seed on top then cleaned up remaining plot seed until done.','',2016),(207,0,21,4,'2017-03-23 06:01:01','2017-12-31','Extremely dry seed bed. Rained on 3/27/2017 and 3/31/17','',2017),(208,103,2,1,'2017-05-01 19:01:24','2017-12-01','variety 1',' ',2017),(209,92,2,1,'2017-05-04 14:06:20','2017-12-31','variety 6',' ',2017),(210,94,2,1,'2017-05-04 14:01:09','2017-12-31','variety 1 \r\nAfter completing the Heckman field at the top we went to the north side and started planting on the north side of the farm toward the east then we ended up having two and a half rounds on the North side to Mark the beginning of our plot.','',2017),(211,95,2,1,'2017-05-01 20:18:11','2017-12-31','variety 4',' ',2017),(212,96,2,1,'2017-05-01 20:18:31','2017-12-31','variety 5',' ',2017),(213,97,2,1,'2017-05-01 20:18:54','2017-12-31','variety 6',' ',2017),(214,98,2,1,'2017-05-01 20:19:33','2017-12-31','variety 7',' ',2017),(215,99,2,1,'2017-05-01 20:20:02','2017-12-31','variety 8',' ',2017),(216,91,2,1,'2017-05-04 14:04:27','2017-12-31','variety 4','',2017),(217,102,2,1,'2017-05-01 20:21:14','2017-12-31','variety 10',' ',2017),(218,103,2,1,'2017-05-04 14:03:01','2017-12-31','Variety 3\r\nVariety started at the curve of the creek.\r\n9 bag and plot seed',' ',2017),(219,91,19,18,'2017-04-25 06:01:01','2017-12-31','START SEVERANCE NORTH SIDE. We planted the bottom and the northwest corner by the modular house for the same variety.\r\n\r\nFirst fill on April 20th','104.86\r\n40.54\r\nTo\r\n104.86071\r\n40.54300',2017),(220,94,12,2,'2017-03-31 20:24:58','2017-12-31','START SEVERANCE NORTH SIDE','104.86\r\n40.54\r\nTo\r\n 104.86\r\n40.54',2017),(221,106,2,1,'2017-05-04 14:02:01','2017-12-31','Variety number 2','',2017),(222,91,7,15,'2017-05-05 06:01:01','2017-12-31','START NORTH SIDE',' ',2017),(223,94,15,9,'2017-04-28 06:01:01','2017-12-31','One bag of seed was planted to finish the field in the pivot field on the southwest corner','',2017),(224,103,19,24,'2017-04-26 06:01:01','2017-12-31','10 bags 1pm 6 bags 3pm, 8 bags 4/27\r\nThis variety of corn is surrounding the pivot tower so there will be DeKalb on both sides.','104.86071\r\n40.54300\r\n To\r\n104.86\r\n40.54',2017),(225,91,12,18,'2017-04-27 06:01:01','2017-12-31','Set the population back to the way it really was to a lower population.','104.86052\r\n40.54057\r\nTo\r\n104.86071\r\n40.54300',2017),(226,94,4,2,'2017-04-04 22:09:00','2017-12-31','START FROM NORTH SIDE','',2017),(227,94,12,1,'2017-04-28 18:03:16','2017-12-31','One bag of seed was planted to finish the field in the pivot field on the southwest corner','',2017),(228,94,1,8,'2017-05-02 12:44:24','2017-12-31','We filled the corn plan with those 6 bags approximately in the middle of that 14 acre field','',2017),(229,103,5,23,'2017-05-05 09:33:54','2017-12-31','Added at pivot tower \r\n8.75 bags dekalb\r\nI am guessing that we put some in a little later closer to the hay shed','',2017),(230,105,2,1,'2017-05-04 14:05:42','2017-12-31',' Variety 5',' ',2017),(231,109,14,14,'2018-04-26 16:09:40','2018-12-31','We were experimenting with this new planter 12-row first year and we had might have a few skip spots just because we didn\'t know what we were doing. We actually planted this over the course of 3 days actually started on the 23rd but we had to get a singular later and he also had to push a pressure valve on our planter to get it to work properly','',2018),(232,109,11,22,'2018-04-26 16:39:48','2018-12-31','We were experimenting with this new planter 12-row first year and we had might have a few skip spots just because we didn\'t know what we were doing. We actually planted this over the course of 3 days actually started on the 23rd but we had to get a singular later and he also had to push a pressure valve on our planter to get it to work properly','',2018),(233,111,19,24,'2018-04-27 12:39:21','2018-12-31','This variety starts just to the south of the wood Builders shed about where the outlet of the pipe comes out for the PVC pipe','40.5 42449 \r\n-104.86 0 5 5 2',2018),(234,110,12,25,'2018-04-28 05:43:51','2018-12-31','','Lat 40.539465 Long -104.869639',2018),(235,109,8,12,'2018-04-28 16:25:05','2018-12-31','','Lat 40.546393 Dekalb',2018),(236,112,1,12,'2018-04-29 16:06:39','2018-12-31','','',2018),(237,115,8,12,'2019-04-25 06:01:01','2019-12-31','Finish up with this variety at sev and mod field','40.546667 End Poiner South',2019),(238,116,15,24,'2019-04-24 06:01:01','2019-12-31','Finish sev08 Include the bottom part of the east circle sevPiv06. Start north side if anything left\r\n\r\nAfter planting fill with DK46-36','Start 40.532501 In Sev08',2019),(239,117,12,36,'2019-04-25 06:01:01','2019-12-31','Try finishing up south side with Dekalb\r\nEdit 12 bags in the morning and added 12 more bags here about 11 a.m. there are two rounds of 9978 here to finish up the field','40.533581 End P9998\r\nStart 40 543768 Dk43-56',2019),(240,118,1,24,'2019-04-26 06:01:01','2019-12-31','Population + 33000 at start. Starting point was near the wear the long roads in the short rows meet with the old cheap grills rat\r\nSwitch population to 35000 at 40.551563','',2019),(241,117,1,12,'2019-04-27 03:26:33','2019-12-31','Try finishing up south side with Dekalb and go to HP','',2019),(242,114,14,8,'2019-04-23 06:01:01','2019-12-31','This corn variety seems to have an extremely good emergency. The plants are an inch tall almost and the other Pioneer 99 AMX T is just coming through the soil right now and they were basically planning the same date\r\n\r\n\r\nFill up with P9998AMXT after planting','40.532419 End',2019),(243,119,19,12,'2020-04-27 16:51:01','2020-12-31','Next to pioneer 9998AMXT plant N to S','-104.867455, 40.543933 33000\r\n\r\n-104.860810, 40.542707 35000',2020),(244,120,15,4,'2020-04-28 10:01:01','2020-12-31','Continued from sevpivSW. Some used to finish pivot field went until 3 rounds from pasture corne.','',2020),(245,120,12,6,'2020-04-04 22:17:14','2020-12-31','South of channel variety','',2020),(246,122,14,12,'2020-04-27 06:01:01','2020-12-31','Planted up to long rows S to N. Skipped 8 rounds for hemp, sweet corn and garden.\r\n\r\nThis variety has good germination','',2020),(247,120,12,26,'2020-04-28 06:01:01','2020-12-31','Kept population 35000. Next to Channel plant N to S started North of pivot tower. DeKalb on both sides of tower. Switch 33000 at the tower','',2020),(248,122,19,12,'2020-04-27 16:01:01','2020-12-31','Moved from sev08. Started along 76.5. Planted east curve with this variety.','',2020),(249,119,5,12,'2020-04-29 06:01:01','2020-12-31','Started by long rows north of pivot tower \r\n\r\n33000','-104.909128, 40.548959',2020),(250,123,1,12,'2020-04-29 14:23:36','2020-12-31','Near pivot tower planting north\r\n\r\nField plot south','-104.909403 , 40.550440',2020),(251,121,8,11,'2020-04-29 06:01:01','2020-12-31','Came from sev06','',2020),(252,121,15,1,'2020-04-28 20:09:55','2020-12-31','Both sides of hemp set aside','',2020),(253,125,9,24,'2021-04-30 10:07:56','2021-12-31','Plant east curve also','',2021),(254,124,9,19,'2021-04-30 16:07:44','2021-12-31','Midway between s road and pivot tower. South of channel','-104.863406\r\n40.540480',2021),(255,124,12,6,'2021-05-01 07:00:46','2021-12-31','Midway between s road and pivot tower. South of channel','-104.863406\r\n40.540480',2021),(256,126,15,7,'2021-05-01 10:51:48','2021-12-31','1st field moved then to 08','-104.862223\r\n40.538332',2021),(257,126,14,17,'2021-05-01 11:54:16','2021-12-31','Finished 08','',2021),(258,124,15,4,'2021-05-18 09:50:25','2021-12-31','beginning of field switch to channel at cord','',2021);
/*!40000 ALTER TABLE `inventory` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `iphistory`
--
DROP TABLE IF EXISTS `iphistory`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `iphistory` (
`historyid` mediumint(9) NOT NULL AUTO_INCREMENT,
`date` date NOT NULL,
`ipaddress` varchar(19) NOT NULL,
`counter` smallint(6) NOT NULL,
`blocking` tinyint(4) NOT NULL,
PRIMARY KEY (`historyid`)
) ENGINE=MyISAM AUTO_INCREMENT=43 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `iphistory`
--
LOCK TABLES `iphistory` WRITE;
/*!40000 ALTER TABLE `iphistory` DISABLE KEYS */;
INSERT INTO `iphistory` VALUES (1,'2009-04-13','208.73.252.147',1,2),(2,'2010-11-01','76.76.65.132',19,0),(3,'2010-01-19','208.68.49.115',2,0),(4,'2010-02-05','209.183.51.44',1,0),(5,'2010-02-08','174.132.127.186',2,0),(6,'2010-03-14','174.132.58.186',2,0),(7,'2010-05-18','174.132.94.170',1,0),(8,'2010-05-19','174.132.94.178',1,0),(9,'2010-05-21','174.132.94.18',1,0),(10,'2010-05-22','174.132.94.10',2,0),(11,'2010-05-24','174.132.35.202',2,0),(12,'2010-06-03','174.132.64.106',3,0),(13,'2010-07-19','174.132.58.250',2,0),(14,'2010-12-10','74.54.240.58',3,0),(15,'2010-07-13','174.132.18.66',1,0),(16,'2010-08-14','174.132.66.114',2,0),(17,'2010-11-07','174.132.97.130',1,0),(18,'2011-06-13','76.76.85.235',8,0),(19,'2010-12-05','71.218.41.209',1,0),(20,'2011-04-14','166.205.8.250',1,0),(21,'2011-04-27','184.99.204.10',2,0),(22,'2011-04-27','166.205.11.144',1,0),(23,'2011-04-28','166.205.9.72',1,0),(24,'2011-04-29','166.205.11.184',2,0),(25,'2011-04-29','166.205.10.194',2,0),(26,'2011-04-30','166.205.9.215',1,0),(27,'2011-05-01','166.205.10.212',1,0),(28,'2011-05-02','166.205.11.5',1,0),(29,'2011-05-03','166.205.8.116',1,0),(30,'2011-05-05','166.205.11.22',1,0),(31,'2011-06-02','166.205.8.110',2,0),(32,'2011-06-04','166.205.11.134',1,0),(33,'2011-06-06','166.205.11.124',1,0),(34,'2011-06-07','166.205.11.227',1,0),(35,'2011-06-08','166.205.10.27',3,0),(36,'2011-11-21','166.205.140.144',1,0),(37,'2011-11-22','166.205.142.68',1,0),(38,'2011-11-28','198.22.122.158',1,0),(39,'2011-11-28','198.22.122.123',1,0),(40,'2011-12-21','75.196.192.9',3,0),(41,'2011-12-24','71.218.40.124',1,0),(42,'2012-04-23','76.76.69.184',1,0);
/*!40000 ALTER TABLE `iphistory` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `map`
--
DROP TABLE IF EXISTS `map`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `map` (
`mapid` mediumint(9) NOT NULL AUTO_INCREMENT,
`farmid` smallint(6) NOT NULL,
`field_name` varchar(30) NOT NULL,
`acres` decimal(5,1) NOT NULL,
`img` varchar(10) NOT NULL,
`diagram` varchar(12) NOT NULL,
`diagramS` varchar(12) NOT NULL,
`archive` tinyint(4) NOT NULL,
`mix` varchar(100) NOT NULL,
`left_column` varchar(255) NOT NULL,
`history` varchar(255) NOT NULL,
`soil_test_year` smallint(6) NOT NULL,
`notes` text NOT NULL,
`budget` mediumint(9) NOT NULL,
`gps` varchar(255) NOT NULL,
`crop` varchar(25) NOT NULL,
`active` tinyint(4) NOT NULL,
PRIMARY KEY (`mapid`),
KEY `field_name` (`field_name`)
) ENGINE=MyISAM AUTO_INCREMENT=23 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `map`
--
LOCK TABLES `map` WRITE;
/*!40000 ALTER TABLE `map` DISABLE KEYS */;
INSERT INTO `map` VALUES (1,2,'hpPivNW',65.0,'1.jpg','1.jpg','1.jpg',0,'n,0,p,70,k,50,s,0,z,0,mn,0,cu,0,bo,0,fe,0,mg,0,gy,0,es,0','2022 fall application \r\nN 0\r\nP 70\r\nK 50\r\n\r\n\r\n
Sprayed Herbicde twice july 5Sprayed Herbicde twice july 5Sprayed Herbicde twice july 5Sprayed Herbicde twice july 5Sprayed Herbicde twice july 5Sprayed Herbicde twice july 5Sprayed Herbicde twice july 5\r\nmimicked the hplake soiltest\r\n\r\n2017\r\nN 100\r\nP 90\r\nK 90\r\nSu 0\r\nMn 6\r\n\r\n2012\r\nN 140\r\nP 30\r\nK 10\r\nSu 10\r\nMn 5\r\n\r\n\r\n2012\r\nN 150\r\nP 60\r\nK 60\r\nSu 10\r\nMn 6\r\nCu 1\r\n\r\n2011\r\nN 50\r\nP 60\r\nK 60\r\nSu 25\r\nMn 4\r\n3/5/2011',0,'Lat: 40 33\' 6.177\r\nLong: -104� 54\' 30.9888\r\n\r\nNorth East Entrance\r\nLat: 40� 33\' 8.7984\r\nLong: -104� 54\' 29.7504\r\n\r\n392 ft for N gated pipe','CORN',1),(5,3,'hpCattle',0.0,'5.jpg','5.jpg','5.jpg',1,'n,150,p,20,k,20,s,0,z,0,mn,6,cu,0.5,bo,0.5,fe,0,mg,0,gy,0,es,0','Do the three locations on the home place','Planted alfalfa 4/10/2010\r\n\r\nField had lots of rain when it started. In fact we were wondering if some of the seed may have washed away. Spring will tell of the stand',2017,'
FERTILIZER DATA HERE\r\n\r\n\r\n\r\n2024 spring Application\r\nN 75\r\nP 70\r\nK 60\r\nMn 0\r\n\r\n2022 Fall Application\r\nN 0\r\nP 70\r\nK 50\r\nMn 0\r\n\r\n
Spread Follow pivot tracks\r\n\r\n2020\r\nN 0\r\nP 60\r\nK 60\r\nMn 0\r\n\r\n11/1/20 fall application \r\n\r\n2017\r\nN 130\r\nP 30\r\nK 10\r\nMn 5\r\n\r\n2016\r\nN 175\r\nP 30\r\nK 20\r\nMn 6\r\n\r\n2015\r\nN 170\r\nP 20\r\nK 20\r\nMn 6\r\n\r\n2014\r\nN 160\r\nP 20\r\nK 20\r\nMn 6\r\n\r\n2/24/2012\r\nN P2O5 K2O Mg S Zn Mn Fe Cu B\r\n225 -- -- -- -- -- 6.1 -- 0.9 --\r\n\r\n\r\n2013\r\nN 140\r\nP 20\r\nK 30\r\nMn 4\r\n\r\n2012\r\nN 170\r\nP 20\r\nK 15\r\nMn 6\r\nCu 1\r\n2011\r\nN 145\r\nP 25\r\nMn 5\r\n3/4/11\r\n\r\n2010\r\nN 125\r\nP 40\r\nK 0\r\nMn 5',2542,'1108 ft x 1309 \r\n\r\nSW: -104.915636, 40.546220\r\nNW: 40.54888 , -104.915636\r\nNE: 40.54888, -104.91344\r\nSE: 40.546220, -104.91344','CORN',1),(8,2,'hpSheep',35.5,'8.jpg','8.jpg','8.jpg',0,'n,190,p,20,k,20,s,0,z,0,mn,0,cu,0,bo,0,fe,0,mg,0,gy,0,es,0','2024\r\nN 190\r\nP 20\r\nK 20\r\nS 10\r\nMn 0\r\nCU 0\r\nBO 0.0\r\n\r\nSPREAD EAST & WEST up to alfalfa field','2017\r\narea 1300 ft x 1500 ft - 434ft x 660 ft (yard)\r\nHPHCC on soil test. sweet corn 2011\r\n\r\nExpanded 2007',2023,'
\r\n4/24/19\r\n\r\n2018\r\nN 130\r\nP 10\r\nK 0\r\nMn 6\r\n\r\n4/14/18 WINDY2024\r\nN 190\r\nP 20\r\nK 20\r\nS 10\r\nMn 0\r\nCU 0\r\nBO 0.0\r\n\r\nSPREAD EAST & WEST up to alfalfa field
Merged 2025-01-01
2024\r\nN 190\r\nP 20\r\nK 20\r\nS 10\r\nMn 0\r\nCU 0\r\nBO 0.0\r\n\r\nSPREAD EAST & WEST up to alfalfa field
Merged 2024-10-26
2024\r\nN 190\r\nP 20\r\nK 20\r\nS 10\r\nMn 0\r\nCU 0\r\nBO 0.0\r\n\r\nSPREAD EAST & WEST up to alfalfa field
Merged 2024-10-25
2023\r\nN 170\r\nP 30\r\nK 30\r\nMn 0\r\nCU 1\r\nBO 0.0\r\n\r\nSPREAD EAST & WEST up to alfalfa field
Merged 2024-02-10
2022\r\nN 170\r\nP 20\r\nK 20\r\nMn 0\r\nCU 1\r\nBO 0.0\r\n\r\nSPREAD EAST & WEST up to alfalfa field
\r\n4/24/19\r\n\r\n2018\r\nN 150\r\nP 60\r\nK 40\r\nMn 6\r\nZn 2\r\nuse plowed field to make east border\r\n\r\n2024\r\nN 200\r\nP 30\r\nK 25\r\nS 10\r\nMn 0\r\nCU 0\r\nBO 0\r\n\r\n
Run spreader truck East & West
Merged 2025-01-01
use plowed field to make east border\r\n\r\n2024\r\nN 200\r\nP 30\r\nK 25\r\nS 10\r\nMn 0\r\nCU 0\r\nBO 0\r\n\r\n
Run spreader truck East & West
Merged 2024-10-26
use plowed field to make east border\r\n\r\n2024\r\nN 200\r\nP 30\r\nK 25\r\nS 10\r\nMn 0\r\nCU 0\r\nBO 0\r\n\r\n
Run spreader truck East & West
Merged 2024-10-25
use plowed field to make east border\r\n\r\n2023\r\nN 175\r\nP 25\r\nK 25\r\nMn 0\r\nCU 0\r\nBO 0\r\n\r\n
Run spreader truck East & West
Merged 2024-02-10
Do SevE06 first to make border\r\n\r\n2022\r\nN 175\r\nP 20\r\nK 20\r\nMn 0\r\nCU 0\r\nBO 0\r\n\r\n
\r\n\r\nThere is only one field on Severance','This quarter 37 acres\r\n\r\n2016\r\nleach line cause the bottom field to be absorbed as part of this half floor spreading fertilizer. 75 acres in this section.\r\n\r\nSW corner of pivot\r\ngas line laid summer 2012 south end',2020,'
\r\n\r\nThere is only one field on Severance\r\nStart spreading dead furrow first.\r\n\r\nRemaining corn field from dead furrow north, cement ditch west, to fence line east and waste ditch south. \r\n\r\n2018\r\nN 155\r\nP 100\r\nK 90\r\nMn 6\r\nzinc 4\r\n2/14/17
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2025-01-01
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2024-10-26
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2024-10-25
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2024-02-10
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2022-11-09
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2021-02-23
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance2019-01-12 17:13:28\r\n\r\nStart spreading dead furrow first.\r\n\r\nRemaining corn field from dead furrow north, cement ditch west, to fence line east and waste ditch south. \r\n\r\n2018\r\nN 155\r\nP 100\r\nK 90\r\nMn 6\r\nzinc 4\r\n2/14/172019-01-12 17:08:39
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2025-01-01
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2024-10-26
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2024-10-25
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2024-02-10
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2022-11-09
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
Merged 2021-02-23
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance
SOIL TEST SOUTH OF PIVOT TOWER
\r\n\r\nThere is only one field on Severance\r\n\r\n38 ACRE3 in corner\r\nsave 68 acres\r\n-\r\n\r\n2017\r\nN 155\r\nP 35\r\nK 10\r\nMn 6\r\n2/14/17\r\n\r\n2016\r\nN 175\r\nP 35\r\nK 10\r\nMn 6\r\n\r\nacres area - 35\r\n\r\n2015\r\nN 150\r\nP 35\r\nK 10\r\nMn 5\r\n\r\nApply both 9 & 10 total 70 acres\r\n\r\n2014\r\nN 160\r\nP 25\r\nK 10\r\nMn 5\r\nTue 3/18/2014 7:38 AM\r\n\r\n2013\r\nN 140\r\nP 20\r\nK 20\r\nMn 4\r\n\r\n2012\r\nN 150\r\nP 30\r\nK 30\r\nMn 5\r\n\r\n2011\r\nN 140\r\nP 30\r\nK 0\r\nMn 5\r\n4/25/11\r\n\r\n2010\r\nN 125\r\nP 50\r\nK 0\r\nMn 5',0,'','CORN',0),(13,1,'sev07',35.0,'13.jpg','13.png','13.jpg',0,'n,210,p,20,k,20,s,10,z,0,mn,0,cu,0,bo,0,fe,0,mg,0,gy,0,es,0','2024 spring application\r\nN 210\r\nP 20\r\nK 20\r\nS 10\r\nMn 0\r\n\r\n
Run Spreader truck East and west
','alfalfa hope start 2016\r\nOriginal field record before split',2024,'
\r\n|`N `P2O5 `K2O `Mg `S `Zn `Mn `Fe `Cu `B `code \r\n|`285`0 `00 `-- `--- `-- `--- `-- `--- `--- `250 bu 11/21/23\r\n|`230`30 `30 `-- `16 `-- `7.1 `-- `1.2 `0.6 `sev7 north oct 7, 2021\r\n|`240`30 `30 `-- `17 `-- `7.1 `-- `1.2 `0.6 `sev7 South oct 7, 2021\r\n
\r\n\r\n2024 spring application\r\nN 210\r\nP 20\r\nK 20\r\nS 10\r\nMn 0\r\n\r\n
Run Spreader truck East and west
Merged 2025-01-01
plowed up to west. N in as S in 10/30\r\n\r\n2024 spring application\r\nN 210\r\nP 20\r\nK 20\r\nS 10\r\nMn 0\r\n\r\n
Run Spreader truck East and west
Merged 2024-10-26
2024 spring application\r\nN 210\r\nP 20\r\nK 20\r\nS 10\r\nMn 0\r\n\r\n
Run Spreader truck East and west
Merged 2024-10-25
2023 spring application\r\nN 150\r\n\r\n
Run Spreader truck East and west
Merged 2024-02-10
\r\n2022 fall application\r\nN 50\r\nP 60\r\nK 50\r\nS 10\r\nMn 0\r\n\r\n2020 late\r\nN 0\r\nP 60\r\nK 60\r\nMn 0\r\n11/1/20 fall application \r\n\r\nAPPLY NORTH OF PIT CROSSING. Start application on north end of field. \r\n\r\n2016\r\nP 50\r\nK 30\r\n\r\napply 2/29/16\r\n\r\n2015\r\nN 160\r\nP 60\r\nK 30\r\nMn 6\r\n\r\n\r\n2014\r\nN 170\r\nP 90\r\nK 30\r\nMn 6\r\n\r\n2013\r\nN 140\r\nP 20\r\nK 20\r\nMn 4\r\n\r\n2012\r\nN 150\r\nP 40\r\nK 20\r\nMn 6\r\n\r\n2011\r\nN 150\r\nP 30\r\nK 0\r\nMn 5\r\n4/25/11\r\n\r\n2010\r\nN 125\r\nP 40\r\nK 0\r\nMn 3.5',0,'','CORN',1),(14,1,'sev08',20.6,'14.jpg','14.png','14.jpg',0,'n,180,p,20,k,20,s,0,z,0,mn,0,cu,0,bo,0,fe,0,mg,0,gy,0,es,0','2024\r\nN 180\r\nP 20\r\nK 20\r\nS 0\r\nMn 0\r\nCU 0.0\r\nBO 0.0\r\n\r\n
\r\nxx2019-01-12 17:13:28\r\n\r\ncement ditch start 40.533960, -104.862163 & end 40.530666, -104.859985 1338 feet estimate google maps\r\n\r\nsold 1.3 acres to moody reducing acrage from 32 to 30.67\r\ntriangle piece on east end is approximately 7 acres \r\ncalculate triangle piece\r\n597.8076919755667feet 1187.7813330167849feet=355212ft2\r\n\r\npoint in settlers landind\r\n297.74970069309023feet 159.27893609057872feet=47680ft2\r\n\r\n2011 start alfalfa\r\n\r\nFERTILIZER MIX CALCULATED\r\nProduct LBS/ACRE POUNDS\r\n0-0-60 134 1 $0.22\r\n11-52-0 154 1 $0.28\r\nCopper 3 1 $3.10\r\nManganese Sulfate 22 1 $1.20\r\nZinc 360 2 1 $0.62\r\n46-0-0 116 1 $0.20\r\n\r\nESTIMATED COST LESS APPLICATION\r\nacres=\r\nCost per Acre Total Cost\r\n$ 127.56 $ 0\r\nMY VARIABLES\r\nNitrogen=70\r\nPhosphorous=80\r\nPotash=80\r\nSulfate=0\r\nZinc=.5 Manganese=7\r\nCopper=.5\r\nBoron=0\r\nIron=0\r\nMagnesium=0\r\nGypsum=0\r\nElemental Sulphur=0',0,'Cone road 40.53432, 104.86190','CORN',1),(15,1,'SevE06',23.0,'15.jpg','15.png','15.jpg',0,'n,200,p,30,k,30,s,0,z,0,mn,0,cu,0,bo,0,fe,0,mg,0,gy,0,es,0','
no till field east border. Run truck at you discretion.
\r\nEast of pivot circle \r\n23 acres\r\n2024\r\nN 200\r\nP 30\r\nK 30\r\nS 5\r\nMn 0\r\nCU 0.0\r\nBO 0.0\r\n\r\n
start by plowed ground, drive towards wood shed. Spread to the east
','2023 19.6 acres corn. 22 acres for rectangle measurement\r\n2014 West of Pivot circle, field size 25 acres\r\n1st corn 2012\r\n2013 No plant',2024,'Actual crop acres 22\r\n
\r\n\r\n=====================FERTILIZER========================\r\napply last\r\n\r\n2022 Fall application on Alfalfa\r\nN 0\r\nP 70\r\nK 50\r\n\r\n\r\n
Run spreader truck between pivot tracks
Merged 2025-01-01
apply last\r\n\r\n2022 Fall application on Alfalfa\r\nN 0\r\nP 70\r\nK 50\r\n\r\n\r\n
Run spreader truck between pivot tracks
Merged 2024-10-26
apply last\r\n\r\n2022 Fall application on Alfalfa\r\nN 0\r\nP 70\r\nK 50\r\n\r\n\r\n
Run spreader truck between pivot tracks
Merged 2024-10-25
apply last\r\n\r\n2022 Fall application on Alfalfa\r\nN 0\r\nP 70\r\nK 50\r\n\r\n\r\n
start north end and spread south. Stay out of SE corner swamp land
Merged 2025-01-01
2024\r\nN 210\r\nP 40\r\nK 30\r\nMn 0\r\n\r\n
start north end and spread south. Stay out of SE corner swamp land
Merged 2024-10-26
2024\r\nN 210\r\nP 40\r\nK 30\r\nMn 0\r\n\r\n
start north end and spread south. Stay out of SE corner swamp land
Merged 2024-10-25
\r\nsubsoiled fall 2023\r\n2023\r\nN 200\r\nP 70\r\nK 70\r\nMn 0\r\n\r\n
start north end and spread south. Stay out of SE corner swamp land
\r\n2022\r\nN 200\r\nP 70\r\nK 70\r\nMn 0\r\n\r\n
start north end and spread south. Stay out of SE corner swamp land
',0,'SE LatLong(40.538148, -104.908190)\r\nwest LatLong(40.540627, -104.911366)\r\nNE LatLong(40.543872, -104.908147);\"','CORN',1);
/*!40000 ALTER TABLE `map` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `products`
--
DROP TABLE IF EXISTS `products`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `products` (
`productid` smallint(6) NOT NULL AUTO_INCREMENT,
`categoryid` tinyint(4) NOT NULL,
`product` varchar(50) NOT NULL,
`manufactured` varchar(25) NOT NULL,
`technology` varchar(200) NOT NULL,
`notes` text NOT NULL,
`number_bags` smallint(6) NOT NULL,
`price` decimal(10,2) NOT NULL,
`year` smallint(6) NOT NULL,
`code` varchar(1) NOT NULL,
`archive` tinyint(6) NOT NULL,
`weightCount` mediumint(9) NOT NULL,
`applied_rate` mediumint(9) NOT NULL,
`img` varchar(9) NOT NULL,
PRIMARY KEY (`productid`)
) ENGINE=MyISAM AUTO_INCREMENT=129 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `products`
--
LOCK TABLES `products` WRITE;
/*!40000 ALTER TABLE `products` DISABLE KEYS */;
INSERT INTO `products` VALUES (1,0,'38H72','Pioneer','Liberty Link, Roundup Ready 2, Herculex xtra, CruisereXTREME 250','RM: 100\r\nSize: F14\r\nGerm: 95%\r\nOrigin:IA\r\nLot No: N3ALG11011-N1\r\n\r\n2010\r\n LOT:N3ALG11011-N1\r\nSEED: PDR ALG1\r\n16 bags (1 returned)',12,0.00,2011,'C',1,80000,32000,'1.jpg'),(2,0,'DKC52-59','Dekalb','YieldGuard VT Triple, Roundup Ready 2, Poncho 250','RM 102 LOT:757CDV9NX\r\nSEED: AF2',26,0.00,2011,'C',1,80000,32000,'2.jpg'),(3,0,'DKC52-62','Dekalb','Roundup Ready 2, Poncho 1250','RM 102 lot:746D3F4NX\r\nSEED AF2 (1 returned)',0,0.00,2011,'C',1,80000,32000,'3.jpg'),(4,0,'DKC45-79','Dekalb','YieldGuard VT Triple, Roundup Ready 2, Poncho 250','this variety appears to have a good stand\r\nfor early corn it does not dry fast\r\n\r\nRM 95 LOT:754PMT4NX\r\nSEED: P22 (1 returned)',10,0.00,2011,'C',1,80000,32000,'4.jpg'),(5,0,'37K11','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250','best vigor and height\r\n\r\nRM 99\r\n2011\r\nSize: F14\r\nGerm: 95%\r\nOrigin:IA\r\nLot No: M3DYS11013-N\r\n\r\n\r\n2010 \r\nLOT:P3PLY11056-00\r\nSEED: PDF PLY1\r\n16 bags (4 Returned)',18,0.00,2011,'C',1,80000,32000,'5.jpg'),(6,0,'38H08','Pioneer','Liberty Link, Roundup Ready 2, Herculex xtra, Cruiser Mid Rate','RM 92 LOT:P3DYS11027-00\r\nSEED: PDR DON1\r\n16 bags (5 returned)',0,0.00,2011,'C',1,80000,32000,'6.jpg'),(7,0,'DKC50-44','Dekalb','Roundup Ready 2, Poncho 1250','this variety stands poor in two fields. Does not like alkily but still yields good.\r\nMaximum yielder 260 bu in hpswest where stand is good.\r\n\r\nRM 100 LOT:757NED1NX\r\nSEED: AR2 (1 returned)',0,0.00,2011,'C',1,80000,32000,'7.jpg'),(8,0,'DKC50-47','Dekalb','Roundup Ready 2, Poncho 250','SEED SIZE: AR2\r\nMATURITY: 100\r\nMID-POLLINATION: 1265\r\nBLACK LAYER: 2530\r\nLOT NO: 253EAV4JX\r\nVARIETY: 79714221\r\nORIGIN: IL',8,0.00,2011,'C',1,80000,32000,'8.jpg'),(9,0,'54V09 Alfalfa','Pioneer','','Lot: P14NWPF13\r\nBATCH: P14NWPF13',8,0.00,2011,'A',1,50,12,'9.jpg'),(10,0,'P0125WB','Pioneer','Liberty Link, Roundup Ready 2 , Herculex xtra, Cruiser Mid Rate, PONCHO 1250, RAXIL HEAD SMUT','LOT:N3DON11023- N1 SEED: PDF REZ1\r\n RM 101\r\nCONTAINS 90% P0125XR & 10% P0125HR\r\n9 bags (0 returned)',0,0.00,2011,'C',1,80000,32000,'10.jpg'),(11,0,'P0125R','Pioneer','Roundup Ready 2, PONCHO 1250, RAXIL HEAD SMUT','RM 101 LOT:N3PRI11078- N1 SEED: PDR ALG1',0,0.00,2011,'C',1,80000,32000,'11.jpg'),(12,0,'P9252HR','Pioneer','Liberty Link, Roundup Ready 2 , Herculex I, PONCHO 1250 , RAXIL HEAD SMUT','2012 225.2@13.7 \r\n\r\n2011\r\nLOT:M1PNE11153-00 \r\nSEED: F14 YOR1\r\nRM 92',0,0.00,2012,'C',1,80000,32000,'12.jpg'),(13,0,'Pioneer P8917XR','Pioneer','','Delete PIONEER P0125 WB Liberty Link, Roundup Ready 2 , Herculex xtra, Cruiser Mid Rate, PONCHO 1250 , RAXIL HEAD SMUT LOT:N3 DON 11023- N1 SEED: PDF REZ1 RM 101 CONTAINS 90 % P0125 XR & 10 % ',0,0.00,2011,'C',1,80000,32000,'13.jpg'),(14,0,'P9512XR','Pioneer','Liberty Link, Roundup Ready 2, Herculex xtra, CruiserEXTREME 250','PAT PLOT\r\n\r\nLOT:N3DYS11014-00\r\nSEED: PDF\r\nRM 95\r\nORIGIN: IA',1,0.00,2011,'C',1,40000,32000,'14.jpg'),(15,0,'Sweet Corn','Burpee','None','Full bag of gotta have it.',0,500.00,2011,'C',1,80000,32000,'15.jpg'),(20,0,'P9512R','Pioneer','Roundup Ready 2, Poncho 1250','RM: 95\r\nSize: PDR\r\nGerm: 95%\r\nOrigin:IA\r\nLot No: N3ALG11025-N1',12,0.00,2011,'C',1,80000,32000,'20.jpg'),(21,0,'P0231HR','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250','RM 99\r\n2011\r\nHY3RID:P:23:H.11 Kind: Field Corn\r\nSIZE: FI4 Wa- 1 ECT NO: M3PRI11043—N\r\nGERM: 93% t..5 5.D: DEC 010\r\nORIGIN:IL KERNELS/UNIT:80,000\r\nFERTILE CYTOPLASM\r\nPass tobbosscel proy,ded under restecr,u condf ions. See bag/tag/invoice for',1,0.00,2011,'C',1,80000,32000,'21.jpg'),(22,0,'monida oats','sharp seed','Spring\r\ncertified lot: W55-088-2955C\r\nConditioner: 10','',10,0.00,2011,'A',1,50,25,'22.jpg'),(23,0,'P9519HR','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250','RM 99\r\n2011\r\nNv02 pdf 80k hi ist v $261.90\r\n\r\n2010 \r\nLOT:P3PLY11056-00\r\nSEED: PDF PLY1\r\n16 bags (4 Returned)',1,0.00,2011,'C',1,80000,32000,'23.jpg'),(24,0,'P0181XR','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250, RALIX HEAD SMUT','RM: 101\r\nSize: F14\r\nGerm: 95%\r\nOrigin: OR\r\nLot No: M3HES11372-P5',1,0.00,2011,'C',1,80000,32000,'24.jpg'),(25,0,'DKC52-43','Dekalb','YIELDGUARD VT TRIPLE\r\nROUNDUP READY 2','SEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1285\r\nBLACK LAYER: 2550\r\nLOT NO: 7554LLL3JG\r\nVARIETY: B0000948\r\nORIGIN: IA',10,0.00,2011,'C',1,80000,32000,'25.jpg'),(26,0,'P9519HR','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250, RAXIL HEAD SMUT','207.1@13.9\r\n\r\nRM: 95\r\n\r\n2012 SAMPLE\r\nSize: R23 LOT NO: L3CON11068-0\r\nGERM: 95% TESTED: MAR 2012\r\nORIGIN: MI \r\n\r\n2011\r\nSize: PDR\r\nGerm: 95%\r\nOrigin: WA\r\nLot No: M3CNN11031-P5',0,0.00,2012,'C',1,80000,32000,'26.jpg'),(27,0,'P9714XR','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250','PAT PLOT\r\n\r\nRM 99\r\n2011\r\nNv02 pdf 80k hi ist v $261.90\r\n\r\n2010 \r\nLOT:P3PLY11056-00\r\nSEED: PDF PLY1\r\n16 bags (4 Returned)',1,0.00,2011,'C',1,40000,32000,'27.jpg'),(28,0,'P9252HR','Pioneer','PAT PLOT\r\n\r\nLiberty Link, Roundup Ready 2, Herculex xtra, Cruiser Mid Rate','LOT:N3DYS11014-00\r\nSEED: PDR MTP1\r\nRM 95',1,0.00,2011,'C',1,40000,32000,'28.jpg'),(29,0,'3212X','triump','CRUISER\r\nExtreme250\r\n900-015980/00336095\r\nn\\\', t) \\\" A _\r\nBox 1050 - Rails. TX 79357\r\nSTATE PERMITS—TX 13032, —MO W70481. —OK 7497. —AR R609\r\n\r\nBrand: 3212X\r\nWARNING: SEED TREATED WITH\r\nCI NO: C.I.\r\nM','GRADE SZ: F1 LOT: 06FY0J-C2\r\nKERNELS: 80,000 GERM: 95%\r\nSEEDS/LB: 2,041 DATE TESTED: Mar-11\r\nPLATE: B17 ORIGIN: NE\r\nPURE SEED: 99.50% OTHER CROP SEED: 0.00%\r\nINERT: 0.50% WEED SEED: 0.00%\r\nNOXIOUS WEED SEED: NONE',1,0.00,2011,'C',1,80000,32000,'29.jpg'),(30,0,'9502S','triumph','','GRADE SZ: F2 LOT: 50FGOD-A\r\nKERNELS: 80,000 GERM: 95%\r\nSEEDS/LB: 1,572 DATE TESTED: Feb-11\r\nPLATE: 87 ORIGIN: IL\r\nPURE SEED: 99.50% OTHER CROP SEED 0.00%\r\nINERT: 0.50% WED SEED: 0.00%\r\nNOXIOUS WEED SEED: NONE',1,0.00,2011,'C',1,80000,32000,'30.jpg'),(31,0,'9502S','Triumph','SMARTSTAX, Roundup 2, LIBERTY LINK','2012\r\nGRADE SZ: F2 LOT: 50FYOD1-C2\r\nKERNELS: 80,000 GERM: 95%\r\nSEEDS/LB: 1,572 DATE TESTED: DEC-11\r\nPLATE: B7-C7 ORIGIN: NE\r\nPURE SEED: 99.50% OTHER CROP SEED 0.00%\r\nINERT: 0.50% WED SEED: 0.00%\r\nNOXIOUS WEED SEED: NONE\r\nPrice up from 205 to 209\r\n\r\n2011\r\nGRADE SZ: F2 LOT: 50FGOD-A\r\nKERNELS: 80,000 GERM: 95%\r\nSEEDS/LB: 1,572 DATE TESTED: Feb-11\r\nPLATE: 87 ORIGIN: IL\r\nPURE SEED: 99.50% OTHER CROP SEED 0.00%\r\nINERT: 0.50% WED SEED: 0.00%\r\nNOXIOUS WEED SEED: NONE',0,209.00,2012,'C',1,80000,32000,'31.jpg'),(32,0,'3212S','Triumph','SMARTSTAX, ROUNDUP READY 2, LIBERTY LINK','233 bu @ 15.8%\r\n\r\n2012\r\nGRADE SZ: R1 LOT: 06RY1K-A2\r\nKERNELS: 80,000 GERM: 92%\r\nSEEDS/LB: 1697 DATE TESTED: DEC-11\r\nPLATE: B2 - C2X ORIGIN: NE\r\nPURE SEED: 99.0% OTHER CROP SEED: 0.02%\r\nINERT: 0.98% WEED SEED: 0.00%\r\nNOXIOUS WEED SEED: NONE\r\n\r\n2011\r\nGRADE SZ: F1 LOT: 06FY0J-C2\r\nKERNELS: 80,000 GERM: 95%\r\nSEEDS/LB: 2,041 DATE TESTED: Mar-11\r\nPLATE: B17 ORIGIN: NE\r\nPURE SEED: 99.50% OTHER CROP SEED: 0.00%\r\nINERT: 0.50% WEED SEED: 0.00%\r\nNOXIOUS WEED SEED: NONE\r\n$205',0,209.00,2012,'C',1,80000,32000,'32.jpg'),(33,0,'DKC52-59','Dekalb','YieldGuard VT Triple, Roundup Ready 2, Poncho 250','230.8@14.9%\r\nRM 102\r\n2012\r\nreceived 30 units and returned 14 bags\r\nLOT: 757W4R4JX\r\nVARIETY: 4688380 \r\nSEED SIZE: AR2 and AR\r\nMATURITY: 102\r\nMID-POLLINATION: 1280\r\nBLACK LAYER: 2540\r\n\r\n2011 $229.00\r\nLOT NO: 253EAV4JX\r\nVARIETY: 79714221\r\nORIGIN: IL\r\n2011\r\n LOT:757CDV9NX\r\nSEED: AF2',0,301.00,2012,'C',0,80000,32000,'33.jpg'),(34,0,'P37K11','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250','best vigor and height\r\n196.6@14.3%\r\n\r\n2013\r\nNV02 PDF 80K HI IST V\r\n\r\nRM 99\r\n2012\r\nSize: R23 YOR1\r\nGerm: 95%\r\nOrigin:IA\r\nLot No: M3DYS11013-N\r\n\r\n2011\r\nSize: F14\r\nGerm: 95%\r\nOrigin:IA\r\nLot No: M3DYS11013-N\r\n\r\n\r\n2010 \r\nLOT:P3PLY11056-00\r\nSEED: PDF PLY1\r\n16 bags (4 Returned)',12,264.03,2013,'C',0,80000,32000,'34.jpg'),(35,0,'P9252HR','Pioneer','Liberty Link, Roundup Ready 2 , Herculex I, PONCHO 1250 , RAXIL HEAD SMUT','2012\r\n\r\n2011\r\nLOT:M1PNE11153-00 \r\nSEED: F14 YOR1\r\nRM 92',0,235.00,2012,'C',1,80000,32000,'35.jpg'),(36,0,'DKC50-47','Dekalb','Roundup Ready 2, Poncho 250','poorest drying good yield\r\n\r\n242.8@15.8\r\n2012\r\nSEED SIZE: AR2\r\nMATURITY: 100\r\nMID-POLLINATION: 1265\r\nBLACK LAYER: 2530\r\nLOT NO: 766 W R R7 JX\r\nVARIETY: 7971421\r\nORIGIN: IL\r\n\r\n2011\r\nSEED SIZE: AR2\r\nMATURITY: 100\r\nMID-POLLINATION: 1265\r\nBLACK LAYER: 2530\r\nLOT NO: 253EAV4JX\r\nVARIETY: 79714221\r\nORIGIN: IL',0,215.00,2012,'C',1,80000,32000,'36.jpg'),(37,0,'P0231HR','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250','Triumph better 214@15.3%\r\n\r\n2013\r\nNS07 MF 80 M IST RA\r\n\r\nRM 99\r\nTop yielder in 2011 plot\r\n\r\n2011\r\nHY3RID:P:23:H.11 Kind: Field Corn\r\nSIZE: FI4 Wa- 1 ECT NO: M3PRI11043—N\r\nGERM: 93% t..5 5.D: DEC 010\r\nORIGIN:IL KERNELS/UNIT:80,000\r\nFERTILE CYTOPLASM\r\nPass tobbosscel proy,ded under restecr,u condf ions. See bag/tag/invoice for',6,275.91,2013,'C',0,80000,32000,'37.jpg'),(38,0,'DKC45-79','Dekalb','YieldGuard VT Triple, Roundup Ready 2, Poncho 250','this variety appears to have a good stand\r\nfor early corn it does not dry fast\r\n2012\r\nSize AR and AR2\r\n\r\nRM 95\r\n2011 $215.00\r\nLOT:754PMT4NX\r\nSEED: P22 (1 returned)',0,257.00,2012,'C',1,80000,32000,'38.jpg'),(39,0,'DKC52-43','Dekalb','YIELDGUARD VT TRIPLE\r\nROUNDUP READY 2','Fastest drying corn \r\n237.8@14.1\r\n2011\r\n\r\n2012\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1285\r\nBLACK LAYER: 2550\r\nLOT NO: 757KL97JX\r\nVARIETY: B0000948\r\nORIGIN: IA\r\nTREATMENT: WAIH1\r\n\r\n2011\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1285\r\nBLACK LAYER: 2550\r\nLOT NO: 7554LLL3JG\r\nVARIETY: B0000948\r\nORIGIN: IA',18,235.00,2013,'C',0,80000,32000,'39.jpg'),(40,0,'Counter','Amarican Cyanimid','death',' ',0,80.00,2013,'I',0,45,5,'40.jpg'),(41,0,'P0181HR','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250, RALIX HEAD SMUT\r\ndo not plant in alkali the triumph does much better.','241.7@15.5\r\n\r\n2013\r\nNW04 MR 80 H IST V RA\r\n\r\nRM: 101\r\nSize: F14\r\nGerm: 95%\r\nOrigin: OR\r\nLot No: M3HES11372-P5',12,267.69,2013,'C',0,80000,32000,'41.jpg'),(42,0,'P8640HR','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250','Poor yield but very dry\r\n\r\nRM: 101\r\nSize: PDF\r\nGerm: 95%\r\nOrigin: OR\r\nLot No:',0,0.00,2012,'C',1,80000,32000,'42.jpg'),(43,0,'P9252R','Pioneer','PAT PLOT\r\n\r\nRoundup Ready 2, RAXIL, PONCHO 1250','poor at severance.\r\n\r\nRM 92\r\nLOT: L3REI11027-N TESTED: MAR 2012\r\nSEED: PDF \r\nGERM: 95%\r\nORIGIN: IA',0,0.00,2012,'C',1,40000,32000,'43.jpg'),(44,0,'P9690HR','Pioneer','PAT PLOT\r\n\r\nLiberty Link, Roundup Ready 2, Herculex xtra, Cruiser Mid Rate','2012: 223.8@14.8\r\n\r\nLOT:\r\nSEED: MF\r\nRM',0,0.00,2012,'C',1,80000,32000,'44.jpg'),(45,0,'P9714AM1','Pioneer','Liberty Link, Roundup Ready 2, AM1, PONCHO 1250','PAT PLOT 2012: 205.9@ 14.5',0,0.00,2012,'C',1,80000,32000,'45.jpg'),(46,0,'DKC46-20','Dekalb','YieldGuard VT Triple, Roundup Ready 2, Poncho 250','this variety appears to have a good stand\r\nfor early corn it does not dry fast\r\n2012\r\nSize AR and AR2\r\n\r\nRM 95\r\n2011 $215.00\r\nLOT:754PMT4NX\r\nSEED: P22 (1 returned)',18,257.00,2013,'C',0,80000,32000,'46.jpg'),(47,0,'P9305YHR','Pioneer','YGCB/HX1/LL/RR2','NW02 PDF 80 H IST V R',1,310.90,2013,'C',0,80000,32000,'47.jpg'),(48,0,'P9675AMX','Pioneer','AMX/LL/RR2','NM07 MF 80K MD IST',1,307.00,2013,'C',0,80000,32000,'48.jpg'),(49,0,'P9690AM','Pioneer','AM/LL/RR2/A Q','NW02 PDF 80 H IST V R',1,320.90,2013,'C',0,80000,32000,'49.jpg'),(50,0,'P9973YXR','Pioneer','YGCB/HXX/LL/RR2','NW02 PDF 80 H IST V\r\nR',1,342.90,2013,'C',0,80000,32000,'50.jpg'),(51,0,'T3212RA','Triumph','SMARTSTAX, ROUNDUP READY 2, LIBERTY LINK','',12,230.00,2013,'C',0,80000,32000,'51.jpg'),(52,0,'T9669RA','Triumph','SMARTSTAX, Roundup 2, LIBERTY LINK','does dry down good but is not as fast as the DK 52 dash 43',3,230.00,2013,'C',0,80000,32000,'52.jpg'),(53,0,'T9811S','Triumph','SMARTSTAX, Roundup 2, LIBERTY LINK',' ',6,220.00,2013,'C',0,80000,32000,'53.jpg'),(54,0,'T9946RA','Triumph','SMARTSTAX, Roundup 2, LIBERTY LINK',' ',3,230.00,2013,'C',0,80000,32000,'54.jpg'),(55,0,'Willow Wheat','Sharp Brothers','Nobe',' ',15,40.00,2014,'W',1,0,70,'55.jpg'),(56,0,'DKC52-59','Dekalb','YIELDGUARD VT TRIPLE\r\nROUNDUP READY 2','Fastest drying corn \r\n237.8@14.1\r\n2011\r\n\r\n2012\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1285\r\nBLACK LAYER: 2550\r\nLOT NO: 757KL97JX\r\nVARIETY: B0000948\r\nORIGIN: IA\r\nTREATMENT: WAIH1\r\n\r\n2011\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1285\r\nBLACK LAYER: 2550\r\nLOT NO: 7554LLL3JG\r\nVARIETY: B0000948\r\nORIGIN: IA',23,315.00,2014,'C',0,80000,32000,'56.jpg'),(57,0,'P0231HR','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250','2013\r\nNS07 MF 80 M IST RA\r\n\r\nRM 99\r\nTop yielder in 2011 plot\r\n\r\n2011\r\nHY3RID:P:23:H.11 Kind: Field Corn\r\nSIZE: FI4 Wa- 1 ECT NO: M3PRI11043—N\r\nGERM: 93% t..5 5.D: DEC 010\r\nORIGIN:IL KERNELS/UNIT:80,000\r\nFERTILE CYTOPLASM\r\nPass tobbosscel proy,ded under restecr,u condf ions. See bag/tag/invoice for',12,275.91,2014,'C',0,80000,32000,'57.jpg'),(58,0,'T3212RA','Triumph','SMARTSTAX, ROUNDUP READY 2, LIBERTY LINK\r\n50FM2P3-C2','Steve,\r\n\r\nHere is the following corn order as we discussed yesterday.\r\n\r\n20 bags of 3212RA - $225/bag\r\n12 bags of 9669RA - $225/bag\r\n6 bags of 9331RA - $225/bag (buy three get three)\r\n\r\nPlease let me know if you have any further questions!\r\n\r\nThanks,\r\nTrent\r\n\r\nTrent Leisy Sales Representative\r\nCell: 970-215-0331 TLLeisy@dow.com\r\n\r\nMycogen Seeds www.mycogen.com \r\n921 Campfire Drive, Fort Collins, CO 80524\r\n\r\nDow AgroSciences LLC',26,225.00,2014,'C',0,80000,32000,'58.jpg'),(59,0,'T9669RA','Triumph','SMARTSTAX, Roundup 2, LIBERTY LINK','6 _ 06RP1T3-C2 AND 6- 50RP1T3 - C2',18,225.00,2014,'C',0,80000,32000,'59.jpg'),(60,0,'P9690HR','Pioneer','AM/LL/RR2/A Q','NW02 PDF 80 H IST V R',12,320.90,2014,'C',0,80000,32000,'60.jpg'),(61,0,'T9331RA','Triumph','SMARTSTAX, Roundup 2, LIBERTY LINK',' 6 bags of 9331RA - $225/bag (buy three get three)',6,225.00,2014,'C',0,80000,32000,'61.jpg'),(62,0,'DKC49-29','Dekalb','YIELDGUARD VT TRIPLE\r\nROUNDUP READY 2','',4,355.00,2014,'C',0,80000,32000,'62.jpg'),(63,0,'DKRIB','Dekalb','YIELDGUARD VT TRIPLE\r\nROUNDUP READY 2','',9,237.00,2014,'C',0,80000,32000,'63.jpg'),(64,0,'P54VR03 Alfalfa','Pioneer','Roundup Ready',' ',5,400.00,2014,'A',1,50,12,'64.jpg'),(65,0,'P0157YXR','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250','2013\r\nNS07 MF 80 M IST RA\r\n\r\nRM 99\r\nTop yielder in 2011 plot\r\n\r\n2011\r\nHY3RID:P:23:H.11 Kind: Field Corn\r\nSIZE: FI4 Wa- 1 ECT NO: M3PRI11043—N\r\nGERM: 93% t..5 5.D: DEC 010\r\nORIGIN:IL KERNELS/UNIT:80,000\r\nFERTILE CYTOPLASM\r\nPass tobbosscel proy,ded under restecr,u condf ions. See bag/tag/invoice for',1,275.91,2014,'C',0,80000,32000,'65.jpg'),(66,0,'P0157AMX','Pioneer','Liberty Link, Roundup Ready 2, Herculex I, PONCHO 1250','2013\r\nNS07 MF 80 M IST RA\r\n\r\nRM 99\r\nTop yielder in 2011 plot\r\n\r\n2011\r\nHY3RID:P:23:H.11 Kind: Field Corn\r\nSIZE: FI4 Wa- 1 ECT NO: M3PRI11043—N\r\nGERM: 93% t..5 5.D: DEC 010\r\nORIGIN:IL KERNELS/UNIT:80,000\r\nFERTILE CYTOPLASM\r\nPass tobbosscel proy,ded under restecr,u condf ions. See bag/tag/invoice for',1,275.91,2014,'C',0,80000,32000,'66.jpg'),(67,0,'P9973AMX','Pioneer','AM/LL/RR2/A Q','NW02 PDF 80 H IST V R',1,320.90,2014,'C',0,80000,32000,'67.jpg'),(68,0,'P9789AMX','Pioneer','AM/LL/RR2/A Q','NW02 PDF 80 H IST V R',1,320.90,2014,'C',0,80000,32000,'68.jpg'),(69,0,'P9697AM','Pioneer','AM/LL/RR2/A Q','NW02 PDF 80 H IST V R',1,320.90,2014,'C',0,80000,32000,'69.jpg'),(70,0,'DKC52-04RIB','Dekalb','YIELDGUARD VT TRIPLE\r\nROUNDUP READY 2\r\nLot 757RXJ7JT','Fastest drying corn \r\n237.8@14.1\r\n2011\r\n\r\n2012\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1285\r\nBLACK LAYER: 2550\r\nLOT NO: 757KL97JX\r\nVARIETY: B0000948\r\nORIGIN: IA\r\nTREATMENT: WAIH1\r\n\r\n2011\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1271\r\nBLACK LAYER: 2550A',40,34.00,2015,'C',0,80000,32000,'70.jpg'),(71,0,'P9690AM','Pioneer','AM/LL/RR2/AQ NW07 MF 8O H IST V RA \r\n\r\nRegular 12.0 $333.00 $3,996.00 $303.03','NW02 PDF 80 H IST V R',12,33.00,2015,'C',0,80000,32000,'71.jpg'),(72,0,'2A557a','MYCOGEN','SMARTSTAX, ROUNDUP READY 2, LIBERTY LINK\r\n50FM2P3-C2','3 bags triumph 3212RA from last year included\r\nSteve,\r\n\r\nHere is the following corn order as we discussed yesterday.\r\n\r\n20 bags of 3212RA - $225/bag\r\n12 bags of 9669RA - $225/bag\r\n6 bags of 9331RA - $225/bag (buy three get three)\r\n\r\nPlease let me know if you have any further questions!\r\n\r\nThanks,\r\nTrent\r\n\r\nTrent Leisy Sales Representative\r\nCell: 970-215-0331 TLLeisy@dow.com\r\n\r\nMycogen Seeds www.mycogen.com \r\n921 Campfire Drive, Fort Collins, CO 80524\r\n\r\nDow AgroSciences LLC',33,225.00,2015,'C',0,80000,32000,'72.jpg'),(73,0,'55VR05','Pioneer','55VR05 Muscle GEN N221 50# BAG FST \r\nRR \r\nRegular 5.0 $315.00 $1,575.00 $292.95\r\n\r\nRound up ready','',5,292.00,2015,'C',0,50,12,'73.jpg'),(74,0,'P9690R','Pioneer','REFUGE\r\n\r\nRR2/AQ NW02 PDF 80 H IST V R \r\n\r\nRegular 5.0 $317.00 $1585.00','NW02 PDF 80 H IST V R',5,31.00,2015,'C',0,80000,32000,'74.jpg'),(75,0,'P9697AM','Pioneer','P9697AM AMILLIRR2IA NW01 PDR 80 H IST V R \r\n0 \r\nRegular 12.0 $343.00 $4,116.00 $312.13','NW02',21,312.10,2015,'C',0,80000,32000,'75.jpg'),(77,0,'P0157R','Pioneer','RR2/AQ','',1,0.00,2015,'C',0,80000,32000,'77.jpg'),(78,0,'P0302CHR','Pioneer','RW/HX1/LL/RR2','',1,0.00,2015,'C',0,80000,32000,'78.jpg'),(79,0,'P9789AMXT','Pioneer',' AMXT/LL/RR2 NM07 MF 80K MD IST',' ',1,0.00,2015,'C',0,80000,32000,'79.jpg'),(80,0,'P9697AMT','Pioneer','AMT/LL/RR2/AQ NW02 PDF 80 H IST V R \r\n0 \r\nRegular 12.0 $343.00 $4,116.00 $312.13','NW02',6,312.10,2015,'C',0,80000,32000,'80.jpg'),(81,0,'DKC52-04RIB','Dekalb','YIELDGUARD VT TRIPLE\r\nROUNDUP READY 2\r\nLot 757RXJ7JT\r\n\r\n?????','Fastest drying corn \r\n237.8@14.1\r\n2011\r\n\r\n2012\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1285\r\nBLACK LAYER: 2550\r\nLOT NO: 757KL97JX\r\nVARIETY: B0000948\r\nORIGIN: IA\r\nTREATMENT: WAIH1\r\n\r\n2011\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1271\r\nBLACK LAYER: 2550A',40,340.00,2016,'C',0,80000,32000,'81.jpg'),(82,0,'P0157R','Pioneer','P0157R RR2/AQ NW02 PDF 80 H IST V R',' ',23,288.50,2016,'C',0,80000,32000,'82.jpg'),(83,0,'P9789AMXT','Pioneer','P9789AMXT AMXT/LL/RR2 NM04 MR 80K MD IST',' ',29,315.00,2016,'C',0,80000,32000,'83.jpg'),(84,0,'2A557a','MYCOGEN','SMARTSTAX, ROUNDUP READY 2, LIBERTY LINK\r\n50FM2P3-C2','3 bags triumph 3212RA from last year included\r\nSteve,\r\n\r\nHere is the following corn order as we discussed yesterday.\r\n\r\n20 bags of 3212RA - $225/bag\r\n12 bags of 9669RA - $225/bag\r\n6 bags of 9331RA - $225/bag (buy three get three)\r\n\r\nPlease let me know if you have any further questions!\r\n\r\nThanks,\r\nTrent\r\n\r\nTrent Leisy Sales Representative\r\nCell: 970-215-0331 TLLeisy@dow.com\r\n\r\nMycogen Seeds www.mycogen.com \r\n921 Campfire Drive, Fort Collins, CO 80524\r\n\r\nDow AgroSciences LLC',33,225.00,2016,'C',0,80000,32000,'84.jpg'),(85,0,'55VR05','Pioneer','Muscle GEN RR N221 50# BAG FST\r\n\r\nRound up ready','Regular 6.0 $292 down from $315.00 $1,575.00 $292.95',6,292.00,2016,'A',0,50,13,'85.jpg'),(86,0,'RC5112 3122A','Rob Seed','NO LIBERTY LINK','',10,0.00,2016,'C',0,80000,32000,'86.jpg'),(87,0,'P9697AMT','Pioneer','P9697AMT AMT/LL/RR2/AQ NW04 MR 80 H IST V RA','',1,0.00,2016,'C',0,80000,32000,'87.jpg'),(88,0,'P0157AMX','Pioneer','P0157AMX AMX/LL/RR2/AQ NS01 PDR 80 M IST R','',1,0.00,2016,'C',0,80000,32000,'88.jpg'),(89,0,'P0339AMT','Pioneer','P0339AMT AMT/LL/RR2/AQ NW04 MR 80 H IST V RA','',1,0.00,2016,'C',0,80000,32000,'89.jpg'),(90,0,'55VR05','Pioneer','55VR05 Muscle GEN RR N221 50# BAG FST\r\n\r\nRound up ready','??? Regular 6.0 $292 down from $315.00 $1,575.00 $292.95',6,292.00,2017,'A',0,50,14,'90.jpg'),(91,0,'P9789AMXT','Pioneer','AMXT/LL/RR2 NM04 MR 80K MD IST','P9789AMXT AMXT/LL/RR2 NM04 MR 80K MD IST Regular 33.0 $354.00 $11,682.00 $297.61',51,297.00,2017,'C',0,80000,34000,'91.jpg'),(92,0,'P0157AMX','Pioneer','AMX/LL/RR2/AQ NWP9 40 PKP H IST R VO','P0157AMX AMX/LL/RR2/AQ NWP9 40 PKP H IST R VO Regular 1.0 $191.00 $191.00 $160.57',1,160.50,2017,'C',0,80000,34000,'92.jpg'),(93,0,'P0157AMX','Pioneer','AMX/LL/RR2/AQ NS02 PDF 80 M IST R','P0157AMX AMX/LL/RR2/AQ NS02 PDF 80 M IST R Regular 1.0 $355.00 $355.00 $298.45',1,298.45,2017,'C',0,80000,34000,'93.jpg'),(94,0,'P0157R','Pioneer','RR2/AQ NW02 PDF 80 H IST V R','P0157R RR2/AQ NW02 PDF 80 H IST V R Regular 23.0 $322.00 $7,406.00 $270.70',23,270.70,2017,'C',0,80000,34000,'94.jpg'),(95,0,'P0339AMT','Pioneer','AMT/LL/RR2/AQ NW02 PDF 80 H IST V R','P0339AMT AMT/LL/RR2/AQ NW02 PDF 80 H IST V R Regular 1.0 $369.00 $369.00 $310.22',1,310.22,2017,'C',0,80000,34000,'95.jpg'),(96,0,'P9188AMX','Pioneer','AMX/LL/RR2 NWP9 40 PKP H IST R VO','P9188AMX AMX/LL/RR2 NWP9 40 PKP H IST R VO Regular 1.0 $193.50 $193.50 $162.67',1,162.67,2017,'C',0,80000,34000,'96.jpg'),(97,0,'P9608AM','Pioneer','AM/LL/RR2 NWP9 40 PKP H IST R VO','P9608AM AM/LL/RR2 NWP9 40 PKP H IST R VO Regular 1.0 $173.50 $173.50 $145.86',1,145.86,2017,'C',0,80000,34000,'97.jpg'),(98,0,'P9621AMXT','Pioneer','AMXT/LL/RR2 NJP9 40K PKP MD LR','P9621AMXT AMXT/LL/RR2 NJP9 40K PKP MD LR Regular 1.0 $184.00 $184.00 $154.69',1,154.69,2017,'C',0,80000,34000,'98.jpg'),(99,0,'P9697AMT','Pioneer','AMT/LL/RR2/AQ NWP9 40 PKP H IST R VO','P9697AMT AMT/LL/RR2/AQ NWP9 40 PKP H IST R VO Regular 1.0 $179.50 $179.50 $150.90',1,150.90,2017,'C',0,80000,34000,'99.jpg'),(100,0,'P9697AMT','Pioneer','AMT/LL/RR2/AQ NW02 PDF 80 H IST V R','P9697AMT AMT/LL/RR2/AQ NW02 PDF 80 H IST V R Regular 1.0 $359.00 $359.00 $301.81',1,301.81,2017,'C',0,80000,34000,'100.jpg'),(101,0,'P9789AMXT','Pioneer','AMXT/LL/RR2 NVP9 40K PKP HI IST VO','P9789AMXT AMXT/LL/RR2 NVP9 40K PKP HI IST VO Regular 1.0 $190.50 $190.50 $160.15',1,160.15,2017,'C',0,80000,34000,'101.jpg'),(102,0,'P9998AMXT','Pioneer','AMXT/LL/RR2/AQ NJP9 40K PKP MD LR','P9998AMXT AMXT/LL/RR2/AQ NJP9 40K PKP MD LR Regular 1.0 $183.50 $183.50 $154.28',1,154.28,2017,'C',0,80000,34000,'102.jpg'),(103,0,'DK46-36','Dekalb','YIELDGUARD VT TRIPLE\r\nROUNDUP READY 2\r\nLot 757RXJ7JT\r\n\r\n?????','SEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1285\r\nBLACK LAYER: 2550\r\nLOT NO: 757KL97JX\r\nVARIETY: B0000948\r\nORIGIN: IA\r\nTREATMENT: WAIH1\r\n\r\n2011\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1271\r\nBLACK LAYER: 2550A',50,340.00,2017,'C',0,80000,34000,'103.jpg'),(104,0,'DUMMY','DUMMY','','',18,0.00,2018,'C',0,80000,34000,'104.jpg'),(105,0,'197-68STX','Challenger','197-68STXRIB BLEND 80M A500V','',1,313.00,2017,'C',0,80000,32000,'105.jpg'),(106,0,'203-01STX','Challenger','203-01STXRIB BLEND 80M A500V','',1,366.00,2017,'C',0,80000,32000,'106.jpg'),(107,0,'P9120AM','Pioneer','AMX/LL/RR2 NWP9 40 PKP H IST R VO','P9188AMX AMX/LL/RR2 NWP9 40 PKP H IST R VO Regular 1.0 $193.50 $193.50 $162.67',1,0.00,2017,'C',0,80000,32000,'107.jpg'),(108,0,'P8761AMXT','Pioneer','AMXT/LL/RR2 NM04 MR 80K MD IST','P9789AMXT AMXT/LL/RR2 NM04 MR 80K MD IST Regular 33.0 $354.00 $11,682.00 $297.61',1,0.00,2017,'C',0,80000,32000,'108.jpg'),(109,0,'DK46-36','Dekalb','SmartStax RIB complete\r\n?????','SEED SIZE: P22\r\nMATURITY: 96\r\nMID-POLLINATION: 1246\r\nBLACK LAYER: 2400\r\nLOT NO: 786MY33JX\r\nVARIETY: A 105252 94% germ\r\nORIGIN: IA\r\nTREATMENT: WAIH1\r\n\r\n2011\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1271\r\nBLACK LAYER: 2550A',50,340.00,2018,'C',0,80000,34000,'109.jpg'),(110,0,'P9998AMXT','Pioneer','AMXT/LL/\r\nLiberty link Hercules and Cruiser 500 and acre Max\r\n\r\n\r\n\r\nGermination 95%','P9998AMXT AMXT/LL/RR2/AQ NJP9 40K PKP MD LR Regular 1.0 $183.50 $183.50 $154.28\r\nLot number D3DON 11042 - 00',25,300.00,2018,'C',0,80000,34000,'110.jpg'),(111,0,'P9789AMXT','Pioneer','AMXT/LL/RR2 NM04 MR 80K MD IST','Germ 95% \r\nLot number D3CON11053 - 00',25,300.00,2018,'C',0,80000,34000,'111.jpg'),(112,0,'203-01STX','Channel','203-01STXRIB BLEND 80M A500V','103 day corn\r\n variety: 1062 990 also variety: 106547 7\r\nLot number E48gx52W8',1,366.00,2018,'C',0,80000,34000,'112.jpg'),(113,0,'55VR05','Pioneer','Muscle GEN RR N221 50# BAG FST','55VR05 Muscle GEN RR N221 50# BAG FST Regular P14C49 Winter; Steve â€1.0\r\nAlfalfa Total â€1.0',2,400.00,2019,'A',0,80000,34000,'113.jpg'),(114,0,'P9492AM','Pioneer','AM/LL/RR2 NJ07 MF','80K MD IST LR Winter; Steve 8.0 8.0 0.0',8,333.00,2019,'C',0,80000,33000,'114.jpg'),(115,0,'P9789AMXT','Pioneer','AMXT/LL/RR2 NS02 PDF','80 M IST R Winter; Steve 24.0 24.0 0.0',24,333.00,2019,'C',0,80000,33000,'115.jpg'),(116,0,'P9998AMXT','Pioneer','AMXT/LL/RR2/AQ NC02 PDF','80MK MID RAX Winter; Steve 24.0 24.0 0.0',24,333.00,2019,'C',0,80000,33000,'116.jpg'),(117,0,'DK46-36','Dekalb','SmartStax RIB complete','SEED SIZE: AR2\r\nMATURITY: 96\r\nMID-POLLINATION: 1246\r\nBLACK LAYER: 2400\r\nLOT NO: 786MY33JX\r\nVARIETY: A 105252 94% germ\r\nORIGIN: IA\r\nTREATMENT: WAIH1\r\n\r\n2011\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1271\r\nBLACK LAYER: 2550A',50,340.00,2019,'C',0,80000,33000,'117.jpg'),(118,0,'203-01STXRIB','Channel','203-01STXRIB BLEND 80M A500V','103 day corn\r\n variety: 1062 990 also variety: 106547 7\r\nLot number E48gx52W8',24,366.00,2019,'C',0,80000,33000,'118.jpg'),(119,0,'197-90STXRIB','Channel','BLEND 80M A500V 97 day LOT G54R36GD8','97 day',24,366.00,2020,'C',0,80000,33000,'119.jpg'),(120,0,'DK46-36','Dekalb','SmartStax RIB complete','SEED SIZE: AR2\r\nMATURITY: 96\r\nMID-POLLINATION: 1246\r\nBLACK LAYER: 2400\r\nLOT NO: 786PK37JX\r\nVARIETY: A 105252 94% germ\r\nORIGIN: IA\r\nTREATMENT: WAIH1\r\n\r\n2011\r\nSEED SIZE: P22\r\nMATURITY: 102\r\nMID-POLLINATION: 1271\r\nBLACK LAYER: 2550A',36,340.00,2020,'C',0,80000,33000,'120.jpg'),(121,0,'P9789AMXT','Pioneer','AMXT/LL/RR2 NS02 PDF','80 M IST R Winter; Steve 24.0 24.0 0.0',24,329.00,2020,'C',0,80000,32000,'121.jpg'),(122,0,'P9998AMXT','Pioneer','AMXT/LL/RR2/AQ NC02 PDF','80MK MID RAX Winter; Steve 24.0 24.0 0.0',24,348.00,2020,'C',0,80000,32000,'122.jpg'),(123,0,'DK45-65','Dekalb','SmartStax RIB complete','SEED SIZE: AR2\r\nMATURITY: 95\r\nMID-POLLINATION: 1244\r\nBLACK LAYER: 2375\r\nLOT NO: 748WNA4JX\r\nVARIETY: A 105252 94% germ\r\nORIGIN: IA\r\nTREATMENT: FALH2V',12,340.00,2020,'C',0,80000,33000,'123.jpg'),(124,0,'DKC51-91RIB','Dekalb','SmartStax RIB complete','SEED SIZE: AR2\r\nMATURITY: 95\r\nMID-POLLINATION: 1244\r\nBLACK LAYER: 2375\r\nLOT NO: 748WNA4JX\r\nVARIETY: A 105252 94% germ\r\nORIGIN: IA\r\nTREATMENT: FALH2V',46,340.00,2021,'C',0,80000,33000,'124.jpg'),(125,0,'197-90STXRIB','Channel','BLEND 80M A500V 97 day LOT G54R36GD8','97 day',24,366.00,2021,'C',0,80000,33000,'125.jpg'),(126,0,'199-60STXRIB','Channel','99 day','',24,366.00,2021,'C',0,80000,33000,'126.jpg'),(127,0,'RR488','Channel','Alfalfa','',10,499.00,2021,'C',0,50,19,'127.jpg'),(128,0,'199-11STXRIB','Channel','99 day','',12,366.00,2021,'C',0,80000,33000,'128.jpg');
/*!40000 ALTER TABLE `products` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `storage`
--
DROP TABLE IF EXISTS `storage`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `storage` (
`storageid` tinyint(4) NOT NULL,
`date_stored` date NOT NULL,
`stored` varchar(250) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `storage`
--
LOCK TABLES `storage` WRITE;
/*!40000 ALTER TABLE `storage` DISABLE KEYS */;
INSERT INTO `storage` VALUES (1,'2012-07-17','LEVEL|10|ATTEMPTS|1'),(2,'0000-00-00','');
/*!40000 ALTER TABLE `storage` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `swd_commentmeta`
--
DROP TABLE IF EXISTS `swd_commentmeta`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `swd_commentmeta` (
`meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`comment_id` bigint(20) unsigned NOT NULL DEFAULT '0',
`meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
`meta_value` longtext COLLATE utf8mb4_unicode_520_ci,
PRIMARY KEY (`meta_id`),
KEY `comment_id` (`comment_id`),
KEY `meta_key` (`meta_key`(191))
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `swd_commentmeta`
--
LOCK TABLES `swd_commentmeta` WRITE;
/*!40000 ALTER TABLE `swd_commentmeta` DISABLE KEYS */;
/*!40000 ALTER TABLE `swd_commentmeta` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `swd_comments`
--
DROP TABLE IF EXISTS `swd_comments`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `swd_comments` (
`comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT '0',
`comment_author` tinytext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`comment_author_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`comment_author_url` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`comment_content` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
`comment_karma` int(11) NOT NULL DEFAULT '0',
`comment_approved` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '1',
`comment_agent` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`comment_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'comment',
`comment_parent` bigint(20) unsigned NOT NULL DEFAULT '0',
`user_id` bigint(20) unsigned NOT NULL DEFAULT '0',
PRIMARY KEY (`comment_ID`),
KEY `comment_post_ID` (`comment_post_ID`),
KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`),
KEY `comment_date_gmt` (`comment_date_gmt`),
KEY `comment_parent` (`comment_parent`),
KEY `comment_author_email` (`comment_author_email`(10))
) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `swd_comments`
--
LOCK TABLES `swd_comments` WRITE;
/*!40000 ALTER TABLE `swd_comments` DISABLE KEYS */;
INSERT INTO `swd_comments` VALUES (1,1,'A WordPress Commenter','wapuu@wordpress.example','https://wordpress.org/','','2017-02-08 03:46:34','2017-02-08 03:46:34','Hi, this is a comment.\nTo get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.\nCommenter avatars come from Gravatar.',0,'1','','comment',0,0);
/*!40000 ALTER TABLE `swd_comments` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `swd_links`
--
DROP TABLE IF EXISTS `swd_links`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `swd_links` (
`link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`link_url` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_name` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_image` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_target` varchar(25) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_description` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_visible` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'Y',
`link_owner` bigint(20) unsigned NOT NULL DEFAULT '1',
`link_rating` int(11) NOT NULL DEFAULT '0',
`link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`link_rel` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_notes` mediumtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`link_rss` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
PRIMARY KEY (`link_id`),
KEY `link_visible` (`link_visible`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `swd_links`
--
LOCK TABLES `swd_links` WRITE;
/*!40000 ALTER TABLE `swd_links` DISABLE KEYS */;
/*!40000 ALTER TABLE `swd_links` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `swd_options`
--
DROP TABLE IF EXISTS `swd_options`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `swd_options` (
`option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`option_name` varchar(191) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`option_value` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`autoload` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'yes',
PRIMARY KEY (`option_id`),
UNIQUE KEY `option_name` (`option_name`),
KEY `autoload` (`autoload`)
) ENGINE=MyISAM AUTO_INCREMENT=18617 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `swd_options`
--
LOCK TABLES `swd_options` WRITE;
/*!40000 ALTER TABLE `swd_options` DISABLE KEYS */;
INSERT INTO `swd_options` VALUES (1,'siteurl','http://www.acctcrop.softwarewebdesign.com','yes'),(2,'home','http://www.acctcrop.softwarewebdesign.com','yes'),(3,'blogname','Wordpress','yes'),(4,'blogdescription','S&J, Crops, & part files','yes'),(5,'users_can_register','0','yes'),(6,'admin_email','stevew@thinairnet.com','yes'),(7,'start_of_week','1','yes'),(8,'use_balanceTags','0','yes'),(9,'use_smilies','1','yes'),(10,'require_name_email','1','yes'),(11,'comments_notify','1','yes'),(12,'posts_per_rss','10','yes'),(13,'rss_use_excerpt','0','yes'),(14,'mailserver_url','mail.example.com','yes'),(15,'mailserver_login','login@example.com','yes'),(16,'mailserver_pass','password','yes'),(17,'mailserver_port','110','yes'),(18,'default_category','1','yes'),(19,'default_comment_status','open','yes'),(20,'default_ping_status','open','yes'),(21,'default_pingback_flag','0','yes'),(22,'posts_per_page','10','yes'),(23,'date_format','F j, Y','yes'),(24,'time_format','g:i a','yes'),(25,'links_updated_date_format','F j, Y g:i a','yes'),(26,'comment_moderation','0','yes'),(27,'moderation_notify','1','yes'),(28,'permalink_structure','/%year%/%monthnum%/%day%/%postname%/','yes'),(29,'rewrite_rules','a:91:{s:11:\"^wp-json/?$\";s:22:\"index.php?rest_route=/\";s:14:\"^wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:21:\"^index.php/wp-json/?$\";s:22:\"index.php?rest_route=/\";s:24:\"^index.php/wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:47:\"category/(.+?)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?category_name=$matches[1]&feed=$matches[2]\";s:42:\"category/(.+?)/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?category_name=$matches[1]&feed=$matches[2]\";s:23:\"category/(.+?)/embed/?$\";s:46:\"index.php?category_name=$matches[1]&embed=true\";s:35:\"category/(.+?)/page/?([0-9]{1,})/?$\";s:53:\"index.php?category_name=$matches[1]&paged=$matches[2]\";s:17:\"category/(.+?)/?$\";s:35:\"index.php?category_name=$matches[1]\";s:44:\"tag/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?tag=$matches[1]&feed=$matches[2]\";s:39:\"tag/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?tag=$matches[1]&feed=$matches[2]\";s:20:\"tag/([^/]+)/embed/?$\";s:36:\"index.php?tag=$matches[1]&embed=true\";s:32:\"tag/([^/]+)/page/?([0-9]{1,})/?$\";s:43:\"index.php?tag=$matches[1]&paged=$matches[2]\";s:14:\"tag/([^/]+)/?$\";s:25:\"index.php?tag=$matches[1]\";s:45:\"type/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?post_format=$matches[1]&feed=$matches[2]\";s:40:\"type/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?post_format=$matches[1]&feed=$matches[2]\";s:21:\"type/([^/]+)/embed/?$\";s:44:\"index.php?post_format=$matches[1]&embed=true\";s:33:\"type/([^/]+)/page/?([0-9]{1,})/?$\";s:51:\"index.php?post_format=$matches[1]&paged=$matches[2]\";s:15:\"type/([^/]+)/?$\";s:33:\"index.php?post_format=$matches[1]\";s:12:\"robots\\.txt$\";s:18:\"index.php?robots=1\";s:48:\".*wp-(atom|rdf|rss|rss2|feed|commentsrss2)\\.php$\";s:18:\"index.php?feed=old\";s:20:\".*wp-app\\.php(/.*)?$\";s:19:\"index.php?error=403\";s:18:\".*wp-register.php$\";s:23:\"index.php?register=true\";s:32:\"feed/(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:27:\"(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:8:\"embed/?$\";s:21:\"index.php?&embed=true\";s:20:\"page/?([0-9]{1,})/?$\";s:28:\"index.php?&paged=$matches[1]\";s:27:\"comment-page-([0-9]{1,})/?$\";s:38:\"index.php?&page_id=2&cpage=$matches[1]\";s:41:\"comments/feed/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:36:\"comments/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:17:\"comments/embed/?$\";s:21:\"index.php?&embed=true\";s:44:\"search/(.+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:39:\"search/(.+)/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:20:\"search/(.+)/embed/?$\";s:34:\"index.php?s=$matches[1]&embed=true\";s:32:\"search/(.+)/page/?([0-9]{1,})/?$\";s:41:\"index.php?s=$matches[1]&paged=$matches[2]\";s:14:\"search/(.+)/?$\";s:23:\"index.php?s=$matches[1]\";s:47:\"author/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:42:\"author/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:23:\"author/([^/]+)/embed/?$\";s:44:\"index.php?author_name=$matches[1]&embed=true\";s:35:\"author/([^/]+)/page/?([0-9]{1,})/?$\";s:51:\"index.php?author_name=$matches[1]&paged=$matches[2]\";s:17:\"author/([^/]+)/?$\";s:33:\"index.php?author_name=$matches[1]\";s:69:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:64:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:45:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/embed/?$\";s:74:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&embed=true\";s:57:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:81:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&paged=$matches[4]\";s:39:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/?$\";s:63:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]\";s:56:\"([0-9]{4})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:51:\"([0-9]{4})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:32:\"([0-9]{4})/([0-9]{1,2})/embed/?$\";s:58:\"index.php?year=$matches[1]&monthnum=$matches[2]&embed=true\";s:44:\"([0-9]{4})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:65:\"index.php?year=$matches[1]&monthnum=$matches[2]&paged=$matches[3]\";s:26:\"([0-9]{4})/([0-9]{1,2})/?$\";s:47:\"index.php?year=$matches[1]&monthnum=$matches[2]\";s:43:\"([0-9]{4})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:38:\"([0-9]{4})/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:19:\"([0-9]{4})/embed/?$\";s:37:\"index.php?year=$matches[1]&embed=true\";s:31:\"([0-9]{4})/page/?([0-9]{1,})/?$\";s:44:\"index.php?year=$matches[1]&paged=$matches[2]\";s:13:\"([0-9]{4})/?$\";s:26:\"index.php?year=$matches[1]\";s:58:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:68:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:88:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:83:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:83:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:64:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:53:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/embed/?$\";s:91:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&embed=true\";s:57:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/trackback/?$\";s:85:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&tb=1\";s:77:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:97:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&feed=$matches[5]\";s:72:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:97:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&feed=$matches[5]\";s:65:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/page/?([0-9]{1,})/?$\";s:98:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&paged=$matches[5]\";s:72:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/comment-page-([0-9]{1,})/?$\";s:98:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&cpage=$matches[5]\";s:61:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)(?:/([0-9]+))?/?$\";s:97:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&page=$matches[5]\";s:47:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:57:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:77:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:72:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:72:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:53:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:64:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/comment-page-([0-9]{1,})/?$\";s:81:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&cpage=$matches[4]\";s:51:\"([0-9]{4})/([0-9]{1,2})/comment-page-([0-9]{1,})/?$\";s:65:\"index.php?year=$matches[1]&monthnum=$matches[2]&cpage=$matches[3]\";s:38:\"([0-9]{4})/comment-page-([0-9]{1,})/?$\";s:44:\"index.php?year=$matches[1]&cpage=$matches[2]\";s:27:\".?.+?/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:37:\".?.+?/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:57:\".?.+?/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:33:\".?.+?/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:16:\"(.?.+?)/embed/?$\";s:41:\"index.php?pagename=$matches[1]&embed=true\";s:20:\"(.?.+?)/trackback/?$\";s:35:\"index.php?pagename=$matches[1]&tb=1\";s:40:\"(.?.+?)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:35:\"(.?.+?)/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:28:\"(.?.+?)/page/?([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&paged=$matches[2]\";s:35:\"(.?.+?)/comment-page-([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&cpage=$matches[2]\";s:24:\"(.?.+?)(?:/([0-9]+))?/?$\";s:47:\"index.php?pagename=$matches[1]&page=$matches[2]\";}','yes'),(30,'hack_file','0','yes'),(31,'blog_charset','UTF-8','yes'),(32,'moderation_keys','','no'),(33,'active_plugins','a:2:{i:0;s:35:\"backupwordpress/backupwordpress.php\";i:1;s:41:\"wp-visitors-widget/wp-visitors-widget.php\";}','yes'),(34,'category_base','','yes'),(35,'ping_sites','http://rpc.pingomatic.com/','yes'),(36,'comment_max_links','2','yes'),(37,'gmt_offset','0','yes'),(38,'default_email_category','1','yes'),(39,'recently_edited','a:3:{i:0;s:74:\"/home1/softwax3/public_html/SWD/wp-content/themes/responsiveswd/header.php\";i:2;s:73:\"/home1/softwax3/public_html/SWD/wp-content/themes/responsiveswd/style.css\";i:3;s:0:\"\";}','no'),(40,'template','twentyseventeen','yes'),(41,'stylesheet','twentyseventeen','yes'),(44,'comment_registration','0','yes'),(45,'html_type','text/html','yes'),(46,'use_trackback','0','yes'),(47,'default_role','subscriber','yes'),(48,'db_version','60717','yes'),(49,'uploads_use_yearmonth_folders','1','yes'),(50,'upload_path','','yes'),(51,'blog_public','0','yes'),(52,'default_link_category','2','yes'),(53,'show_on_front','page','yes'),(54,'tag_base','','yes'),(55,'show_avatars','1','yes'),(56,'avatar_rating','G','yes'),(57,'upload_url_path','','yes'),(58,'thumbnail_size_w','150','yes'),(59,'thumbnail_size_h','150','yes'),(60,'thumbnail_crop','1','yes'),(61,'medium_size_w','300','yes'),(62,'medium_size_h','300','yes'),(63,'avatar_default','mystery','yes'),(64,'large_size_w','1024','yes'),(65,'large_size_h','1024','yes'),(66,'image_default_link_type','none','yes'),(67,'image_default_size','','yes'),(68,'image_default_align','','yes'),(69,'close_comments_for_old_posts','0','yes'),(70,'close_comments_days_old','14','yes'),(71,'thread_comments','1','yes'),(72,'thread_comments_depth','5','yes'),(73,'page_comments','0','yes'),(74,'comments_per_page','50','yes'),(75,'default_comments_page','newest','yes'),(76,'comment_order','asc','yes'),(77,'sticky_posts','a:0:{}','yes'),(78,'widget_categories','a:2:{i:2;a:4:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:12:\"hierarchical\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(79,'widget_text','a:2:{i:1;a:0:{}s:12:\"_multiwidget\";i:1;}','yes'),(80,'widget_rss','a:2:{i:1;a:0:{}s:12:\"_multiwidget\";i:1;}','yes'),(81,'uninstall_plugins','a:1:{s:41:\"wp-visitors-widget/wp-visitors-widget.php\";s:13:\"wvw_uninstall\";}','no'),(82,'timezone_string','','yes'),(83,'page_for_posts','0','yes'),(84,'page_on_front','2','yes'),(85,'default_post_format','0','yes'),(86,'link_manager_enabled','0','yes'),(87,'finished_splitting_shared_terms','1','yes'),(88,'site_icon','0','yes'),(89,'medium_large_size_w','768','yes'),(90,'medium_large_size_h','0','yes'),(91,'initial_db_version','38590','yes'),(92,'swd_user_roles','a:5:{s:13:\"administrator\";a:2:{s:4:\"name\";s:13:\"Administrator\";s:12:\"capabilities\";a:61:{s:13:\"switch_themes\";b:1;s:11:\"edit_themes\";b:1;s:16:\"activate_plugins\";b:1;s:12:\"edit_plugins\";b:1;s:10:\"edit_users\";b:1;s:10:\"edit_files\";b:1;s:14:\"manage_options\";b:1;s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:6:\"import\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:8:\"level_10\";b:1;s:7:\"level_9\";b:1;s:7:\"level_8\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:12:\"delete_users\";b:1;s:12:\"create_users\";b:1;s:17:\"unfiltered_upload\";b:1;s:14:\"edit_dashboard\";b:1;s:14:\"update_plugins\";b:1;s:14:\"delete_plugins\";b:1;s:15:\"install_plugins\";b:1;s:13:\"update_themes\";b:1;s:14:\"install_themes\";b:1;s:11:\"update_core\";b:1;s:10:\"list_users\";b:1;s:12:\"remove_users\";b:1;s:13:\"promote_users\";b:1;s:18:\"edit_theme_options\";b:1;s:13:\"delete_themes\";b:1;s:6:\"export\";b:1;}}s:6:\"editor\";a:2:{s:4:\"name\";s:6:\"Editor\";s:12:\"capabilities\";a:34:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;}}s:6:\"author\";a:2:{s:4:\"name\";s:6:\"Author\";s:12:\"capabilities\";a:10:{s:12:\"upload_files\";b:1;s:10:\"edit_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"delete_published_posts\";b:1;}}s:11:\"contributor\";a:2:{s:4:\"name\";s:11:\"Contributor\";s:12:\"capabilities\";a:5:{s:10:\"edit_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;}}s:10:\"subscriber\";a:2:{s:4:\"name\";s:10:\"Subscriber\";s:12:\"capabilities\";a:2:{s:4:\"read\";b:1;s:7:\"level_0\";b:1;}}}','yes'),(93,'fresh_site','0','off'),(94,'widget_search','a:3:{i:2;a:1:{s:5:\"title\";s:0:\"\";}i:3;a:1:{s:5:\"title\";s:6:\"Search\";}s:12:\"_multiwidget\";i:1;}','yes'),(95,'widget_recent-posts','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(96,'widget_recent-comments','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(97,'widget_archives','a:2:{i:2;a:3:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(98,'widget_meta','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(99,'sidebars_widgets','a:5:{s:19:\"wp_inactive_widgets\";a:1:{i:0;s:8:\"search-3\";}s:9:\"sidebar-1\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}s:9:\"sidebar-2\";a:1:{i:0;s:17:\"visitors_widget-2\";}s:9:\"sidebar-3\";a:0:{}s:13:\"array_version\";i:3;}','yes'),(100,'widget_pages','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(101,'widget_calendar','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(102,'widget_tag_cloud','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(103,'widget_nav_menu','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(104,'cron','a:11:{i:1773318902;a:1:{s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1773329532;a:1:{s:21:\"wp_update_user_counts\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1773330395;a:3:{s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1773356400;a:1:{s:19:\"hmbkp_schedule_hook\";a:1:{s:32:\"cf85e262980b9c7cc64afdd47a51445c\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:1:{s:2:\"id\";s:10:\"1486525727\";}s:8:\"interval\";i:86400;}}}i:1773362101;a:1:{s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1773373606;a:1:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1773380876;a:1:{s:30:\"wp_scheduled_auto_draft_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1773448501;a:1:{s:30:\"wp_site_health_scheduled_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}i:1773543600;a:1:{s:19:\"hmbkp_schedule_hook\";a:1:{s:32:\"abcbd8e888a4e545221d46fe5eaa0abb\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:1:{s:2:\"id\";s:10:\"1486525728\";}s:8:\"interval\";i:604800;}}}i:1773766294;a:1:{s:30:\"wp_delete_temp_updater_backups\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}s:7:\"version\";i:2;}','on'),(105,'theme_mods_twentyseventeen','a:2:{s:18:\"custom_css_post_id\";i:-1;s:18:\"nav_menu_locations\";a:2:{s:11:\"header-menu\";i:2;s:3:\"top\";i:2;}}','yes'),(18611,'_site_transient_timeout_theme_roots','1773317516','off'),(18612,'_site_transient_theme_roots','a:10:{s:10:\"responsive\";s:7:\"/themes\";s:13:\"responsiveswd\";s:7:\"/themes\";s:13:\"twentyfifteen\";s:7:\"/themes\";s:14:\"twentynineteen\";s:7:\"/themes\";s:15:\"twentyseventeen\";s:7:\"/themes\";s:13:\"twentysixteen\";s:7:\"/themes\";s:12:\"twentytwenty\";s:7:\"/themes\";s:16:\"twentytwentyfive\";s:7:\"/themes\";s:16:\"twentytwentyfour\";s:7:\"/themes\";s:17:\"twentytwentythree\";s:7:\"/themes\";}','off'),(1060,'WPLANG','','yes'),(136,'current_theme','Twenty Seventeen','yes'),(137,'theme_mods_responsive2','a:3:{i:0;b:0;s:18:\"custom_css_post_id\";i:-1;s:16:\"sidebars_widgets\";a:2:{s:4:\"time\";i:1512011729;s:4:\"data\";a:13:{s:19:\"wp_inactive_widgets\";a:0:{}s:12:\"main-sidebar\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}s:13:\"right-sidebar\";a:0:{}s:12:\"left-sidebar\";a:0:{}s:17:\"left-sidebar-half\";N;s:18:\"right-sidebar-half\";N;s:13:\"home-widget-1\";N;s:13:\"home-widget-2\";N;s:13:\"home-widget-3\";N;s:14:\"gallery-widget\";N;s:15:\"colophon-widget\";N;s:10:\"top-widget\";N;s:13:\"footer-widget\";N;}}}','off'),(138,'theme_switched','','yes'),(139,'responsive_theme_options','a:68:{s:15:\"featured_images\";i:0;s:10:\"breadcrumb\";i:0;s:10:\"cta_button\";i:0;s:12:\"minified_css\";b:0;s:10:\"front_page\";i:0;s:13:\"home_headline\";N;s:16:\"home_subheadline\";N;s:17:\"home_content_area\";N;s:8:\"cta_text\";N;s:7:\"cta_url\";N;s:16:\"featured_content\";N;s:12:\"testimonials\";i:0;s:17:\"testimonial_title\";N;s:24:\"google_site_verification\";N;s:22:\"bing_site_verification\";N;s:23:\"yahoo_site_verification\";N;s:23:\"site_statistics_tracker\";N;s:11:\"twitter_uid\";s:0:\"\";s:12:\"facebook_uid\";s:0:\"\";s:12:\"linkedin_uid\";s:0:\"\";s:11:\"youtube_uid\";s:0:\"\";s:11:\"stumble_uid\";s:0:\"\";s:7:\"rss_uid\";s:0:\"\";s:15:\"google_plus_uid\";s:0:\"\";s:13:\"instagram_uid\";s:0:\"\";s:13:\"pinterest_uid\";s:0:\"\";s:8:\"yelp_uid\";s:0:\"\";s:9:\"vimeo_uid\";s:0:\"\";s:14:\"foursquare_uid\";s:0:\"\";s:9:\"email_uid\";s:0:\"\";s:15:\"testimonial_val\";s:0:\"\";s:11:\"teammember1\";s:0:\"\";s:11:\"teammember2\";s:0:\"\";s:11:\"teammember3\";s:0:\"\";s:8:\"feature1\";s:0:\"\";s:8:\"feature2\";s:0:\"\";s:8:\"feature3\";s:0:\"\";s:21:\"responsive_inline_css\";s:0:\"\";s:25:\"responsive_inline_js_head\";s:0:\"\";s:27:\"responsive_inline_js_footer\";s:0:\"\";s:31:\"responsive_inline_css_js_footer\";s:0:\"\";s:26:\"static_page_layout_default\";s:15:\"full-width-page\";s:26:\"single_post_layout_default\";s:15:\"full-width-page\";s:31:\"blog_posts_index_layout_default\";s:15:\"full-width-page\";s:18:\"site_layout_option\";s:17:\"full-width-no-box\";s:12:\"button_style\";s:7:\"default\";s:12:\"home-widgets\";b:0;s:18:\"site_footer_option\";s:12:\"footer-3-col\";s:19:\"res_hide_site_title\";b:0;s:16:\"res_hide_tagline\";b:1;s:13:\"sticky-header\";b:0;s:20:\"blog_post_title_text\";s:0:\"\";s:17:\"copyright_textbox\";s:0:\"\";s:11:\"home_slider\";s:0:\"\";s:11:\"about_title\";s:0:\"\";s:10:\"about_text\";s:0:\"\";s:14:\"about_cta_text\";s:0:\"\";s:13:\"about_cta_url\";s:0:\"\";s:13:\"feature_title\";s:0:\"\";s:10:\"team_title\";s:0:\"\";s:13:\"contact_title\";s:0:\"\";s:17:\"contact_subtitlet\";s:0:\"\";s:11:\"contact_add\";s:0:\"\";s:13:\"contact_email\";s:0:\"\";s:10:\"contact_ph\";s:0:\"\";s:15:\"contact_content\";s:0:\"\";s:14:\"googleplus_uid\";s:0:\"\";s:15:\"stumbleupon_uid\";s:0:\"\";}','yes'),(144,'recently_activated','a:0:{}','off'),(18616,'_site_transient_wp_theme_files_patterns-b6cbbc6195c262f28352aa132f49b746','a:2:{s:7:\"version\";s:3:\"3.4\";s:8:\"patterns\";a:0:{}}','off'),(147,'hmbkp_plugin_version','3.10','yes'),(150,'hmbkp_schedule_1486525727','a:8:{s:11:\"max_backups\";i:30;s:8:\"excludes\";a:0:{}s:4:\"type\";s:8:\"database\";s:12:\"reoccurrence\";s:5:\"daily\";s:19:\"schedule_start_time\";i:1486594800;s:5:\"email\";a:1:{s:5:\"email\";s:21:\"stevew@thinairnet.com\";}s:14:\"duration_total\";i:2779435899756;s:16:\"backup_run_count\";i:1665;}','yes'),(151,'hmbkp_schedule_1486525728','a:8:{s:11:\"max_backups\";i:10;s:8:\"excludes\";a:9:{i:0;s:10:\"HAIRSHOPPE\";i:1;s:4:\"ACCT\";i:2;s:8:\"iqofpost\";i:3;s:5:\"EMAIL\";i:4;s:4:\"CODE\";i:5;s:10:\"WINTERBROS\";i:6;s:9:\"mailstuff\";i:7;s:7:\"cgi-bin\";i:8;s:12:\"default.html\";}s:4:\"type\";s:8:\"complete\";s:12:\"reoccurrence\";s:6:\"weekly\";s:19:\"schedule_start_time\";i:1512874800;s:5:\"email\";a:1:{s:5:\"email\";s:21:\"stevew@thinairnet.com\";}s:14:\"duration_total\";i:259075226919;s:16:\"backup_run_count\";i:164;}','yes'),(171,'hmbkp_notices','a:1:{s:13:\"backup_errors\";a:11:{i:0;s:44:\"Zip: zip warning: No such file or directory\n\";i:1;s:200:\"Zip: zip warning: No such file or directory\nzip warning: No such file or directory\nzip warning: No such file or directory\nzip warning: No such file or directory\nzip warning: No such file or directory\n\";i:2;s:122:\"Zip: zip warning: No such file or directory\nzip warning: No such file or directory\nzip warning: No such file or directory\n\";i:3;s:211:\"php: ZipArchive::close(): Renaming temporary file failed: No such file or directory, /home1/softwax3/public_html/SWD/wp-content/plugins/backupwordpress/classes/backup/class-backup-engine-file-zip-archive.php, 46\";i:4;s:211:\"php: ZipArchive::close(): Renaming temporary file failed: No such file or directory, /home2/softwax3/public_html/SWD/wp-content/plugins/backupwordpress/classes/backup/class-backup-engine-file-zip-archive.php, 46\";i:5;s:83:\"Zip: zip warning: No such file or directory\nzip warning: No such file or directory\n\";i:6;s:36:\"Zip: zip warning: Permission denied\n\";i:7;s:161:\"Zip: zip warning: No such file or directory\nzip warning: No such file or directory\nzip warning: No such file or directory\nzip warning: No such file or directory\n\";i:8;s:233:\"Mysqldump: mysqldump: [Warning] Using a password on the command line interface can be insecure.\nmysqldump: Got error: 1203: User softwax3_Steve99 already has more than \'max_user_connections\' active connections when trying to connect\n\";i:9;s:161:\"IMysqldump: Connection to mysql failed with message: SQLSTATE[HY000] [1203] User softwax3_Steve99 already has more than \'max_user_connections\' active connections\";i:10;s:286:\"php: filesize(): stat failed for /home2/softwax3/public_html/SWD/wp-content/backupwordpress-fb2574a438-backups/database-acctcrop-softwarewebdesign-com-1486525727.sql, /home2/softwax3/public_html/SWD/wp-content/plugins/backupwordpress/classes/backup/class-backup-engine-database.php, 202\";}}','yes'),(1375,'auto_core_update_notified','a:4:{s:4:\"type\";s:7:\"success\";s:5:\"email\";s:21:\"stevew@thinairnet.com\";s:7:\"version\";s:5:\"6.9.4\";s:9:\"timestamp\";i:1773268271;}','off'),(960,'theme_mods_responsiveswd','a:11:{i:0;b:0;s:18:\"custom_css_post_id\";i:15;s:18:\"nav_menu_locations\";a:1:{s:11:\"header-menu\";i:2;}s:26:\"responsive_container_width\";i:1140;s:32:\"responsive_blog_sidebar_position\";s:2:\"no\";s:29:\"responsive_blog_content_width\";i:100;s:39:\"responsive_single_blog_sidebar_position\";s:2:\"no\";s:36:\"responsive_single_blog_content_width\";i:100;s:32:\"responsive_page_sidebar_position\";s:2:\"no\";s:29:\"responsive_page_content_width\";i:100;s:16:\"sidebars_widgets\";a:2:{s:4:\"time\";i:1703214034;s:4:\"data\";a:13:{s:19:\"wp_inactive_widgets\";a:0:{}s:12:\"main-sidebar\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}s:13:\"right-sidebar\";a:0:{}s:12:\"left-sidebar\";a:0:{}s:17:\"left-sidebar-half\";a:0:{}s:18:\"right-sidebar-half\";a:0:{}s:13:\"home-widget-1\";a:0:{}s:13:\"home-widget-2\";a:0:{}s:13:\"home-widget-3\";a:0:{}s:14:\"gallery-widget\";a:0:{}s:15:\"colophon-widget\";a:0:{}s:10:\"top-widget\";a:1:{i:0;s:8:\"search-3\";}s:13:\"footer-widget\";a:0:{}}}}','off'),(961,'theme_mods_responsive','a:2:{i:0;b:0;s:16:\"sidebars_widgets\";a:2:{s:4:\"time\";i:1512012162;s:4:\"data\";a:13:{s:19:\"wp_inactive_widgets\";a:0:{}s:12:\"main-sidebar\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}s:13:\"right-sidebar\";a:0:{}s:12:\"left-sidebar\";a:0:{}s:17:\"left-sidebar-half\";N;s:18:\"right-sidebar-half\";N;s:13:\"home-widget-1\";N;s:13:\"home-widget-2\";N;s:13:\"home-widget-3\";N;s:14:\"gallery-widget\";N;s:15:\"colophon-widget\";N;s:10:\"top-widget\";N;s:13:\"footer-widget\";N;}}}','off'),(18614,'_site_transient_update_plugins','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1773315716;s:8:\"response\";a:7:{s:19:\"akismet/akismet.php\";O:8:\"stdClass\":13:{s:2:\"id\";s:21:\"w.org/plugins/akismet\";s:4:\"slug\";s:7:\"akismet\";s:6:\"plugin\";s:19:\"akismet/akismet.php\";s:11:\"new_version\";s:3:\"5.6\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/akismet/\";s:7:\"package\";s:54:\"https://downloads.wordpress.org/plugin/akismet.5.6.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:60:\"https://ps.w.org/akismet/assets/icon-256x256.png?rev=2818463\";s:2:\"1x\";s:60:\"https://ps.w.org/akismet/assets/icon-128x128.png?rev=2818463\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:63:\"https://ps.w.org/akismet/assets/banner-1544x500.png?rev=2900731\";s:2:\"1x\";s:62:\"https://ps.w.org/akismet/assets/banner-772x250.png?rev=2900731\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"5.8\";s:6:\"tested\";s:5:\"6.9.4\";s:12:\"requires_php\";s:3:\"7.2\";s:16:\"requires_plugins\";a:0:{}}s:49:\"better-recent-comments/better-recent-comments.php\";O:8:\"stdClass\":13:{s:2:\"id\";s:36:\"w.org/plugins/better-recent-comments\";s:4:\"slug\";s:22:\"better-recent-comments\";s:6:\"plugin\";s:49:\"better-recent-comments/better-recent-comments.php\";s:11:\"new_version\";s:5:\"1.2.0\";s:3:\"url\";s:53:\"https://wordpress.org/plugins/better-recent-comments/\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/plugin/better-recent-comments.1.2.0.zip\";s:5:\"icons\";a:2:{s:2:\"1x\";s:67:\"https://ps.w.org/better-recent-comments/assets/icon.svg?rev=3100094\";s:3:\"svg\";s:67:\"https://ps.w.org/better-recent-comments/assets/icon.svg?rev=3100094\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:78:\"https://ps.w.org/better-recent-comments/assets/banner-1544x500.png?rev=3100094\";s:2:\"1x\";s:77:\"https://ps.w.org/better-recent-comments/assets/banner-772x250.png?rev=3100094\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"6.0\";s:6:\"tested\";s:5:\"6.5.8\";s:12:\"requires_php\";s:3:\"7.4\";s:16:\"requires_plugins\";a:0:{}}s:19:\"jetpack/jetpack.php\";O:8:\"stdClass\":13:{s:2:\"id\";s:21:\"w.org/plugins/jetpack\";s:4:\"slug\";s:7:\"jetpack\";s:6:\"plugin\";s:19:\"jetpack/jetpack.php\";s:11:\"new_version\";s:4:\"15.6\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/jetpack/\";s:7:\"package\";s:55:\"https://downloads.wordpress.org/plugin/jetpack.15.6.zip\";s:5:\"icons\";a:2:{s:2:\"1x\";s:52:\"https://ps.w.org/jetpack/assets/icon.svg?rev=2819237\";s:3:\"svg\";s:52:\"https://ps.w.org/jetpack/assets/icon.svg?rev=2819237\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:63:\"https://ps.w.org/jetpack/assets/banner-1544x500.png?rev=2653649\";s:2:\"1x\";s:62:\"https://ps.w.org/jetpack/assets/banner-772x250.png?rev=2653649\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"6.8\";s:6:\"tested\";s:5:\"6.9.4\";s:12:\"requires_php\";s:3:\"7.2\";s:16:\"requires_plugins\";a:0:{}}s:47:\"latest-post-shortcode/latest-post-shortcode.php\";O:8:\"stdClass\":13:{s:2:\"id\";s:35:\"w.org/plugins/latest-post-shortcode\";s:4:\"slug\";s:21:\"latest-post-shortcode\";s:6:\"plugin\";s:47:\"latest-post-shortcode/latest-post-shortcode.php\";s:11:\"new_version\";s:6:\"14.2.2\";s:3:\"url\";s:52:\"https://wordpress.org/plugins/latest-post-shortcode/\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/plugin/latest-post-shortcode.14.2.2.zip\";s:5:\"icons\";a:1:{s:2:\"1x\";s:74:\"https://ps.w.org/latest-post-shortcode/assets/icon-128x128.gif?rev=2355649\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:77:\"https://ps.w.org/latest-post-shortcode/assets/banner-1544x500.png?rev=3117513\";s:2:\"1x\";s:76:\"https://ps.w.org/latest-post-shortcode/assets/banner-772x250.png?rev=3117513\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:5:\"5.5.0\";s:6:\"tested\";s:5:\"6.9.4\";s:12:\"requires_php\";s:5:\"7.3.5\";s:16:\"requires_plugins\";a:0:{}}s:45:\"organize-media-folder/organizemediafolder.php\";O:8:\"stdClass\":13:{s:2:\"id\";s:35:\"w.org/plugins/organize-media-folder\";s:4:\"slug\";s:21:\"organize-media-folder\";s:6:\"plugin\";s:45:\"organize-media-folder/organizemediafolder.php\";s:11:\"new_version\";s:4:\"1.36\";s:3:\"url\";s:52:\"https://wordpress.org/plugins/organize-media-folder/\";s:7:\"package\";s:69:\"https://downloads.wordpress.org/plugin/organize-media-folder.1.36.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:74:\"https://ps.w.org/organize-media-folder/assets/icon-256x256.png?rev=2446017\";s:2:\"1x\";s:74:\"https://ps.w.org/organize-media-folder/assets/icon-256x256.png?rev=2446017\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:77:\"https://ps.w.org/organize-media-folder/assets/banner-1544x500.jpg?rev=2446017\";s:2:\"1x\";s:76:\"https://ps.w.org/organize-media-folder/assets/banner-772x250.jpg?rev=2446017\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.7\";s:6:\"tested\";s:5:\"6.9.4\";s:12:\"requires_php\";s:3:\"8.0\";s:16:\"requires_plugins\";a:0:{}}s:45:\"phoenix-media-rename/phoenix-media-rename.php\";O:8:\"stdClass\":13:{s:2:\"id\";s:34:\"w.org/plugins/phoenix-media-rename\";s:4:\"slug\";s:20:\"phoenix-media-rename\";s:6:\"plugin\";s:45:\"phoenix-media-rename/phoenix-media-rename.php\";s:11:\"new_version\";s:6:\"3.13.1\";s:3:\"url\";s:51:\"https://wordpress.org/plugins/phoenix-media-rename/\";s:7:\"package\";s:70:\"https://downloads.wordpress.org/plugin/phoenix-media-rename.3.13.1.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:73:\"https://ps.w.org/phoenix-media-rename/assets/icon-256x256.png?rev=3120623\";s:2:\"1x\";s:73:\"https://ps.w.org/phoenix-media-rename/assets/icon-128x128.png?rev=3120623\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:75:\"https://ps.w.org/phoenix-media-rename/assets/banner-772x250.png?rev=1490792\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"5.0\";s:6:\"tested\";s:5:\"6.8.5\";s:12:\"requires_php\";s:3:\"8.0\";s:16:\"requires_plugins\";a:0:{}}s:47:\"really-simple-ssl/rlrsssl-really-simple-ssl.php\";O:8:\"stdClass\":13:{s:2:\"id\";s:31:\"w.org/plugins/really-simple-ssl\";s:4:\"slug\";s:17:\"really-simple-ssl\";s:6:\"plugin\";s:47:\"really-simple-ssl/rlrsssl-really-simple-ssl.php\";s:11:\"new_version\";s:5:\"9.5.8\";s:3:\"url\";s:48:\"https://wordpress.org/plugins/really-simple-ssl/\";s:7:\"package\";s:66:\"https://downloads.wordpress.org/plugin/really-simple-ssl.9.5.8.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:70:\"https://ps.w.org/really-simple-ssl/assets/icon-256x256.png?rev=2839720\";s:2:\"1x\";s:70:\"https://ps.w.org/really-simple-ssl/assets/icon-128x128.png?rev=2839720\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:73:\"https://ps.w.org/really-simple-ssl/assets/banner-1544x500.png?rev=3100992\";s:2:\"1x\";s:72:\"https://ps.w.org/really-simple-ssl/assets/banner-772x250.png?rev=3100992\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"6.6\";s:6:\"tested\";s:5:\"6.9.4\";s:12:\"requires_php\";s:3:\"7.4\";s:16:\"requires_plugins\";a:0:{}}}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:2:{s:35:\"backupwordpress/backupwordpress.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:29:\"w.org/plugins/backupwordpress\";s:4:\"slug\";s:15:\"backupwordpress\";s:6:\"plugin\";s:35:\"backupwordpress/backupwordpress.php\";s:11:\"new_version\";s:4:\"3.14\";s:3:\"url\";s:46:\"https://wordpress.org/plugins/backupwordpress/\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/plugin/backupwordpress.3.14.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:68:\"https://ps.w.org/backupwordpress/assets/icon-256x256.jpg?rev=1105225\";s:2:\"1x\";s:68:\"https://ps.w.org/backupwordpress/assets/icon-128x128.png?rev=1105225\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:70:\"https://ps.w.org/backupwordpress/assets/banner-1544x500.jpg?rev=904756\";s:2:\"1x\";s:69:\"https://ps.w.org/backupwordpress/assets/banner-772x250.jpg?rev=904756\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"3.9\";}s:41:\"wp-visitors-widget/wp-visitors-widget.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:32:\"w.org/plugins/wp-visitors-widget\";s:4:\"slug\";s:18:\"wp-visitors-widget\";s:6:\"plugin\";s:41:\"wp-visitors-widget/wp-visitors-widget.php\";s:11:\"new_version\";s:3:\"2.2\";s:3:\"url\";s:49:\"https://wordpress.org/plugins/wp-visitors-widget/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/plugin/wp-visitors-widget.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:71:\"https://ps.w.org/wp-visitors-widget/assets/icon-256x256.png?rev=2178611\";s:2:\"1x\";s:71:\"https://ps.w.org/wp-visitors-widget/assets/icon-256x256.png?rev=2178611\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:74:\"https://ps.w.org/wp-visitors-widget/assets/banner-1544x500.jpg?rev=2178619\";s:2:\"1x\";s:73:\"https://ps.w.org/wp-visitors-widget/assets/banner-772x250.jpg?rev=2178619\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.0\";}}s:7:\"checked\";a:15:{s:19:\"akismet/akismet.php\";s:3:\"3.2\";s:35:\"backupwordpress/backupwordpress.php\";s:4:\"3.14\";s:49:\"better-recent-comments/better-recent-comments.php\";s:5:\"1.1.2\";s:27:\"scriptures/ShowComments.php\";s:3:\"1.0\";s:12:\"fileView.php\";s:3:\"1.0\";s:29:\"gravityforms/gravityforms.php\";s:8:\"2.2.5.11\";s:19:\"jetpack/jetpack.php\";s:4:\"14.1\";s:47:\"latest-post-shortcode/latest-post-shortcode.php\";s:6:\"14.1.0\";s:41:\"wp-visitors-widget/wp-visitors-widget.php\";s:3:\"2.2\";s:30:\"movie_library/movieLibrary.php\";s:3:\"1.0\";s:45:\"organize-media-folder/organizemediafolder.php\";s:4:\"1.33\";s:45:\"phoenix-media-rename/phoenix-media-rename.php\";s:5:\"3.8.8\";s:47:\"really-simple-ssl/rlrsssl-really-simple-ssl.php\";s:5:\"3.3.3\";s:35:\"slider-pro-master/swd_sliderpro.php\";s:3:\"1.0\";s:30:\"directorySWD/ShowDirectory.php\";s:3:\"1.0\";}}','off'),(1206,'nav_menu_options','a:2:{i:0;b:0;s:8:\"auto_add\";a:0:{}}','off'),(18615,'_site_transient_timeout_wp_theme_files_patterns-b6cbbc6195c262f28352aa132f49b746','1773318660','off'),(13618,'_transient_health-check-site-status-result','{\"good\":17,\"recommended\":7,\"critical\":0}','yes'),(13845,'_transient_wp_styles_for_blocks','a:2:{s:4:\"hash\";s:32:\"ac5d1e337abdcb7c09762e96707a996c\";s:6:\"blocks\";a:6:{s:11:\"core/button\";s:0:\"\";s:14:\"core/site-logo\";s:0:\"\";s:18:\"core/post-template\";s:120:\":where(.wp-block-post-template.is-layout-flex){gap: 1.25em;}:where(.wp-block-post-template.is-layout-grid){gap: 1.25em;}\";s:18:\"core/term-template\";s:120:\":where(.wp-block-term-template.is-layout-flex){gap: 1.25em;}:where(.wp-block-term-template.is-layout-grid){gap: 1.25em;}\";s:12:\"core/columns\";s:102:\":where(.wp-block-columns.is-layout-flex){gap: 2em;}:where(.wp-block-columns.is-layout-grid){gap: 2em;}\";s:14:\"core/pullquote\";s:69:\":root :where(.wp-block-pullquote){font-size: 1.5em;line-height: 1.6;}\";}}','on'),(8422,'widget_responsive_about_me_widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(8489,'responsive-theme-old-setup','1','yes'),(8428,'responsive_version_410','1','yes'),(8509,'widget_visitors_widget','a:2:{i:2;a:8:{s:5:\"title\";s:5:\"Crops\";s:12:\"select_style\";s:1:\"4\";s:6:\"colors\";s:5:\"light\";s:10:\"data_row_1\";s:10:\"visit_live\";s:10:\"data_row_2\";s:11:\"visit_today\";s:10:\"data_row_3\";s:11:\"visit_total\";s:6:\"shadow\";s:0:\"\";s:13:\"initial_value\";s:1:\"2\";}s:12:\"_multiwidget\";i:1;}','yes'),(8510,'_transient_is_multi_author','0','yes'),(13584,'widget_media_image','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(13585,'widget_media_gallery','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(13586,'widget_media_video','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(13587,'widget_custom_html','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(13841,'widget_block','a:1:{s:12:\"_multiwidget\";i:1;}','auto'),(13591,'recovery_keys','a:0:{}','off'),(13544,'_transient_twentyseventeen_categories','1','yes'),(13583,'widget_media_audio','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(13543,'category_children','a:0:{}','yes'),(18597,'user_count','1','off'),(18598,'db_upgraded','1','auto'),(18599,'_site_transient_update_core','O:8:\"stdClass\":4:{s:7:\"updates\";a:1:{i:0;O:8:\"stdClass\":10:{s:8:\"response\";s:6:\"latest\";s:8:\"download\";s:59:\"https://downloads.wordpress.org/release/wordpress-6.9.4.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:59:\"https://downloads.wordpress.org/release/wordpress-6.9.4.zip\";s:10:\"no_content\";s:70:\"https://downloads.wordpress.org/release/wordpress-6.9.4-no-content.zip\";s:11:\"new_bundled\";s:71:\"https://downloads.wordpress.org/release/wordpress-6.9.4-new-bundled.zip\";s:7:\"partial\";s:0:\"\";s:8:\"rollback\";s:0:\"\";}s:7:\"current\";s:5:\"6.9.4\";s:7:\"version\";s:5:\"6.9.4\";s:11:\"php_version\";s:6:\"7.2.24\";s:13:\"mysql_version\";s:5:\"5.5.5\";s:11:\"new_bundled\";s:3:\"6.7\";s:15:\"partial_version\";s:0:\"\";}}s:12:\"last_checked\";i:1773315715;s:15:\"version_checked\";s:5:\"6.9.4\";s:12:\"translations\";a:0:{}}','off'),(18613,'_site_transient_update_themes','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1773315716;s:7:\"checked\";a:10:{s:10:\"responsive\";s:5:\"4.9.5\";s:13:\"responsiveswd\";s:0:\"\";s:13:\"twentyfifteen\";s:3:\"1.7\";s:14:\"twentynineteen\";s:3:\"1.6\";s:15:\"twentyseventeen\";s:3:\"3.4\";s:13:\"twentysixteen\";s:3:\"1.3\";s:12:\"twentytwenty\";s:3:\"1.4\";s:16:\"twentytwentyfive\";s:3:\"1.2\";s:16:\"twentytwentyfour\";s:3:\"1.3\";s:17:\"twentytwentythree\";s:3:\"1.6\";}s:8:\"response\";a:8:{s:10:\"responsive\";a:6:{s:5:\"theme\";s:10:\"responsive\";s:11:\"new_version\";s:5:\"6.3.5\";s:3:\"url\";s:40:\"https://wordpress.org/themes/responsive/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/theme/responsive.6.3.5.zip\";s:8:\"requires\";b:0;s:12:\"requires_php\";s:3:\"5.6\";}s:13:\"twentyfifteen\";a:6:{s:5:\"theme\";s:13:\"twentyfifteen\";s:11:\"new_version\";s:3:\"4.1\";s:3:\"url\";s:43:\"https://wordpress.org/themes/twentyfifteen/\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/theme/twentyfifteen.4.1.zip\";s:8:\"requires\";s:3:\"4.1\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:14:\"twentynineteen\";a:6:{s:5:\"theme\";s:14:\"twentynineteen\";s:11:\"new_version\";s:3:\"3.2\";s:3:\"url\";s:44:\"https://wordpress.org/themes/twentynineteen/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/theme/twentynineteen.3.2.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentyseventeen\";a:6:{s:5:\"theme\";s:15:\"twentyseventeen\";s:11:\"new_version\";s:3:\"4.0\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentyseventeen/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentyseventeen.4.0.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:13:\"twentysixteen\";a:6:{s:5:\"theme\";s:13:\"twentysixteen\";s:11:\"new_version\";s:3:\"3.7\";s:3:\"url\";s:43:\"https://wordpress.org/themes/twentysixteen/\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/theme/twentysixteen.3.7.zip\";s:8:\"requires\";s:3:\"4.4\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:12:\"twentytwenty\";a:6:{s:5:\"theme\";s:12:\"twentytwenty\";s:11:\"new_version\";s:3:\"3.0\";s:3:\"url\";s:42:\"https://wordpress.org/themes/twentytwenty/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/theme/twentytwenty.3.0.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:16:\"twentytwentyfive\";a:6:{s:5:\"theme\";s:16:\"twentytwentyfive\";s:11:\"new_version\";s:3:\"1.4\";s:3:\"url\";s:46:\"https://wordpress.org/themes/twentytwentyfive/\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/theme/twentytwentyfive.1.4.zip\";s:8:\"requires\";s:3:\"6.7\";s:12:\"requires_php\";s:3:\"7.2\";}s:16:\"twentytwentyfour\";a:6:{s:5:\"theme\";s:16:\"twentytwentyfour\";s:11:\"new_version\";s:3:\"1.4\";s:3:\"url\";s:46:\"https://wordpress.org/themes/twentytwentyfour/\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/theme/twentytwentyfour.1.4.zip\";s:8:\"requires\";s:3:\"6.4\";s:12:\"requires_php\";s:3:\"7.0\";}}s:9:\"no_update\";a:1:{s:17:\"twentytwentythree\";a:6:{s:5:\"theme\";s:17:\"twentytwentythree\";s:11:\"new_version\";s:3:\"1.6\";s:3:\"url\";s:47:\"https://wordpress.org/themes/twentytwentythree/\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/theme/twentytwentythree.1.6.zip\";s:8:\"requires\";s:3:\"6.1\";s:12:\"requires_php\";s:3:\"5.6\";}}s:12:\"translations\";a:0:{}}','off'),(16792,'_transient_wp_core_block_css_files','a:2:{s:7:\"version\";s:5:\"6.9.4\";s:5:\"files\";a:584:{i:0;s:31:\"accordion-heading/style-rtl.css\";i:1;s:35:\"accordion-heading/style-rtl.min.css\";i:2;s:27:\"accordion-heading/style.css\";i:3;s:31:\"accordion-heading/style.min.css\";i:4;s:28:\"accordion-item/style-rtl.css\";i:5;s:32:\"accordion-item/style-rtl.min.css\";i:6;s:24:\"accordion-item/style.css\";i:7;s:28:\"accordion-item/style.min.css\";i:8;s:29:\"accordion-panel/style-rtl.css\";i:9;s:33:\"accordion-panel/style-rtl.min.css\";i:10;s:25:\"accordion-panel/style.css\";i:11;s:29:\"accordion-panel/style.min.css\";i:12;s:23:\"accordion/style-rtl.css\";i:13;s:27:\"accordion/style-rtl.min.css\";i:14;s:19:\"accordion/style.css\";i:15;s:23:\"accordion/style.min.css\";i:16;s:23:\"archives/editor-rtl.css\";i:17;s:27:\"archives/editor-rtl.min.css\";i:18;s:19:\"archives/editor.css\";i:19;s:23:\"archives/editor.min.css\";i:20;s:22:\"archives/style-rtl.css\";i:21;s:26:\"archives/style-rtl.min.css\";i:22;s:18:\"archives/style.css\";i:23;s:22:\"archives/style.min.css\";i:24;s:20:\"audio/editor-rtl.css\";i:25;s:24:\"audio/editor-rtl.min.css\";i:26;s:16:\"audio/editor.css\";i:27;s:20:\"audio/editor.min.css\";i:28;s:19:\"audio/style-rtl.css\";i:29;s:23:\"audio/style-rtl.min.css\";i:30;s:15:\"audio/style.css\";i:31;s:19:\"audio/style.min.css\";i:32;s:19:\"audio/theme-rtl.css\";i:33;s:23:\"audio/theme-rtl.min.css\";i:34;s:15:\"audio/theme.css\";i:35;s:19:\"audio/theme.min.css\";i:36;s:21:\"avatar/editor-rtl.css\";i:37;s:25:\"avatar/editor-rtl.min.css\";i:38;s:17:\"avatar/editor.css\";i:39;s:21:\"avatar/editor.min.css\";i:40;s:20:\"avatar/style-rtl.css\";i:41;s:24:\"avatar/style-rtl.min.css\";i:42;s:16:\"avatar/style.css\";i:43;s:20:\"avatar/style.min.css\";i:44;s:21:\"button/editor-rtl.css\";i:45;s:25:\"button/editor-rtl.min.css\";i:46;s:17:\"button/editor.css\";i:47;s:21:\"button/editor.min.css\";i:48;s:20:\"button/style-rtl.css\";i:49;s:24:\"button/style-rtl.min.css\";i:50;s:16:\"button/style.css\";i:51;s:20:\"button/style.min.css\";i:52;s:22:\"buttons/editor-rtl.css\";i:53;s:26:\"buttons/editor-rtl.min.css\";i:54;s:18:\"buttons/editor.css\";i:55;s:22:\"buttons/editor.min.css\";i:56;s:21:\"buttons/style-rtl.css\";i:57;s:25:\"buttons/style-rtl.min.css\";i:58;s:17:\"buttons/style.css\";i:59;s:21:\"buttons/style.min.css\";i:60;s:22:\"calendar/style-rtl.css\";i:61;s:26:\"calendar/style-rtl.min.css\";i:62;s:18:\"calendar/style.css\";i:63;s:22:\"calendar/style.min.css\";i:64;s:25:\"categories/editor-rtl.css\";i:65;s:29:\"categories/editor-rtl.min.css\";i:66;s:21:\"categories/editor.css\";i:67;s:25:\"categories/editor.min.css\";i:68;s:24:\"categories/style-rtl.css\";i:69;s:28:\"categories/style-rtl.min.css\";i:70;s:20:\"categories/style.css\";i:71;s:24:\"categories/style.min.css\";i:72;s:19:\"code/editor-rtl.css\";i:73;s:23:\"code/editor-rtl.min.css\";i:74;s:15:\"code/editor.css\";i:75;s:19:\"code/editor.min.css\";i:76;s:18:\"code/style-rtl.css\";i:77;s:22:\"code/style-rtl.min.css\";i:78;s:14:\"code/style.css\";i:79;s:18:\"code/style.min.css\";i:80;s:18:\"code/theme-rtl.css\";i:81;s:22:\"code/theme-rtl.min.css\";i:82;s:14:\"code/theme.css\";i:83;s:18:\"code/theme.min.css\";i:84;s:22:\"columns/editor-rtl.css\";i:85;s:26:\"columns/editor-rtl.min.css\";i:86;s:18:\"columns/editor.css\";i:87;s:22:\"columns/editor.min.css\";i:88;s:21:\"columns/style-rtl.css\";i:89;s:25:\"columns/style-rtl.min.css\";i:90;s:17:\"columns/style.css\";i:91;s:21:\"columns/style.min.css\";i:92;s:33:\"comment-author-name/style-rtl.css\";i:93;s:37:\"comment-author-name/style-rtl.min.css\";i:94;s:29:\"comment-author-name/style.css\";i:95;s:33:\"comment-author-name/style.min.css\";i:96;s:29:\"comment-content/style-rtl.css\";i:97;s:33:\"comment-content/style-rtl.min.css\";i:98;s:25:\"comment-content/style.css\";i:99;s:29:\"comment-content/style.min.css\";i:100;s:26:\"comment-date/style-rtl.css\";i:101;s:30:\"comment-date/style-rtl.min.css\";i:102;s:22:\"comment-date/style.css\";i:103;s:26:\"comment-date/style.min.css\";i:104;s:31:\"comment-edit-link/style-rtl.css\";i:105;s:35:\"comment-edit-link/style-rtl.min.css\";i:106;s:27:\"comment-edit-link/style.css\";i:107;s:31:\"comment-edit-link/style.min.css\";i:108;s:32:\"comment-reply-link/style-rtl.css\";i:109;s:36:\"comment-reply-link/style-rtl.min.css\";i:110;s:28:\"comment-reply-link/style.css\";i:111;s:32:\"comment-reply-link/style.min.css\";i:112;s:30:\"comment-template/style-rtl.css\";i:113;s:34:\"comment-template/style-rtl.min.css\";i:114;s:26:\"comment-template/style.css\";i:115;s:30:\"comment-template/style.min.css\";i:116;s:42:\"comments-pagination-numbers/editor-rtl.css\";i:117;s:46:\"comments-pagination-numbers/editor-rtl.min.css\";i:118;s:38:\"comments-pagination-numbers/editor.css\";i:119;s:42:\"comments-pagination-numbers/editor.min.css\";i:120;s:34:\"comments-pagination/editor-rtl.css\";i:121;s:38:\"comments-pagination/editor-rtl.min.css\";i:122;s:30:\"comments-pagination/editor.css\";i:123;s:34:\"comments-pagination/editor.min.css\";i:124;s:33:\"comments-pagination/style-rtl.css\";i:125;s:37:\"comments-pagination/style-rtl.min.css\";i:126;s:29:\"comments-pagination/style.css\";i:127;s:33:\"comments-pagination/style.min.css\";i:128;s:29:\"comments-title/editor-rtl.css\";i:129;s:33:\"comments-title/editor-rtl.min.css\";i:130;s:25:\"comments-title/editor.css\";i:131;s:29:\"comments-title/editor.min.css\";i:132;s:23:\"comments/editor-rtl.css\";i:133;s:27:\"comments/editor-rtl.min.css\";i:134;s:19:\"comments/editor.css\";i:135;s:23:\"comments/editor.min.css\";i:136;s:22:\"comments/style-rtl.css\";i:137;s:26:\"comments/style-rtl.min.css\";i:138;s:18:\"comments/style.css\";i:139;s:22:\"comments/style.min.css\";i:140;s:20:\"cover/editor-rtl.css\";i:141;s:24:\"cover/editor-rtl.min.css\";i:142;s:16:\"cover/editor.css\";i:143;s:20:\"cover/editor.min.css\";i:144;s:19:\"cover/style-rtl.css\";i:145;s:23:\"cover/style-rtl.min.css\";i:146;s:15:\"cover/style.css\";i:147;s:19:\"cover/style.min.css\";i:148;s:22:\"details/editor-rtl.css\";i:149;s:26:\"details/editor-rtl.min.css\";i:150;s:18:\"details/editor.css\";i:151;s:22:\"details/editor.min.css\";i:152;s:21:\"details/style-rtl.css\";i:153;s:25:\"details/style-rtl.min.css\";i:154;s:17:\"details/style.css\";i:155;s:21:\"details/style.min.css\";i:156;s:20:\"embed/editor-rtl.css\";i:157;s:24:\"embed/editor-rtl.min.css\";i:158;s:16:\"embed/editor.css\";i:159;s:20:\"embed/editor.min.css\";i:160;s:19:\"embed/style-rtl.css\";i:161;s:23:\"embed/style-rtl.min.css\";i:162;s:15:\"embed/style.css\";i:163;s:19:\"embed/style.min.css\";i:164;s:19:\"embed/theme-rtl.css\";i:165;s:23:\"embed/theme-rtl.min.css\";i:166;s:15:\"embed/theme.css\";i:167;s:19:\"embed/theme.min.css\";i:168;s:19:\"file/editor-rtl.css\";i:169;s:23:\"file/editor-rtl.min.css\";i:170;s:15:\"file/editor.css\";i:171;s:19:\"file/editor.min.css\";i:172;s:18:\"file/style-rtl.css\";i:173;s:22:\"file/style-rtl.min.css\";i:174;s:14:\"file/style.css\";i:175;s:18:\"file/style.min.css\";i:176;s:23:\"footnotes/style-rtl.css\";i:177;s:27:\"footnotes/style-rtl.min.css\";i:178;s:19:\"footnotes/style.css\";i:179;s:23:\"footnotes/style.min.css\";i:180;s:23:\"freeform/editor-rtl.css\";i:181;s:27:\"freeform/editor-rtl.min.css\";i:182;s:19:\"freeform/editor.css\";i:183;s:23:\"freeform/editor.min.css\";i:184;s:22:\"gallery/editor-rtl.css\";i:185;s:26:\"gallery/editor-rtl.min.css\";i:186;s:18:\"gallery/editor.css\";i:187;s:22:\"gallery/editor.min.css\";i:188;s:21:\"gallery/style-rtl.css\";i:189;s:25:\"gallery/style-rtl.min.css\";i:190;s:17:\"gallery/style.css\";i:191;s:21:\"gallery/style.min.css\";i:192;s:21:\"gallery/theme-rtl.css\";i:193;s:25:\"gallery/theme-rtl.min.css\";i:194;s:17:\"gallery/theme.css\";i:195;s:21:\"gallery/theme.min.css\";i:196;s:20:\"group/editor-rtl.css\";i:197;s:24:\"group/editor-rtl.min.css\";i:198;s:16:\"group/editor.css\";i:199;s:20:\"group/editor.min.css\";i:200;s:19:\"group/style-rtl.css\";i:201;s:23:\"group/style-rtl.min.css\";i:202;s:15:\"group/style.css\";i:203;s:19:\"group/style.min.css\";i:204;s:19:\"group/theme-rtl.css\";i:205;s:23:\"group/theme-rtl.min.css\";i:206;s:15:\"group/theme.css\";i:207;s:19:\"group/theme.min.css\";i:208;s:21:\"heading/style-rtl.css\";i:209;s:25:\"heading/style-rtl.min.css\";i:210;s:17:\"heading/style.css\";i:211;s:21:\"heading/style.min.css\";i:212;s:19:\"html/editor-rtl.css\";i:213;s:23:\"html/editor-rtl.min.css\";i:214;s:15:\"html/editor.css\";i:215;s:19:\"html/editor.min.css\";i:216;s:20:\"image/editor-rtl.css\";i:217;s:24:\"image/editor-rtl.min.css\";i:218;s:16:\"image/editor.css\";i:219;s:20:\"image/editor.min.css\";i:220;s:19:\"image/style-rtl.css\";i:221;s:23:\"image/style-rtl.min.css\";i:222;s:15:\"image/style.css\";i:223;s:19:\"image/style.min.css\";i:224;s:19:\"image/theme-rtl.css\";i:225;s:23:\"image/theme-rtl.min.css\";i:226;s:15:\"image/theme.css\";i:227;s:19:\"image/theme.min.css\";i:228;s:29:\"latest-comments/style-rtl.css\";i:229;s:33:\"latest-comments/style-rtl.min.css\";i:230;s:25:\"latest-comments/style.css\";i:231;s:29:\"latest-comments/style.min.css\";i:232;s:27:\"latest-posts/editor-rtl.css\";i:233;s:31:\"latest-posts/editor-rtl.min.css\";i:234;s:23:\"latest-posts/editor.css\";i:235;s:27:\"latest-posts/editor.min.css\";i:236;s:26:\"latest-posts/style-rtl.css\";i:237;s:30:\"latest-posts/style-rtl.min.css\";i:238;s:22:\"latest-posts/style.css\";i:239;s:26:\"latest-posts/style.min.css\";i:240;s:18:\"list/style-rtl.css\";i:241;s:22:\"list/style-rtl.min.css\";i:242;s:14:\"list/style.css\";i:243;s:18:\"list/style.min.css\";i:244;s:22:\"loginout/style-rtl.css\";i:245;s:26:\"loginout/style-rtl.min.css\";i:246;s:18:\"loginout/style.css\";i:247;s:22:\"loginout/style.min.css\";i:248;s:19:\"math/editor-rtl.css\";i:249;s:23:\"math/editor-rtl.min.css\";i:250;s:15:\"math/editor.css\";i:251;s:19:\"math/editor.min.css\";i:252;s:18:\"math/style-rtl.css\";i:253;s:22:\"math/style-rtl.min.css\";i:254;s:14:\"math/style.css\";i:255;s:18:\"math/style.min.css\";i:256;s:25:\"media-text/editor-rtl.css\";i:257;s:29:\"media-text/editor-rtl.min.css\";i:258;s:21:\"media-text/editor.css\";i:259;s:25:\"media-text/editor.min.css\";i:260;s:24:\"media-text/style-rtl.css\";i:261;s:28:\"media-text/style-rtl.min.css\";i:262;s:20:\"media-text/style.css\";i:263;s:24:\"media-text/style.min.css\";i:264;s:19:\"more/editor-rtl.css\";i:265;s:23:\"more/editor-rtl.min.css\";i:266;s:15:\"more/editor.css\";i:267;s:19:\"more/editor.min.css\";i:268;s:30:\"navigation-link/editor-rtl.css\";i:269;s:34:\"navigation-link/editor-rtl.min.css\";i:270;s:26:\"navigation-link/editor.css\";i:271;s:30:\"navigation-link/editor.min.css\";i:272;s:29:\"navigation-link/style-rtl.css\";i:273;s:33:\"navigation-link/style-rtl.min.css\";i:274;s:25:\"navigation-link/style.css\";i:275;s:29:\"navigation-link/style.min.css\";i:276;s:33:\"navigation-submenu/editor-rtl.css\";i:277;s:37:\"navigation-submenu/editor-rtl.min.css\";i:278;s:29:\"navigation-submenu/editor.css\";i:279;s:33:\"navigation-submenu/editor.min.css\";i:280;s:25:\"navigation/editor-rtl.css\";i:281;s:29:\"navigation/editor-rtl.min.css\";i:282;s:21:\"navigation/editor.css\";i:283;s:25:\"navigation/editor.min.css\";i:284;s:24:\"navigation/style-rtl.css\";i:285;s:28:\"navigation/style-rtl.min.css\";i:286;s:20:\"navigation/style.css\";i:287;s:24:\"navigation/style.min.css\";i:288;s:23:\"nextpage/editor-rtl.css\";i:289;s:27:\"nextpage/editor-rtl.min.css\";i:290;s:19:\"nextpage/editor.css\";i:291;s:23:\"nextpage/editor.min.css\";i:292;s:24:\"page-list/editor-rtl.css\";i:293;s:28:\"page-list/editor-rtl.min.css\";i:294;s:20:\"page-list/editor.css\";i:295;s:24:\"page-list/editor.min.css\";i:296;s:23:\"page-list/style-rtl.css\";i:297;s:27:\"page-list/style-rtl.min.css\";i:298;s:19:\"page-list/style.css\";i:299;s:23:\"page-list/style.min.css\";i:300;s:24:\"paragraph/editor-rtl.css\";i:301;s:28:\"paragraph/editor-rtl.min.css\";i:302;s:20:\"paragraph/editor.css\";i:303;s:24:\"paragraph/editor.min.css\";i:304;s:23:\"paragraph/style-rtl.css\";i:305;s:27:\"paragraph/style-rtl.min.css\";i:306;s:19:\"paragraph/style.css\";i:307;s:23:\"paragraph/style.min.css\";i:308;s:35:\"post-author-biography/style-rtl.css\";i:309;s:39:\"post-author-biography/style-rtl.min.css\";i:310;s:31:\"post-author-biography/style.css\";i:311;s:35:\"post-author-biography/style.min.css\";i:312;s:30:\"post-author-name/style-rtl.css\";i:313;s:34:\"post-author-name/style-rtl.min.css\";i:314;s:26:\"post-author-name/style.css\";i:315;s:30:\"post-author-name/style.min.css\";i:316;s:25:\"post-author/style-rtl.css\";i:317;s:29:\"post-author/style-rtl.min.css\";i:318;s:21:\"post-author/style.css\";i:319;s:25:\"post-author/style.min.css\";i:320;s:33:\"post-comments-count/style-rtl.css\";i:321;s:37:\"post-comments-count/style-rtl.min.css\";i:322;s:29:\"post-comments-count/style.css\";i:323;s:33:\"post-comments-count/style.min.css\";i:324;s:33:\"post-comments-form/editor-rtl.css\";i:325;s:37:\"post-comments-form/editor-rtl.min.css\";i:326;s:29:\"post-comments-form/editor.css\";i:327;s:33:\"post-comments-form/editor.min.css\";i:328;s:32:\"post-comments-form/style-rtl.css\";i:329;s:36:\"post-comments-form/style-rtl.min.css\";i:330;s:28:\"post-comments-form/style.css\";i:331;s:32:\"post-comments-form/style.min.css\";i:332;s:32:\"post-comments-link/style-rtl.css\";i:333;s:36:\"post-comments-link/style-rtl.min.css\";i:334;s:28:\"post-comments-link/style.css\";i:335;s:32:\"post-comments-link/style.min.css\";i:336;s:26:\"post-content/style-rtl.css\";i:337;s:30:\"post-content/style-rtl.min.css\";i:338;s:22:\"post-content/style.css\";i:339;s:26:\"post-content/style.min.css\";i:340;s:23:\"post-date/style-rtl.css\";i:341;s:27:\"post-date/style-rtl.min.css\";i:342;s:19:\"post-date/style.css\";i:343;s:23:\"post-date/style.min.css\";i:344;s:27:\"post-excerpt/editor-rtl.css\";i:345;s:31:\"post-excerpt/editor-rtl.min.css\";i:346;s:23:\"post-excerpt/editor.css\";i:347;s:27:\"post-excerpt/editor.min.css\";i:348;s:26:\"post-excerpt/style-rtl.css\";i:349;s:30:\"post-excerpt/style-rtl.min.css\";i:350;s:22:\"post-excerpt/style.css\";i:351;s:26:\"post-excerpt/style.min.css\";i:352;s:34:\"post-featured-image/editor-rtl.css\";i:353;s:38:\"post-featured-image/editor-rtl.min.css\";i:354;s:30:\"post-featured-image/editor.css\";i:355;s:34:\"post-featured-image/editor.min.css\";i:356;s:33:\"post-featured-image/style-rtl.css\";i:357;s:37:\"post-featured-image/style-rtl.min.css\";i:358;s:29:\"post-featured-image/style.css\";i:359;s:33:\"post-featured-image/style.min.css\";i:360;s:34:\"post-navigation-link/style-rtl.css\";i:361;s:38:\"post-navigation-link/style-rtl.min.css\";i:362;s:30:\"post-navigation-link/style.css\";i:363;s:34:\"post-navigation-link/style.min.css\";i:364;s:27:\"post-template/style-rtl.css\";i:365;s:31:\"post-template/style-rtl.min.css\";i:366;s:23:\"post-template/style.css\";i:367;s:27:\"post-template/style.min.css\";i:368;s:24:\"post-terms/style-rtl.css\";i:369;s:28:\"post-terms/style-rtl.min.css\";i:370;s:20:\"post-terms/style.css\";i:371;s:24:\"post-terms/style.min.css\";i:372;s:31:\"post-time-to-read/style-rtl.css\";i:373;s:35:\"post-time-to-read/style-rtl.min.css\";i:374;s:27:\"post-time-to-read/style.css\";i:375;s:31:\"post-time-to-read/style.min.css\";i:376;s:24:\"post-title/style-rtl.css\";i:377;s:28:\"post-title/style-rtl.min.css\";i:378;s:20:\"post-title/style.css\";i:379;s:24:\"post-title/style.min.css\";i:380;s:26:\"preformatted/style-rtl.css\";i:381;s:30:\"preformatted/style-rtl.min.css\";i:382;s:22:\"preformatted/style.css\";i:383;s:26:\"preformatted/style.min.css\";i:384;s:24:\"pullquote/editor-rtl.css\";i:385;s:28:\"pullquote/editor-rtl.min.css\";i:386;s:20:\"pullquote/editor.css\";i:387;s:24:\"pullquote/editor.min.css\";i:388;s:23:\"pullquote/style-rtl.css\";i:389;s:27:\"pullquote/style-rtl.min.css\";i:390;s:19:\"pullquote/style.css\";i:391;s:23:\"pullquote/style.min.css\";i:392;s:23:\"pullquote/theme-rtl.css\";i:393;s:27:\"pullquote/theme-rtl.min.css\";i:394;s:19:\"pullquote/theme.css\";i:395;s:23:\"pullquote/theme.min.css\";i:396;s:39:\"query-pagination-numbers/editor-rtl.css\";i:397;s:43:\"query-pagination-numbers/editor-rtl.min.css\";i:398;s:35:\"query-pagination-numbers/editor.css\";i:399;s:39:\"query-pagination-numbers/editor.min.css\";i:400;s:31:\"query-pagination/editor-rtl.css\";i:401;s:35:\"query-pagination/editor-rtl.min.css\";i:402;s:27:\"query-pagination/editor.css\";i:403;s:31:\"query-pagination/editor.min.css\";i:404;s:30:\"query-pagination/style-rtl.css\";i:405;s:34:\"query-pagination/style-rtl.min.css\";i:406;s:26:\"query-pagination/style.css\";i:407;s:30:\"query-pagination/style.min.css\";i:408;s:25:\"query-title/style-rtl.css\";i:409;s:29:\"query-title/style-rtl.min.css\";i:410;s:21:\"query-title/style.css\";i:411;s:25:\"query-title/style.min.css\";i:412;s:25:\"query-total/style-rtl.css\";i:413;s:29:\"query-total/style-rtl.min.css\";i:414;s:21:\"query-total/style.css\";i:415;s:25:\"query-total/style.min.css\";i:416;s:20:\"query/editor-rtl.css\";i:417;s:24:\"query/editor-rtl.min.css\";i:418;s:16:\"query/editor.css\";i:419;s:20:\"query/editor.min.css\";i:420;s:19:\"quote/style-rtl.css\";i:421;s:23:\"quote/style-rtl.min.css\";i:422;s:15:\"quote/style.css\";i:423;s:19:\"quote/style.min.css\";i:424;s:19:\"quote/theme-rtl.css\";i:425;s:23:\"quote/theme-rtl.min.css\";i:426;s:15:\"quote/theme.css\";i:427;s:19:\"quote/theme.min.css\";i:428;s:23:\"read-more/style-rtl.css\";i:429;s:27:\"read-more/style-rtl.min.css\";i:430;s:19:\"read-more/style.css\";i:431;s:23:\"read-more/style.min.css\";i:432;s:18:\"rss/editor-rtl.css\";i:433;s:22:\"rss/editor-rtl.min.css\";i:434;s:14:\"rss/editor.css\";i:435;s:18:\"rss/editor.min.css\";i:436;s:17:\"rss/style-rtl.css\";i:437;s:21:\"rss/style-rtl.min.css\";i:438;s:13:\"rss/style.css\";i:439;s:17:\"rss/style.min.css\";i:440;s:21:\"search/editor-rtl.css\";i:441;s:25:\"search/editor-rtl.min.css\";i:442;s:17:\"search/editor.css\";i:443;s:21:\"search/editor.min.css\";i:444;s:20:\"search/style-rtl.css\";i:445;s:24:\"search/style-rtl.min.css\";i:446;s:16:\"search/style.css\";i:447;s:20:\"search/style.min.css\";i:448;s:20:\"search/theme-rtl.css\";i:449;s:24:\"search/theme-rtl.min.css\";i:450;s:16:\"search/theme.css\";i:451;s:20:\"search/theme.min.css\";i:452;s:24:\"separator/editor-rtl.css\";i:453;s:28:\"separator/editor-rtl.min.css\";i:454;s:20:\"separator/editor.css\";i:455;s:24:\"separator/editor.min.css\";i:456;s:23:\"separator/style-rtl.css\";i:457;s:27:\"separator/style-rtl.min.css\";i:458;s:19:\"separator/style.css\";i:459;s:23:\"separator/style.min.css\";i:460;s:23:\"separator/theme-rtl.css\";i:461;s:27:\"separator/theme-rtl.min.css\";i:462;s:19:\"separator/theme.css\";i:463;s:23:\"separator/theme.min.css\";i:464;s:24:\"shortcode/editor-rtl.css\";i:465;s:28:\"shortcode/editor-rtl.min.css\";i:466;s:20:\"shortcode/editor.css\";i:467;s:24:\"shortcode/editor.min.css\";i:468;s:24:\"site-logo/editor-rtl.css\";i:469;s:28:\"site-logo/editor-rtl.min.css\";i:470;s:20:\"site-logo/editor.css\";i:471;s:24:\"site-logo/editor.min.css\";i:472;s:23:\"site-logo/style-rtl.css\";i:473;s:27:\"site-logo/style-rtl.min.css\";i:474;s:19:\"site-logo/style.css\";i:475;s:23:\"site-logo/style.min.css\";i:476;s:27:\"site-tagline/editor-rtl.css\";i:477;s:31:\"site-tagline/editor-rtl.min.css\";i:478;s:23:\"site-tagline/editor.css\";i:479;s:27:\"site-tagline/editor.min.css\";i:480;s:26:\"site-tagline/style-rtl.css\";i:481;s:30:\"site-tagline/style-rtl.min.css\";i:482;s:22:\"site-tagline/style.css\";i:483;s:26:\"site-tagline/style.min.css\";i:484;s:25:\"site-title/editor-rtl.css\";i:485;s:29:\"site-title/editor-rtl.min.css\";i:486;s:21:\"site-title/editor.css\";i:487;s:25:\"site-title/editor.min.css\";i:488;s:24:\"site-title/style-rtl.css\";i:489;s:28:\"site-title/style-rtl.min.css\";i:490;s:20:\"site-title/style.css\";i:491;s:24:\"site-title/style.min.css\";i:492;s:26:\"social-link/editor-rtl.css\";i:493;s:30:\"social-link/editor-rtl.min.css\";i:494;s:22:\"social-link/editor.css\";i:495;s:26:\"social-link/editor.min.css\";i:496;s:27:\"social-links/editor-rtl.css\";i:497;s:31:\"social-links/editor-rtl.min.css\";i:498;s:23:\"social-links/editor.css\";i:499;s:27:\"social-links/editor.min.css\";i:500;s:26:\"social-links/style-rtl.css\";i:501;s:30:\"social-links/style-rtl.min.css\";i:502;s:22:\"social-links/style.css\";i:503;s:26:\"social-links/style.min.css\";i:504;s:21:\"spacer/editor-rtl.css\";i:505;s:25:\"spacer/editor-rtl.min.css\";i:506;s:17:\"spacer/editor.css\";i:507;s:21:\"spacer/editor.min.css\";i:508;s:20:\"spacer/style-rtl.css\";i:509;s:24:\"spacer/style-rtl.min.css\";i:510;s:16:\"spacer/style.css\";i:511;s:20:\"spacer/style.min.css\";i:512;s:20:\"table/editor-rtl.css\";i:513;s:24:\"table/editor-rtl.min.css\";i:514;s:16:\"table/editor.css\";i:515;s:20:\"table/editor.min.css\";i:516;s:19:\"table/style-rtl.css\";i:517;s:23:\"table/style-rtl.min.css\";i:518;s:15:\"table/style.css\";i:519;s:19:\"table/style.min.css\";i:520;s:19:\"table/theme-rtl.css\";i:521;s:23:\"table/theme-rtl.min.css\";i:522;s:15:\"table/theme.css\";i:523;s:19:\"table/theme.min.css\";i:524;s:24:\"tag-cloud/editor-rtl.css\";i:525;s:28:\"tag-cloud/editor-rtl.min.css\";i:526;s:20:\"tag-cloud/editor.css\";i:527;s:24:\"tag-cloud/editor.min.css\";i:528;s:23:\"tag-cloud/style-rtl.css\";i:529;s:27:\"tag-cloud/style-rtl.min.css\";i:530;s:19:\"tag-cloud/style.css\";i:531;s:23:\"tag-cloud/style.min.css\";i:532;s:28:\"template-part/editor-rtl.css\";i:533;s:32:\"template-part/editor-rtl.min.css\";i:534;s:24:\"template-part/editor.css\";i:535;s:28:\"template-part/editor.min.css\";i:536;s:27:\"template-part/theme-rtl.css\";i:537;s:31:\"template-part/theme-rtl.min.css\";i:538;s:23:\"template-part/theme.css\";i:539;s:27:\"template-part/theme.min.css\";i:540;s:24:\"term-count/style-rtl.css\";i:541;s:28:\"term-count/style-rtl.min.css\";i:542;s:20:\"term-count/style.css\";i:543;s:24:\"term-count/style.min.css\";i:544;s:30:\"term-description/style-rtl.css\";i:545;s:34:\"term-description/style-rtl.min.css\";i:546;s:26:\"term-description/style.css\";i:547;s:30:\"term-description/style.min.css\";i:548;s:23:\"term-name/style-rtl.css\";i:549;s:27:\"term-name/style-rtl.min.css\";i:550;s:19:\"term-name/style.css\";i:551;s:23:\"term-name/style.min.css\";i:552;s:28:\"term-template/editor-rtl.css\";i:553;s:32:\"term-template/editor-rtl.min.css\";i:554;s:24:\"term-template/editor.css\";i:555;s:28:\"term-template/editor.min.css\";i:556;s:27:\"term-template/style-rtl.css\";i:557;s:31:\"term-template/style-rtl.min.css\";i:558;s:23:\"term-template/style.css\";i:559;s:27:\"term-template/style.min.css\";i:560;s:27:\"text-columns/editor-rtl.css\";i:561;s:31:\"text-columns/editor-rtl.min.css\";i:562;s:23:\"text-columns/editor.css\";i:563;s:27:\"text-columns/editor.min.css\";i:564;s:26:\"text-columns/style-rtl.css\";i:565;s:30:\"text-columns/style-rtl.min.css\";i:566;s:22:\"text-columns/style.css\";i:567;s:26:\"text-columns/style.min.css\";i:568;s:19:\"verse/style-rtl.css\";i:569;s:23:\"verse/style-rtl.min.css\";i:570;s:15:\"verse/style.css\";i:571;s:19:\"verse/style.min.css\";i:572;s:20:\"video/editor-rtl.css\";i:573;s:24:\"video/editor-rtl.min.css\";i:574;s:16:\"video/editor.css\";i:575;s:20:\"video/editor.min.css\";i:576;s:19:\"video/style-rtl.css\";i:577;s:23:\"video/style-rtl.min.css\";i:578;s:15:\"video/style.css\";i:579;s:19:\"video/style.min.css\";i:580;s:19:\"video/theme-rtl.css\";i:581;s:23:\"video/theme-rtl.min.css\";i:582;s:15:\"video/theme.css\";i:583;s:19:\"video/theme.min.css\";}}','on'),(16357,'finished_updating_comment_type','1','auto'),(18585,'wp_page_for_privacy_policy','0','on'),(18586,'show_comments_cookies_opt_in','1','on'),(18587,'admin_email_lifespan','0','on'),(18588,'disallowed_keys','','off'),(18589,'comment_previously_approved','1','on'),(18590,'auto_plugin_theme_update_emails','a:0:{}','off'),(18591,'auto_update_core_dev','enabled','on'),(18592,'auto_update_core_minor','enabled','on'),(18593,'auto_update_core_major','unset','on'),(18594,'wp_force_deactivated_plugins','a:0:{}','off'),(18595,'wp_attachment_pages_enabled','1','on'),(18596,'wp_notes_notify','1','on');
/*!40000 ALTER TABLE `swd_options` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `swd_postmeta`
--
DROP TABLE IF EXISTS `swd_postmeta`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `swd_postmeta` (
`meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`post_id` bigint(20) unsigned NOT NULL DEFAULT '0',
`meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
`meta_value` longtext COLLATE utf8mb4_unicode_520_ci,
PRIMARY KEY (`meta_id`),
KEY `post_id` (`post_id`),
KEY `meta_key` (`meta_key`(191))
) ENGINE=MyISAM AUTO_INCREMENT=165 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `swd_postmeta`
--
LOCK TABLES `swd_postmeta` WRITE;
/*!40000 ALTER TABLE `swd_postmeta` DISABLE KEYS */;
INSERT INTO `swd_postmeta` VALUES (1,2,'_wp_page_template','full-width-page.php'),(2,2,'_edit_lock','1512011648:1'),(3,2,'_edit_last','1'),(4,2,'_responsive_layout','default'),(5,6,'_edit_last','1'),(6,6,'_edit_lock','1512691156:1'),(7,6,'_wp_page_template','full-width-page.php'),(8,6,'_responsive_layout','default'),(9,9,'_edit_last','1'),(10,9,'_wp_page_template','full-width-page.php'),(11,9,'_responsive_layout','default'),(12,9,'_edit_lock','1512686536:1'),(13,12,'_edit_last','1'),(14,12,'_edit_lock','1512690497:1'),(15,12,'_wp_page_template','full-width-page.php'),(16,12,'_responsive_layout','default'),(19,17,'_edit_last','1'),(20,17,'_edit_lock','1512972840:1'),(21,17,'_wp_page_template','full-width-page.php'),(22,17,'_responsive_layout','default'),(23,19,'_edit_last','1'),(24,19,'_edit_lock','1512973540:1'),(25,19,'_wp_page_template','full-width-page.php'),(26,19,'_responsive_layout','default'),(27,22,'_edit_last','1'),(28,22,'_wp_page_template','full-width-page.php'),(29,22,'_responsive_layout','default'),(30,22,'_edit_lock','1513903124:1'),(31,24,'_edit_last','1'),(32,24,'_wp_page_template','default'),(33,24,'_responsive_layout','default'),(34,24,'_edit_lock','1513903801:1'),(35,26,'_menu_item_type','custom'),(36,26,'_menu_item_menu_item_parent','0'),(37,26,'_menu_item_object_id','26'),(38,26,'_menu_item_object','custom'),(39,26,'_menu_item_target',''),(40,26,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(41,26,'_menu_item_xfn',''),(42,26,'_menu_item_url','#'),(44,27,'_menu_item_type','post_type'),(45,27,'_menu_item_menu_item_parent','26'),(46,27,'_menu_item_object_id','24'),(47,27,'_menu_item_object','page'),(48,27,'_menu_item_target',''),(49,27,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(50,27,'_menu_item_xfn',''),(51,27,'_menu_item_url',''),(53,28,'_menu_item_type','post_type'),(54,28,'_menu_item_menu_item_parent','26'),(55,28,'_menu_item_object_id','22'),(56,28,'_menu_item_object','page'),(57,28,'_menu_item_target',''),(58,28,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(59,28,'_menu_item_xfn',''),(60,28,'_menu_item_url',''),(62,29,'_menu_item_type','post_type'),(63,29,'_menu_item_menu_item_parent','0'),(64,29,'_menu_item_object_id','6'),(65,29,'_menu_item_object','page'),(66,29,'_menu_item_target',''),(67,29,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(68,29,'_menu_item_xfn',''),(69,29,'_menu_item_url',''),(71,30,'_menu_item_type','post_type'),(72,30,'_menu_item_menu_item_parent','29'),(73,30,'_menu_item_object_id','12'),(74,30,'_menu_item_object','page'),(75,30,'_menu_item_target',''),(76,30,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(77,30,'_menu_item_xfn',''),(78,30,'_menu_item_url',''),(80,31,'_menu_item_type','post_type'),(81,31,'_menu_item_menu_item_parent','29'),(82,31,'_menu_item_object_id','9'),(83,31,'_menu_item_object','page'),(84,31,'_menu_item_target',''),(85,31,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(86,31,'_menu_item_xfn',''),(87,31,'_menu_item_url',''),(89,32,'_menu_item_type','post_type'),(90,32,'_menu_item_menu_item_parent','0'),(91,32,'_menu_item_object_id','19'),(92,32,'_menu_item_object','page'),(93,32,'_menu_item_target',''),(94,32,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(95,32,'_menu_item_xfn',''),(96,32,'_menu_item_url',''),(97,33,'_edit_last','1'),(98,33,'_edit_lock','1514063915:1'),(99,33,'_wp_page_template','full-width-page.php'),(100,33,'_responsive_layout','default'),(101,36,'_menu_item_type','post_type'),(102,36,'_menu_item_menu_item_parent','39'),(103,36,'_menu_item_object_id','33'),(104,36,'_menu_item_object','page'),(105,36,'_menu_item_target',''),(106,36,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(107,36,'_menu_item_xfn',''),(108,36,'_menu_item_url',''),(110,37,'_edit_last','1'),(111,37,'_edit_lock','1514068895:1'),(112,37,'_wp_page_template','default'),(113,37,'_responsive_layout','default'),(114,39,'_menu_item_type','custom'),(115,39,'_menu_item_menu_item_parent','0'),(116,39,'_menu_item_object_id','39'),(117,39,'_menu_item_object','custom'),(118,39,'_menu_item_target',''),(119,39,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(120,39,'_menu_item_xfn',''),(121,39,'_menu_item_url','#'),(123,40,'_menu_item_type','post_type'),(124,40,'_menu_item_menu_item_parent','39'),(125,40,'_menu_item_object_id','37'),(126,40,'_menu_item_object','page'),(127,40,'_menu_item_target',''),(128,40,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(129,40,'_menu_item_xfn',''),(130,40,'_menu_item_url',''),(131,42,'_menu_item_type','custom'),(132,42,'_menu_item_menu_item_parent','0'),(133,42,'_menu_item_object_id','42'),(134,42,'_menu_item_object','custom'),(135,42,'_menu_item_target',''),(136,42,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(137,42,'_menu_item_xfn',''),(138,42,'_menu_item_url','#'),(140,43,'_edit_last','1'),(141,43,'_edit_lock','1522982181:1'),(142,43,'_wp_page_template','default'),(143,43,'_responsive_layout','default'),(144,45,'_menu_item_type','post_type'),(145,45,'_menu_item_menu_item_parent','42'),(146,45,'_menu_item_object_id','43'),(147,45,'_menu_item_object','page'),(148,45,'_menu_item_target',''),(149,45,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(150,45,'_menu_item_xfn',''),(151,45,'_menu_item_url',''),(153,46,'_edit_last','1'),(154,46,'_edit_lock','1522982711:1'),(155,46,'_wp_page_template','default'),(156,46,'_responsive_layout','default'),(157,48,'_menu_item_type','post_type'),(158,48,'_menu_item_menu_item_parent','42'),(159,48,'_menu_item_object_id','46'),(160,48,'_menu_item_object','page'),(161,48,'_menu_item_target',''),(162,48,'_menu_item_classes','a:1:{i:0;s:0:\"\";}'),(163,48,'_menu_item_xfn',''),(164,48,'_menu_item_url','');
/*!40000 ALTER TABLE `swd_postmeta` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `swd_posts`
--
DROP TABLE IF EXISTS `swd_posts`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `swd_posts` (
`ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`post_author` bigint(20) unsigned NOT NULL DEFAULT '0',
`post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`post_content` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`post_title` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
`post_excerpt` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
`post_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'publish',
`comment_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open',
`ping_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open',
`post_password` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`post_name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`to_ping` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
`pinged` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
`post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`post_content_filtered` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`post_parent` bigint(20) unsigned NOT NULL DEFAULT '0',
`guid` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`menu_order` int(11) NOT NULL DEFAULT '0',
`post_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'post',
`post_mime_type` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`comment_count` bigint(20) NOT NULL DEFAULT '0',
PRIMARY KEY (`ID`),
KEY `post_name` (`post_name`(191)),
KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`),
KEY `post_parent` (`post_parent`),
KEY `post_author` (`post_author`),
KEY `type_status_author` (`post_type`,`post_status`,`post_author`)
) ENGINE=MyISAM AUTO_INCREMENT=50 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `swd_posts`
--
LOCK TABLES `swd_posts` WRITE;
/*!40000 ALTER TABLE `swd_posts` DISABLE KEYS */;
INSERT INTO `swd_posts` VALUES (1,1,'2017-02-08 03:46:34','2017-02-08 03:46:34','Welcome to WordPress. This is your first post. Edit or delete it, then start writing!','Hello world!','','publish','open','open','','hello-world','','','2017-02-08 03:46:34','2017-02-08 03:46:34','',0,'http://www.acctcrop.softwarewebdesign.com/?p=1',0,'post','',1),(2,1,'2017-02-08 03:46:34','2017-02-08 03:46:34',' \r\n\r\nWordPress File Lock – Lock index.php, .htaccess files, wp-config.php and wp-blog-header.php With Read Only Permissions\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n\r\n404 File Permissions\r\n\r\n.htaccess files should have 404 File Permissions\r\n\r\nOwner Permissions – Read On – Write X – Execute X\r\nGroup Permissions – Read X – Write X – Execute X\r\nPublic Permissions – Read On – Write X – Execute X\r\n\r\n400 File Permissions\r\n\r\nindex.php, wp-config.php and wp-blog-header.php should have 400 File Permissions\r\n\r\nOwner Permissions – Read On – Write X – Execute X\r\nGroup Permissions – Read X – Write X – Execute X\r\nPublic Permissions – Read X – Write X – Execute X\r\n\r\n
@media screen and (min-width: 981px) { .menu { text-align:center } .menu li { display:inline-block; float:none; margin-left: -5px; } .menu li li { display:block; text-align:left } }
','Center menu','','inherit','closed','closed','','6-revision-v1','','','2017-12-07 05:48:28','2017-12-07 05:48:28','',6,'http://www.acctcrop.softwarewebdesign.com/2017/12/07/6-revision-v1/',0,'revision','',0),(5,1,'2017-10-12 01:00:24','2017-10-12 01:00:24',' \r\n\r\nWordPress File Lock – Lock index.php, .htaccess files, wp-config.php and wp-blog-header.php With Read Only Permissions\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n\r\n404 File Permissions\r\n\r\n.htaccess files should have 404 File Permissions\r\n\r\nOwner Permissions – Read On – Write X – Execute X\r\nGroup Permissions – Read X – Write X – Execute X\r\nPublic Permissions – Read On – Write X – Execute X\r\n\r\n400 File Permissions\r\n\r\nindex.php, wp-config.php and wp-blog-header.php should have 400 File Permissions\r\n\r\nOwner Permissions – Read On – Write X – Execute X\r\nGroup Permissions – Read X – Write X – Execute X\r\nPublic Permissions – Read X – Write X – Execute X\r\n\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n ','FILE PERMISSIONS','','inherit','closed','closed','','2-revision-v1','','','2017-10-12 01:00:24','2017-10-12 01:00:24','',2,'http://www.acctcrop.softwarewebdesign.com/2017/10/12/2-revision-v1/',0,'revision','',0),(4,1,'2017-10-12 00:59:55','2017-10-12 00:59:55',' \r\n\r\nWordPress File Lock – Lock index.php, .htaccess files, wp-config.php and wp-blog-header.php With Read Only Permissions\r\n\r\n \r\n\r\n \r\n\r\n \r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n\r\n404 File Permissions\r\n\r\n.htaccess files should have 404 File Permissions\r\n\r\nOwner Permissions – Read On – Write X – Execute X\r\nGroup Permissions – Read X – Write X – Execute X\r\nPublic Permissions – Read On – Write X – Execute X\r\n\r\n400 File Permissions\r\n\r\nindex.php, wp-config.php and wp-blog-header.php should have 400 File Permissions\r\n\r\nOwner Permissions – Read On – Write X – Execute X\r\nGroup Permissions – Read X – Write X – Execute X\r\nPublic Permissions – Read X – Write X – Execute X\r\n\r\n
','responsive theme nav color change','','publish','closed','closed','','responsive-theme-nav-color-change','','','2017-12-07 22:44:35','2017-12-07 22:44:35','',6,'http://www.acctcrop.softwarewebdesign.com/?page_id=9',0,'page','',0),(10,1,'2017-12-07 22:13:40','2017-12-07 22:13:40','
','responsive theme nav color change','','inherit','closed','closed','','9-revision-v1','','','2017-12-07 22:13:40','2017-12-07 22:13:40','',9,'http://www.acctcrop.softwarewebdesign.com/2017/12/07/9-revision-v1/',0,'revision','',0),(11,1,'2017-12-07 22:44:35','2017-12-07 22:44:35','
','responsive theme nav color change','','inherit','closed','closed','','9-revision-v1','','','2017-12-07 22:44:35','2017-12-07 22:44:35','',9,'http://www.acctcrop.softwarewebdesign.com/2017/12/07/9-revision-v1/',0,'revision','',0),(12,1,'2017-12-07 23:49:42','2017-12-07 23:49:42','
In this post I’ll discuss the HTTP headers we can use to improve a web site’s security and mitigate certain attack types. I’ll use this blag as my example.
First up we’ll look at X-Frame-Options. This header helps prevent clickjacking by indicating to a browser that it shouldn’t render the page in a frame (or an iframe or object). We’ll use the strictest setting: DENY. Here’s how to set it in .htaccess:
X-XSS-Protection helps mitigate Cross-site scripting (XSS) attacks. We’ll use the strictest setting again here: “1; blockâ€. This will instruct IE to not even render the page if it detects an XSS attack.
X-Content-Type-Options only has one value—“nosniffâ€â€”which instructs IE not to sniff mime types, preventing attacks related to mime-sniffing. You should be fine to use this header unless you’re serving files with bad Content-Type headers (don’t do that).
Here’s what we need to add to .htaccess for these two headers:
1
2
Header set X-XSS-Protection \"1; mode=block\"
Header set X-Content-Type-Options nosniff
Now we’ll take a look at HTTP Strict Transport Security (HSTS). HSTS is a way for the server to instruct the browser that it (the browser) should only communicate with the server over HTTPS. This helps avoid man-in-the-middle attacks over insecure HTTP. The first thing we need to do is ensure that we’re redirecting all HTTP connections to the equivalent HTTPS URL. Here’s one way to achieve that in .htaccess:
Now we can set the HSTS header. I’m using a max-age equivalent to 30 days.
1
Header set Strict-Transport-Security \"max-age=2592000\" env=HTTPS
We must not send this header over plain HTTP, so we add env=HTTPS.
Next we’ll implement the Content Security Policy (CSP) header. CSP helps mitigate XSS attacks by whitelisting the allowed sources of content such as scripts, styles and images. Using WordPress 3.9.1, Accessible Zen 1.1.3 and Crayon 2.6.5, this is as tight as I could make the CSP header for this blag. I’ve inserted line breaks for readability.
We block all objects (such as Flash) with object-src ‘none’. Good riddance.
We unfortunately have to allow inline scripts and styles using ‘unsafe-inline’ for both script-src and style-src.
We only allow https and data schemes, we don’t allow any insecure http.
Finally we’ll look at X-Permitted-Cross-Domain-Policies. Setting this header to “master-only†will instruct Flash and PDF files that they should only read the master crossdomain.xml file from the root of the website.
1
Header set X-Permitted-Cross-Domain-Policies \"master-only\"
Here’s everything we’ve added to .htaccess so far:
Unfortunately, something in the WordPress backend uses eval, so we have to include the ‘unsafe-eval’ source in our CSP script-src directive. Fortunately, we can get away with only including ‘unsafe-eval’ in an .htaccess in the wp-admin directory. This setup allows eval in the WordPress backend but blocks it for frontend pages. The CSP header in wp-admin’s .htaccess adds ‘unsafe-eval’ but is otherwise identical to that in the root .htaccess:
And that’s it for security headers on danielnixon.org. With the unfortunate exception of those unsafe-inline and unsafe-eval sources in the CSP header, these six headers lock things down pretty well. It’s worth stressing that none of this is a replacement for writing secure code in the first place; think of these headers as just another layer of protection.
As an aside, Play Framework’s SecurityHeadersFilter provides all the above (except HSTS), with each header defaulting to a secure default value.
While we’re on the topic of HTTP headers and security, there are also some headers that should be removed. Server and X-Powered-By are two common headers that reveal information about a website that could be useful to attackers, so we should remove them if we can. Unfortunately, we’re stuck with the Server header on Apache. What we can do is shrink it down to simply “Apacheâ€, omitting the Apache version, the OS, the OS version, etc.
You can test your own site’s security headers at https://securityheaders.com/. This site scores 90%, with that pesky Server: Apache header costing me 10%. Maybe you can beat me?
6 thoughts on “HTTP Security Headersâ€
Hi,
Thank for your article, i already implement to my website except the “Content-Security-Policy†part.
You should use apache httpd’s “Header always set†otherwise in case of HTTP status > 200 the headers aren’t set and someone can still exploit you by finding an 400 bad request/500 internal server error – which is very easy in apache.
In this post I’ll discuss the HTTP headers we can use to improve a web site’s security and mitigate certain attack types. I’ll use this blag as my example.
First up we’ll look at X-Frame-Options. This header helps prevent clickjacking by indicating to a browser that it shouldn’t render the page in a frame (or an iframe or object). We’ll use the strictest setting: DENY. Here’s how to set it in .htaccess:
X-XSS-Protection helps mitigate Cross-site scripting (XSS) attacks. We’ll use the strictest setting again here: “1; blockâ€. This will instruct IE to not even render the page if it detects an XSS attack.
X-Content-Type-Options only has one value—“nosniffâ€â€”which instructs IE not to sniff mime types, preventing attacks related to mime-sniffing. You should be fine to use this header unless you’re serving files with bad Content-Type headers (don’t do that).
Here’s what we need to add to .htaccess for these two headers:
1
2
Header set X-XSS-Protection \"1; mode=block\"
Header set X-Content-Type-Options nosniff
Now we’ll take a look at HTTP Strict Transport Security (HSTS). HSTS is a way for the server to instruct the browser that it (the browser) should only communicate with the server over HTTPS. This helps avoid man-in-the-middle attacks over insecure HTTP. The first thing we need to do is ensure that we’re redirecting all HTTP connections to the equivalent HTTPS URL. Here’s one way to achieve that in .htaccess:
Now we can set the HSTS header. I’m using a max-age equivalent to 30 days.
1
Header set Strict-Transport-Security \"max-age=2592000\" env=HTTPS
We must not send this header over plain HTTP, so we add env=HTTPS.
Next we’ll implement the Content Security Policy (CSP) header. CSP helps mitigate XSS attacks by whitelisting the allowed sources of content such as scripts, styles and images. Using WordPress 3.9.1, Accessible Zen 1.1.3 and Crayon 2.6.5, this is as tight as I could make the CSP header for this blag. I’ve inserted line breaks for readability.
We block all objects (such as Flash) with object-src ‘none’. Good riddance.
We unfortunately have to allow inline scripts and styles using ‘unsafe-inline’ for both script-src and style-src.
We only allow https and data schemes, we don’t allow any insecure http.
Finally we’ll look at X-Permitted-Cross-Domain-Policies. Setting this header to “master-only†will instruct Flash and PDF files that they should only read the master crossdomain.xml file from the root of the website.
1
Header set X-Permitted-Cross-Domain-Policies \"master-only\"
Here’s everything we’ve added to .htaccess so far:
Unfortunately, something in the WordPress backend uses eval, so we have to include the ‘unsafe-eval’ source in our CSP script-src directive. Fortunately, we can get away with only including ‘unsafe-eval’ in an .htaccess in the wp-admin directory. This setup allows eval in the WordPress backend but blocks it for frontend pages. The CSP header in wp-admin’s .htaccess adds ‘unsafe-eval’ but is otherwise identical to that in the root .htaccess:
And that’s it for security headers on danielnixon.org. With the unfortunate exception of those unsafe-inline and unsafe-eval sources in the CSP header, these six headers lock things down pretty well. It’s worth stressing that none of this is a replacement for writing secure code in the first place; think of these headers as just another layer of protection.
As an aside, Play Framework’s SecurityHeadersFilter provides all the above (except HSTS), with each header defaulting to a secure default value.
While we’re on the topic of HTTP headers and security, there are also some headers that should be removed. Server and X-Powered-By are two common headers that reveal information about a website that could be useful to attackers, so we should remove them if we can. Unfortunately, we’re stuck with the Server header on Apache. What we can do is shrink it down to simply “Apacheâ€, omitting the Apache version, the OS, the OS version, etc.
You can test your own site’s security headers at https://securityheaders.com/. This site scores 90%, with that pesky Server: Apache header costing me 10%. Maybe you can beat me?
6 thoughts on “HTTP Security Headersâ€
Hi,
Thank for your article, i already implement to my website except the “Content-Security-Policy†part.
You should use apache httpd’s “Header always set†otherwise in case of HTTP status > 200 the headers aren’t set and someone can still exploit you by finding an 400 bad request/500 internal server error – which is very easy in apache.
When you have a website, you need to deal with and protect yourself from common attacks such as Cross-Site Scripting, Local File Inclusion and SQL Injection which all start with transmission of hostile commands via the HTTP Request. The challenge consists of separating legitimate requests from the hostile or malicious ones.
If the website is hosted on an Apache server, there is a powerful mechanism available to help mitigating attacks: the Apache .htaccess file. Properly configured, the .htaccess file on a server with mod_rewrite enabled can provide a robust defense against many HTTP Request attacks.
The .htaccess file is very powerful; therefore I recommend a full backup of your website before you start editing your .htaccess file. The slightest syntax error can result in an internal server malfunction and usually you\'ll get a 500 error (Internal Server Error) message. Once you’re done it is very important to verify your entire website’s functionality. If any errors are encountered, remove or comment out the newly added directives.
Note: if you\'re using Notepad for editing purposes, which I DO NOT recommend, turn of word-wrap and when saving the .htaccess file make sure to save it as:
File Type: All Files (not as a text document or it wont work). Name: .htaccess
What is an .htaccess file?
An .htaccess file or distributed configuration file is a plain text file containing a list of configuration directives (rules) and provides a way to make configuration changes on a per-directory basis.
A website can have more than one .htaccess file, i.e. specific instructions may be applied at individual directory level. The .htaccess file will be read on every HTTP Request submitted to the web server. Changes made to this file therefore take immediate effect.
Will my hosting provider let me use an htaccess file?
If your website is hosted on an Apache server, your hosting company should allow the use of .htaccess files. If your host does not allow the use of .htaccess files, I’d recommend you change to one that does.
Is mod_rewrite enabled?
If you don\'t have shell (or other) access to the apache configuration file (httpd.conf) and the host supports php, just paste the text below into a text editor and save the file as info.php in your public html path.
Next run info.php from a browser. Scroll down to the Apache section and check Loaded Modules. Once you’ve obtained the necessary info, delete info.php from your server.
Another simple way to verify if mod_rewrite is enabled consists of creating a single redirect to test it. Add the following lines to the top of your .htaccess file and re-upload it to your server.
Once the .htaccess file has been updated, enter the following into your browser:
http://www.yoursite.com/testpage.html
Replace www.yoursite.com with your website\'s name. This should automatically redirect you to Google. If this redirect works, then mod_rewrite IS working on your server.
Is .htaccess enabled?
It\'s rather unusual, but possible that .htaccess is not enabled on your site. If you have access to the server configuration files, it\'s quite easy to fix; open your httpd.conf in a text editor (without word-wrap enabled), and locate the section.
Locate the line that reads..
AllowOverride None
And change it to..
AllowOverride All
Restart Apache. Now .htaccess should work.
If you don’t have access to the server configuration files then you’re probably on shared hosting and if your .htaccess file doesn’t work then you’ll need to contact your webhosting provider and ask them if they provide support for it.
If you don’t have FTP or cPanel access to your website, DO NOT upload or create a .htaccess file(s). Seek assistance from your hosting company instead as you might fire off a 500 error (Internal Server Error) and once this occurs you won’t be able to access the site through a browser.
What types of rules can the file contain?
The most common security related directives (rules) .htaccess may contain are:
Authorization or authentication (username/password) control at directory level
Use of allow/deny rules to block users by IP address or domain
Customized error responses - e.g. page not found (404)
Directory listing – what to do if a directory rather than a page is requested
URL Rewriting – can be used for a number of purposes including search engine optimization (SEO), redirection of moved content, hot linking and security processing of the HTTP Request.
Commenting .htaccess code
Comments in the .htaccess file are allowed on a per-line basis, each line of comments is preceded by the # (pound) sign. Comments running over several lines require thus multiple # signs. It’s also advised to use only letters, numbers, dashes, and underscores in the comments. This safe practice will contribute in avoiding potential server parsing errors.
Some webhosting companies may have swapped FollowSymLinks to SymLinksIfOwnerMatch due to security reasons. Check with your provider which directive should be used.
What is order allow,deny?
Order allow,deny is a setting in your Apache web server configuration that is used to allow or restrict access.
The allow directive affects who can access an area of the server or website. Access is usually controlled by hostname, IP address, or IP address range.
The deny directive restricts access to the server. Restrictions can be based again on hostname, IP address, or environment variables.
Order allow,deny tells your server that the allow rules are processed before the deny rules. If the client does not match the allow rule or it does match the deny rule, then the client will be denied access.
Order deny, allow means that the deny rules are processed before the allow rules. If the client does not match the deny rule or it does match the allow rule, then it will be granted access.
Deny Access to .htaccess
Any attempt to access the .htaccess file will result in a 403 error message.
To restrict access to certain file types, add the following code and edit the file types you wish to protect. As you might notice you need to escape the dot (.) this is done by typing a backslash (\\) in front of the character that needs escaping.
If your site does not have default index page everything within the root of your site will be accessible to all visitors. Disabling directory browsing will instruct the server to display a \"403 Forbidden - Authorization Required\" message for any request to view a directory.
Restricting directory / folder access is probably one of the most frequently used .htaccess techniques. To deny all requests for the restricted directory or folder, prepare a .htaccess file in that directory and put the following directive in it:
Secure the site contents by requiring user authentication for specified files and/or directories. Adjust the AuthName field to suit your needs: members only , admin section ...
01.# block a partial domain via network/netmask values
02.deny from 76.73.0.0/255.255.0.0
03.# block domain.com but allow sub.domain.com
04.deny from domain.com
05.allow from sub.domain.com
06.#RFI attacks
07.deny from 70.86.235.162
08.deny from 72.249.108.140
09.deny from 81.176.226.194
10.allow from all
Stop Hotlinking
Bandwidth theft or hotlinking is direct linking to a web site\'s files, usually images, video, etc...
Example: You’ve got some pictures illustrating an article and someone else uses an <img> tag to show that image on their webpage page instead of hosting the image themselves.
Bandwidth refers to the amount of data transferred from a web site to a user\'s computer. When you visit a web page, you are using that site\'s bandwidth to display the files. Depending on your web hosting provider, if a site is over its monthly bandwidth, the owner gets billed for the extra data or the site might be taken offline.
To stop hotlinking of your images from other sites and display a replacement image called hotlink.gif, place this code in your .htaccess file:
Allow hotlinking from a couple of websites can be done in two ways, either put each domain on its own line or simply put several keywords separated by a pipe (|) character.
To deliver a standard or custom error page instead of a replacement image, replace the line containing the RewriteRule in the above htaccess directive with the following line:
You can also get an excellent PHP script called Auto-HotLink. What I like most about it: It logs the HTTP requests so you can actually see who’s hotlinking your files.
Block Evil Robots, Site Rippers ...
The block of code below will block some unwanted junk from accessing your website. Any listed user agents will be denied access and receive an error message instead. Below are a couple of examples of user agents you really don\'t want to access your site.
Note: DO NOT include the \"[OR]\" on the very last RewriteCond or your server will crash, delivering 500 Errors to all page requests.
Instead of delivering a friendly error message you could also send these bad boys to a (bad) website of your choice by replacing the RewriteRule in the last line with the name of the domain where you want to redirect them to.
Block empty user agents and empty HTTP referrers
Sometimes you want to block empty user agents and empty HTTP referrers as there\'s no reason for browsers to request only images from your website and if those requests show up with an empty user agent and HTTP referrer, it\'s most certainly a bot that\'s scraping those images. The directive below will stop such requests.
Sometimes you want to create permanent redirect (301) when the request is coming from a particular IP. In other words, if someone from 123.45.67.8 visits the website, the visitor will be redirected to Google for example. All other visitors will be able to access the site.
Sometimes you might want to redirect multiple IP addresses to another URL, preventing access to your webiste from those IP\'s. One way of doing this is to add [OR] to the end of the first RewriteCond and add another IP on the next line. Do NOT place an [OR] on the final RewriteCond.
During site development for example you might want to allow the administrators / developers to access the frontend of the CMS and redirect other visitors to a maintenance page.
The rules are pretty similar to the above ones, except that with when using a negation sign - ! - you DON\'T add the [OR] to the end of the RewriteCond.
Using the above rules you can also prevent a visitor from a particular IP from accessing a specific page on your site and redirect the visitor to Google.
You could also redirect multiple IP\'s to a PHP script which will send them to different destinations. When someone is abusing your website you could for example redirect them to the acceptable use policy (AUP) of their webhost.
Below are a couple of rules initially posted on 0x000000.com, a white hacker website, according to a post here. They will help in blocking attacks against your server.
I personally took out the single quote / apostrophe (\') in the rule on line 05 that \"blocks out the use of illegal or unsafe characters in the Referer Variable of the HTTP Request\". The quote may appear in a search query as seen below and thus innocently block the visitor.
Many websites, about 70-80%, are vulnerable against LFI attacks and hackers will attempt to exploit this to get a shell on the server. Below is an example of php code that is vulnerable to LFI:
Adding the following directive in the .htaccess file should give you an additional layer of security against this type of attacks using the proc/self/environ method.
Around 40.000 web sites have been catalogued by XSSed as being vulnerable to cross-site scripting (XSS). These attacks leave your users open to cookie theft, information theft, account hijacking, clickjacking and more.
Modern web browsers have some powerful protection build in nowadays but you need to tell the browser that you want those protection mechanisms used for your website. This can be archived by setting specific HTTP headers.
X-Frame-Options
The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a <frame> or <iframe>. This can be used to avoid clickjacking attacks, by ensuring that your content is not embedded into other sites.
DENY - This setting prevents any pages served from being placed in a frame even if it is on the same website it originates from. should be used if you never intend for your pages to be used inside of a frame.
SAMEORIGIN - This setting allows pages to be served in a frame of a page on the same website. If an external site attempts to load the page in a frame the request will be denied.
ALLOW-FROM origin - If the value contains the token ALLOW-FROM origin, the browser will block rendering only if the origin of the top-level browsing context is different than the origin value supplied with the Allow-From directive.
The code below sets the directive to DENY, preventing our pages from being served in any frames, even from our own website.
This header is exclusive to Internet Explorer 8 and 9, it turns on cross site scripting protection in IE 8 and IE 9 which is turned off by default as it could potentially break some websites. To turn on the XSS filter, use the header X-XSS-Protection \"1; mode=block\". If you wish to prevent this filter from being turned on for your website set the headers value to \"0\";
Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. This header is designed to specify how content interacts with your website.
Setting this directive to \"allow \'self\';\" will prevent our pages from loading any external JavaScript or running any inline JavaScript. Our website will be safer from XSS attacks as it becomes more difficult for an attacker to run JavaScript in the visitor’s browser through a framed page on our website or through a SQL injection.
There are a lot of settings available for this header and I really urge you to read the Mozilla Wiki page before using CSP as you will have to allow certain external content if you run Google Adsense for example.
0.# Only allow JavaScript from the same domain to be run.
1.# Don\'t allow inline JavaScript to run.
2.Header set X-Content-Security-Policy \"allow \'self\';\"
X-Content-Type-Options: nosniff
This header prevents \"mime\" based attacks. This header prevents Internet Explorer from MIME-sniffing a response away from the declared content-type as the header instructs the browser not to override the response content type. With the nosniff option, if the server says the content is text/html, the browser will render it as text/html.
# the # instructs the server to ignore the line. used for including comments. each line of comments requires it’s own #. when including comments, it is good practice to use only letters, numbers, dashes, and underscores. this practice will help eliminate/avoid potential server parsing errors.
[F] Forbidden: instructs the server to return a 403 Forbidden to the client.
[L] Last rule: instructs the server to stop rewriting after the preceding directive is processed.
[N] Next: instructs Apache to rerun the rewrite rule until all rewriting directives have been achieved.
[G] Gone: instructs the server to deliver Gone (no longer exists) status message.
[P] Proxy: instructs server to handle requests by mod_proxy
[C] Chain: instructs server to chain the current rule with the previous rule.
[R] Redirect: instructs Apache to issue a redirect, causing the browser to request the rewritten/modified URL.
[NC] No Case: defines any associated argument as case-insensitive. i.e., \"NC\" = \"No Case\".
[PT] Pass Through: instructs mod_rewrite to pass the rewritten URL back to Apache for further processing.
[OR] Or: specifies a logical \"or\" that ties two expressions together such that either one proving true will cause the associated rule to be applied.
[NE] No Escape: instructs the server to parse output without escaping characters.
[NS] No Subrequest: instructs the server to skip the directive if internal sub-request.
[QSA] Append Query String: directs server to add the query string to the end of the expression (URL).
[S=x] Skip: instructs the server to skip the next \"x\" number of rules if a match is detected.
[E=variable:value] Environmental Variable: instructs the server to set the environmental variable \"variable\" to \"value\".
[T=MIME-type] Mime Type: declares the mime type of the target resource.
[] specifies a character class, in which any character within the brackets will be a match. e.g., [xyz] will match either an x, y, or z.
[]+ character class in which any combination of items within the brackets will be a match. e.g., [xyz]+ will match any number of x’s, y’s, z’s, or any combination of these characters.
[^] specifies not within a character class. e.g., [^xyz] will match any character that is neither x, y, nor z.
[a-z] a dash (-) between two characters within a character class ([]) denotes the range of characters between them. e.g., [a-zA-Z] matches all lowercase and uppercase letters from a to z.
a{n} specifies an exact number, n, of the preceding character. e.g., x{3} matches exactly three x’s.
a{n,} specifies n or more of the preceding character. e.g., x{3,} matches three or more x’s.
a{n,m} specifies a range of numbers, between n and m, of the preceding character. e.g., x{3,7} matches three, four, five, six, or seven x’s.
() used to group characters together, thereby considering them as a single unit. e.g., (perishable)?press will match press, with or without the perishable prefix.
^ denotes the beginning of a regex (regex = regular expression) test string. i.e., begin argument with the proceeding character.
$ denotes the end of a regex (regex = regular expression) test string. i.e., end argument with the previous character.
? declares as optional the preceding character. e.g., monzas? will match monza or monzas, while mon(za)? will match either mon or monza. i.e., x? matches zero or one of x.
When you have a website, you need to deal with and protect yourself from common attacks such as Cross-Site Scripting, Local File Inclusion and SQL Injection which all start with transmission of hostile commands via the HTTP Request. The challenge consists of separating legitimate requests from the hostile or malicious ones.
If the website is hosted on an Apache server, there is a powerful mechanism available to help mitigating attacks: the Apache .htaccess file. Properly configured, the .htaccess file on a server with mod_rewrite enabled can provide a robust defense against many HTTP Request attacks.
The .htaccess file is very powerful; therefore I recommend a full backup of your website before you start editing your .htaccess file. The slightest syntax error can result in an internal server malfunction and usually you\'ll get a 500 error (Internal Server Error) message. Once you’re done it is very important to verify your entire website’s functionality. If any errors are encountered, remove or comment out the newly added directives.
Note: if you\'re using Notepad for editing purposes, which I DO NOT recommend, turn of word-wrap and when saving the .htaccess file make sure to save it as:
File Type: All Files (not as a text document or it wont work). Name: .htaccess
What is an .htaccess file?
An .htaccess file or distributed configuration file is a plain text file containing a list of configuration directives (rules) and provides a way to make configuration changes on a per-directory basis.
A website can have more than one .htaccess file, i.e. specific instructions may be applied at individual directory level. The .htaccess file will be read on every HTTP Request submitted to the web server. Changes made to this file therefore take immediate effect.
Will my hosting provider let me use an htaccess file?
If your website is hosted on an Apache server, your hosting company should allow the use of .htaccess files. If your host does not allow the use of .htaccess files, I’d recommend you change to one that does.
Is mod_rewrite enabled?
If you don\'t have shell (or other) access to the apache configuration file (httpd.conf) and the host supports php, just paste the text below into a text editor and save the file as info.php in your public html path.
Next run info.php from a browser. Scroll down to the Apache section and check Loaded Modules. Once you’ve obtained the necessary info, delete info.php from your server.
Another simple way to verify if mod_rewrite is enabled consists of creating a single redirect to test it. Add the following lines to the top of your .htaccess file and re-upload it to your server.
Once the .htaccess file has been updated, enter the following into your browser:
http://www.yoursite.com/testpage.html
Replace www.yoursite.com with your website\'s name. This should automatically redirect you to Google. If this redirect works, then mod_rewrite IS working on your server.
Is .htaccess enabled?
It\'s rather unusual, but possible that .htaccess is not enabled on your site. If you have access to the server configuration files, it\'s quite easy to fix; open your httpd.conf in a text editor (without word-wrap enabled), and locate the section.
Locate the line that reads..
AllowOverride None
And change it to..
AllowOverride All
Restart Apache. Now .htaccess should work.
If you don’t have access to the server configuration files then you’re probably on shared hosting and if your .htaccess file doesn’t work then you’ll need to contact your webhosting provider and ask them if they provide support for it.
If you don’t have FTP or cPanel access to your website, DO NOT upload or create a .htaccess file(s). Seek assistance from your hosting company instead as you might fire off a 500 error (Internal Server Error) and once this occurs you won’t be able to access the site through a browser.
What types of rules can the file contain?
The most common security related directives (rules) .htaccess may contain are:
Authorization or authentication (username/password) control at directory level
Use of allow/deny rules to block users by IP address or domain
Customized error responses - e.g. page not found (404)
Directory listing – what to do if a directory rather than a page is requested
URL Rewriting – can be used for a number of purposes including search engine optimization (SEO), redirection of moved content, hot linking and security processing of the HTTP Request.
Commenting .htaccess code
Comments in the .htaccess file are allowed on a per-line basis, each line of comments is preceded by the # (pound) sign. Comments running over several lines require thus multiple # signs. It’s also advised to use only letters, numbers, dashes, and underscores in the comments. This safe practice will contribute in avoiding potential server parsing errors.
Some webhosting companies may have swapped FollowSymLinks to SymLinksIfOwnerMatch due to security reasons. Check with your provider which directive should be used.
What is order allow,deny?
Order allow,deny is a setting in your Apache web server configuration that is used to allow or restrict access.
The allow directive affects who can access an area of the server or website. Access is usually controlled by hostname, IP address, or IP address range.
The deny directive restricts access to the server. Restrictions can be based again on hostname, IP address, or environment variables.
Order allow,deny tells your server that the allow rules are processed before the deny rules. If the client does not match the allow rule or it does match the deny rule, then the client will be denied access.
Order deny, allow means that the deny rules are processed before the allow rules. If the client does not match the deny rule or it does match the allow rule, then it will be granted access.
Deny Access to .htaccess
Any attempt to access the .htaccess file will result in a 403 error message.
To restrict access to certain file types, add the following code and edit the file types you wish to protect. As you might notice you need to escape the dot (.) this is done by typing a backslash (\\) in front of the character that needs escaping.
If your site does not have default index page everything within the root of your site will be accessible to all visitors. Disabling directory browsing will instruct the server to display a \"403 Forbidden - Authorization Required\" message for any request to view a directory.
Restricting directory / folder access is probably one of the most frequently used .htaccess techniques. To deny all requests for the restricted directory or folder, prepare a .htaccess file in that directory and put the following directive in it:
Secure the site contents by requiring user authentication for specified files and/or directories. Adjust the AuthName field to suit your needs: members only , admin section ...
01.# block a partial domain via network/netmask values
02.deny from 76.73.0.0/255.255.0.0
03.# block domain.com but allow sub.domain.com
04.deny from domain.com
05.allow from sub.domain.com
06.#RFI attacks
07.deny from 70.86.235.162
08.deny from 72.249.108.140
09.deny from 81.176.226.194
10.allow from all
Stop Hotlinking
Bandwidth theft or hotlinking is direct linking to a web site\'s files, usually images, video, etc...
Example: You’ve got some pictures illustrating an article and someone else uses an <img> tag to show that image on their webpage page instead of hosting the image themselves.
Bandwidth refers to the amount of data transferred from a web site to a user\'s computer. When you visit a web page, you are using that site\'s bandwidth to display the files. Depending on your web hosting provider, if a site is over its monthly bandwidth, the owner gets billed for the extra data or the site might be taken offline.
To stop hotlinking of your images from other sites and display a replacement image called hotlink.gif, place this code in your .htaccess file:
Allow hotlinking from a couple of websites can be done in two ways, either put each domain on its own line or simply put several keywords separated by a pipe (|) character.
To deliver a standard or custom error page instead of a replacement image, replace the line containing the RewriteRule in the above htaccess directive with the following line:
You can also get an excellent PHP script called Auto-HotLink. What I like most about it: It logs the HTTP requests so you can actually see who’s hotlinking your files.
Block Evil Robots, Site Rippers ...
The block of code below will block some unwanted junk from accessing your website. Any listed user agents will be denied access and receive an error message instead. Below are a couple of examples of user agents you really don\'t want to access your site.
Note: DO NOT include the \"[OR]\" on the very last RewriteCond or your server will crash, delivering 500 Errors to all page requests.
Instead of delivering a friendly error message you could also send these bad boys to a (bad) website of your choice by replacing the RewriteRule in the last line with the name of the domain where you want to redirect them to.
Block empty user agents and empty HTTP referrers
Sometimes you want to block empty user agents and empty HTTP referrers as there\'s no reason for browsers to request only images from your website and if those requests show up with an empty user agent and HTTP referrer, it\'s most certainly a bot that\'s scraping those images. The directive below will stop such requests.
Sometimes you want to create permanent redirect (301) when the request is coming from a particular IP. In other words, if someone from 123.45.67.8 visits the website, the visitor will be redirected to Google for example. All other visitors will be able to access the site.
Sometimes you might want to redirect multiple IP addresses to another URL, preventing access to your webiste from those IP\'s. One way of doing this is to add [OR] to the end of the first RewriteCond and add another IP on the next line. Do NOT place an [OR] on the final RewriteCond.
During site development for example you might want to allow the administrators / developers to access the frontend of the CMS and redirect other visitors to a maintenance page.
The rules are pretty similar to the above ones, except that with when using a negation sign - ! - you DON\'T add the [OR] to the end of the RewriteCond.
Using the above rules you can also prevent a visitor from a particular IP from accessing a specific page on your site and redirect the visitor to Google.
You could also redirect multiple IP\'s to a PHP script which will send them to different destinations. When someone is abusing your website you could for example redirect them to the acceptable use policy (AUP) of their webhost.
Below are a couple of rules initially posted on 0x000000.com, a white hacker website, according to a post here. They will help in blocking attacks against your server.
I personally took out the single quote / apostrophe (\') in the rule on line 05 that \"blocks out the use of illegal or unsafe characters in the Referer Variable of the HTTP Request\". The quote may appear in a search query as seen below and thus innocently block the visitor.
Many websites, about 70-80%, are vulnerable against LFI attacks and hackers will attempt to exploit this to get a shell on the server. Below is an example of php code that is vulnerable to LFI:
Adding the following directive in the .htaccess file should give you an additional layer of security against this type of attacks using the proc/self/environ method.
Around 40.000 web sites have been catalogued by XSSed as being vulnerable to cross-site scripting (XSS). These attacks leave your users open to cookie theft, information theft, account hijacking, clickjacking and more.
Modern web browsers have some powerful protection build in nowadays but you need to tell the browser that you want those protection mechanisms used for your website. This can be archived by setting specific HTTP headers.
X-Frame-Options
The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a <frame> or <iframe>. This can be used to avoid clickjacking attacks, by ensuring that your content is not embedded into other sites.
DENY - This setting prevents any pages served from being placed in a frame even if it is on the same website it originates from. should be used if you never intend for your pages to be used inside of a frame.
SAMEORIGIN - This setting allows pages to be served in a frame of a page on the same website. If an external site attempts to load the page in a frame the request will be denied.
ALLOW-FROM origin - If the value contains the token ALLOW-FROM origin, the browser will block rendering only if the origin of the top-level browsing context is different than the origin value supplied with the Allow-From directive.
The code below sets the directive to DENY, preventing our pages from being served in any frames, even from our own website.
This header is exclusive to Internet Explorer 8 and 9, it turns on cross site scripting protection in IE 8 and IE 9 which is turned off by default as it could potentially break some websites. To turn on the XSS filter, use the header X-XSS-Protection \"1; mode=block\". If you wish to prevent this filter from being turned on for your website set the headers value to \"0\";
Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. This header is designed to specify how content interacts with your website.
Setting this directive to \"allow \'self\';\" will prevent our pages from loading any external JavaScript or running any inline JavaScript. Our website will be safer from XSS attacks as it becomes more difficult for an attacker to run JavaScript in the visitor’s browser through a framed page on our website or through a SQL injection.
There are a lot of settings available for this header and I really urge you to read the Mozilla Wiki page before using CSP as you will have to allow certain external content if you run Google Adsense for example.
0.# Only allow JavaScript from the same domain to be run.
1.# Don\'t allow inline JavaScript to run.
2.Header set X-Content-Security-Policy \"allow \'self\';\"
X-Content-Type-Options: nosniff
This header prevents \"mime\" based attacks. This header prevents Internet Explorer from MIME-sniffing a response away from the declared content-type as the header instructs the browser not to override the response content type. With the nosniff option, if the server says the content is text/html, the browser will render it as text/html.
# the # instructs the server to ignore the line. used for including comments. each line of comments requires it’s own #. when including comments, it is good practice to use only letters, numbers, dashes, and underscores. this practice will help eliminate/avoid potential server parsing errors.
[F] Forbidden: instructs the server to return a 403 Forbidden to the client.
[L] Last rule: instructs the server to stop rewriting after the preceding directive is processed.
[N] Next: instructs Apache to rerun the rewrite rule until all rewriting directives have been achieved.
[G] Gone: instructs the server to deliver Gone (no longer exists) status message.
[P] Proxy: instructs server to handle requests by mod_proxy
[C] Chain: instructs server to chain the current rule with the previous rule.
[R] Redirect: instructs Apache to issue a redirect, causing the browser to request the rewritten/modified URL.
[NC] No Case: defines any associated argument as case-insensitive. i.e., \"NC\" = \"No Case\".
[PT] Pass Through: instructs mod_rewrite to pass the rewritten URL back to Apache for further processing.
[OR] Or: specifies a logical \"or\" that ties two expressions together such that either one proving true will cause the associated rule to be applied.
[NE] No Escape: instructs the server to parse output without escaping characters.
[NS] No Subrequest: instructs the server to skip the directive if internal sub-request.
[QSA] Append Query String: directs server to add the query string to the end of the expression (URL).
[S=x] Skip: instructs the server to skip the next \"x\" number of rules if a match is detected.
[E=variable:value] Environmental Variable: instructs the server to set the environmental variable \"variable\" to \"value\".
[T=MIME-type] Mime Type: declares the mime type of the target resource.
[] specifies a character class, in which any character within the brackets will be a match. e.g., [xyz] will match either an x, y, or z.
[]+ character class in which any combination of items within the brackets will be a match. e.g., [xyz]+ will match any number of x’s, y’s, z’s, or any combination of these characters.
[^] specifies not within a character class. e.g., [^xyz] will match any character that is neither x, y, nor z.
[a-z] a dash (-) between two characters within a character class ([]) denotes the range of characters between them. e.g., [a-zA-Z] matches all lowercase and uppercase letters from a to z.
a{n} specifies an exact number, n, of the preceding character. e.g., x{3} matches exactly three x’s.
a{n,} specifies n or more of the preceding character. e.g., x{3,} matches three or more x’s.
a{n,m} specifies a range of numbers, between n and m, of the preceding character. e.g., x{3,7} matches three, four, five, six, or seven x’s.
() used to group characters together, thereby considering them as a single unit. e.g., (perishable)?press will match press, with or without the perishable prefix.
^ denotes the beginning of a regex (regex = regular expression) test string. i.e., begin argument with the proceeding character.
$ denotes the end of a regex (regex = regular expression) test string. i.e., end argument with the previous character.
? declares as optional the preceding character. e.g., monzas? will match monza or monzas, while mon(za)? will match either mon or monza. i.e., x? matches zero or one of x.
<node>cheat sheets <node>constants <node>directory <node>example <node>hooks <node>SESSIONS <node>html5 <node>reserved words <node>Settings <node>Upgrades <node>uploads <node>urls <node>How to Include a WordPress Page <node>Stupid WordPress Tricks <node>Ten Things Every WordPress Plugin Developer Should Know <node>WARNINGS <Treepad version 3.0> dt= <node>cheat sheets 0 http://www.buildyourownblog.net/blog/time-saving-copypaste-wordpress-cheat-sheet/The Time Saving Copy/Paste WordPress Cheat Sheet while(have_posts()) { the_post(); }
Use this WordPress Cheat Sheet page for a quick, categorized list of WordPress functions that are commonly used when building, updating and maintaining templates. Simple, Easy, Copy-Paste. The quick guide to common WordPress > Template functions. Pdf Icon
-------------------------------------------------------------------------------- Basic Template Files File Name Description style.css style sheet file index.php home page file header.php header content file single.php single post page file archive.php archive/category file searchform.php search form file search.php search content file 404.php error page file comments.php comments template file footer.php footer content file sidebar.php sidebar content file page.php single page file front-page.php latest posts or static page tag.php display tags in archive format category.php display categories in archive format Header Functions Function Description <?php site_url(); ?> root url for website <?php wp_title(); ?> title of specific post/page <?php bloginfo('name'); ?> title of site <?php bloginfo('description'); ?> site description <?php get_stylesheet_directory(); ?> stylesheet folder location <?php bloginfo('stylesheet_url'); ?> style.css file location <?php bloginfo('pingback_url'); ?> pingback url <?php bloginfo('template_url'); ?> template folder path <?php bloginfo('version'); ?> wordpress blog version <?php bloginfo('atom_url'); ?> atom url <?php bloginfo('rss2_url'); ?> rss2 url <?php bloginfo('url'); ?> root url for website <?php bloginfo('html_type'); ?> html version <?php bloginfo('charset'); ?> charset parameter Navigation Menu Default Navigation Menu <?php wp_nav_menu(); ?> Specific Navigation Menu <?php wp_nav_menu( array('menu' => 'Project Nav' )); ?> Category Based Navigation <ul id="menu"> <li <?php if(is_home()) { ?> class="current-cat" <?php } ?>> <a href="<?php bloginfo('home'); ?>">Home</a></li> <?php wp_list_categories('title_li=&orderby=id');?> </ul> Page Based Navigation <ul id="menu"> <li <?php if(is_home()) { ?> class="current-page-item" <?php } ?>> <a href="<?php bloginfo('home'); ?>">Home</a></li> <?php wp_list_pages('sort_column=menu_order&depth=1&title_li=');?> </ul> -------------------------------------------------------------------------------- Template Functions Function Description <?php the_content(); ?> content of posts/pages <?php if(have_posts()): ?> check if there are posts <?php while(have_posts()): the_post(); ?> shows posts <?php endwhile; ?> closes loop <?php endif; ?> closes if <?php get_header(); ?> header.php file contents <?php get_sidebar(); ?> sidebar.php file contents <?php get_footer(); ?> footer.php file contents <?php the_time('m-d-y'); ?> the date is ’08-18-07' <?php comments_popup_link(); ?> link to comments of post <?php the_title(); ?> title of post/page <?php the_permalink(); ?> url of post/page <?php the_category(); ?> category of post/page <?php the_author(); ?> author of post/page <?php the_ID(); ?> id of post/page <?php edit_post_link(); ?> edit link of post/page <?php wp_list_bookmarks(); ?> links from blogroll <?php comments_template(); ?> comment.php file contents <?php wp_list_pages(); ?> list all pages <?php wp_list_categories(); ?> list all categories <?php next_post_link('%link'); ?> url to next post <?php previous_post_list('%link'); ?> url to previous post <?php get_calendar(); ?> show post calendar <?php wp_get_archives(); ?> list of archive urls <?php posts_nav_link(); ?> next and previous post link <?php rewind_posts(); ?> rewinds post for a second loop The Loop Basic Loop <?php if(have_posts()) { ?> <?php while(have_posts()) { ?> <?php the_post(); ?> <?php // custom post content code for title, excerpt and featured image ?> <?php } // end while ?> <?php } // end if ?> Extra Functions Function Description /%postname%/ custom permalinks <?php include(TEMPLATEPATH . '/x'); ?> include file from template folder <?php the_search_query(); ?> value returned from search from <?php _e('Message'); ?> return translated text from translate() <?php wp_register(); ?> register link <?php wp_loginout(); ?> login/logout link <!--nextpage--> divide content into pages <!--more--> cut off content and create link to full post <?php wp_meta(); ?> admin meta data <?php timer_start(); ?> start page timer (header.php) <?php timer_stop(1); ?> time to load the page (footer.php) <?php echo get_num_queries(); ?> show queries executed to generate page <end node> 5P9i0s8y19Z dt= <node>constants 1 get_site_url() get_theme_root_uri(), get_stylesheet(), get_stylesheet_uri(), get_stylesheet_directory(), get_stylesheet_directory_uri(), get_bloginfo() WordPress Directories: home_url() Home URL http://www.example.com site_url() Site directory URL http://www.example.com or http://www.example.com/wordpress admin_url() Admin directory URL http://www.example.com/wp-admin includes_url() Includes directory URL http://www.example.com/wp-includes content_url() Content directory URL http://www.example.com/wp-content plugins_url() Plugins directory URL http://www.example.com/wp-content/plugins theme_url() Themes directory URL (#18302) http://www.example.com/wp-content/themes wp_upload_dir() Upload directory URL (returns an array) http://www.example.com/wp-content/uploads
Categories: WordPress Constants Here are some of the constants and how they are used. There are probably a few that I missed. I’ll add to this as I find more. Security Constants These constants are declared in wp-config.php and are required for the normal operation of WordPress. All of these constants are 64 character random strings and are used for hashes, nonces and other security purposes. Each installation of WordPress should use different strings to ensure that your site is harder to “hack.” If you haven’t already changed your security keys, you can use WordPress’s online security key generator. AUTH_KEY - Used for authenticating a user and setting cookies. SECURE_AUTH_KEY - Used for authenticating a user and setting cookies under the https protocol. LOGGED_IN_KEY - Used for marking a user’s cookie data as logged in. NONCE_KEY - Used for creating Nonces, which are used as one-time values to ensure that humans are entering data in forms. AUTH_SALT - Used to “salt” the authentication data. Salts are random data added to passwords, keys and other data to make them harder to guess. SECURE_AUTH_SALT - Used to “salt” the secure authentication data. LOGGED_IN_SALT - Used to “salt” the logged in cookie data. NONCE_SALT - Used to “salt” the nonce data. Database Constants These are used to declare your database connection information. If you ever need to change your database password or location, you can effect this by editing your wp-config.php file and change these values: DB_NAME - The name of your database. DB_USER - The user name for your database connection. DB_PASSWORD - The password for your database connection. DB_HOST - The host name, or computer name where your database server is located. DB_CHARSET - The character set used when creating tables in your database. Unless you have a specific requirement for something else, this should have a value of ‘utf8?. DB_COLLATE - The collation (sorting) type to use for indexed data in your tables. This should be left empty unless you have a specific requirement otherwise. Other wp-config.php Constants These are the last few constants that are normally declared in wp-config.php: COOKIE_DOMAIN - Specifies the domain set in cookies for those with unusual domain configurations. This can help to prevent cookies being sent with requests for static content. Example: define(‘COOKIE_DOMAIN’, ‘www.staticdomain.com’);. WP_DEBUG - Sets WordPress’s “debug” mode on or off. Normally, this is set to false. Changing it to define(‘WP_DEBUG’, true); will turn on debug mode. This can be useful if you need to track down errors. WP_HOME - This overrides the configuration setting for the home url, but doesn’t change it permanently. This should include the http:// prefix, as in: define(‘WP_HOME’, ‘http://domain.com/optionalsubdirectory’);. WP_SITEURL - Declares the site’s URL. This defines the address where your WordPress code files reside. It should include the http:// prefix. An example would be: define(‘WP_SITEURL’, ‘http://mydomain.com’);. WPLANG - Used to localize your WordPress install. This should be left empty for a default language of American English. If you need to localize your WordPress installation, you need to change this and install a corresponding MO file for your language. For example, changing this to: define(‘WPLANG’, ‘de_DE’); will set your language to German. DISABLE_WP_CRON - Used to turn off WP Cron tasks that are initiated y a page load. When this is disabled, it is recommended to set up a separate Cron job to run the wp-cron.php script on a regular basis in order to still have cron-related operations run. System Constants These constants are set to describe the state of how WordPress handles various requests. APP_REQUEST - Set within wp-app.php to indicate that WordPress is handling an Atom Publishing Protocol request. Default Constants These values are declared in the wp-includes/default-constants.php file. You to change these settings, add them to your wp-config.php file so they are declared before the wp-includes/default-constants.php file is loaded. ADMIN_COOKIE_PATH - Sets the cookie path for admin-based cookies. If not already defined, this will take the value: define(‘ADMIN_COOKIE_PATH’, SITECOOKIEPATH . ‘wp-admin’); AUTH_COOKIE - Sets the authentication cookie name. If not already set, will be: define(‘AUTH_COOKIE’, ‘wordpress_’ . COOKIEHASH); COOKIEHASH - Defines an MD5 hash of the site’s domain name for use in user and password cookie names. COOKIEPATH - Defines the path name to be used in setting and retrieving cookies. If not already set, will be the domain name in which WordPress is installed. On MultiSite installs, will be the subdomain name, or the domain name including the directory of the Site. FORCE_SSL_ADMIN - Enforces the use of SSL for Admin access. Normally, this is disabled. To force SSL for all Admin pages, you can: define(‘FORCE_SSL_ADMIN’, true); FORCE_SSL_LOGIN - Enforces the use of SSL for site logins. Normally, this is disabled. To force SSL for login requests, you can: define(‘FORCE_SSL_LOGIN’, true); SITECOOKIEPATH - Sets the cookie path for normal site cookies. If not set, this will take the value define(‘SITECOOKIEPATH’, preg_replace(‘|https?://[^/]+|i’, ”, get_option(‘siteurl’) . ‘/’ ) ); WP_CONTENT_DIR - Sets the name of the content directory. Normally, this is ‘wp-content’. To change this, you can: define(‘WP_CONTENT_DIR’, ‘mycontentdirectory’); This can also be obtained by using plugin_dir_path() WP_CONTENT_URL - Sets the URL for the content directory references. if you change the WP_CONTENT_DIR, you will also need to change this to match the directory name for http requests. WP_DEBUG_DISPLAY - Controls display of errors. The default is to use the display_errors setting and not force errors to be displayed. To force errors to display, you can: define(‘WP_DEBUG_DISPLAY’, true); WP_DEBUG_LOG - Controls error logging to the file wp-content/debug.log. The default is no logging. To change this, you can: define(‘WP_DEBUG_LOG’, true); WP_DEFAULT_THEME - Sets the default theme. The current version of WordPress assumes a default theme of ‘twentyeleven’. If you want to change this, you can: define(‘WP_DEFAULT_THEME’, ‘mydefaulttheme’); WP_PLUGIN_DIR - Sets the directory for plugin files. The default is ‘plugins’. To change this, you can: define(‘WP_PLUGIN_DIR’, ‘/newplugindir’); WP_PLUGIN_URL - Sets the URL for the plugin directory. If you change the WP_PLUGIN_DIR, you will also need to change this to match the directory name for http requests. If you have compatibility issues with some plugins, you can set an additional value, as in: define(‘PLUGINDIR’, ‘/wpdir/wp-content/plugins’);. WPMU_PLUGIN_DIR - Sets the directory to store the Must Use plugins. The default location is /mu-plugins. To change this, you can: define(‘WPMU_PLUGIN_DIR’, ‘/requiredplugins’); WPMU_PLUGIN_URL - Sets the URL for the Must Use plugin directory. If you change the WPMU_PLUGIN_DIR, you will also need to change this to match the directory name for http requests. Capability Settings These can be used to control certain behaviors that users are allowed to perform. Some of these are confusing because you are turning “on” the ability to “disallow” a feature. So be careful on how you’re declaring these values. Most of these are used in the wp-includes/capabilities.php file, but if you want to change the settings, you should add your settings to your wp-config.php file. ALLOW_UNFILTERED_UPLOADS - Allows unfiltered uploads. You can: define(‘ALLOW_UNFILTERED_UPLOADS’, true); to enable users to upload files without filtering. Be careful: this is a potential security risk. DISALLOW_FILE_EDIT - Allows users to edit theme and plugin files. If you do not want your users to be able to edit these files, you can change this: define(‘DISALLOW_FILE_EDIT’, true); DISALLOW_FILE_MODS - Allows users to update theme and plugin files via the WordPress Repository. If you do not want your users to be able to update their WordPress install, you can change this: define(‘DISALLOW_FILE_MODS’, true); DISALLOW_UNFILTERED_HTML - Disables the ability to allow unfiltered HTML. Using define(‘DISALLOW_UNFILTERED_HTML’, false); will turn off the ability to allow unfiltered HTML. WP_CACHE - Enables the built-in WordPress caching capability. If you want to enable this caching, you can: define(‘WP_CACHE’, true); WP_USE_THEMES - Declared in /index.php. Tells WordPress whether or not use load it’s template engine. If you want access to WordPress APIs but don’t want or need the overhead of the template engine, define this to false: define(‘WP_USE_THEMES’, false); Script Control These settings control how scripts (Javascript and CSS) are handled by the system. COMPRESS_CSS - Compresses CSS. To enable CSS compression, you can: define(‘COMPRESS_CSS’, true); COMPRESS_SCRIPTS - Compresses scripts. To enable compression, you can: define(‘COMPRESS_SCRIPTS’, true); CONCATENATE_SCRIPTS - Concatenates Javascript and CSS files. To enable, you can define(‘CONCATENATE_SCRIPTS’, true); ENFORCE_GZIP - Forces gzip for compressoin of data sent to browsers. The default setting is to use the mod_deflate Apache module. If your host does not have this installed, you can: SCRIPT_DEBUG - Include the development (or non-minified) versions of all Javascript and CSS files. It also disabled compression and concatenation. To enable, you can: define(‘SCRIPT_DEBUG’, true); Optimization Settings These values can be used to control and optimize your WordPress install. AUTOSAVE_INTERVAL - Sets the interval for saving revisions while editing posts. CORE_UPGRADE_SKIP_NEW_BUNDLED - Enables skipping of theme and plugin updates when upgrading WordPress. DOING_AJAX - Set to TRUE when processing an AJAX request. EMPTY_TRASH_DAYS - Sets the number of days before trashed items are removed. IMAGE_EDIT_OVERWRITE - Allows overwriting images when editing them. MEDIA_TRASH - Enables the trash function for Media files. WP_MEMORY_LIMIT - Sets the memory limit used. WP_MAX_MEMORY_LIMIT - Controls the maximum memory size used. Some WordPress processes require more memory. This setting controls the upper limit used by these high memory use procedures. SHORTINIT - Turns on only the core WordPress functions. Often used when interfacing to other platforms. WP_POST_REVISIONS - Sets the maximum number of revisions to save. If set to FALSE it will be unlimited, an integer set the maximum number of revisions to save. MultiSite Settings These values control how WordPress MultiSite behaves. NOBLOGREDIRECT - Sets the URL to redirect visitors to when they request a non-existent MultiSite blog. The default is ‘%siteurl%’, which is the default site. If you wish to use a different location, you can: define(‘NOBLOGREDIRECT’, ‘mynewdomain.com’); WP_ALLOW_MULTISITE - Turns on MultiSite. Just enabling this using define(‘WP_ALLOW_MULTISITE’, true); does not by itself make your WordPress install a MultiSite install. It just starts the process. When you add this to your wp-config.php file, it turns on the Network menu in the Admin. This allows you to make certain choices and continue the setup process for your MultiSite install. WPMU_ACCEL_REDIRECT - When using Apache X-Sendfile for quicker loading, this helps you turn it on natively in WordPress for MultiSites. To enable, you can: define(‘WPMU_ACCEL_REDIRECT’, true); ABSPATH Definitions: 5 References: 597 ADMIN_COOKIE_PATH Definitions: 3 References: 8 AKISMET_DELETE_LIMIT Definitions: 1 References: 3 AKISMET_VERSION Definitions: 1 References: 8 AKISMET__MINIMUM_WP_VERSION Definitions: 1 References: 3 AKISMET__PLUGIN_DIR Definitions: 1 References: 7 AKISMET__PLUGIN_URL Definitions: 1 References: 5 ARRAY_A Definitions: 1 References: 71 ARRAY_N Definitions: 1 References: 16 ATOM Definitions: 1 References: 10 AUTH_COOKIE Definitions: 1 References: 12 AUTH_KEY Definitions: 1 References: 4 AUTH_SALT Definitions: 1 References: 3 AUTOSAVE_INTERVAL Definitions: 1 References: 3 BACKGROUND_COLOR Definitions: 1 References: 3 BACKGROUND_IMAGE Definitions: 1 References: 3 BLOGUPLOADDIR Definitions: 1 References: 5 BLOG_ID_CURRENT_SITE Definitions: 1 References: 3 COMMENTS_TEMPLATE Definitions: 1 References: 2 COOKIEHASH Definitions: 2 References: 29 COOKIEPATH Definitions: 2 References: 17 COOKIE_DOMAIN Definitions: 3 References: 28 CRLF Definitions: 1 References: 37 CUSTOM_TAGS Definitions: 1 References: 3 DAY_IN_SECONDS Definitions: 1 References: 33 DB_CHARSET Definitions: 1 References: 3 DB_COLLATE Definitions: 1 References: 6 DB_HOST Definitions: 2 References: 4 DB_NAME Definitions: 2 References: 5 DB_PASSWORD Definitions: 2 References: 4 DB_USER Definitions: 2 References: 4 DOING_AJAX Definitions: 2 References: 34 DOING_AUTOSAVE Definitions: 1 References: 4 DOING_CRON Definitions: 1 References: 24 DOMAIN_CURRENT_SITE Definitions: 1 References: 3 EBML_ID_ASPECTRATIOTYPE Definitions: 1 References: 3 EBML_ID_ATTACHEDFILE Definitions: 1 References: 3 EBML_ID_ATTACHMENTLINK Definitions: 1 References: 2 EBML_ID_ATTACHMENTS Definitions: 1 References: 3 EBML_ID_AUDIO Definitions: 1 References: 4 EBML_ID_BITDEPTH Definitions: 1 References: 3 EBML_ID_CHANNELPOSITIONS Definitions: 1 References: 3 EBML_ID_CHANNELS Definitions: 1 References: 3 EBML_ID_CHAPCOUNTRY Definitions: 1 References: 3 EBML_ID_CHAPLANGUAGE Definitions: 1 References: 3 EBML_ID_CHAPPROCESS Definitions: 1 References: 2 EBML_ID_CHAPPROCESSCODECID Definitions: 1 References: 2 EBML_ID_CHAPPROCESSCOMMAND Definitions: 1 References: 2 EBML_ID_CHAPPROCESSDATA Definitions: 1 References: 2 EBML_ID_CHAPPROCESSPRIVATE Definitions: 1 References: 2 EBML_ID_CHAPPROCESSTIME Definitions: 1 References: 2 EBML_ID_CHAPSTRING Definitions: 1 References: 3 EBML_ID_CHAPTERATOM Definitions: 1 References: 4 EBML_ID_CHAPTERDISPLAY Definitions: 1 References: 4 EBML_ID_CHAPTERFLAGENABLED Definitions: 1 References: 3 EBML_ID_CHAPTERFLAGHIDDEN Definitions: 1 References: 3 EBML_ID_CHAPTERPHYSICALEQUIV Definitions: 1 References: 2 EBML_ID_CHAPTERS Definitions: 1 References: 3 EBML_ID_CHAPTERSEGMENTEDITIONUID Definitions: 1 References: 3 EBML_ID_CHAPTERSEGMENTUID Definitions: 1 References: 3 EBML_ID_CHAPTERTIMEEND Definitions: 1 References: 3 EBML_ID_CHAPTERTIMESTART Definitions: 1 References: 3 EBML_ID_CHAPTERTRACK Definitions: 1 References: 4 EBML_ID_CHAPTERTRACKNUMBER Definitions: 1 References: 3 EBML_ID_CHAPTERTRANSLATE Definitions: 1 References: 3 EBML_ID_CHAPTERTRANSLATECODEC Definitions: 1 References: 3 EBML_ID_CHAPTERTRANSLATEEDITIONUID Definitions: 1 References: 3 EBML_ID_CHAPTERTRANSLATEID Definitions: 1 References: 3 EBML_ID_CHAPTERUID Definitions: 1 References: 3 EBML_ID_CLUSTER Definitions: 1 References: 5 EBML_ID_CLUSTERBLOCK Definitions: 1 References: 5 EBML_ID_CLUSTERBLOCKADDID Definitions: 1 References: 2 EBML_ID_CLUSTERBLOCKADDITIONAL Definitions: 1 References: 2 EBML_ID_CLUSTERBLOCKADDITIONID Definitions: 1 References: 2 EBML_ID_CLUSTERBLOCKADDITIONS Definitions: 1 References: 2 EBML_ID_CLUSTERBLOCKDURATION Definitions: 1 References: 3 EBML_ID_CLUSTERBLOCKGROUP Definitions: 1 References: 4 EBML_ID_CLUSTERBLOCKMORE Definitions: 1 References: 2 EBML_ID_CLUSTERBLOCKVIRTUAL Definitions: 1 References: 2 EBML_ID_CLUSTERCODECSTATE Definitions: 1 References: 3 EBML_ID_CLUSTERDELAY Definitions: 1 References: 2 EBML_ID_CLUSTERDURATION Definitions: 1 References: 2 EBML_ID_CLUSTERENCRYPTEDBLOCK Definitions: 1 References: 2 EBML_ID_CLUSTERFRAMENUMBER Definitions: 1 References: 2 EBML_ID_CLUSTERLACENUMBER Definitions: 1 References: 2 EBML_ID_CLUSTERPOSITION Definitions: 1 References: 3 EBML_ID_CLUSTERPREVSIZE Definitions: 1 References: 3 EBML_ID_CLUSTERREFERENCEBLOCK Definitions: 1 References: 3 EBML_ID_CLUSTERREFERENCEPRIORITY Definitions: 1 References: 3 EBML_ID_CLUSTERREFERENCEVIRTUAL Definitions: 1 References: 2 EBML_ID_CLUSTERSILENTTRACKNUMBER Definitions: 1 References: 3 EBML_ID_CLUSTERSILENTTRACKS Definitions: 1 References: 4 EBML_ID_CLUSTERSIMPLEBLOCK Definitions: 1 References: 7 EBML_ID_CLUSTERSLICES Definitions: 1 References: 2 EBML_ID_CLUSTERTIMECODE Definitions: 1 References: 3 EBML_ID_CLUSTERTIMESLICE Definitions: 1 References: 2 EBML_ID_CODECDECODEALL Definitions: 1 References: 3 EBML_ID_CODECDOWNLOADURL Definitions: 1 References: 2 EBML_ID_CODECID Definitions: 1 References: 3 EBML_ID_CODECINFOURL Definitions: 1 References: 2 EBML_ID_CODECNAME Definitions: 1 References: 3 EBML_ID_CODECPRIVATE Definitions: 1 References: 4 EBML_ID_CODECSETTINGS Definitions: 1 References: 2 EBML_ID_COLOURSPACE Definitions: 1 References: 3 EBML_ID_CONTENTCOMPALGO Definitions: 1 References: 3 EBML_ID_CONTENTCOMPRESSION Definitions: 1 References: 4 EBML_ID_CONTENTCOMPSETTINGS Definitions: 1 References: 3 EBML_ID_CONTENTENCALGO Definitions: 1 References: 3 EBML_ID_CONTENTENCKEYID Definitions: 1 References: 3 EBML_ID_CONTENTENCODING Definitions: 1 References: 3 EBML_ID_CONTENTENCODINGORDER Definitions: 1 References: 3 EBML_ID_CONTENTENCODINGS Definitions: 1 References: 4 EBML_ID_CONTENTENCODINGSCOPE Definitions: 1 References: 3 EBML_ID_CONTENTENCODINGTYPE Definitions: 1 References: 3 EBML_ID_CONTENTENCRYPTION Definitions: 1 References: 4 EBML_ID_CONTENTSIGALGO Definitions: 1 References: 3 EBML_ID_CONTENTSIGHASHALGO Definitions: 1 References: 3 EBML_ID_CONTENTSIGKEYID Definitions: 1 References: 3 EBML_ID_CONTENTSIGNATURE Definitions: 1 References: 3 EBML_ID_CRC32 Definitions: 1 References: 3 EBML_ID_CUEBLOCKNUMBER Definitions: 1 References: 3 EBML_ID_CUECLUSTERPOSITION Definitions: 1 References: 3 EBML_ID_CUECODECSTATE Definitions: 1 References: 3 EBML_ID_CUEPOINT Definitions: 1 References: 3 EBML_ID_CUEREFCLUSTER Definitions: 1 References: 2 EBML_ID_CUEREFCODECSTATE Definitions: 1 References: 2 EBML_ID_CUEREFERENCE Definitions: 1 References: 2 EBML_ID_CUEREFNUMBER Definitions: 1 References: 2 EBML_ID_CUEREFTIME Definitions: 1 References: 2 EBML_ID_CUES Definitions: 1 References: 3 EBML_ID_CUETIME Definitions: 1 References: 3 EBML_ID_CUETRACK Definitions: 1 References: 3 EBML_ID_CUETRACKPOSITIONS Definitions: 1 References: 4 EBML_ID_DATEUTC Definitions: 1 References: 3 EBML_ID_DEFAULTDURATION Definitions: 1 References: 3 EBML_ID_DISPLAYHEIGHT Definitions: 1 References: 3 EBML_ID_DISPLAYUNIT Definitions: 1 References: 3 EBML_ID_DISPLAYWIDTH Definitions: 1 References: 3 EBML_ID_DOCTYPE Definitions: 1 References: 3 EBML_ID_DOCTYPEREADVERSION Definitions: 1 References: 3 EBML_ID_DOCTYPEVERSION Definitions: 1 References: 3 EBML_ID_DURATION Definitions: 1 References: 3 EBML_ID_EBML Definitions: 1 References: 3 EBML_ID_EBMLMAXIDLENGTH Definitions: 1 References: 3 EBML_ID_EBMLMAXSIZELENGTH Definitions: 1 References: 3 EBML_ID_EBMLREADVERSION Definitions: 1 References: 3 EBML_ID_EBMLVERSION Definitions: 1 References: 3 EBML_ID_EDITIONENTRY Definitions: 1 References: 3 EBML_ID_EDITIONFLAGDEFAULT Definitions: 1 References: 3 EBML_ID_EDITIONFLAGHIDDEN Definitions: 1 References: 3 EBML_ID_EDITIONFLAGORDERED Definitions: 1 References: 3 EBML_ID_EDITIONUID Definitions: 1 References: 3 EBML_ID_FILEDATA Definitions: 1 References: 4 EBML_ID_FILEDESCRIPTION Definitions: 1 References: 3 EBML_ID_FILEMIMETYPE Definitions: 1 References: 3 EBML_ID_FILENAME Definitions: 1 References: 3 EBML_ID_FILEREFERRAL Definitions: 1 References: 2 EBML_ID_FILEUID Definitions: 1 References: 3 EBML_ID_FLAGDEFAULT Definitions: 1 References: 3 EBML_ID_FLAGENABLED Definitions: 1 References: 3 EBML_ID_FLAGFORCED Definitions: 1 References: 3 EBML_ID_FLAGINTERLACED Definitions: 1 References: 3 EBML_ID_FLAGLACING Definitions: 1 References: 3 EBML_ID_GAMMAVALUE Definitions: 1 References: 3 EBML_ID_INFO Definitions: 1 References: 3 EBML_ID_LANGUAGE Definitions: 1 References: 3 EBML_ID_MAXBLOCKADDITIONID Definitions: 1 References: 3 EBML_ID_MAXCACHE Definitions: 1 References: 3 EBML_ID_MINCACHE Definitions: 1 References: 3 EBML_ID_MUXINGAPP Definitions: 1 References: 3 EBML_ID_NAME Definitions: 1 References: 3 EBML_ID_NEXTFILENAME Definitions: 1 References: 3 EBML_ID_NEXTUID Definitions: 1 References: 3 EBML_ID_OLDSTEREOMODE Definitions: 1 References: 3 EBML_ID_OUTPUTSAMPLINGFREQUENCY Definitions: 1 References: 3 EBML_ID_PIXELCROPBOTTOM Definitions: 1 References: 3 EBML_ID_PIXELCROPLEFT Definitions: 1 References: 3 EBML_ID_PIXELCROPRIGHT Definitions: 1 References: 3 EBML_ID_PIXELCROPTOP Definitions: 1 References: 3 EBML_ID_PIXELHEIGHT Definitions: 1 References: 3 EBML_ID_PIXELWIDTH Definitions: 1 References: 3 EBML_ID_PREVFILENAME Definitions: 1 References: 3 EBML_ID_PREVUID Definitions: 1 References: 3 EBML_ID_SAMPLINGFREQUENCY Definitions: 1 References: 3 EBML_ID_SEEK Definitions: 1 References: 3 EBML_ID_SEEKHEAD Definitions: 1 References: 3 EBML_ID_SEEKID Definitions: 1 References: 3 EBML_ID_SEEKPOSITION Definitions: 1 References: 3 EBML_ID_SEGMENT Definitions: 1 References: 3 EBML_ID_SEGMENTFAMILY Definitions: 1 References: 3 EBML_ID_SEGMENTFILENAME Definitions: 1 References: 3 EBML_ID_SEGMENTUID Definitions: 1 References: 3 EBML_ID_SIMPLETAG Definitions: 1 References: 5 EBML_ID_STEREOMODE Definitions: 1 References: 3 EBML_ID_TAG Definitions: 1 References: 3 EBML_ID_TAGATTACHMENTUID Definitions: 1 References: 3 EBML_ID_TAGBINARY Definitions: 1 References: 3 EBML_ID_TAGCHAPTERUID Definitions: 1 References: 3 EBML_ID_TAGDEFAULT Definitions: 1 References: 3 EBML_ID_TAGEDITIONUID Definitions: 1 References: 3 EBML_ID_TAGLANGUAGE Definitions: 1 References: 3 EBML_ID_TAGNAME Definitions: 1 References: 3 EBML_ID_TAGS Definitions: 1 References: 3 EBML_ID_TAGSTRING Definitions: 1 References: 3 EBML_ID_TAGTRACKUID Definitions: 1 References: 3 EBML_ID_TARGETS Definitions: 1 References: 3 EBML_ID_TARGETTYPE Definitions: 1 References: 3 EBML_ID_TARGETTYPEVALUE Definitions: 1 References: 3 EBML_ID_TIMECODESCALE Definitions: 1 References: 3 EBML_ID_TITLE Definitions: 1 References: 3 EBML_ID_TRACKENTRY Definitions: 1 References: 3 EBML_ID_TRACKNUMBER Definitions: 1 References: 3 EBML_ID_TRACKOFFSET Definitions: 1 References: 2 EBML_ID_TRACKOVERLAY Definitions: 1 References: 2 EBML_ID_TRACKS Definitions: 1 References: 3 EBML_ID_TRACKTIMECODESCALE Definitions: 1 References: 3 EBML_ID_TRACKTRANSLATE Definitions: 1 References: 2 EBML_ID_TRACKTRANSLATECODEC Definitions: 1 References: 2 EBML_ID_TRACKTRANSLATEEDITIONUID Definitions: 1 References: 2 EBML_ID_TRACKTRANSLATETRACKID Definitions: 1 References: 2 EBML_ID_TRACKTYPE Definitions: 1 References: 3 EBML_ID_TRACKUID Definitions: 1 References: 3 EBML_ID_VIDEO Definitions: 1 References: 4 EBML_ID_VOID Definitions: 1 References: 3 EBML_ID_WRITINGAPP Definitions: 1 References: 3 EMPTY_TRASH_DAYS Definitions: 1 References: 28 EP_ALL Definitions: 1 References: 1 EP_ALL_ARCHIVES Definitions: 1 References: 2 EP_ATTACHMENT Definitions: 1 References: 3 EP_AUTHORS Definitions: 1 References: 3 EP_CATEGORIES Definitions: 1 References: 3 EP_COMMENTS Definitions: 1 References: 3 EP_DATE Definitions: 1 References: 3 EP_DAY Definitions: 1 References: 3 EP_MONTH Definitions: 1 References: 3 EP_NONE Definitions: 1 References: 6 EP_PAGES Definitions: 1 References: 4 EP_PERMALINK Definitions: 1 References: 5 EP_ROOT Definitions: 1 References: 4 EP_SEARCH Definitions: 1 References: 3 EP_TAGS Definitions: 1 References: 3 EP_YEAR Definitions: 1 References: 3 EZSQL_VERSION Definitions: 1 References: 1 FORCE_SSL_ADMIN Definitions: 1 References: 3 FORCE_SSL_LOGIN Definitions: 1 References: 3 FS_CHMOD_DIR Definitions: 1 References: 17 FS_CHMOD_FILE Definitions: 1 References: 21 FS_CONNECT_TIMEOUT Definitions: 1 References: 5 FS_TIMEOUT Definitions: 2 References: 8 FTP_ASCII Definitions: 1 References: 21 FTP_AUTOASCII Definitions: 1 References: 9 FTP_BINARY Definitions: 1 References: 19 FTP_FORCE Definitions: 1 References: 3 GETID3_FLV_TAG_AUDIO Definitions: 1 References: 2 GETID3_FLV_TAG_META Definitions: 1 References: 2 GETID3_FLV_TAG_VIDEO Definitions: 1 References: 2 GETID3_FLV_VIDEO_H263 Definitions: 1 References: 3 GETID3_FLV_VIDEO_H264 Definitions: 1 References: 3 GETID3_FLV_VIDEO_SCREEN Definitions: 1 References: 2 GETID3_FLV_VIDEO_SCREENV2 Definitions: 1 References: 2 GETID3_FLV_VIDEO_VP6FLV Definitions: 1 References: 2 GETID3_FLV_VIDEO_VP6FLV_ALPHA Definitions: 1 References: 2 GETID3_HELPERAPPSDIR Definitions: 1 References: 11 GETID3_INCLUDEPATH Definitions: 1 References: 24 GETID3_MP3_VALID_CHECK_FRAMES Definitions: 1 References: 4 GETID3_OS_ISWINDOWS Definitions: 1 References: 7 GETID3_TEMP_DIR Definitions: 1 References: 6 H264_AVC_SEQUENCE_HEADER Definitions: 1 References: 2 H264_PROFILE_BASELINE Definitions: 1 References: 1 H264_PROFILE_EXTENDED Definitions: 1 References: 1 H264_PROFILE_HIGH Definitions: 1 References: 2 H264_PROFILE_HIGH10 Definitions: 1 References: 2 H264_PROFILE_HIGH422 Definitions: 1 References: 2 H264_PROFILE_HIGH444 Definitions: 1 References: 2 H264_PROFILE_HIGH444_PREDICTIVE Definitions: 1 References: 2 H264_PROFILE_MAIN Definitions: 1 References: 1 HEADER_IMAGE Definitions: 3 References: 5 HEADER_IMAGE_HEIGHT Definitions: 3 References: 7 HEADER_IMAGE_WIDTH Definitions: 3 References: 10 HEADER_TEXTCOLOR Definitions: 3 References: 7 HOUR_IN_SECONDS Definitions: 1 References: 45 IFRAME_REQUEST Definitions: 8 References: 12 IS_PROFILE_PAGE Definitions: 2 References: 24 LANGDIR Definitions: 2 References: 4 LOGGED_IN_COOKIE Definitions: 1 References: 12 LOGGED_IN_KEY Definitions: 1 References: 3 LOGGED_IN_SALT Definitions: 1 References: 3 MAGPIE_CACHE_AGE Definitions: 1 References: 3 MAGPIE_CACHE_DIR Definitions: 1 References: 3 MAGPIE_CACHE_FRESH_ONLY Definitions: 1 References: 2 MAGPIE_CACHE_ON Definitions: 1 References: 4 MAGPIE_DEBUG Definitions: 1 References: 10 MAGPIE_FETCH_TIME_OUT Definitions: 1 References: 3 MAGPIE_INITALIZED Definitions: 1 References: 2 MAGPIE_USER_AGENT Definitions: 2 References: 3 MAGPIE_USE_GZIP Definitions: 1 References: 2 MEDIA_TRASH Definitions: 1 References: 13 MINUTE_IN_SECONDS Definitions: 1 References: 9 MULTISITE Definitions: 2 References: 12 MUPLUGINDIR Definitions: 1 References: 2 NONCE_KEY Definitions: 1 References: 3 NONCE_SALT Definitions: 1 References: 3 NO_HEADER_TEXT Definitions: 2 References: 4 OBJECT Definitions: 1 References: 44 OBJECT_K Definitions: 1 References: 4 PASS_COOKIE Definitions: 1 References: 4 PATH_CURRENT_SITE Definitions: 1 References: 3 PCLZIP_ATT_FILE_COMMENT Definitions: 1 References: 4 PCLZIP_ATT_FILE_CONTENT Definitions: 1 References: 4 PCLZIP_ATT_FILE_MTIME Definitions: 1 References: 4 PCLZIP_ATT_FILE_NAME Definitions: 1 References: 6 PCLZIP_ATT_FILE_NEW_FULL_NAME Definitions: 1 References: 4 PCLZIP_ATT_FILE_NEW_SHORT_NAME Definitions: 1 References: 4 PCLZIP_CB_POST_ADD Definitions: 1 References: 7 PCLZIP_CB_POST_DELETE Definitions: 1 References: 2 PCLZIP_CB_POST_EXTRACT Definitions: 1 References: 13 PCLZIP_CB_POST_LIST Definitions: 1 References: 2 PCLZIP_CB_PRE_ADD Definitions: 1 References: 7 PCLZIP_CB_PRE_DELETE Definitions: 1 References: 2 PCLZIP_CB_PRE_EXTRACT Definitions: 1 References: 13 PCLZIP_CB_PRE_LIST Definitions: 1 References: 2 PCLZIP_ERROR_EXTERNAL Definitions: 1 References: 6 PCLZIP_ERR_ALREADY_A_DIRECTORY Definitions: 1 References: 2 PCLZIP_ERR_BAD_CHECKSUM Definitions: 1 References: 3 PCLZIP_ERR_BAD_EXTENSION Definitions: 1 References: 3 PCLZIP_ERR_BAD_EXTRACTED_FILE Definitions: 1 References: 3 PCLZIP_ERR_BAD_FORMAT Definitions: 1 References: 14 PCLZIP_ERR_DELETE_FILE_FAIL Definitions: 1 References: 3 PCLZIP_ERR_DIRECTORY_RESTRICTION Definitions: 1 References: 4 PCLZIP_ERR_DIR_CREATE_FAIL Definitions: 1 References: 4 PCLZIP_ERR_FILENAME_TOO_LONG Definitions: 1 References: 3 PCLZIP_ERR_INVALID_ARCHIVE_ZIP Definitions: 1 References: 8 PCLZIP_ERR_INVALID_ATTRIBUTE_VALUE Definitions: 1 References: 11 PCLZIP_ERR_INVALID_OPTION_VALUE Definitions: 1 References: 11 PCLZIP_ERR_INVALID_PARAMETER Definitions: 1 References: 24 PCLZIP_ERR_INVALID_ZIP Definitions: 1 References: 3 PCLZIP_ERR_MISSING_FILE Definitions: 1 References: 8 PCLZIP_ERR_MISSING_OPTION_VALUE Definitions: 1 References: 12 PCLZIP_ERR_NO_ERROR Definitions: 1 References: 6 PCLZIP_ERR_READ_OPEN_FAIL Definitions: 1 References: 16 PCLZIP_ERR_RENAME_FILE_FAIL Definitions: 1 References: 3 PCLZIP_ERR_UNSUPPORTED_COMPRESSION Definitions: 1 References: 4 PCLZIP_ERR_UNSUPPORTED_ENCRYPTION Definitions: 1 References: 5 PCLZIP_ERR_USER_ABORTED Definitions: 1 References: 7 PCLZIP_ERR_WRITE_OPEN_FAIL Definitions: 1 References: 7 PCLZIP_OPT_ADD_COMMENT Definitions: 1 References: 5 PCLZIP_OPT_ADD_PATH Definitions: 1 References: 14 PCLZIP_OPT_ADD_TEMP_FILE_OFF Definitions: 1 References: 1 PCLZIP_OPT_ADD_TEMP_FILE_ON Definitions: 1 References: 1 PCLZIP_OPT_ADD_TEMP_FILE_THRESHOLD Definitions: 1 References: 1 PCLZIP_OPT_BY_EREG Definitions: 1 References: 4 PCLZIP_OPT_BY_INDEX Definitions: 1 References: 23 PCLZIP_OPT_BY_NAME Definitions: 1 References: 21 PCLZIP_OPT_BY_PREG Definitions: 1 References: 11 PCLZIP_OPT_COMMENT Definitions: 1 References: 10 PCLZIP_OPT_EXTRACT_AS_STRING Definitions: 1 References: 10 PCLZIP_OPT_EXTRACT_DIR_RESTRICTION Definitions: 1 References: 7 PCLZIP_OPT_EXTRACT_IN_OUTPUT Definitions: 1 References: 5 PCLZIP_OPT_NO_COMPRESSION Definitions: 1 References: 8 PCLZIP_OPT_PATH Definitions: 1 References: 8 PCLZIP_OPT_PREPEND_COMMENT Definitions: 1 References: 5 PCLZIP_OPT_REMOVE_ALL_PATH Definitions: 1 References: 15 PCLZIP_OPT_REMOVE_PATH Definitions: 1 References: 14 PCLZIP_OPT_REPLACE_NEWER Definitions: 1 References: 7 PCLZIP_OPT_SET_CHMOD Definitions: 1 References: 6 PCLZIP_OPT_STOP_ON_ERROR Definitions: 1 References: 14 PCLZIP_OPT_TEMP_FILE_OFF Definitions: 1 References: 13 PCLZIP_OPT_TEMP_FILE_ON Definitions: 1 References: 10 PCLZIP_OPT_TEMP_FILE_THRESHOLD Definitions: 1 References: 17 PCLZIP_READ_BLOCK_SIZE Definitions: 1 References: 34 PCLZIP_SEPARATOR Definitions: 1 References: 4 PCLZIP_TEMPORARY_DIR Definitions: 1 References: 7 PCLZIP_TEMPORARY_FILE_RATIO Definitions: 1 References: 3 PHP_INT_MIN Definitions: 1 References: 3 PLUGINDIR Definitions: 1 References: 2 PLUGINS_COOKIE_PATH Definitions: 1 References: 5 PO_MAX_LINE_LEN Definitions: 1 References: 2 RSS Definitions: 1 References: 33 SCRIPT_DEBUG Definitions: 2 References: 14 SECURE_AUTH_COOKIE Definitions: 1 References: 12 SECURE_AUTH_KEY Definitions: 1 References: 3 SECURE_AUTH_SALT Definitions: 1 References: 3 SERVICES_JSON_IN_ARR Definitions: 1 References: 10 SERVICES_JSON_IN_CMT Definitions: 1 References: 3 SERVICES_JSON_IN_OBJ Definitions: 1 References: 10 SERVICES_JSON_IN_STR Definitions: 1 References: 4 SERVICES_JSON_LOOSE_TYPE Definitions: 1 References: 4 SERVICES_JSON_SLICE Definitions: 1 References: 7 SERVICES_JSON_SUPPRESS_ERRORS Definitions: 1 References: 3 SERVICES_JSON_USE_TO_JSON Definitions: 1 References: 2 SHORTINIT Definitions: 2 References: 4 SIMPLEPIE_BUILD Definitions: 1 References: 6 SIMPLEPIE_CONSTRUCT_ALL Definitions: 1 References: 1 SIMPLEPIE_CONSTRUCT_BASE64 Definitions: 1 References: 5 SIMPLEPIE_CONSTRUCT_HTML Definitions: 1 References: 18 SIMPLEPIE_CONSTRUCT_IRI Definitions: 1 References: 60 SIMPLEPIE_CONSTRUCT_MAYBE_HTML Definitions: 1 References: 18 SIMPLEPIE_CONSTRUCT_NONE Definitions: 1 References: 5 SIMPLEPIE_CONSTRUCT_TEXT Definitions: 1 References: 258 SIMPLEPIE_CONSTRUCT_XHTML Definitions: 1 References: 8 SIMPLEPIE_FILE_SOURCE_CURL Definitions: 1 References: 2 SIMPLEPIE_FILE_SOURCE_FILE_GET_CONTENTS Definitions: 1 References: 2 SIMPLEPIE_FILE_SOURCE_FSOCKOPEN Definitions: 1 References: 2 SIMPLEPIE_FILE_SOURCE_LOCAL Definitions: 1 References: 3 SIMPLEPIE_FILE_SOURCE_NONE Definitions: 1 References: 2 SIMPLEPIE_FILE_SOURCE_REMOTE Definitions: 1 References: 11 SIMPLEPIE_IANA_LINK_RELATIONS_REGISTRY Definitions: 1 References: 19 SIMPLEPIE_LINKBACK Definitions: 1 References: 1 SIMPLEPIE_LOCATOR_ALL Definitions: 1 References: 4 SIMPLEPIE_LOCATOR_AUTODISCOVERY Definitions: 1 References: 2 SIMPLEPIE_LOCATOR_LOCAL_BODY Definitions: 1 References: 3 SIMPLEPIE_LOCATOR_LOCAL_EXTENSION Definitions: 1 References: 3 SIMPLEPIE_LOCATOR_NONE Definitions: 1 References: 2 SIMPLEPIE_LOCATOR_REMOTE_BODY Definitions: 1 References: 3 SIMPLEPIE_LOCATOR_REMOTE_EXTENSION Definitions: 1 References: 3 SIMPLEPIE_LOWERCASE Definitions: 1 References: 1 SIMPLEPIE_NAME Definitions: 1 References: 5 SIMPLEPIE_NAMESPACE_ATOM_03 Definitions: 1 References: 79 SIMPLEPIE_NAMESPACE_ATOM_10 Definitions: 1 References: 89 SIMPLEPIE_NAMESPACE_DC_10 Definitions: 1 References: 21 SIMPLEPIE_NAMESPACE_DC_11 Definitions: 1 References: 21 SIMPLEPIE_NAMESPACE_GEORSS Definitions: 1 References: 7 SIMPLEPIE_NAMESPACE_ITUNES Definitions: 1 References: 24 SIMPLEPIE_NAMESPACE_MEDIARSS Definitions: 1 References: 116 SIMPLEPIE_NAMESPACE_MEDIARSS_WRONG Definitions: 1 References: 2 SIMPLEPIE_NAMESPACE_MEDIARSS_WRONG2 Definitions: 1 References: 2 SIMPLEPIE_NAMESPACE_MEDIARSS_WRONG3 Definitions: 1 References: 2 SIMPLEPIE_NAMESPACE_MEDIARSS_WRONG4 Definitions: 1 References: 2 SIMPLEPIE_NAMESPACE_MEDIARSS_WRONG5 Definitions: 1 References: 2 SIMPLEPIE_NAMESPACE_RDF Definitions: 1 References: 20 SIMPLEPIE_NAMESPACE_RSS_090 Definitions: 1 References: 23 SIMPLEPIE_NAMESPACE_RSS_10 Definitions: 1 References: 23 SIMPLEPIE_NAMESPACE_RSS_20 Definitions: 1 References: 50 SIMPLEPIE_NAMESPACE_W3C_BASIC_GEO Definitions: 1 References: 10 SIMPLEPIE_NAMESPACE_XHTML Definitions: 1 References: 3 SIMPLEPIE_NAMESPACE_XML Definitions: 1 References: 5 SIMPLEPIE_PCRE_HTML_ATTRIBUTE Definitions: 1 References: 4 SIMPLEPIE_PCRE_XML_ATTRIBUTE Definitions: 1 References: 3 SIMPLEPIE_SAME_CASE Definitions: 1 References: 1 SIMPLEPIE_TYPE_ALL Definitions: 1 References: 2 SIMPLEPIE_TYPE_ATOM_03 Definitions: 1 References: 3 SIMPLEPIE_TYPE_ATOM_10 Definitions: 1 References: 3 SIMPLEPIE_TYPE_ATOM_ALL Definitions: 1 References: 2 SIMPLEPIE_TYPE_NONE Definitions: 1 References: 3 SIMPLEPIE_TYPE_RSS_090 Definitions: 1 References: 4 SIMPLEPIE_TYPE_RSS_091 Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_091_NETSCAPE Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_091_USERLAND Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_092 Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_093 Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_094 Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_10 Definitions: 1 References: 4 SIMPLEPIE_TYPE_RSS_20 Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_ALL Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_RDF Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_SYNDICATION Definitions: 1 References: 7 SIMPLEPIE_UPPERCASE Definitions: 1 References: 1 SIMPLEPIE_URL Definitions: 1 References: 3 SIMPLEPIE_USERAGENT Definitions: 1 References: 4 SIMPLEPIE_VERSION Definitions: 1 References: 4 SITECOOKIEPATH Definitions: 2 References: 20 SITE_ID_CURRENT_SITE Definitions: 1 References: 3 STYLESHEETPATH Definitions: 1 References: 8 SUBDOMAIN_INSTALL Definitions: 3 References: 13 TEMPLATEPATH Definitions: 1 References: 9 TEST_COOKIE Definitions: 1 References: 5 UPLOADBLOGSDIR Definitions: 1 References: 5 UPLOADS Definitions: 1 References: 7 USER_COOKIE Definitions: 1 References: 4 VHOST Definitions: 2 References: 11 WEEK_IN_SECONDS Definitions: 1 References: 6 WPINC Definitions: 5 References: 204 WPLANG Definitions: 1 References: 22 WPMU_ACCEL_REDIRECT Definitions: 1 References: 3 WPMU_PLUGIN_DIR Definitions: 1 References: 20 WPMU_PLUGIN_URL Definitions: 1 References: 3 WPMU_SENDFILE Definitions: 1 References: 3 WP_ADMIN Definitions: 4 References: 10 WP_ALLOW_REPAIR Definitions: 2 References: 3 WP_BLOG_ADMIN Definitions: 1 References: 3 WP_CACHE Definitions: 1 References: 6 WP_CONTENT_DIR Definitions: 3 References: 95 WP_CONTENT_URL Definitions: 1 References: 10 WP_CRON_LOCK_TIMEOUT Definitions: 1 References: 4 WP_DEBUG Definitions: 3 References: 26 WP_DEBUG_DISPLAY Definitions: 1 References: 5 WP_DEBUG_LOG Definitions: 1 References: 5 WP_DEFAULT_THEME Definitions: 1 References: 19 WP_IMPORTING Definitions: 1 References: 7 WP_INSTALLING Definitions: 5 References: 37 WP_INSTALLING_NETWORK Definitions: 2 References: 9 WP_LANG_DIR Definitions: 2 References: 32 WP_LOAD_IMPORTERS Definitions: 2 References: 3 WP_MAIL_INTERVAL Definitions: 1 References: 3 WP_MAX_MEMORY_LIMIT Definitions: 1 References: 8 WP_MEMORY_LIMIT Definitions: 2 References: 7 WP_NETWORK_ADMIN Definitions: 2 References: 9 WP_PLUGIN_DIR Definitions: 1 References: 58 WP_PLUGIN_URL Definitions: 1 References: 4 WP_POST_REVISIONS Definitions: 1 References: 3 WP_REPAIRING Definitions: 1 References: 4 WP_SETUP_CONFIG Definitions: 1 References: 5 WP_UNINSTALL_PLUGIN Definitions: 1 References: 1 WP_USER_ADMIN Definitions: 2 References: 9 WP_USE_THEMES Definitions: 1 References: 6 WXR_VERSION Definitions: 1 References: 1 XMLRPC_REQUEST Definitions: 1 References: 8 YEAR_IN_SECONDS Definitions: 1 References: 21
If done correctly your functions.php file should now look like this at the top. add_action('init', 'start_session', 1); function start_session() { if(!session_id()) { session_start(); } add_action(‘wp_logout’, ‘end_session’); add_action(‘wp_login’, ‘end_session’); add_action(‘end_session_action’, ‘end_session’); function end_session() { session_destroy (); } You can now add data to the global $_SESSION variable that will be accessible at any point within the application during a user session by accessing the $_SESSION variable. The variable is an array; below is an example of adding data to the session array. $foo = ‘Foo Data’; $_SESSION[‘foo’] = $foo; Something to think about: If you are building a scalable or load balanced website, you may not want to use sessions. HTTP is Stateless and PHP SESSIONS are State driven. Sessions are stored and handled by the server. Routing each session to the proper server requires more complex configuration and creates a single point of failure for the users who’s sessions are stored on that server. When possible, it is best to store session information in the client’s browser. Though it may not be extremely expensive to the server resources to query session objects, it is always wise to reduce overhead whenever possible. Thank you for reading. I hope you find this article helpful and please comment below with any questions. Happy coding! ?? <end node> 5P9i0s8y19Z dt= <node>html5 1 <input required min='' max='' placeholder='' > <input type="number" min="0" max="100" step="5"> accept audio/* video/* image/* MIME_type Specifies the types of files that the server accepts (only for type="file") align left right top middle bottom Not supported in HTML5. Deprecated in HTML 4.01. Specifies the alignment of an image input (only for type="image") alt text Specifies an alternate text for images (only for type="image") autocompleteNew on off Specifies whether an <input> element should have autocomplete enabled autofocusNew autofocus Specifies that an <input> element should automatically get focus when the page loads checked checked Specifies that an <input> element should be pre-selected when the page loads (for type="checkbox" or type="radio") disabled disabled Specifies that an <input> element should be disabled formNew form_id Specifies one or more forms the <input> element belongs to formactionNew URL Specifies the URL of the file that will process the input control when the form is submitted (for type="submit" and type="image") formenctypeNew application/x-www-form-urlencoded multipart/form-data text/plain Specifies how the form-data should be encoded when submitting it to the server (for type="submit" and type="image") formmethodNew get post Defines the HTTP method for sending data to the action URL (for type="submit" and type="image") formnovalidateNew formnovalidate Defines that form elements should not be validated when submitted formtargetNew _blank _self _parent _top framename Specifies where to display the response that is received after submitting the form (for type="submit" and type="image") heightNew pixels Specifies the height of an <input> element (only for type="image") listNew datalist_id Refers to a <datalist> element that contains pre-defined options for an <input> element max New number date Specifies the maximum value for an <input> element maxlength number Specifies the maximum number of characters allowed in an <input> element min New number date Specifies a minimum value for an <input> element multiple New multiple Specifies that a user can enter more than one value in an <input> element name text Specifies the name of an <input> element patternNew regexp Specifies a regular expression that an <input> element's value is checked against placeholder New text Specifies a short hint that describes the expected value of an <input> element readonly readonly Specifies that an input field is read-only required New required Specifies that an input field must be filled out before submitting the form size number Specifies the width, in characters, of an <input> element src URL Specifies the URL of the image to use as a submit button (only for type="image") stepNew number Specifies the legal number intervals for an input field HTML5 Input Types checkbox color date datetime datetime-local email file hidden image month number password radio range reset search submit tel text time url week Specifies the type <input> element to display value text Specifies the value of an <input> element
width New pixels Specifies the width of an <input> element (only for type="image") <end node> 5P9i0s8y19Z dt= <node>reserved words 1 List of reserved names in $_POST and $_REQUEST used by WordPress 3.5 _ajax_nonce _page _per_page _signup_form _total _url _wp_http_referer _wp_original_http_referer _wp_unfiltered_html_comment _wpnonce _wpnonce-custom-header-upload aa action action2 active_post_lock add_new add_new_users addmeta admin_bar_front admin_color admin_email admin_password admin_password2 ajax align allblogs allusers alt approve_parent approved attachment attachment_id attachments auth_cookie author author_name autocomplete_type auto_draft auto-add-pages autosave background-attachment background-color background-position-x background-repeat banned_email_domains blog blog_name blog_public blog_upload_space blogname bulk_edit c calendar cat category_base category_name catslist changeit changes charset checkbox checked clear-recent-list closed comment comment_approved comment_author comment_author_email comment_author_url comment_content comment_date comment_ID comment_parent comment_post_ID comment_shortcuts comment_status comments_listing comments_popup confirmdelete connection_type content context cpage create-new-attachment createuser customize_messenger_channel customized customlink-tab date date_format date_format_custom day default-header delete delete_all delete_all2 delete_comments delete_option delete_tags delete_widget deletebookmarks deletecomment deleted deletemeta deletepost description detached dismiss display_name do edit_date email error exact excerpt features feed fetch fheight file fileupload_maxk filter find_detached first_comment first_comment_author first_comment_url first_name first_page first_post found_post_id fwidth global_terms_enabled GLOBALS gmt_offset guid height hh hidden hidden_aa hidden_jj hidden_mm hidden_mn hidden_hh history hostname hour html-upload id ID ids id_base illegal_names insert-gallery insertonlybutton interim-login item-object item-type jj json json_data key last_name limited_email_domains link_id link_image link_name link_rss link_url link_visible linkcheck locale locked log logged_in_cookie m media media_type menu menu_items menu-item menu-item-attr-title menu-item-classes menu-item-db-id menu-item-description menu-item-object menu-item-object-id menu-item-parent-id menu-item-position menu-item-target menu-item-title menu-item-type menu-item-url menu-item-xfn menu-locations menu-name message meta metakeyinput metakeyselect metavalue minute mm mn mode monthnum more move multi_number name nav-menu-locations new new_role new_slug new_title newcat newcomment_author newcomment_author_email newcomment_author_url newcontent newuser nickname no_placeholder noapi noconfirmation noredir number offset oitar option option_page order orderby p pb page page_columns page_id page_options paged pagegen_timestamp pagename parent_id pass1 pass2 password permalink_structure photo_description photo_src phperror ping_status plugin plugin_status pointer position post post_category post_data post_format post_ID post_id post_mime_type post_password post_status post_title post_type post_view postid posts preview primary_blog private_key ps public_key publish pwd query reassign_user reauth redirect redirect_to ref referredby registration registrationnotification rememberme remove-background removeheader removewidget reset-background resetheader review rich_editing robots role s same save savewidget savewidgets screen scrollto search second section selectall selection send send_password sentence short show_sticky sidebar sidebars signup_for signup_form_id site_id site_name sitename size skip-cropping spam spammed src ss stage start static status sticky subdomain_install submit subpost subpost_id super_admin tab tag tag_ID tag-name tag_base tags_input tax tax_input tag-name target taxonomy tb term text-color the-widget-id theme theme_status thumb timezone_string time_format time_format_custom title thumbnail_id trash trashed type undismiss unspam unspammed untrash untrashed url update_home_url updated upgrade upload_filetypes upload_space_check_disabled use_ssl user user_id user_login user_name username users verify-delete version visibility visible w weblog_title welcome_email welcome_user_email widget_id widget_number widget-id widget-recent-comments widget-rss width withcomments withoutcomments wp_customize wp_http_referer wp_screen_options wp-preview WPLANG x1 y1 year <end node> 5P9i0s8y19Z dt= <node>Settings 1 wp_options in the database table <end node> 5P9i0s8y19Z dt= <node>Upgrades 1 http://codex.wordpress.org/Files_Automatically_Replaced_by_Core_Upgrade When using the core upgrade function, introduced with Version 2.7, some old files, which are no longer included with the latest release, will be deleted. The list of files to be deleted is in the wp-admin/includes/update-core.php file. In addition to the files to be deleted, all other core files are replaced with the newer versions. If you have made modifications to any core files, including the WordPress Default theme files, you'll need to insure they are backed up before attempting the core upgrade. After the upgrade, you'll have to retrofit the modifications to the new core files again. Simply re-using the old modified files is NOT recommended. Files Set For Deletion $_old_files = array( // 2.0 'wp-admin/import-b2.php', 'wp-admin/import-blogger.php', 'wp-admin/import-greymatter.php', 'wp-admin/import-livejournal.php', 'wp-admin/import-mt.php', 'wp-admin/import-rss.php', 'wp-admin/import-textpattern.php', 'wp-admin/quicktags.js', 'wp-images/fade-butt.png', 'wp-images/get-firefox.png', 'wp-images/header-shadow.png', 'wp-images/smilies', 'wp-images/wp-small.png', 'wp-images/wpminilogo.png', 'wp.php', // 2.0.8 'wp-includes/js/tinymce/plugins/inlinepopups/readme.txt', // 2.1 'wp-admin/edit-form-ajax-cat.php', 'wp-admin/execute-pings.php', 'wp-admin/inline-uploading.php', 'wp-admin/link-categories.php', 'wp-admin/list-manipulation.js', 'wp-admin/list-manipulation.php', 'wp-includes/comment-functions.php', 'wp-includes/feed-functions.php', 'wp-includes/functions-compat.php', 'wp-includes/functions-formatting.php', 'wp-includes/functions-post.php', 'wp-includes/js/dbx-key.js', 'wp-includes/js/tinymce/plugins/autosave/langs/cs.js', 'wp-includes/js/tinymce/plugins/autosave/langs/sv.js', 'wp-includes/links.php', 'wp-includes/pluggable-functions.php', 'wp-includes/template-functions-author.php', 'wp-includes/template-functions-category.php', 'wp-includes/template-functions-general.php', 'wp-includes/template-functions-links.php', 'wp-includes/template-functions-post.php', 'wp-includes/wp-l10n.php', // 2.2 'wp-admin/cat-js.php', 'wp-admin/import/b2.php', 'wp-includes/js/autosave-js.php', 'wp-includes/js/list-manipulation-js.php', 'wp-includes/js/wp-ajax-js.php', // 2.3 'wp-admin/admin-db.php', 'wp-admin/cat.js', 'wp-admin/categories.js', 'wp-admin/custom-fields.js', 'wp-admin/dbx-admin-key.js', 'wp-admin/edit-comments.js', 'wp-admin/install-rtl.css', 'wp-admin/install.css', 'wp-admin/upgrade-schema.php', 'wp-admin/upload-functions.php', 'wp-admin/upload-rtl.css', 'wp-admin/upload.css', 'wp-admin/upload.js', 'wp-admin/users.js', 'wp-admin/widgets-rtl.css', 'wp-admin/widgets.css', 'wp-admin/xfn.js', 'wp-includes/js/tinymce/license.html', // 2.5 'wp-admin/css/upload.css', 'wp-admin/images/box-bg-left.gif', 'wp-admin/images/box-bg-right.gif', 'wp-admin/images/box-bg.gif', 'wp-admin/images/box-butt-left.gif', 'wp-admin/images/box-butt-right.gif', 'wp-admin/images/box-butt.gif', 'wp-admin/images/box-head-left.gif', 'wp-admin/images/box-head-right.gif', 'wp-admin/images/box-head.gif', 'wp-admin/images/heading-bg.gif', 'wp-admin/images/login-bkg-bottom.gif', 'wp-admin/images/login-bkg-tile.gif', 'wp-admin/images/notice.gif', 'wp-admin/images/toggle.gif', 'wp-admin/includes/upload.php', 'wp-admin/js/dbx-admin-key.js', 'wp-admin/js/link-cat.js', 'wp-admin/profile-update.php', 'wp-admin/templates.php', 'wp-includes/images/wlw/WpComments.png', 'wp-includes/images/wlw/WpIcon.png', 'wp-includes/images/wlw/WpWatermark.png', 'wp-includes/js/dbx.js', 'wp-includes/js/fat.js', 'wp-includes/js/list-manipulation.js', 'wp-includes/js/tinymce/langs/en.js', 'wp-includes/js/tinymce/plugins/autosave/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/autosave/langs', 'wp-includes/js/tinymce/plugins/directionality/images', 'wp-includes/js/tinymce/plugins/directionality/langs', 'wp-includes/js/tinymce/plugins/inlinepopups/css', 'wp-includes/js/tinymce/plugins/inlinepopups/images', 'wp-includes/js/tinymce/plugins/inlinepopups/jscripts', 'wp-includes/js/tinymce/plugins/paste/images', 'wp-includes/js/tinymce/plugins/paste/jscripts', 'wp-includes/js/tinymce/plugins/paste/langs', 'wp-includes/js/tinymce/plugins/spellchecker/classes/HttpClient.class.php', 'wp-includes/js/tinymce/plugins/spellchecker/classes/TinyGoogleSpell.class.php', 'wp-includes/js/tinymce/plugins/spellchecker/classes/TinyPspell.class.php', 'wp-includes/js/tinymce/plugins/spellchecker/classes/TinyPspellShell.class.php', 'wp-includes/js/tinymce/plugins/spellchecker/css/spellchecker.css', 'wp-includes/js/tinymce/plugins/spellchecker/images', 'wp-includes/js/tinymce/plugins/spellchecker/langs', 'wp-includes/js/tinymce/plugins/spellchecker/tinyspell.php', 'wp-includes/js/tinymce/plugins/wordpress/images', 'wp-includes/js/tinymce/plugins/wordpress/langs', 'wp-includes/js/tinymce/plugins/wordpress/wordpress.css', 'wp-includes/js/tinymce/plugins/wphelp', 'wp-includes/js/tinymce/themes/advanced/css', 'wp-includes/js/tinymce/themes/advanced/images', 'wp-includes/js/tinymce/themes/advanced/jscripts', 'wp-includes/js/tinymce/themes/advanced/langs', // 2.5.1 'wp-includes/js/tinymce/tiny_mce_gzip.php', // 2.6 'wp-admin/bookmarklet.php', 'wp-includes/js/jquery/jquery.dimensions.min.js', 'wp-includes/js/tinymce/plugins/wordpress/popups.css', 'wp-includes/js/wp-ajax.js', // 2.7 'wp-admin/css/press-this-ie-rtl.css', 'wp-admin/css/press-this-ie.css', 'wp-admin/css/upload-rtl.css', 'wp-admin/edit-form.php', 'wp-admin/images/comment-pill.gif', 'wp-admin/images/comment-stalk-classic.gif', 'wp-admin/images/comment-stalk-fresh.gif', 'wp-admin/images/comment-stalk-rtl.gif', 'wp-admin/images/del.png', 'wp-admin/images/gear.png', 'wp-admin/images/media-button-gallery.gif', 'wp-admin/images/media-buttons.gif', 'wp-admin/images/postbox-bg.gif', 'wp-admin/images/tab.png', 'wp-admin/images/tail.gif', 'wp-admin/js/forms.js', 'wp-admin/js/upload.js', 'wp-admin/link-import.php', 'wp-includes/images/audio.png', 'wp-includes/images/css.png', 'wp-includes/images/default.png', 'wp-includes/images/doc.png', 'wp-includes/images/exe.png', 'wp-includes/images/html.png', 'wp-includes/images/js.png', 'wp-includes/images/pdf.png', 'wp-includes/images/swf.png', 'wp-includes/images/tar.png', 'wp-includes/images/text.png', 'wp-includes/images/video.png', 'wp-includes/images/zip.png', 'wp-includes/js/tinymce/tiny_mce_config.php', 'wp-includes/js/tinymce/tiny_mce_ext.js', // 2.8 'wp-admin/js/users.js', 'wp-includes/js/swfupload/plugins/swfupload.documentready.js', 'wp-includes/js/swfupload/plugins/swfupload.graceful_degradation.js', 'wp-includes/js/swfupload/swfupload_f9.swf', 'wp-includes/js/tinymce/plugins/autosave', 'wp-includes/js/tinymce/plugins/paste/css', 'wp-includes/js/tinymce/utils/mclayer.js', 'wp-includes/js/tinymce/wordpress.css', // 2.8.5 'wp-admin/import/btt.php', 'wp-admin/import/jkw.php', // 2.9 'wp-admin/js/page.dev.js', 'wp-admin/js/page.js', 'wp-admin/js/set-post-thumbnail-handler.dev.js', 'wp-admin/js/set-post-thumbnail-handler.js', 'wp-admin/js/slug.dev.js', 'wp-admin/js/slug.js', 'wp-includes/gettext.php', 'wp-includes/js/tinymce/plugins/wordpress/js', 'wp-includes/streams.php', // MU 'README.txt', 'htaccess.dist', 'index-install.php', 'wp-admin/css/mu-rtl.css', 'wp-admin/css/mu.css', 'wp-admin/images/site-admin.png', 'wp-admin/includes/mu.php', 'wp-admin/wpmu-admin.php', 'wp-admin/wpmu-blogs.php', 'wp-admin/wpmu-edit.php', 'wp-admin/wpmu-options.php', 'wp-admin/wpmu-themes.php', 'wp-admin/wpmu-upgrade-site.php', 'wp-admin/wpmu-users.php', 'wp-includes/images/wordpress-mu.png', 'wp-includes/wpmu-default-filters.php', 'wp-includes/wpmu-functions.php', 'wpmu-settings.php', // 3.0 'wp-admin/categories.php', 'wp-admin/edit-category-form.php', 'wp-admin/edit-page-form.php', 'wp-admin/edit-pages.php', 'wp-admin/images/admin-header-footer.png', 'wp-admin/images/browse-happy.gif', 'wp-admin/images/ico-add.png', 'wp-admin/images/ico-close.png', 'wp-admin/images/ico-edit.png', 'wp-admin/images/ico-viewpage.png', 'wp-admin/images/fav-top.png', 'wp-admin/images/screen-options-left.gif', 'wp-admin/images/wp-logo-vs.gif', 'wp-admin/images/wp-logo.gif', 'wp-admin/import', 'wp-admin/js/wp-gears.dev.js', 'wp-admin/js/wp-gears.js', 'wp-admin/options-misc.php', 'wp-admin/page-new.php', 'wp-admin/page.php', 'wp-admin/rtl.css', 'wp-admin/rtl.dev.css', 'wp-admin/update-links.php', 'wp-admin/wp-admin.css', 'wp-admin/wp-admin.dev.css', 'wp-includes/js/codepress', 'wp-includes/js/codepress/engines/khtml.js', 'wp-includes/js/codepress/engines/older.js', 'wp-includes/js/jquery/autocomplete.dev.js', 'wp-includes/js/jquery/autocomplete.js', 'wp-includes/js/jquery/interface.js', 'wp-includes/js/scriptaculous/prototype.js', 'wp-includes/js/tinymce/wp-tinymce.js', // 3.1 'wp-admin/edit-attachment-rows.php', 'wp-admin/edit-link-categories.php', 'wp-admin/edit-link-category-form.php', 'wp-admin/edit-post-rows.php', 'wp-admin/images/button-grad-active-vs.png', 'wp-admin/images/button-grad-vs.png', 'wp-admin/images/fav-arrow-vs-rtl.gif', 'wp-admin/images/fav-arrow-vs.gif', 'wp-admin/images/fav-top-vs.gif', 'wp-admin/images/list-vs.png', 'wp-admin/images/screen-options-right-up.gif', 'wp-admin/images/screen-options-right.gif', 'wp-admin/images/visit-site-button-grad-vs.gif', 'wp-admin/images/visit-site-button-grad.gif', 'wp-admin/link-category.php', 'wp-admin/sidebar.php', 'wp-includes/classes.php', 'wp-includes/js/tinymce/blank.htm', 'wp-includes/js/tinymce/plugins/media/css/content.css', 'wp-includes/js/tinymce/plugins/media/img', 'wp-includes/js/tinymce/plugins/safari', // 3.2 'wp-admin/images/logo-login.gif', 'wp-admin/images/star.gif', 'wp-admin/js/list-table.dev.js', 'wp-admin/js/list-table.js', 'wp-includes/default-embeds.php', 'wp-includes/js/tinymce/plugins/wordpress/img/help.gif', 'wp-includes/js/tinymce/plugins/wordpress/img/more.gif', 'wp-includes/js/tinymce/plugins/wordpress/img/toolbars.gif', 'wp-includes/js/tinymce/themes/advanced/img/fm.gif', 'wp-includes/js/tinymce/themes/advanced/img/sflogo.png', // 3.3 'wp-admin/css/colors-classic-rtl.css', 'wp-admin/css/colors-classic-rtl.dev.css', 'wp-admin/css/colors-fresh-rtl.css', 'wp-admin/css/colors-fresh-rtl.dev.css', 'wp-admin/css/dashboard-rtl.dev.css', 'wp-admin/css/dashboard.dev.css', 'wp-admin/css/global-rtl.css', 'wp-admin/css/global-rtl.dev.css', 'wp-admin/css/global.css', 'wp-admin/css/global.dev.css', 'wp-admin/css/install-rtl.dev.css', 'wp-admin/css/login-rtl.dev.css', 'wp-admin/css/login.dev.css', 'wp-admin/css/ms.css', 'wp-admin/css/ms.dev.css', 'wp-admin/css/nav-menu-rtl.css', 'wp-admin/css/nav-menu-rtl.dev.css', 'wp-admin/css/nav-menu.css', 'wp-admin/css/nav-menu.dev.css', 'wp-admin/css/plugin-install-rtl.css', 'wp-admin/css/plugin-install-rtl.dev.css', 'wp-admin/css/plugin-install.css', 'wp-admin/css/plugin-install.dev.css', 'wp-admin/css/press-this-rtl.dev.css', 'wp-admin/css/press-this.dev.css', 'wp-admin/css/theme-editor-rtl.css', 'wp-admin/css/theme-editor-rtl.dev.css', 'wp-admin/css/theme-editor.css', 'wp-admin/css/theme-editor.dev.css', 'wp-admin/css/theme-install-rtl.css', 'wp-admin/css/theme-install-rtl.dev.css', 'wp-admin/css/theme-install.css', 'wp-admin/css/theme-install.dev.css', 'wp-admin/css/widgets-rtl.dev.css', 'wp-admin/css/widgets.dev.css', 'wp-admin/includes/internal-linking.php', 'wp-includes/images/admin-bar-sprite-rtl.png', 'wp-includes/js/jquery/ui.button.js', 'wp-includes/js/jquery/ui.core.js', 'wp-includes/js/jquery/ui.dialog.js', 'wp-includes/js/jquery/ui.draggable.js', 'wp-includes/js/jquery/ui.droppable.js', 'wp-includes/js/jquery/ui.mouse.js', 'wp-includes/js/jquery/ui.position.js', 'wp-includes/js/jquery/ui.resizable.js', 'wp-includes/js/jquery/ui.selectable.js', 'wp-includes/js/jquery/ui.sortable.js', 'wp-includes/js/jquery/ui.tabs.js', 'wp-includes/js/jquery/ui.widget.js', 'wp-includes/js/l10n.dev.js', 'wp-includes/js/l10n.js', 'wp-includes/js/tinymce/plugins/wplink/css', 'wp-includes/js/tinymce/plugins/wplink/img', 'wp-includes/js/tinymce/plugins/wplink/js', 'wp-includes/js/tinymce/themes/advanced/img/wpicons.png', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/butt2.png', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/button_bg.png', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/down_arrow.gif', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/fade-butt.png', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/separator.gif', // Don't delete, yet: 'wp-rss.php', // Don't delete, yet: 'wp-rdf.php', // Don't delete, yet: 'wp-rss2.php', // Don't delete, yet: 'wp-commentsrss2.php', // Don't delete, yet: 'wp-atom.php', // Don't delete, yet: 'wp-feed.php', // 3.4 'wp-admin/images/gray-star.png', 'wp-admin/images/logo-login.png', 'wp-admin/images/star.png', 'wp-admin/index-extra.php', 'wp-admin/network/index-extra.php', 'wp-admin/user/index-extra.php', 'wp-admin/images/screenshots/admin-flyouts.png', 'wp-admin/images/screenshots/coediting.png', 'wp-admin/images/screenshots/drag-and-drop.png', 'wp-admin/images/screenshots/help-screen.png', 'wp-admin/images/screenshots/media-icon.png', 'wp-admin/images/screenshots/new-feature-pointer.png', 'wp-admin/images/screenshots/welcome-screen.png', 'wp-includes/css/editor-buttons.css', 'wp-includes/css/editor-buttons.dev.css', 'wp-includes/js/tinymce/plugins/paste/blank.htm', 'wp-includes/js/tinymce/plugins/wordpress/css', 'wp-includes/js/tinymce/plugins/wordpress/editor_plugin.dev.js', 'wp-includes/js/tinymce/plugins/wordpress/img/embedded.png', 'wp-includes/js/tinymce/plugins/wordpress/img/more_bug.gif', 'wp-includes/js/tinymce/plugins/wordpress/img/page_bug.gif', 'wp-includes/js/tinymce/plugins/wpdialogs/editor_plugin.dev.js', 'wp-includes/js/tinymce/plugins/wpeditimage/css/editimage-rtl.css', 'wp-includes/js/tinymce/plugins/wpeditimage/editor_plugin.dev.js', 'wp-includes/js/tinymce/plugins/wpfullscreen/editor_plugin.dev.js', 'wp-includes/js/tinymce/plugins/wpgallery/editor_plugin.dev.js', 'wp-includes/js/tinymce/plugins/wpgallery/img/gallery.png', 'wp-includes/js/tinymce/plugins/wplink/editor_plugin.dev.js', // Don't delete, yet: 'wp-pass.php', // Don't delete, yet: 'wp-register.php', // 3.5 'wp-admin/gears-manifest.php', 'wp-admin/includes/manifest.php', 'wp-admin/images/archive-link.png', 'wp-admin/images/blue-grad.png', 'wp-admin/images/button-grad-active.png', 'wp-admin/images/button-grad.png', 'wp-admin/images/ed-bg-vs.gif', 'wp-admin/images/ed-bg.gif', 'wp-admin/images/fade-butt.png', 'wp-admin/images/fav-arrow-rtl.gif', 'wp-admin/images/fav-arrow.gif', 'wp-admin/images/fav-vs.png', 'wp-admin/images/fav.png', 'wp-admin/images/gray-grad.png', 'wp-admin/images/loading-publish.gif', 'wp-admin/images/logo-ghost.png', 'wp-admin/images/logo.gif', 'wp-admin/images/menu-arrow-frame-rtl.png', 'wp-admin/images/menu-arrow-frame.png', 'wp-admin/images/menu-arrows.gif', 'wp-admin/images/menu-bits-rtl-vs.gif', 'wp-admin/images/menu-bits-rtl.gif', 'wp-admin/images/menu-bits-vs.gif', 'wp-admin/images/menu-bits.gif', 'wp-admin/images/menu-dark-rtl-vs.gif', 'wp-admin/images/menu-dark-rtl.gif', 'wp-admin/images/menu-dark-vs.gif', 'wp-admin/images/menu-dark.gif', 'wp-admin/images/required.gif', 'wp-admin/images/screen-options-toggle-vs.gif', 'wp-admin/images/screen-options-toggle.gif', 'wp-admin/images/toggle-arrow-rtl.gif', 'wp-admin/images/toggle-arrow.gif', 'wp-admin/images/upload-classic.png', 'wp-admin/images/upload-fresh.png', 'wp-admin/images/white-grad-active.png', 'wp-admin/images/white-grad.png', 'wp-admin/images/widgets-arrow-vs.gif', 'wp-admin/images/widgets-arrow.gif', 'wp-admin/images/wpspin_dark.gif', 'wp-includes/images/upload.png', 'wp-includes/js/prototype.js', 'wp-includes/js/scriptaculous', 'wp-admin/css/wp-admin-rtl.dev.css', 'wp-admin/css/wp-admin.dev.css', 'wp-admin/css/media-rtl.dev.css', 'wp-admin/css/media.dev.css', 'wp-admin/css/colors-classic.dev.css', 'wp-admin/css/customize-controls-rtl.dev.css', 'wp-admin/css/customize-controls.dev.css', 'wp-admin/css/ie-rtl.dev.css', 'wp-admin/css/ie.dev.css', 'wp-admin/css/install.dev.css', 'wp-admin/css/colors-fresh.dev.css', 'wp-includes/js/customize-base.dev.js', 'wp-includes/js/json2.dev.js', 'wp-includes/js/comment-reply.dev.js', 'wp-includes/js/customize-preview.dev.js', 'wp-includes/js/wplink.dev.js', 'wp-includes/js/tw-sack.dev.js', 'wp-includes/js/wp-list-revisions.dev.js', 'wp-includes/js/autosave.dev.js', 'wp-includes/js/admin-bar.dev.js', 'wp-includes/js/quicktags.dev.js', 'wp-includes/js/wp-ajax-response.dev.js', 'wp-includes/js/wp-pointer.dev.js', 'wp-includes/js/hoverIntent.dev.js', 'wp-includes/js/colorpicker.dev.js', 'wp-includes/js/wp-lists.dev.js', 'wp-includes/js/customize-loader.dev.js', 'wp-includes/js/jquery/jquery.table-hotkeys.dev.js', 'wp-includes/js/jquery/jquery.color.dev.js', 'wp-includes/js/jquery/jquery.color.js', 'wp-includes/js/jquery/jquery.hotkeys.dev.js', 'wp-includes/js/jquery/jquery.form.dev.js', 'wp-includes/js/jquery/suggest.dev.js', 'wp-admin/js/xfn.dev.js', 'wp-admin/js/set-post-thumbnail.dev.js', 'wp-admin/js/comment.dev.js', 'wp-admin/js/theme.dev.js', 'wp-admin/js/cat.dev.js', 'wp-admin/js/password-strength-meter.dev.js', 'wp-admin/js/user-profile.dev.js', 'wp-admin/js/theme-preview.dev.js', 'wp-admin/js/post.dev.js', 'wp-admin/js/media-upload.dev.js', 'wp-admin/js/word-count.dev.js', 'wp-admin/js/plugin-install.dev.js', 'wp-admin/js/edit-comments.dev.js', 'wp-admin/js/media-gallery.dev.js', 'wp-admin/js/custom-fields.dev.js', 'wp-admin/js/custom-background.dev.js', 'wp-admin/js/common.dev.js', 'wp-admin/js/inline-edit-tax.dev.js', 'wp-admin/js/gallery.dev.js', 'wp-admin/js/utils.dev.js', 'wp-admin/js/widgets.dev.js', 'wp-admin/js/wp-fullscreen.dev.js', 'wp-admin/js/nav-menu.dev.js', 'wp-admin/js/dashboard.dev.js', 'wp-admin/js/link.dev.js', 'wp-admin/js/user-suggest.dev.js', 'wp-admin/js/postbox.dev.js', 'wp-admin/js/tags.dev.js', 'wp-admin/js/image-edit.dev.js', 'wp-admin/js/media.dev.js', 'wp-admin/js/customize-controls.dev.js', 'wp-admin/js/inline-edit-post.dev.js', 'wp-admin/js/categories.dev.js', 'wp-admin/js/editor.dev.js', 'wp-includes/js/tinymce/plugins/wpeditimage/js/editimage.dev.js', 'wp-includes/js/tinymce/plugins/wpdialogs/js/popup.dev.js', 'wp-includes/js/tinymce/plugins/wpdialogs/js/wpdialog.dev.js', 'wp-includes/js/plupload/handlers.dev.js', 'wp-includes/js/plupload/wp-plupload.dev.js', 'wp-includes/js/swfupload/handlers.dev.js', 'wp-includes/js/jcrop/jquery.Jcrop.dev.js', 'wp-includes/js/jcrop/jquery.Jcrop.js', 'wp-includes/js/jcrop/jquery.Jcrop.css', 'wp-includes/js/imgareaselect/jquery.imgareaselect.dev.js', 'wp-includes/css/wp-pointer.dev.css', 'wp-includes/css/editor.dev.css', 'wp-includes/css/jquery-ui-dialog.dev.css', 'wp-includes/css/admin-bar-rtl.dev.css', 'wp-includes/css/admin-bar.dev.css', 'wp-includes/js/jquery/ui/jquery.effects.clip.min.js', 'wp-includes/js/jquery/ui/jquery.effects.scale.min.js', 'wp-includes/js/jquery/ui/jquery.effects.blind.min.js', 'wp-includes/js/jquery/ui/jquery.effects.core.min.js', 'wp-includes/js/jquery/ui/jquery.effects.shake.min.js', 'wp-includes/js/jquery/ui/jquery.effects.fade.min.js', 'wp-includes/js/jquery/ui/jquery.effects.explode.min.js', 'wp-includes/js/jquery/ui/jquery.effects.slide.min.js', 'wp-includes/js/jquery/ui/jquery.effects.drop.min.js', 'wp-includes/js/jquery/ui/jquery.effects.highlight.min.js', 'wp-includes/js/jquery/ui/jquery.effects.bounce.min.js', 'wp-includes/js/jquery/ui/jquery.effects.pulsate.min.js', 'wp-includes/js/jquery/ui/jquery.effects.transfer.min.js', 'wp-includes/js/jquery/ui/jquery.effects.fold.min.js', 'wp-admin/images/screenshots/captions-1.png', 'wp-admin/images/screenshots/captions-2.png', 'wp-admin/images/screenshots/flex-header-1.png', 'wp-admin/images/screenshots/flex-header-2.png', 'wp-admin/images/screenshots/flex-header-3.png', 'wp-admin/images/screenshots/flex-header-media-library.png', 'wp-admin/images/screenshots/theme-customizer.png', 'wp-admin/images/screenshots/twitter-embed-1.png', 'wp-admin/images/screenshots/twitter-embed-2.png', 'wp-admin/js/utils.js', 'wp-admin/options-privacy.php', 'wp-app.php', 'wp-includes/class-wp-atom-server.php', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/ui.css', // 3.5.2 'wp-includes/js/swfupload/swfupload-all.js', // 3.6 'wp-admin/js/revisions-js.php', 'wp-admin/images/screenshots', 'wp-admin/js/categories.js', 'wp-admin/js/categories.min.js', 'wp-admin/js/custom-fields.js', 'wp-admin/js/custom-fields.min.js', // 3.7 'wp-admin/js/cat.js', 'wp-admin/js/cat.min.js', 'wp-includes/js/tinymce/plugins/wpeditimage/js/editimage.min.js', // 3.8 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/page_bug.gif', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/more_bug.gif', 'wp-includes/js/thickbox/tb-close-2x.png', 'wp-includes/js/thickbox/tb-close.png', 'wp-includes/images/wpmini-blue-2x.png', 'wp-includes/images/wpmini-blue.png', 'wp-admin/css/colors-fresh.css', 'wp-admin/css/colors-classic.css', 'wp-admin/css/colors-fresh.min.css', 'wp-admin/css/colors-classic.min.css', 'wp-admin/js/about.min.js', 'wp-admin/js/about.js', 'wp-admin/images/arrows-dark-vs-2x.png', 'wp-admin/images/wp-logo-vs.png', 'wp-admin/images/arrows-dark-vs.png', 'wp-admin/images/wp-logo.png', 'wp-admin/images/arrows-pr.png', 'wp-admin/images/arrows-dark.png', 'wp-admin/images/press-this.png', 'wp-admin/images/press-this-2x.png', 'wp-admin/images/arrows-vs-2x.png', 'wp-admin/images/welcome-icons.png', 'wp-admin/images/wp-logo-2x.png', 'wp-admin/images/stars-rtl-2x.png', 'wp-admin/images/arrows-dark-2x.png', 'wp-admin/images/arrows-pr-2x.png', 'wp-admin/images/menu-shadow-rtl.png', 'wp-admin/images/arrows-vs.png', 'wp-admin/images/about-search-2x.png', 'wp-admin/images/bubble_bg-rtl-2x.gif', 'wp-admin/images/wp-badge-2x.png', 'wp-admin/images/wordpress-logo-2x.png', 'wp-admin/images/bubble_bg-rtl.gif', 'wp-admin/images/wp-badge.png', 'wp-admin/images/menu-shadow.png', 'wp-admin/images/about-globe-2x.png', 'wp-admin/images/welcome-icons-2x.png', 'wp-admin/images/stars-rtl.png', 'wp-admin/images/wp-logo-vs-2x.png', 'wp-admin/images/about-updates-2x.png', // 3.9 'wp-admin/css/colors.css', 'wp-admin/css/colors.min.css', 'wp-admin/css/colors-rtl.css', 'wp-admin/css/colors-rtl.min.css', 'wp-admin/css/media-rtl.min.css', 'wp-admin/css/media.min.css', 'wp-admin/css/farbtastic-rtl.min.css', 'wp-admin/images/lock-2x.png', 'wp-admin/images/lock.png', 'wp-admin/js/theme-preview.js', 'wp-admin/js/theme-install.min.js', 'wp-admin/js/theme-install.js', 'wp-admin/js/theme-preview.min.js', 'wp-includes/js/plupload/plupload.html4.js', 'wp-includes/js/plupload/plupload.html5.js', 'wp-includes/js/plupload/changelog.txt', 'wp-includes/js/plupload/plupload.silverlight.js', 'wp-includes/js/plupload/plupload.flash.js', 'wp-includes/js/plupload/plupload.js', 'wp-includes/js/tinymce/plugins/spellchecker', 'wp-includes/js/tinymce/plugins/inlinepopups', 'wp-includes/js/tinymce/plugins/media/js', 'wp-includes/js/tinymce/plugins/media/css', 'wp-includes/js/tinymce/plugins/wordpress/img', 'wp-includes/js/tinymce/plugins/wpdialogs/js', 'wp-includes/js/tinymce/plugins/wpeditimage/img', 'wp-includes/js/tinymce/plugins/wpeditimage/js', 'wp-includes/js/tinymce/plugins/wpeditimage/css', 'wp-includes/js/tinymce/plugins/wpgallery/img', 'wp-includes/js/tinymce/plugins/wpfullscreen/css', 'wp-includes/js/tinymce/plugins/paste/js', 'wp-includes/js/tinymce/themes/advanced', 'wp-includes/js/tinymce/tiny_mce.js', 'wp-includes/js/tinymce/mark_loaded_src.js', 'wp-includes/js/tinymce/wp-tinymce-schema.js', 'wp-includes/js/tinymce/plugins/media/editor_plugin.js', 'wp-includes/js/tinymce/plugins/media/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/media/media.htm', 'wp-includes/js/tinymce/plugins/wpview/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wpview/editor_plugin.js', 'wp-includes/js/tinymce/plugins/directionality/editor_plugin.js', 'wp-includes/js/tinymce/plugins/directionality/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wordpress/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wordpress/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wpdialogs/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wpdialogs/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wpeditimage/editimage.html', 'wp-includes/js/tinymce/plugins/wpeditimage/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wpeditimage/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/fullscreen/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/fullscreen/fullscreen.htm', 'wp-includes/js/tinymce/plugins/fullscreen/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wplink/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wplink/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wpgallery/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wpgallery/editor_plugin.js', 'wp-includes/js/tinymce/plugins/tabfocus/editor_plugin.js', 'wp-includes/js/tinymce/plugins/tabfocus/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wpfullscreen/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wpfullscreen/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/paste/editor_plugin.js', 'wp-includes/js/tinymce/plugins/paste/pasteword.htm', 'wp-includes/js/tinymce/plugins/paste/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/paste/pastetext.htm', 'wp-includes/js/tinymce/langs/wp-langs.php', // 4.1 'wp-includes/js/jquery/ui/jquery.ui.accordion.min.js', 'wp-includes/js/jquery/ui/jquery.ui.autocomplete.min.js', 'wp-includes/js/jquery/ui/jquery.ui.button.min.js', 'wp-includes/js/jquery/ui/jquery.ui.core.min.js', 'wp-includes/js/jquery/ui/jquery.ui.datepicker.min.js', 'wp-includes/js/jquery/ui/jquery.ui.dialog.min.js', 'wp-includes/js/jquery/ui/jquery.ui.draggable.min.js', 'wp-includes/js/jquery/ui/jquery.ui.droppable.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-blind.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-bounce.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-clip.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-drop.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-explode.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-fade.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-fold.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-highlight.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-pulsate.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-scale.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-shake.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-slide.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-transfer.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect.min.js', 'wp-includes/js/jquery/ui/jquery.ui.menu.min.js', 'wp-includes/js/jquery/ui/jquery.ui.mouse.min.js', 'wp-includes/js/jquery/ui/jquery.ui.position.min.js', 'wp-includes/js/jquery/ui/jquery.ui.progressbar.min.js', 'wp-includes/js/jquery/ui/jquery.ui.resizable.min.js', 'wp-includes/js/jquery/ui/jquery.ui.selectable.min.js', 'wp-includes/js/jquery/ui/jquery.ui.slider.min.js', 'wp-includes/js/jquery/ui/jquery.ui.sortable.min.js', 'wp-includes/js/jquery/ui/jquery.ui.spinner.min.js', 'wp-includes/js/jquery/ui/jquery.ui.tabs.min.js', 'wp-includes/js/jquery/ui/jquery.ui.tooltip.min.js', 'wp-includes/js/jquery/ui/jquery.ui.widget.min.js', ); <end node> 5P9i0s8y19Z dt= <node>uploads 1 wpconfig.php file define( 'UPLOADS', 'uploads/' ); <end node> 5P9i0s8y19Z dt= <node>urls 1 https://wordpress.org/plugins/bulletproof-security/installation/ http://clicknathan.com/web-design/include-wordpress-page/ How to Include a WordPress Page on Another WP Page or Part of Your Theme (without using a Plugin) Dec052012 So you have some content from one WordPress post or page and you want to include it elsewhere in your theme. Perhaps you have a “Store Hours” page that you’d like to be able to only update once and have it show in various spots of your website, not just on that particular page. The following snippet of code shows you how to tell PHP to grab a particular page via get_pages, and then sets two variables depending on that page’s content and title. The last line shows you how to output the content. $include = get_pages('include=4177'); $content = apply_filters('the_content',$include[0]->post_content); $title = apply_filters('the_title',$include[0]->post_title); echo '<h1>'.$title.'</h1>'; echo $content; Remember to change the 4177 to whatever the ID of your particular page is, and note that you don’t need to keep the last “echo” line in there, you could use that elsewhere in your template. <end node> 5P9i0s8y19Z dt= <node>How to Include a WordPress Page 2 <h1>How to Include a WordPress Page on Another WP Page or Part of Your Theme (without using a Plugin)</h1> <?php $pages = get_pages('include=144'); $count = 0; foreach($pages as $page) { $content = $page->post_content; if(!$content) continue; if($count >= 2) break; $count++; $content = apply_filters('the_content', $content); ?> <div class=\\"entry\\"><?php echo $content ?></div> <?php } ?>
<p>So you have some content from one WordPress post or page and you want to include it elsewhere in your theme. Perhaps you have a “Store Hours” page that you’d like to be able to only update once and have it show in various spots of your website, not just on that particular page.</p> <p>The following snippet of code shows you how to tell PHP to grab a particular page via <code>get_pages</code>, and then sets two variables depending on that page’s content and title. </p> <p>The last line shows you how to output the content.</p> <div class="code-snippet"> <code>$include = get_pages('include=4177');<br> $content = apply_filters('the_content',$include[0]->post_content);<br> $title = apply_filters('the_title',$include[0]->post_title);<br> echo '<h1>'.$title.'</h1>'; echo $content; </code> </div> <p><strong>Remember to change the <code>4177</code> to whatever the ID of your particular page is</strong>, and note that you don’t need to keep the last “echo” line in there, you could use that elsewhere in your template.</p> <end node> 5P9i0s8y19Z dt= <node>Stupid WordPress Tricks 2 http://perishablepress.com/stupid-wordpress-tricks/ Perishable Press WordPress, Web Design, Code & Tutorials Tutorials Plugins Archives Demos Tools New book on WordPress Theme Development: WordPress Themes In Depth x « Getting Serious with a New Design The New Clearfix Method » Stupid WordPress Tricks [ WordPress ] One of the most popular articles here at Perishable Press is my January 2005 post, Stupid htaccess Tricks. In that article, I bring together an extensive collection of awesome copy-&-paste HTAccess code snippets. Four years later, people continue to tell me how much they enjoy and use the content as a bookmarked reference for many of their HTAccess needs. The article was even published in a book on Joomla! Security. This is very inspiring to me, so I have decided to create a similar post for all of the useful WordPress code snippets, tips and tricks that I have collected while working on Digging into WordPress, the new book by co-author Chris Coyier and myself that really “digs in” to all of the awesome ways to get the most out of WordPress. While writing the DiW book, I collected hundreds of incredibly useful WordPress tips and tricks. After packing the book with as many of these techniques as possible, I decided to share the “best of the rest” here at Perishable Press. If you are one of the millions of people who use WordPress, this article will help you improve the appearance, functionality, and performance of your WordPress-powered websites. Each of these “stupid WordPress tricks” is presented as clearly and succinctly as possible, including as many notes, instructions, and pointers as needed for successful implementation. Of course, keep in mind that we are only scratching the surface here. For a much more complete resource that is packed with tons of tasty techniques, you need to get Digging into WordPress. So now, without further ado, here is my personal collection of easy-to-use, copy-&-paste WordPress tricks. Enjoy! :) Table of Contents WordPress Shortcodes WordPress Permalinks Outside of the Loop Custom Message to Returning Visitors Recently Updated Posts and Pages Custom Content to Search Engine Visitors Last Modified Time and Date for Posts Display Total Number of Trackbacks and Pingbacks Display Recently Registered Users List all of Your Site’s Posts List WordPress User Information Display List of Scheduled Posts Display Private Posts to Logged-in Users Display Posts from Exactly One Year Ago Custom CSS Styles for Recent Posts New WordPress-2.7 Comments Loop Backwards-Compatible Comment Templates Disable WordPress Post Revisions Limit WordPress Post Revisions Remove WordPress Post Revisions from the Database Reduce Comment Spam by Blocking No-Referrer Requests Prevent Google Analytics from Tracking Admin Pages Meta Descriptions without a Plugin Differentiate Between Posts Depending on Presence of Excerpt Modify the wp_options Table via the WordPress Admin Alternate Comment Styles Automatically Remove Code Mistakes in Posts Automatically Disable Comments and Trackbacks in Old Posts Access Post Data Outside the Loop Display Posts for a Specified Time Period Unique Single Post Templates for Different Categories Display Performance Statistics for WordPress Pages Custom Post Thumbnails in Two Steps Highlight Author Comments Easy Random Posts Display Dates for Groups of Posts Display a Sticky Post in the Sidebar Display Latest Comments without a Plugin Display Most Commented Posts without a Plugin Change Permalinks from Date-Based to Post-Date Only Test for Sub-Pages Multiple Widgetizable Sidebars Remove Fancy Quotes from Comments Display a List of All Untagged Posts Easy Display of Custom Headers, Footers, and Sidebars A Better Way for Users to Logout Display a Custom Message on a Specific Date Display Three Columns of Posts Disable WordPress Search Functionality Display Posts with Specific Custom Fields How to Number Your Comments, Pingbacks, & Trackbacks in 2.7+ How to Number Your Comments Using the Classic Loop Invite Readers to Comment via Feed Display the Total Number of Users for Your Blog Automatically Insert Content into Your WordPress Post Editor How to Prevent Duplicate Content Conditionally Display Full Posts or Excerpts Display Related Posts without a Plugin Drop-Dead Easy Styles for Author Comments Display Posts Upcoming Scheduled Posts Display Automatic TinyURLs for Your Posts Implement a Site-Maintenance Page for Your Blog Display the First Image from Each of Your Posts Display Most Popular Posts without a Plugin Automatically Highlight Search Terms Automatically Disable Widgets Display All Images from Your Post Content Display Category List in Two Columns Show Ads or Other Content Only in the First Three Posts A Better Way to Display Recent Comments without a Plugin Selectively Disable Automatic Post Formatting Browser Detection via WordPress’ body_class Function Get Post or Page Contents as a PHP Variable Simple Example of How to Use WordPress Cron Add More Default Avatar Choices to the WordPress Admin Add a Private Page to Your Navigation Menu How to Add Additional Links to wp_list_pages WordPress Shortcodes ? Save time by replacing your most commonly typed words and phrases with WordPress shortcodes. For example, if you are frequently typing your blog’s URL, you could place the following code your theme’s functions.php file: function shortURL() { return 'http://perishablepress.com/'; } add_shortcode('myurl', 'shortURL'); Now whenever I write a post via “HTML-mode”, all I need to include my blog’s URL is type “[myurl]”. Works great in WordPress 2.5 or better. Shortcodes with Attributes To create a shortcode for links, we need to include the href attribute information as well as the anchor text for the link itself. We can do this by placing this function in your theme’s functions.php file: function shortLink($atts, $content = null) { extract(shortcode_atts(array( "href" => 'http://' // default URL ), $atts)); return '<a href="'.$href.'">'.$content.'</a>'; } add_shortcode('link', 'shortLink'); Then, when creating a post, emulate the following format to include any links you wish: [link href="http://perishablepress.com/"]Perishable Press[/link] ..which will output the following code: <a href="http://perishablepress.com/">Perishable Press</a> When the href attribute is removed from the shortcode, the default URL will be used. You may specify the default URL in the third line of the funtion (see comment). Source: Digging into WordPress Display WordPress Permalinks Outside of the Loop ? Normally, permalink display via the_permalink() requires the loop. To display permalinks outside of the loop, we may use either of the following methods: <!-- external permalink via post ID --> <a href="<?php echo get_permalink(33); ?>" >Permalink</a> <!-- external permalink via global $post variable --> <a href="<?php echo get_permalink($post->ID); ?>" >Permalink</a> Source: Julien Chauvin (404 link removed 2013/06/27) Display Custom Message to Returning Visitors ? We can greet returning commentators with a custom message by extracting their information from the comment cookie left on their machine. Place the following code into the desired location in your theme and customize the message and markup to whatever you wish: <?php if(isset($_COOKIE['comment_author_'.COOKIEHASH])) { $lastCommenter = $_COOKIE['comment_author_'.COOKIEHASH]; echo "Welcome Back ". $lastCommenter ."!"; } else { echo "Welcome, Guest!"; } ?> Source: ifohdesigns (404 link removed 2012/09/14) Display Recently Updated Posts and Pages ? Easily display a list of recently updated posts by placing the following code into the desired location in your theme: <?php $today = current_time('mysql', 1); $number = 5; // number of posts if($recentposts = $wpdb->get_results("SELECT ID, post_title FROM $wpdb->posts WHERE post_status = 'publish' AND post_modified_gmt < '$today' ORDER BY post_modified_gmt DESC LIMIT $number")): ?> <h2><?php _e("Recently Updated"); ?></h2> <ul> <?php foreach($recentposts as $post) { if($post->post_title == '') $post->post_title = sprintf(__('Post #%s'), $post->ID); echo '<li><a href="'.get_permalink($post->ID).'">'.the_title().'</a></li>'; } ?> </ul> <?php endif; ?> Of course, customize the details as necessary and remember to set the number of posts via the “$howMany” variable. Source: Corey (404 link removed 2014/06/08) Display Custom Content to Search Engine Visitors ? Display custom content to your search-engine traffic by placing the following code into your theme’s functions.php file: <?php function scratch99_fromasearchengine() { $ref = $_SERVER['HTTP_REFERER']; $SE = array('/search?', 'images.google.', 'web.info.com', 'search.', 'del.icio.us/search', 'soso.com', '/search/', '.yahoo.');
foreach($SE as $source) { if(strpos($ref, $source) !== false) return true; } return false; } ?> After checking and editing the $SE array with the search-engine referrer information of your choice, place this next chunk of code into the desired display location in your theme file(s): <?php if(function_exists('scratch99_fromasearchengine')) { if (scratch99_fromasearchengine()) { // INSERT YOUR CODE HERE } } ?> Add whatever content or code you wish to the specified area and enjoy targeted delivery to search-engine visitors only. Source: Stephen Cronin Display Last Modified Time and Date for Posts ? Display the “last-modified” time for your posts by placing this code anywhere within the loop: Posted on <?php the_time('F jS, Y') ?> <?php $u_time = get_the_time('U'); $u_modified_time = get_the_modified_time('U'); if($u_modified_time != $u_time) { echo "and last modified on "; the_modified_time('F jS, Y'); echo ". "; } ?> Source: Kyle Eslick Display Total Number of Trackbacks and Pingbacks ? Display the trackback/pingback count for each of your posts by first placing this code into your theme’s functions.php file: function comment_count() { global $wpdb; $count = "SELECT COUNT(*) FROM $wpdb->comments WHERE comment_type = 'pingback' OR comment_type = 'trackback'"; echo $wpdb->get_var($count); } And then call the number for display anywhere in your theme by adding this code to the desired location: <?php comment_count(); ?> Alternately, in WordPress 2.7, you may display the total number of comments by inserting this code directly into your comments.php template: <?php if(!empty($comments_by_type['comment'])) : $count = count($comments_by_type['comment']); ($count !== 1) ? $txt = "Comments" : $txt = "Comment"; ?> <h3><?php echo $count . " " . $txt; ?></h3> Edit the markup as desired. Will display “” or “”, depending on the number of comments. Source: WPengineer.com Display Recently Registered Users ? Quick and easy method for displaying a list of recently registered users. Place the following code directly into your theme, wherever you would like to display the list: <ul> <?php $usernames = $wpdb->get_results("SELECT user_nicename, user_url FROM $wpdb->users ORDER BY ID DESC LIMIT 5"); foreach ($usernames as $username) { echo '<li><a href="'.$username->user_url.'">'.$username->user_nicename."</a></li>"; } ?> </ul> As-is, this code will spit out the five most recent registered users. This is easily changed to whatever number you wish by simply editing the number “5” in the first line. Source: WPRecipes.com List all of Your Site’s Posts ? If the default wp_get_archives(type=postbypost&limit=) function doesn’t provide enough flexibility to meet your needs, here is another way to list all of your site’s posts: <?php while(have_posts()) : the_post(); ?> <ul> <?php $allposts = get_posts('numberposts=-1&offset=0'); foreach($allposts as $post) : ?> <li><?php the_time('d/m/y'); ?>: <a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></li> <?php endforeach; ?> </ul> <?php endwhile; ?> In place, that code will display a list of all of your blog’s posts. As a bonus, you may use any of the applicable parameters available to the get_posts() function to do just about anything you need with your posts list. Source: WPRecipes.com List WordPress User Information ? Here is an easy way to display flexible lists of your blog’s registered users’ information. In this example, we will list the first and last name of each user registered in the database: <ul> <?php $szSort = "user_nicename"; $aUsersID = $wpdb->get_col($wpdb->prepare("SELECT $wpdb->users.ID FROM $wpdb->users ORDER BY %s ASC", $szSort)); foreach($aUsersID as $iUserID) : $user = get_userdata($iUserID); echo '<li>'.ucwords(strtolower($user->first_name.' '.$user->last_name)).'</li>'; endforeach; ?> </ul> The following variables may be used to display different types of user information and also to specify the sort order of the output list: ID - User ID number user_login - User Login name user_nicename - nice version of login name user_email - User Email Address user_url - User Website URL user_registered - User Registration date To display any of these different types of user information, call it with $user->name_of_the_column anywhere within the function’s foreach() loop. To change the display order of the output, use any of the above as the value of the $szSort variable in the first line of the function. Note that strtolower and ucwords are used to ensure proper capitalization of the user names. Source: Matt Varone Display List of Scheduled Posts ? Got scheduled posts? Cool. Here’s how to display them to your readers: <ul> <?php $my_query = new WP_Query('post_status=future&order=DESC&showposts=5'); if ($my_query->have_posts()) { while ($my_query->have_posts()) : $my_query->the_post(); $do_not_duplicate = $post->ID; ?> <li><?php the_title(); ?></li> <?php endwhile; } ?> </ul> Place that code in the desired location of your WordPress template and display a list of scheduled posts to your readers. To change the total number of displayed posts, edit the showposts=5 parameter to any number you wish. You may also use other parameters available to the WP_Query() function to further customize the output. Source: Pascal Birchler Display Private Posts to Logged-in Users ? To display private posts to your logged-in users, you will need to add a custom field called “private” for each private post and give it a value of “true”. Then, replace your default WordPress loop with the following: <?php if (have_posts()) : while (have_posts()) : the_post(); $private = get_post_custom_values("private"); if (isset($private[0]) && $private == "true") { if (is_user_logged_in()) { // Display private post to logged user } } else { // Display public post to everyone } endwhile; endif; ?> This custom loop will check each post for the presence of a custom-field value of true. For each post that has this value, the loop will then check to see if the user is logged into your site. If the user is in fact logged in, the loop will display the private post(s). Public posts will be displayed as usual and regardless of whether the user is logged in or not. Source: Digging into WordPress Display Posts from Exactly One Year Ago ? Use this code to display posts that are exactly one year old: <?php $current_day = date('j'); $last_year = date('Y')-1; ?> <?php query_posts('day='.$current_day.'&year='.$last_year); if (have_posts()): while (have_posts()) : the_post(); ?> <h1><?php the_title(); ?></h1> <?php the_excerpt(); ?> <?php endwhile; endif; ?> To display posts from different days or different years, edit the two variables in the beginning of the method. Custom CSS Styles for Recent Posts ? Use some custom CSS styles to highlight your recent posts. To do this, replace your existing loop with the following: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> $currentdate = date('Y-m-d',mktime(0,0,0,date('m'),date('d'),date('Y'))); $postdate = get_the_time('Y-m-d'); if ($postdate == $currentdate) { echo '<div class="post new">'; } else { echo '<div class="post">'; } ?> <a href="<?php the_permalink(); ?>"><?php the_title(); ?></a> </div> <?php endwhile; endif; ?> This new loop will check the date of each post and include a CSS class of “new” to any post published within the previous 24-hour time period. Once the new post class is included, you may style it with some custom CSS such as the following: .post{ /* styles for all posts */ } .post.new { /* styles for new posts */ } Source: Fred jaillet [via] WPRecipes.com New WordPress-2.7 Comments Loop ? Due to the changes made to comment-related functions in WordPress 2.7, you will need to upgrade your comments template in order accomodate for the new functionality. The major changes are the new wp_list_comments() function and the next/previous_comments_link() functions. Here is an example comments.php loop to get you started: <?php if (have_comments()) : ?> <h4><?php comments_number('No Comments', 'One Comment', '% Comments' );?></h4> <ul class="commentlist"> <?php wp_list_comments(); ?> </ul> <div class="navigation"> <div class="alignleft"><?php previous_comments_link(); ?></div> <div class="alignright"><?php next_comments_link(); ?></div> </div> <?php else : // if there are no comments so far ?> <?php if ('open' == $post->comment_status) : ?> <p>Comments are open, but there are no comments.</p> <?php else : ?> <p>Comments are closed, and there are no comments.</p> <?php endif; ?> <?php endif; ?> As you can see, we are now using the wp_list_comments() function as the method by which our individual comments are displayed. This function wraps each comment with a set of <li> elements, but this may be changed via customized parameters. We are also using the next/previous_comments_link() functions to accommodate the new built-in paged comments feature. Source: Digging into WordPress Backwards-Compatible Comment Templates ? The easiest way to accommodate for both old (pre-2.7) and new (2.7+) WordPress comment loops is to create two different versions of the comments template and then use some conditional logic to process the correct file. Place the 2.7-compatible code from the previous section into your default comments.php file, and then place your existing (pre-2.7) comments code into a file called legacy-comments.php. Once you have both of these files setup and included among your theme files, place the following function in your theme’s functions.php file: <?php add_filter('comments_template', 'legacy_comments'); function legacy_comments($file) { if(!function_exists('wp_list_comments')) : // WP 2.7-only check $file = TEMPLATEPATH.'/legacy-comments.php'; endif; return $file; } ?> This code will then check for the presence of the new wp_list_comments() function. If it exists, then the version of WordPress is at least 2.7, and the default comments.php file will be used. If the new function doesn’t exist, we have a dinosaur on our hands and so the legacy comments file will be used instead. Source: Justin Tadlock Disable WordPress Post Revisions ? One of the new features rolled out in WordPress 2.6 involved post revisions. Revisions are a way for users to keep a working collection of each different version of a post and then revert back to it in the future if necessary. Some people think this is the greatest thing since lightsabers, others (such as myself) find it to be a royal pain in the database. It convolutes the Admin area, gobbles up disk space, and usually doesn’t work as intended. Fortunately, we can disable this amazing new “feature” (which should NOT have been included in the core) by adding the following line to the wp-config.php file: /* disable post-revisioning nonsense */ define('WP_POST_REVISIONS', FALSE); Just place that line above the “Happy blogging” comment and say goodbye to needless revisioning bloat. Source: Digging into WordPress Limit WordPress Post Revisions ? If you like the idea of WordPress-2.6’s new post-revisioning feature, but don’t want thousands of extra records bloating up your database, here is an easy way to limit the total number of revisions that WordPress is allowed to keep. This code will instruct WordPress to keep only the most recent “x” number of revisions: /* limit number of post revisions */ define('WP_POST_REVISIONS', 3); Place that line above the “Happy blogging” comment in the wp-config.php file and enjoy conserved disk space and less Admin clutter. Change the number “3” to any number you wish. Works a treat. Source: Digging into WordPress Remove WordPress Post Revisions from the Database ? In line with the previous two sections, here we will remove all existing post revisions from the WordPress database. This is useful if you have disabled the post-revisioning feature or perhaps even reduced the total number of allowed revisions. The easiest way to do this is to run the following SQL command via your favorite database interface (such as my personal favorite, phpMyAdmin): DELETE a,b,c FROM wp_posts a LEFT JOIN wp_term_relationships b ON (a.ID = b.object_id) LEFT JOIN wp_postmeta c ON (a.ID = c.post_id) WHERE a.post_type = 'revision'; Note that if you have changed the default WordPress database table prefix to something other than “wp_”, you will want to edit the command to reflect the correct prefix information. This information is available in your site’s wp-config.php file. Also note that you should backup your database before casting any SQL spells on it. Upon successful execution of the above command, all data associated with post revisions will be removed the database. This includes the post revisions themselves and all the meta data associated with each revision. Credit: Andrei Neculau Reduce Comment Spam by Blocking No-Referrer Requests ? As explained in my article, denying access to no-referrer requests, you can greatly reduce the number of spam comments by eliminating all direct requests for your blog’s comments-post.php file. This will block automated spam scripts from bypassing your comments form by hitting the comment processing script directly. Here are two ways to block no-referrer comment requests, one uses HTAccess and the other uses PHP. Here is the HTAccess method: RewriteEngine On RewriteCond %{REQUEST_METHOD} POST RewriteCond %{REQUEST_URI} .wp-comments-post.php RewriteCond %{HTTP_REFERER} !domain.tld [OR] RewriteCond %{HTTP_USER_AGENT} ^$ RewriteRule (.*) http://%{REMOTE_ADDR}/$ [R=301,L] Place that code in your site’s root HTAccess file and edit the “domain.tld” to match your own domain. Once in place, this code will redirect any request for your blog’s comments-post.php file that didn’t originate from your site back to the URL from whence it came. This may also be accomplished via PHP. Place the following function in your theme’s functions.php file: function check_referrer() { if (!isset($_SERVER['HTTP_REFERER']) || $_SERVER['HTTP_REFERER'] == '') { wp_die(__('Please do not access this file directly.')); } } add_action('check_comment_flood', 'check_referrer'); Source: Perishable Press Prevent Google Analytics from Tracking Admin Pages ? This handy snippet will prevent Google Analytics from tracking your Admin pages or anything else that you wish. Replace your default Google Analytics code with the following: <?php if (!current_user_can('level_10')) { ?> /* Google Analytics Code */ <?php } ?> This code will then include your Google Analytics code only on non-Admin pages. This in turn will prevent Google Analytics from gathering statistics about your Admin pages. Note that the basic functionality of this method is great for restricting just about anything - scripts, markup, content - to logged-in administrators. Meta Descriptions without a Plugin ? We don’t need no stinkin’ plugin for custom meta descriptions. All you need is a custom field named “metadescription” with the desired meta description for each post. Once you have that going, include the following function to your theme’s header.php file (within the <head> section: <meta name="description" content=" <?php if ((is_home()) || (is_front_page())) { echo ('Your main description goes here'); } elseif(is_category()) { echo category_description(); } elseif(is_tag()) { echo 'Tag archive page for this blog - ' . single_tag_title(); } elseif(is_month()) { echo 'Archive page for this blog - ' . the_time('F, Y'); } else { echo get_post_meta($post->ID, 'metadescription', true); } ?>" /> This function enables you to customize the descriptions for various types of pages, such as the home page, category pages, tag archives, and so on. For single post-view pages, this function will display the value of the metadescription custom field. Source: Malcolm Coles (404 link removed) Differentiate Between Posts Depending on Presence of Excerpt ? Here is a quick conditional snippet that displays different content depending on the presence of an excerpt: <?php if(!empty($post->post_excerpt)) { // this post has an excerpt, so display it: the_excerpt(); } else { // this post has no excerpt, so display something else instead: the_content(); } ?> Placed inside the loop, this code will check each post for an excerpt. If one is found, the excerpt is displayed; otherwise, the code specified in the else condition is displayed. Modify the wp_options Table via the WordPress Admin ? As you probably know, the wp_options table stores a great deal of useful information, including everything from custom-field values, plugin settings, blog information, and much more. If any table in the WordPress database needs its own friendly user-interface, this would be it. Normally, you would access the wp_options table using a database interface such as phpMyAdmin. This certainly works, but there is a much easier way to work with the options table, especially if you are already logged into WordPress. Once logged in to the Admin area, navigate to the following URL: http://domain.tld/wp-admin/options.php This will open a “secret” Admin page that provides editable options fields for every record in the wp_options table. Bookmark this page, and save yourself a trip to phpMyAdmin! Source: Digging into WordPress Alternate Comment Styles ? Alternating comments for old versions of WordPress (pre-2.7) This is one of the oldest tricks in the book, but it is still a favorite. Alternating comment styles is a great way to enhance usability and add some stylistic flair to your comments display. The trick is to add an alternating set of classes - odd or even - to the containing element of each comment. While there are many ways to do this, here is one of the easiest. Open your comments.php and modify the comments loop as follows: <ul> <?php $i = 0; ?> <?php foreach ($comments as $comment) : ?> <?php $i++; ?> <li id="comment-<?php comment_ID(); ?>" <?php if($i&1) { echo 'class="odd"'; } else { echo 'class="even"'; } ?>> <?php comment_text(); ?> </li> <php endforeach; ?> </ul> With that code in place, your comments will now have alternating CSS classes with which to apply custom styles to your oddly and evenly numbered comments: .odd { background: white; color: black; } .even { background: black; color: white; } Alternating comments for old versions of WordPress (pre-2.7) In WordPress 2.7 and better, comments automagically include “odd” and “even” classes for oddly and evenly numbered comments, respectively. This makes it a snap to throw down your own custom CSS styles for each of these classes. Credit: WordPress Garage Automatically Remove Code Mistakes in Posts ? Here is a handy trick that will automatically remove basic mistakes in XHTML markup, such as empty paragraphs, inline font styles, and more. Place this function in your functions.php file: function clean_bad_content($bPrint = false) { global $post; $szPostContent = $post->post_content; $szRemoveFilter = array("~<p[^>]*>\\s?</p>~", "~<a[^>]*>\\s?</a>~", "~<font[^>]*>~", "~<\\/font>~", "~style\\=\\"[^\\"]*\\"~", "~<span[^>]*>\\s?</span>~"); $szPostContent = preg_replace($szRemoveFilter, '', $szPostContent); $szPostContent = apply_filters('the_content', $szPostContent); if ($bPrint == false) return $szPostContent; else echo $szPostContent; } Once in place, use the following function call to display your “cleaned” content in the loop: <?php if (function_exists('clean_bad_content')) clean_bad_content(true); ?> Note that the clean_bad_content() accepts a boolean argument (true or false) specifying whether or not to print the function output. Credit: Matt Varone Automatically Disable Comments and Trackbacks in Old Posts ? Here is yet another method for auto-disabling comments and trackbacks on old posts. This function automatically closes comments and trackbacks after the specified number of days. Add the following to your functions.php file: <?php function autoclose_comments() { global $wpdb, $tableposts; if (!isset($tableposts)) $tableposts = $wpdb->posts; $age = '21 DAY';
$date = $wpdb->get_var("SELECT DATE_ADD(DATE_SUB(CURDATE(), INTERVAL $age), INTERVAL 1 DAY)"); $wpdb->query("UPDATE $tableposts SET comment_status = 'closed' WHERE comment_status = 'open' AND post_status = 'publish' AND post_date < '$date'"); } function autoclose_trackback() { global $wpdb, $tableposts; if (!isset($tableposts)) $tableposts = $wpdb->posts; $age = '21 DAY';
add_action('publish_post', 'autoclose_comments', 7); add_action('edit_post', 'autoclose_comments', 7); add_action('delete_post', 'autoclose_comments', 7); add_action('comment_post', 'autoclose_comments', 7); add_action('trackback_post', 'autoclose_comments', 7); add_action('pingback_post', 'autoclose_comments', 7); add_action('edit_comment', 'autoclose_comments', 7); add_action('delete_comment', 'autoclose_comments', 7); add_action('template_save', 'autoclose_comments', 7); ?> Once in place, you may change the number of days allowed for comments and trackbacks to stay open by editing the two instances of the $age variable to whatever you wish. No other editing or code is required for this function to operate effectively. The function is executed automatically upon various posting actions. Note that this function is included in newer versions of WordPress (2.7 or better), and is therefore only required for older versions. Source: WP EngineerPlugin: Autoclose Access Post Data Outside the Loop ? The easiest way to access and display post data outside of the loop is to use the built-in WordPress core function get_post(); however, for more control over the process, check out this nifty little function from WP Recipes: function get_post_data($postId) { global $wpdb; return $wpdb->get_row("SELECT * FROM $wpdb->posts WHERE ID=$postId"); } Place this function in your functions.php and then add this code to the desired location outside of the loop: <?php $data = get_post_data(77); echo $data->post_date; // post date echo $data->post_title; // post title echo $data->post_content; // post content echo $data->comment_count; // comments number ?> For the argument of the function, specify the post ID for which you would like to display data. The function will return an array containing all of the available fields for the specified post (post_title, date, content, author_id, post_id, etc). Display Posts for a Specified Time Period ? Here is an easy way to create posts that will only be displayed for the duration of a specified time period. Replace your current loop with the following: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> $expirationtime = get_post_custom_values('expiration'); if (is_array($expirationtime)) { $expirestring = implode($expirationtime); } $secondsbetween = strtotime($expirestring)-time(); if ($secondsbetween > 0) { ?> <h1><?php the_title(); ?></h1> <?php the_excerpt(); ?> <?php } endwhile; endif; ?> And then add a custom field named “expiration” to any post that needs an expiration date. For the value of the expiration key, specify the date/time in the following format: mm/dd/yyyy 00:00:00. Each post that contains such a custom field will expire after the specified date and time and will no longer appear in the loop. Unique Single Post Templates for Different Categories ? Here is an easy way to display custom post styles depending on the post’s category. With the following code, each single-view post will be displayed according to a template that is specific to the post’s category: <?php $post = $wp_query->post; if (in_category('1')) { include(TEMPLATEPATH.'/single-01.php'); } elseif (in_category('2')) { include(TEMPLATEPATH.'/single-02.php'); } else { include(TEMPLATEPATH.'/single-default.php'); } ?> This code should be placed in your theme’s single.php file. As written, this code will display posts from the first category with the single template, “single-01.php”; also, posts from the second category will be displayed with a single template named “single-02.php”; finally, all other posts will be displayed via the default single template, “single-default.php”. Of course, you will want to customize the category IDs according to your own needs, and also you will want to create the customized single files as they are called. That’s all there is to it. Having said that, here is an alternate version of the custom-post-template script: <?php add_filter('single_template', create_function('$t', 'foreach((array) get_the_category() as $cat) { if (file_exists(TEMPLATEPATH . "/single-{$cat->term_id}.php")) return TEMPLATEPATH . "/single-{$cat->term_id}.php"; } return $t;')); ?> Placed in your theme’s functions.php file, this alternate script checks all categories for the presence of a custom single template. Any category with a custom single-post template will then have its posts displayed with that template. If a post’s category does not feature a custom template, the default single.php template will be used. Note that this code will use the template for the first listed category of each post. Even so, you should only create custom post templates for categories that will always be mutually exclusive. That is, make sure that your posts aren’t in more than one custom-templated category. Source: Austin Matzko Display Performance Statistics for WordPress Pages ? Everyone is familair with the following information: <!-- 33 queries in 0.333 seconds --> These statistics are usually seen in the footer area of individual pages and serve as a general indicator of performance. The “queries” refer to the number of times WordPress requested information from the database, while the number of seconds indicates the amount of time required for Apache to generate the page. This information is generated by including the following code in your footer template file (or wherever you would like): <!-- <?php echo get_num_queries(); ?> queries in <?php timer_stop(3); ?> seconds --> Or, if you don’t like the idea of sharing this information with the entire world, you can limit its display to logged-in administrators only: <?php if (current_user_can('level_10')) { echo '<!-- ' . get_num_queries() . ' queries in ' . timer_stop(3) . ' seconds -->'; } ?> Easy breezy beautiful! Source: Digging into WordPress Custom Post Thumbnails in Two Steps ? Alright, kids. Time for the ‘ol three-step custom-field tutorial. This time we’re going to implement post thumbnails. You know, representative images for each of your posts that may be displayed anywhere you wish, including outside of the flow of post content, and even outside of the loop. This is a great trick for advanced page layouts. Ready? Sharpen your keystrokes! Step 1: Open your write panel and create a key called “thumbnail”. Then, for the value of the “thumbnail” key, enter the URL of the thumbnail image for that particular post. Write the post and then publish it as normal. Wash, rinse, repeat to get a nice collection of posts with thumbnails. Or, go back to exisiting posts and add a thumbnail as we have just described. Step 2: Open your theme template file containing the loop and add the following code to the location where you would like the post thumbnail images to appear: <?php $thumbnail = get_post_meta($post->ID, 'image', true); if ($thumbnail) { ?> <img src="<?php echo $thumbnail; ?>" alt="" width="100" height="100" /> <?php } ?> That’s it! Don’t forget to edit the width and height attributes of the <img> element to account for the proper image size. Source: Perishable Press Highlight Author Comments ? Make your author comments look fabulous darling! Newer versions of WordPress come equipped with a specific “author” class that may be targeted with the CSS of your choice. For older versions of WordPress, however, you will need to add the custom class attribute with a little PHP magic. First, open your theme’s comments.php template and add the following code snippet in the (X)HTML element that contains the comment information: <div<?php if ($comment->comment_author_email == "email@domain.tld") echo ' class="author"'; ?> id="comment-<?php comment_ID(); ?>"> . . . </div> After changing the email address to that of your own (i.e., the one used for your WP Admin user profile), style it up with a little CSS: .author { background: red !important; color: yellow !important; } You probably don’t want your author comments to appear with yellow text on a red background, but you get the idea. Anything is possible. For blogs with multiple authors, you can style each of their comments differently as well by using something like this: <div<?php if ($comment->comment_author_email == "email-01@domain.tld") echo ' class="author-01"'; elseif ($comment->comment_author_email == "email-02@domain.tld") echo ' class="author-02"'; elseif ($comment->comment_author_email == "email-03@domain.tld") echo ' class="author-03"'; ?> id="comment-<?php comment_ID(); ?>"> . . . </div> Replace each of the email addresses with those of the various authors. Style to taste. Credit: Nyssa Brown (404 link removed) Easy Random Posts ? Newer versions of WordPress enable easy randomizing of posts by using the (relatively) new “orderby=rand” parameter in any query_posts loop: <?php query_posts('orderby=rand"); ?> But for older versions of WordPress, this randomizing functionality must be added manually. Here is a quick and painless plugin that will enable you to randomize post queries in older versions: <?php /* Plugin Name: Random Posts Query */ function query_random_posts($query) { return query_posts($query . '&random=true'); } class RandomPosts { function orderby($orderby) { if (get_query_var('random') == 'true') return "RAND()"; else return $orderby; } function register_query_var($vars) { $vars[] = 'random'; return $vars; } } add_filter( 'posts_orderby', array('RandomPosts', 'orderby') ); add_filter( 'query_vars', array('RandomPosts', 'register_query_var') ); ?> Once activated, invoke the randomness by adding the “random=true” parameter in your query_posts loop: <?php query_posts('cat=11&showposts=11&random=true'); ?> Here, we are specifying “cat=11” for the category and “showposts=11” for the number of posts to display. There are many other parameters available as well, so knock yourself out. Credit: rembem Display Dates for Groups of Posts ? In order to display the date that a post was published, you have two options: <?php the_time(); ?> - displays the date for each and every post <?php the_date(); ?> - displays the date only once for each group of posts published on a certain day So, if you want to list the post date next to each post, use the the_time(). If, on the other hand, you have multiple posts on any given day, use the_date() to list the post date only once for each days’ posts. Something like this: // the_time(); Jan 01, 2009 - Post #1 Jan 01, 2009 - Post #2 Jan 01, 2009 - Post #3 Jan 02, 2009 - Post #4 Jan 02, 2009 - Post #5 Jan 02, 2009 - Post #6 Jan 03, 2009 - Post #7 Jan 03, 2009 - Post #8 Jan 03, 2009 - Post #9 // the_date(); Jan 01, 2009 Post #1 Post #2 Post #3 Jan 02, 2009 Post #4 Post #5 Post #6 Jan 03, 2009 Post #7 Post #8 Post #9 See the difference? Good, because I’m not going to explain the concept any further. Instead, I will move on by showing you how to use either template tag in your loop. This really doesn’t need explaining either, but for the sake of completeness, here it is. First, the_time() tag: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <h1><?php the_title(); ?></h1> <p><?php the_time(); ?><p> <?php the_content(); ?> <?php endwhile; ?> <?php else : ?> <?php endif; ?> This loop will output the post title, date, and content for every post. Alternately, here is how to use the_date tag: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php the_date('','<p>','</p><hr />'); ?> <h1><?php the_title(); ?></h1> <?php the_content(); ?>
<?php endwhile; ?> <?php else : ?> <?php endif; ?> This loop will output the post title and content for every post, and also output the date for each group of posts published on any given day, as explained above. Notice we are adding the paragraph elements for the post date based on whether or not the date is actually output. If it is, then the date will be wrapped in <p> elements; if it’s not, no <p> elements will be output, thereby preventing repetitive sets of empty paragraph elements. Make sense? Good. Here are the available parameters for the nifty the_date() template tag: <?php the_date('date format', 'before the date', 'after the date'); ?> Display a Sticky Post in the Sidebar ? Here is a juicy little nugget that displays a “sticky” post in the sidebar of your theme: <?php // initialize new query of one post from category 11 $my_query = new WP_Query('cat=11&showposts=1'); // loop through the database to find related information while ($my_query->have_posts()) : $my_query->the_post(); // set expiration time of two days $goAwayDate = time() - (60 * 60 * 24 * 2); // get date of sticky post $postDate = get_the_time('U'); // if post is too old, do nothing if ($postDate < $goAwayDate) { // else show the post } else { ?> <h1><?php the_title(); ?></h1> <?php the_excerpt(); ?> <?php } endwhile; ?> This method employs a second loop to display the sticky post, so it may be placed just about anywhere in your theme’s template files. You can also change the number of days that the post will remain sticky by editing the expiration variable with a number other than "2". For example, to set a duration period of seven days, you would use this: $goAwayDate = time() - (60 * 60 * 24 * 7); Credit: The Closet Entrepreneur Display Latest Comments without a Plugin ? Good rule of thumb when working with WordPress: don’t use a plugin if you can acheive the same functionality without one. Case in point: displaying latest comments on your blog. Sure, you could always install a plugin to do it for you, but you really don’t need to. In fact, it’s actually easier to display recent comments without a plugin. SImply add the following code to the desired location within your theme’s template files: <?php global $wpdb; $sql = "SELECT DISTINCT ID, post_title, post_password, comment_ID, comment_post_ID, comment_author, comment_date_gmt, comment_approved, comment_type,comment_author_url, SUBSTRING(comment_content,1,50) // NUMBER OF CHARACTERS AS com_excerpt FROM $wpdb->comments LEFT OUTER JOIN $wpdb->posts ON ($wpdb->comments.comment_post_ID = $wpdb->posts.ID) WHERE comment_approved = '1' AND comment_type = '' AND post_password = '' ORDER BY comment_date_gmt DESC LIMIT 5"; // NUMBER OF COMMENTS $comments = $wpdb->get_results($sql); $output = $pre_HTML; $output .= "\\n<ul>"; foreach ($comments as $comment) { $output .= "\\n<li>"."<a href=\\"" . get_permalink($comment->ID) . "#comment-" . $comment->comment_ID . "\\" title=\\"on " . $comment->post_title . "\\">" .strip_tags($comment->comment_author) .":<br/><div>" . strip_tags($comment->com_excerpt) ."</div></a></li>"; } $output .= "\\n</ul>"; $output .= $post_HTML; echo $output; ?> This code will display the 5 most recent comments in the following (X)HTML output format: <ul> <li> <a href="http://domain.tld/post#comment-01" title="on Post Title">Comment Author:<br /> <div>This is the first 50 characters of the first most recent comment</div></a> </li> <li> <a href="http://domain.tld/post#comment-01" title="on Post Title">Comment Author:<br /> <div>This is the first 50 characters of the first most recent comment</div></a> </li> <li> <a href="http://domain.tld/post#comment-01" title="on Post Title">Comment Author:<br /> <div>This is the first 50 characters of the first most recent comment</div></a> </li> <li> <a href="http://domain.tld/post#comment-01" title="on Post Title">Comment Author:<br /> <div>This is the first 50 characters of the first most recent comment</div></a> </li> <li> <a href="http://domain.tld/post#comment-01" title="on Post Title">Comment Author:<br /> <div>This is the first 50 characters of the first most recent comment</div></a> </li> </ul> By editing the commented lines in the PHP script, you may specify alternate number of comments and characters. Source: StylizedWeb Display Most Commented Posts without a Plugin ? Here is another trick that will enable you avoid yet another needless plugin. This code results in the display of your most-commented posts in list format: <ul> <?php $result = $wpdb->get_results("SELECT comment_count, ID, post_title FROM $wpdb->posts ORDER BY comment_count DESC LIMIT 0 , 10"); // NUMBER OF POSTS foreach ($result as $topten) { $postid = $topten->ID; $title = $topten->post_title; $commentcount = $topten->comment_count; if ($commentcount != 0) { ?> <li><a href="<?php echo get_permalink($postid); ?>"><?php echo $title ?></a></li> <?php } } ?> </ul> This code may be modified to display any number of posts by changing the LIMIT from “10” to whatever you wish. You may also change the display order from DESC (descending order) to ASC (ascending order). Once in place, this code will display a list of the 10 most-commented posts in the following (X)HTML output format: <ul> <li><a href="http://domain.tld/post-01/">Post Title 01</a></li> <li><a href="http://domain.tld/post-02/">Post Title 02</a></li> <li><a href="http://domain.tld/post-03/">Post Title 03</a></li> . . . </ul> Source: StylizedWeb Change Permalinks from Date-Based to Post-Date Only ? Here is an HTAccess method for switching your permalinks from the lengthy date-based format (i.e., http://domain.tld/2009/03/03/post-name/) to the concise post-name format (i.e., http://domain.tld/post-name/). To do so, first login to the WordPress Admin and switch your permalink structure from this: /%year%/%monthnum%/%day%/%postname%/ ..to this: /%postname%/ This change will ensure that all future posts are located at the new post-name-only URL, but we still need to redirect all requests for existing posts via the old date-based URL format. This is easily accomplished with a single directive in your site’s root HTAccess file: RedirectMatch 301 /([0-9]+)/([0-9]+)/([0-9]+)/(.*)$ http://domain.tld/$4 And that’s all there is to it! Remember to test vigorously to convince yourself that everything is working properly. Source: Perishable Press Test for Sub-Pages ? Until WordPress includes an is_subpage() function, here is a manual method of testing for sub-pages: <?php global $post; if ( is_page() && $post->post_parent ) { // subpage content goes here } else { // non-subpage content goes here } ?> Further, here are some other ways to use this method to test for different combinations of pages and sub-pages: <?php if (is_page('about') || $post->post_parent == '1') { $banner = 'business.png'; } elseif (is_page('archives') || $post->post_parent == '2') { $banner = 'pleasure.png'; } elseif (is_page('contact') || $post->post_parent == '3') { $banner = 'personal.png'; } else { $banner = 'default.png'; } ?> Note that the numbers “1”, “2”, and “3” represent the IDs of the target parent pages. Multiple Widgetizable Sidebars ? Instead of using multiple “if” statements to include multiple widgetizable areas, WPEngineer shows us how to do it a better way: <?php // multiple widgetizable sidebars if (function_exists('register_sidebar')) { $sidebars = array('Home Sidebar', 'Post Sidebar', 'Page Sidebar'); foreach($sidebars as $name) { register_sidebar(array('name'=> $name, 'before_widget' => '<div id="%1$s" class="widget %2$s">', 'after_widget' => '</div>', 'before_title' => '<h3 class="widgetTitle">', 'after_title' => '</h3>', )); } } ?> Source: wpengineer Remove Fancy Quotes from Comments ? Prevent invalid markup and sloppy code by disabling WordPress’ automatic generation of “fancy” or “curly” quotes where they fail the most: your comments area. Only one simple line of code is required, placed into your theme’s functions.php file: remove_filter(‘comment_text’, ‘wptexturize’); Source: WPRecipes.com Display a List of All Untagged Posts ? Here is an easy way to display a list of all untagged posts. All that’s required is a custom loop and a quick check of the get_the_tags variable. Here is the code to make it work: <?php query_posts('orderby=title&order=asc&showposts=-1'); ?> <?php if (have_posts()) : ?> <ul> <?php while (have_posts()) : the_post(); ?> <?php $tag = get_the_tags(); if (!$tag) { ?> <li><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a> <?php edit_post_link('Edit', ' ',''); ?></li> <?php } ?> <?php endwhile; ?> </ul> <?php endif; ?> Place that snippet into the theme file of your choice and navigate to that page in a browser to see a permlink-linked list of all posts that have not yet been tagged. Even better, next to each post title will be a an easy-access “Edit” link that will make it easy to quickly edit each of your untagged posts and add some tags, if necessary. Nothing on this planet could be easier. Almost. Easy Display of Custom Headers, Footers, and Sidebars ? WordPress 2.7 includes new functionality that makes it super-easy to include custom headers, footers, and sidebars into your theme. Normally, you include the default files with the following tags: <?php get_header(); ?> <?php get_sidebar(); ?> <?php get_footer(); ?> These will include the files named “header.php”, “sidebar.php”, and “footer.php”, respectively. Now, to include alternate versions of these files, simply include the name of the file as a parameter in its associated tag. Here is an example that should illustrate the idea: <?php get_header('custom-header'); ?> <?php get_sidebar('custom-sidebar'); ?> <?php get_footer('custom-footer'); ?> These will include the files named “custom-header.php”, “custom-sidebar.php”, and “custom-footer.php”, respectively. We can now use this new functionality to get fine-grained with includes. For example, if we wanted to display a custom footer for the “Bananaz” category, we could use the following code: <?php if is_category('Bananaz') { get_footer('Bananaz'); } else { get_footer(); } ?> Source: WordPress Codex A Better Way for Users to Logout ? The old way of displaying a “Logout” link for your users looks like this: <a href="<?php echo get_option('siteurl'); ?>/wp-login.php?action=logout">Logout</a> Now, since WordPress 2.7, we can simplify this hodgepodge with a sleeker, cleaner, built-in template tag: <a href="<?php echo wp_logout_url(); ?>">Logout</a> Sweetness. Display a Custom Message on a Specific Date ? Using a snippet of PHP, we can display a custom message (or any code, markup, or content) on a specific date: <?php if ((date('m') == 4) && (date('d') == 9)) { ?> <p>Today is <a href="http://naked.dustindiaz.com/">CSS Naked Day</a>!</p> <?php } ?> You could even use this technique to join in on CSS Naked Day by removing your stylesheet on that day. Simply wrap your CSS <link> as follows: <?php // strip for CSS Naked Day if ((date('m') !== 4) && (date('d') !== 9)) { ?> <link rel="stylesheet" href="<?php bloginfo('stylesheet_url'); ?>" type="text/css" media="screen" /> <?php } ?> The possibilities are endless! Display Three Columns of Posts ? Displaying content in multiple columns is a much sought-after WordPress technique. There are some good tutorials around explaining various ways of doing the job, but this one is perhaps the easiest. To display your posts in three columns, begin by segmenting your post with some HTML comments: Lorem ipsum blah blah. This content appears before the three columns. <!--column--> This content will appear in the first column. <!--column--> This content will appear in the second column. <!--column--> This content will appear in the third column. The next step is to create columns based on the markup comments. Open your theme file and include the following code within the loop: <?php // multiple columns $page_columns = explode("<--column-->", $post->post_content); echo $page_columns[0]; // before columns echo '<div class="first column">'.$page_columns[1].'</div>'; // first column echo '<div class="second column">'.$page_columns[2].'</div>'; // second column echo '<div class="third column">'.$page_columns[3].'</div>'; // third column ?> That’s essentially all there is to it. To get the columns to actually look like columns, add something similar to the following in your CSS file: /* column structure */ .column { margin-right: 10px; float: left; width: 33%; } /* column styles */ column.first, column.second, column.third {} The cool thing about this method is that you have full control over the layout of each particular post. Each column may contain as much or as little content as desired, and adding or removing columns is straightforward. Even better is that you can easily remove the column functionality and display your content in a single column by simply removing the custom code from the loop. The post markup consists of HTML comments, so they will be ignored if not acted upon from within the loop. Source: Enhanced version of krimsly’s technique (via the WP Codex) Disable WordPress Search Functionality ? Disabling the WordPress search functionality is as simple as adding the following code to your functions.php file: function fb_filter_query($query, $error = true) {
// to error if ($error == true) $query->is_404 = true; } } if (!is_admin()) { add_action('parse_query', 'fb_filter_query'); add_filter('get_search_form', create_function('$a', "return null;")); } In place, this code will disable the search form for your theme while leaving search functionality intact for the Admin area. As is, the $error variable is set to TRUE, which causes the function to display the theme’s error page. Setting this variable to FALSE will prevent the error message and keep the user on the same page. Source: WPengineer Display Posts with Specific Custom Fields ? Displaying posts that are associated with a certain custom field is as easy as adding an “if” condition to your loop. Here is an example that checks for the presence of a custom field called “name-of-custom-field”. If such a custom field is associated with the post, the entire post is displayed; otherwise, only the excerpt is displayed. <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php $custom_field = get_post_custom_values("name-of-custom-field"); ?> <?php if (isset($custom_field[0])) { ?> <h1><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h1> <?php the_content(); ?> <?php } else { ?> <h2><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h2> <?php the_excerpt(); ?> <?php } ?> <?php endwhile; endif; ?> To get more specific and display only posts associated with a custom-field that is set to a certain value, we simply add an additional parameter to the “if” condition: <?php if ((isset($custom_field[0])) && ($custom_field[0] == "name-of-value")) { ?> Using that line of code, we modify our previous loop as follows: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php $custom_field = get_post_custom_values("name-of-custom-field"); ?> <?php if ((isset($custom_field[0])) && ($custom_field[0] == "name-of-value")) { ?> <h1><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h1> <?php the_content(); ?> <?php } else { ?> <h2><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h2> <?php the_excerpt(); ?> <?php } ?> <?php endwhile; endif; ?> With this code, any post with a custom-field of “name-of-custom-field” that has a specific value of “name-of-value” will be displayed in its entirety. All other posts will be displayed as an excerpt. Source: Perishable Press How to Number Your Comments, Pingbacks, and Trackbacks in 2.7+ ? Numbering comments, pingbacks, and trackbacks in WordPress versions 2.7 and greater requires two steps. First, you need to add a couple of parameters to your comments_template tag, which is used to display your comments template and normally located in your single.php file. Edit this tag so that it looks like this: <?php comments_template('/comments.php',true); ?> Once this is in place, you can display the number of your comments, pingbacks, trackbacks, and both using the following tags: echo count($wp_query->comments_by_type['comment']); // display comment count echo count($wp_query->comments_by_type['pingback']); // display pingback count echo count($wp_query->comments_by_type['trackback']); // display trackback count echo count($wp_query->comments_by_type['pings']); // display pingback and trackback count comments_number('No Responses', 'One Response', '% Responses' ); // display total response count These tags can be placed anywhere in your comments loop. For more information on how to implement this, check out our in-depth article at Digging into WordPress. How to Number Your Comments Using the Classic Loop ? Before, WordPress added the new comments API in version 2.7, the “classic” comment-loop mechanism was used. This loop still works in any version of WordPress, and is useful for extreme formatting of the comment display area. Numbering your comments in the classic loop is as easy as it is in the new-fangled loop. Here’s how: In your comments.php file, add a counter variable ( <?php $i = 0; ?> ) just above the loop’s foreach statement, like so: <?php $i = 0; ?> <?php foreach ($comments as $comment) : ?> Then, to increment the counter variable with each iteration of the loop, we add another snippet just below the foreach line, like so: <?php $i = 0; ?> <?php foreach ($comments as $comment) : ?> <?php $i++; ?> Everything is now set. To display the number of comments, simply echo the value of the counter variable anywhere within your comment loop. Here is an example: There are comments so far! Source: Digging into WordPress Invite Readers to Comment via Feed ? Nice little snippet showing how to invite your readers to leave a comment by clicking on a link within your feed. Just add the following code to your theme’s functions.php file: // comment invite feed link function rss_comment_footer($content) { if (is_feed()) { if (comments_open()) { $content .= 'Comments are open! <a href="'.get_permalink().'">Add yours!</a>'; } } return $content; } In place, this function will output a link that says, “Comments are open! Add yours!” This message will be displayed at the end of each post for which comments are open. If comments are closed, no invite message is displayed. Source: Hendry Lee Display the Total Number of Users for Your Blog ? Here is a tasty little snippet from WPRecipes that will enable you to display the total number of users for your WordPress-powered blog. All you need to do is place the following code in your theme file(s) where you would like to display your total number of users: $users = $wpdb->get_var("SELECT COUNT(ID) FROM $wpdb->users"); echo $users." registered users."; Source: WPRecipes.com Automatically Insert Content into Your WordPress Post Editor ? Here is a nice way to automatically insert some custom content into your post editor. This makes it easy to add repetitive content to your posts while retaining the ability to make changes before publishing. To try it out, add the following code to your functions.php file: <?php // auto-insert content to post editor function my_editor_content($content) { $content = "<h5>Thank you for your generous attention!</h5>."; return $content; } add_filter('default_content', 'my_editor_content'); ?> This code will display a message thanking people for their generous attention, but you can easily edit the message to display whatever content (text/markup) that you wish. After configuring your message, open your WordPress text editor to see the automatically inserted content. Source: Justin Tadlock How to Prevent Duplicate Content ? Unless you’re using excerpts for non-single page views, your post content is being displayed in your single pages, date-based archives, category archive, tags archives, author archives, and so on. From an SEO perspective, this “duplicate” content may be detrimental to your search-engine rankings. To prevent duplicate content, we can conditionally display one of two <meta> tags depending on the type of page being displayed. Pages that we want to have indexed in the search engines will display a “meta-index” tag, while duplicate pages will display a “meta-noindex” tag. To do this, simply add the following code to the <head> section of your theme’s header.php file: <?php if ((is_home() && ($paged < 2 )) || is_single() || is_page() || is_category()) { echo '<meta name="robots" content="index,archive,follow" />'; } else { echo '<meta name="robots" content="noindex,noarchive,follow" />'; } Once in place, this code effectively stops search engines from indexing all types of pages except for single-post, page-page, category-archive, and the first two index pages. These are considered by many to be the most effective pages to have indexed, but feel free to add or remove anything you see fit to customize the technique. Source: Perishable Press Conditionally Display Full Posts or Excerpts ? By default, you can either display full-posts or excerpts when displaying your posts. This may be fine for common blogging purposes, but specialized blogs may find it beneficial to exercise control over which type of post format is displayed. Here’s how to conditionally display either full-post or excerpt based on the presence of a custom field named “full-post-display”. To implement this technique, setup the following loop in your theme file(s): <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php $customdisplay = get_post_custom_values("full-post-display"); ?> <?php if (isset($customdisplay[0])) { ?>
<h1><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h1> <?php the_content(); ?> <?php } else { ?> <h1><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h1> <?php the_excerpt(); ?> <?php } ?> <?php endwhile; endif; ?> Then, for any post that you would like to display with full-post formatting, simply add a custom-field of “full-post-display” and give it a value of “true”. Display Related Posts without a Plugin ? We don’t need no stinking plugins to display related posts! Here’s how to do the job using tags as the associative criteria. Place the following code in your loop and take a nap or something: <?php // related posts based on first tag of current post $tags = wp_get_post_tags($post->ID); if ($tags) { echo '<h3>Related Posts</h3>'; $first_tag = $tags[0]->term_id; $args = array( 'tag__in' => array($first_tag), 'post__not_in' => array($post->ID), 'showposts' => 7, // how many posts? 'caller_get_posts' => 1 ); $my_query = new WP_Query($args); if ($my_query->have_posts()) { ?> <ul> <?php while ($my_query->have_posts()) : $my_query->the_post(); ?> <li><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></li> <?php endwhile; ?> </ul> <?php } ?> <?php } ?> Customize as needed. To change the number of posts, edit the line that says, “how many posts?” Source: Enhanced version of the code provided by MichaelH (via WP Codex) Drop-Dead Easy Styles for Author Comments ? This is almost too easy. To make your Author comments stand out from the crowd in WordPress 2.7 or better, use this code to apply some custom CSS stylez: li.bypostauthor { background: red; color: white; } li.byuser { background: white; color: black; } Display Upcoming Scheduled Posts ? Here’s an easy way to display a list of posts that are scheduled to be published at some point in the future. Create a page called “Upcoming Posts” (or whatever), and use this code for the loop: <?php query_posts('showposts=7&post_status=future'); ?> <?php if (have_posts()) : ?> <h3>Upcoming Scheduled Posts</h3> <ul> <?php while (have_posts()) : the_post(); ?> <li><?php the_title(); ?> — <?php the_time('l, F j, Y'); ?></li> <?php endwhile; ?> </ul> <?php else: ?> <p>Nothing new in queue!</p> <?php endif; ?> In place, this code will output a list of all posts that exist within the database that have a post_status of “future”. I.e., anything that you have setup in draft mode that is set to auto-publish at a certain point in the future. Display Automatic TinyURLs for Your Posts ? Make it super-easy for your visitors to share the URL of your posts with their favorite social-media service. Providing an alternate “short” version of your URLs is possible using the free TinyURL service and a couple snippets of code. To display short URLs at the end of your posts, place this code into your theme’s functions.php file: function getTinyUrl($url) { $tinyurl = file_get_contents("http://tinyurl.com/api-create.php?url=".$url); return $tinyurl; } Then, call the function and display the URL by placing this code into your single.php file in the desired location within the loop: <?php $turl = getTinyUrl(get_permalink($post->ID)); echo 'TinyURL for this post: <a href="'.$turl.'">'.$turl.'</a>'; ?> That’s it! Your posts now feature super-short URLs for all of your tweet-hungry visitors. Tuper Tweet Tude! Source: Perishable Press Implement a Site-Maintenance Page for Your Blog ? Ever do maintenance on your site? Certainly, we all do. Here’s an easy way to display a “site-maintenance” page that will display whatever content you desire. The key here is setting up your HTAccess file to handle the redirect properly. First, you need to create your maintenance page. This can be as simple or as advanced as you would like. At minimum, you could include something like this into a file named “maintenance.html”: <h1>Site Maintenance</h1> <p>Please check back in 15 minutes</p> Then, add this bit of voodoo to your site’s root htaccess file: # SITE MAINTENANCE PAGE RewriteEngine on RewriteCond %{REQUEST_URI} !/maintenance.html$ RewriteCond %{REMOTE_ADDR} !^111\\.222\\.333\\.444 RewriteRule $/maintenance.html [R=302,L] Once that’s in place, replace the example IP address with that of your own. Upload to your site and check it out. What you will see is that you have full access to your site, but all other visitors will see the maintenance page. Once maintenance is complete, simply comment out the code in your htaccess file to allow visitors back into the site. Source: Catswhocode Display the First Image from Each of Your Posts ? If your posts include an image that you would like to display as a thumbnail elsewhere on your blog, here is an easy way to do it with no custom fields required. Place the following code into your theme’s functions.php file: function catch_that_image() { global $post, $posts; $first_img = ''; ob_start(); ob_end_clean(); $output = preg_match_all('/<img.+src=[\\'"]([^\\'"]+)[\\'"].*>/i', $post->post_content, $matches); $first_img = $matches [1] [0]; if(empty($first_img)){ $first_img = "/images/default.jpg"; // default image } return $first_img; } Then, to call the function and display the images as thumbnails, place the following code into the desired location within your loop: <?php echo catch_that_image(); ?> That’s all there is to it. If you would like to display a default image for posts that may not have one, specify its path in the code (on the line that says “default image). Source: WPRecipes Display Most Popular Posts without a Plugin ? Simple but effective method of displaying your blog’s most popular posts based on comment count. This code snippet may be placed anywhere within your theme’s files (i.e., no loop required). Check it out: <h3>Popular Posts</h3> <ul> <?php $result = $wpdb->get_results(" SELECT comment_count, ID, post_title FROM $wpdb->posts ORDER BY comment_count DESC LIMIT 0 , 7 "); foreach ($result as $post) { setup_postdata($post); $postid = $post->ID; $title = $post->post_title; $commentcount = $post->comment_count; if ($commentcount != 0) { ?> <li><a href="<?php echo get_permalink($postid); ?>"> <?php echo $title; ?></a> [<?php echo $commentcount ?>]</li> <?php } ?> <?php } ?> </ul> Once in place, this code will display the seven most popular posts along with their associated comment count in unordered list format. Customize according to your needs. Source: ProBlogDesign (404 link removed 2013/09/15) Automatically Highlight Search Terms ? Make things easy for people who are searching your site by applying some custom styling to the search terms that are displayed in the search results. A common way to display search terms is with a yellow background so that users can easily identify locations of the text that may apply to their query. It’s all about about usability, and improving the way search results are displayed on your site. Here’s how to do it: First, replace the the_title() tag in your search.php file with the following: <?php // highlight search terms in title $title = get_the_title(); $keys = explode(" ", $s); $title = preg_replace('/('.implode('|',$keys).')/iu','<span class="search-terms">\\0</span>',$title); echo $title; ?> This will setup styling for search terms located in the title of each result. Then, for the content, replace the the_excerpt() tag in your search.php file with the following: <?php // highlight search terms in content $excerpt = get_the_excerpt(); $keys = explode(" ", $s); $excerpt = preg_replace('/('.implode('|',$keys).')/iu','<span class="search-terms">\\0</span>',$excerpt); echo $excerpt; ?> Finally, open your theme’s CSS file and add some custom styles for the search terms. A great way to highlight each term is to display it in bold text with yellow highlighting. Something like this: span.search-terms { background: yellow; font-weight: bold; } That’s all there is to it! Go run a few searches to see it in action. Source: Enhanced version of code provided by Yoast.com Automatically Disable Widgets ? Quick tip to disable all widget functionality from your theme. Add the following to your functions.php file and call it done: <?php // disable all widgets function disable_all_widgets($sidebars_widgets) { $sidebars_widgets = array(false); return $sidebars_widgets; } add_filter('sidebars_widgets', 'disable_all_widgets'); ?> Source: Justin Tadlock Display All Images from Your Post Content ? Want to display all of the images from each of your posts somewhere on your blog? Easy. Check out this code snippet from Matt Varone: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php $szPostContent = $post->post_content; $szSearchPattern = '~<img [^\\>]*\\ />~'; // Run preg_match_all to grab all the images and save the results in $aPics preg_match_all($szSearchPattern, $szPostContent, $aPics); // Check to see if we have at least 1 image $iNumberOfPics = count($aPics[0]); if ($iNumberOfPics > 0) { // now here you would do whatever you need to do with the images // for this example the images are just displayed for ( $i=0; $i < $iNumberOfPics ; $i++ ) { echo $aPics[0][$i]; }; }; endwhile; endif; ?> Just customize the output in the second part of the code (see code comments) and paste the function wherever you would like to display the images. Sweetness. Source: Matt Varone Display Category List in Two Columns ? Tired of that boring, single-column category display? Spice things up with a spiffy two-column category list that will get your visitors’ hearts pumping. Let’s deface a WordPress tag, shall we? See this bad boy: <?php wp_list_categories(); ?> We’re going to blow it up, divide its contents into two pieces, and spit it all back out as two unordered lists. Impossible, you say? Nah, just a little PHP to make it all go. Wherever you would like to display your categories in two columns, throw down the following code snippet: <?php // display categories in columns $cats = explode("<br />",wp_list_categories('title_li=&echo=0&depth=1&style=none')); $cat_n = count($cats) - 1; for ($i=0;$i<$cat_n;$i++) : if ($i<$cat_n/2) : $cat_left = $cat_left.'<li>'.$cats[$i].'</li>'; elseif ($i>=$cat_n/2): $cat_right = $cat_right.'<li>'.$cats[$i].'</li>'; endif; endfor; ?> <ul class="left"> <?php echo $cat_left;?> </ul> <ul class="right"> <?php echo $cat_right;?> </ul> Completely awesome. Now let’s add some style to make the columns work: .right { float: left; width: 140px; } .left { float: left; width: 140px; } You are all set. You should probably fine-tune this business until it’s all good. You know. Source: Blog Oh Blog (404 link removed 2013/06/24) Show Ads or Other Content Only in the First Three Posts ? Advertising may require you to limit the number of advertisements on your page to three. For some, this is three too many. For others, it’s far too few. Still others feel that it’s just the right amount. Regardless of your feelings, here is a trick that will enable you to limit the number of posts that displays some specific content - ads, images, scripts, whatever you want. Check out the three indented lines in the following loop: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php if ($wp_query->current_post < 3) { ?> <!-- any content here will be displayed only in first three posts --> <?php } ?> <?php endwhile; else: ?> <?php endif; ?> See what’s happening here. We’ve got a loop, see. In this loop, we specify a condition that says, “if this is one of the first three posts, display this content.” And that’s the magic. Of course, you can use whatever content you would like, and there is nothing special about the number “3” either. Source: Blog Oh Blog (404 link removed 2013/06/24) A Better Way to Display Recent Comments without a Plugin ? Here is a better way to display your recent comments without a plugin. Instead of slapping a bunch of gnarly code into our index.php or sidebar.php file, we are going to slap it right where it belongs: in your theme’s functions.php file. Here is the code, all exploded for your viewing and analytical pleasure (well, for mine anyway). For a more minified version of this snippet, be sure to check out the source link. <?php // display recent comments without a plugin function recent_comments($src_count=10, $src_length=60, $pre_HTML='<ul>', $post_HTML='</ul>') { global $wpdb; $sql = " SELECT DISTINCT ID, post_title, post_password, comment_ID, comment_post_ID, comment_author, comment_date_gmt, comment_approved, comment_type, SUBSTRING( comment_content, 1, $src_length ) AS com_excerpt FROM $wpdb->comments LEFT OUTER JOIN $wpdb->posts ON ( $wpdb->comments.comment_post_ID = $wpdb->posts.ID ) WHERE comment_approved = '1' AND comment_type = '' AND post_password = '' ORDER BY comment_date_gmt DESC LIMIT $src_count "; $comments = $wpdb->get_results($sql); $output = $pre_HTML; foreach ($comments as $comment) { $output .= '<li><a href="'.get_permalink($comment->ID).'#comment-'.$comment->comment_ID.'" title="on '.$comment->post_title.'">'.strip_tags($comment->com_excerpt).'...</a></li>'; } $output .= $post_HTML; echo $output; } ?> Ah, it’s a thing of beauty. Once you have that code in place, rock it out anywhere in your theme with this charming little tag: <?php recent_comments(); ?> see also: Display Latest Comments without a PluginSource: Blog Oh Blog (404 link removed 2013/06/24) Selectively Disable Automatic Post Formatting ? This trick is by far my favorite “stupid WordPress trick.” You know how WordPress likes to mangle HTML comments, empty elements, blockquotes, curly quotes, and other miscellaneous markup elements? Here is a tight little method that will enable you to selectively disable WordPress’ automatic post formatting. Do this: Place the following code into your theme’s functions.php file: // disable auto-formatting function my_formatter($content) { $new_content = ''; $pattern_full = '{(\\[raw\\].*?\\[/raw\\])}is'; $pattern_contents = '{\\[raw\\](.*?)\\[/raw\\]}is'; $pieces = preg_split($pattern_full, $content, -1, PREG_SPLIT_DELIM_CAPTURE); foreach ($pieces as $piece) { if (preg_match($pattern_contents, $piece, $matches)) { $new_content .= $matches[1]; } else { $new_content .= wptexturize(wpautop($piece)); } } return $new_content; } remove_filter('the_content', 'wpautop'); remove_filter('the_content', 'wptexturize'); add_filter('the_content', 'my_formatter', 99); Then do this: Use the [raw] shortcode wherever you would like to disable auto-formatting in your post content. For example, if you wanted to prevent the following sentence from being formatted, you would write this: [raw]This text will not be automatically formatted.[/raw] Absolutely brilliant. Source: WPRecipes Browser Detection via WordPress’ body_class Function ? WordPress makes it possible to detect a handful of different browsers using a variety of built-in global variables. WordPress also provides a body_class tag that outputs a variety of class attributes depending on various page properties. Why not combine these two techniques so that the user’s detected browser is added to the list of output classes for the body tag? Here’s the code that will do it via functions.php: // browser detection via body_class function browser_body_class($classes) { global $is_lynx, $is_gecko, $is_IE, $is_opera, $is_NS4, $is_safari, $is_chrome, $is_iphone; if($is_lynx) $classes[] = 'lynx'; elseif($is_gecko) $classes[] = 'gecko'; elseif($is_opera) $classes[] = 'opera'; elseif($is_NS4) $classes[] = 'ns4'; elseif($is_safari) $classes[] = 'safari'; elseif($is_chrome) $classes[] = 'chrome'; elseif($is_IE) $classes[] = 'ie'; else $classes[] = 'unknown'; if($is_iphone) $classes[] = 'iphone'; return $classes; } add_filter('body_class','browser_body_class'); This code will output the detected browser along with the other body_class tags. Here is an example: <body class="home blog logged-in safari"> Hooked. Sources: Nathan Rice Get Post or Page Contents as a PHP Variable ? Here is a quick snippet for placing all post or page content into a variable. We’re talking the entire page contents here, not just the content of the post. Place this code into your theme’s functions.php file: // post contents as variable function callback($buffer) { return $buffer; } function buffer_start() { ob_start("callback"); } function buffer_end() { ob_end_flush(); } add_action('wp_head', 'buffer_start'); add_action('wp_footer', 'buffer_end'); Once in place, this function will capture the entire page contents into a variable called “$buffer”. You may then do whatever you wish to this variable. Filter it, match it, slap it around a little and show it who’s boss. That sort of thing. Source: Dagon DesignSee also: Digging into WordPress Simple Example of How to Use WordPress Cron ? I have been meaning to get into WordPress’ wp-cron functionality, and this looks like a good way to get started with it. This code snippet uses wp-cron to schedule an automatic email that will be sent every hour. // send automatic scheduled email if (!wp_next_scheduled('my_task_hook')) { wp_schedule_event(time(), 'hourly', 'my_task_hook'); } add_action('my_task_hook', 'my_task_function'); function my_task_function() { wp_mail('you@yoursite.com', 'Automatic email', 'Hello, this is an automatically scheduled email from WordPress.'); } Of course, this is meant only as an example. The key here is to schedule and event and then hook into it with some specific function. Source: slaven.net (404 link removed 2013/02/04) Add More Default Avatar Choices to the WordPress Admin ? Here is a quick and easy way to add more default avatars to the list of available gravatars in the Settings area of the WordPress Admin. Here is the functions.php code to make it happen: // add more default avatars to options if (!function_exists('fb_addgravatar')) { function fb_addgravatar($avatar_defaults) { $myavatar1 = get_bloginfo('template_directory').'/images/avatar-01.png'; $avatar_defaults[$myavatar1] = 'dude';
<meta name="viewport" content="width=device-width, initial-scale=1.0" /> <meta charset="UTF-8"> <!-- Favicon --> <link rel="icon" type="image/x-icon" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/favicon.ico" /><link rel="shortcut icon" type="image/x-icon" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/favicon.ico" /><link type="image/x-icon" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/favicon.ico" /> <!-- Windows 8 Tiles and Feed --> <meta name="application-name" content="Smashing Magazine"/> <meta name="msapplication-TileColor" content="#e53b2c"/> <meta name="msapplication-square70x70logo" content="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/smashing-windows-icon-70-70.png"/> <meta name="msapplication-square150x150logo" content="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/smashing-windows-icon-150-150.png"/> <meta name="msapplication-wide310x150logo" content="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/smashing-windows-icon-310-150.png"/> <meta name="msapplication-square310x310logo" content="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/smashing-windows-icon-310-310.png"/> <meta name="msapplication-notification" content="frequency=30;polling-uri=http://notifications.buildmypinnedsite.com/?feed=http://www.smashingmagazine.com/feed/&id=1;polling-uri2=http://notifications.buildmypinnedsite.com/?feed=http://www.smashingmagazine.com/feed/&id=2;polling-uri3=http://notifications.buildmypinnedsite.com/?feed=http://www.smashingmagazine.com/feed/&id=3;polling-uri4=http://notifications.buildmypinnedsite.com/?feed=http://www.smashingmagazine.com/feed/&id=4;polling-uri5=http://notifications.buildmypinnedsite.com/?feed=http://www.smashingmagazine.com/feed/&id=5; cycle=1"/> <!-- iOS Icons --> <link rel="apple-touch-icon-precomposed" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/apple-touch-icon-precomposed.png" /> <link rel="apple-touch-icon-precomposed" sizes="57x57" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/apple-touch-icon-57x57-precomposed.png" /> <link rel="apple-touch-icon-precomposed" sizes="72x72" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/apple-touch-icon-72x72-precomposed.png" /> <link rel="apple-touch-icon-precomposed" sizes="114x114" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/apple-touch-icon-114x114-precomposed.png" /> <link rel="apple-touch-icon-precomposed" sizes="144x144" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/apple-touch-icon-144x144-precomposed.png" /> <!-- This site is optimized with the Yoast WordPress SEO plugin v1.5.2.7 - https://yoast.com/wordpress/plugins/seo/ --> <meta name="description" content="Plugins are a major part of why WordPress powers millions of blogs and websites around the world. The ability to extend WordPress to meet just about any need is a powerful motivator for choosing WordPress over other alternatives."/> <link rel="canonical" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/" /> <link rel="publisher" href="https://plus.google.com/+SmashingMagazine?"/> <meta property="og:locale" content="en_US" /> <meta property="og:type" content="article" /> <meta property="og:title" content="Ten Things Every WordPress Plugin Developer Should Know - Smashing Magazine" /> <meta property="og:description" content="Plugins are a major part of why WordPress powers millions of blogs and websites around the world. The ability to extend WordPress to meet just about any need is a powerful motivator for choosing WordPress over other alternatives." /> <meta property="og:url" content="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/" /> <meta property="og:site_name" content="Smashing Magazine" /> <meta property="article:publisher" content="https://www.facebook.com/smashmag" /> <meta property="article:tag" content="Essentials" /> <meta property="article:tag" content="PHP" /> <meta property="article:tag" content="Plugins" /> <meta property="article:tag" content="Techniques (WP)" /> <meta property="article:section" content="WordPress" /> <meta property="article:published_time" content="2011-03-08T05:35:31+01:00" /> <meta property="article:modified_time" content="2014-04-25T13:28:41+02:00" /> <meta property="og:updated_time" content="2014-04-25T13:28:41+02:00" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/images/post-pictures/wordpress-blue-illu.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/03/wordpress_plugin.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-black1.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-globals1.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-profiler1.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-sql1.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-errors1.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/general-settings-same-url.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/general-settings-different-url.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/admin-menu-options-page.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/admin-menu-custom.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/plugin-action-links-none.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/plugin-action-links-settings.jpg" /> <meta name="twitter:card" content="summary_large_image"/> <meta name="twitter:site" content="@smashingmag"/> <meta name="twitter:domain" content="Smashing Magazine"/> <meta name="twitter:creator" content="@arcware"/> <meta name="twitter:image:src" content="http://www.smashingmagazine.com/wp-content/uploads/images/post-pictures/wordpress-blue-illu.jpg"/> <!-- / Yoast WordPress SEO plugin. --> <link rel="alternate" type="application/rss+xml" title="Smashing Magazine » Feed" href="http://www.smashingmagazine.com/feed/" /> <link rel="alternate" type="application/rss+xml" title="Smashing Magazine » Comments Feed" href="http://www.smashingmagazine.com/comments/feed/" /> <link rel="alternate" type="application/rss+xml" title="Smashing Magazine » Ten Things Every WordPress Plugin Developer Should Know Comments Feed" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/feed/" /> <link rel='shortlink' href='http://www.smashingmagazine.com/?p=111255' /> <script type="text/javascript">!function(){function e(e,t,n){e.addEventListener?e.addEventListener(t,n,!1):e.attachEvent&&e.attachEvent("on"+t,n)}function t(e){return window.localStorage&&localStorage.font_css_cache&&localStorage.font_css_cache_file===e}function n(){if(window.localStorage&&window.XMLHttpRequest)if(t(o))a(localStorage.font_css_cache);else{var n=new XMLHttpRequest;n.open("GET",o,!0),e(n,"load",function(){4===n.readyState&&(a(n.responseText),localStorage.font_css_cache=n.responseText,localStorage.font_css_cache_file=o)}),n.send()}else{var c=document.createElement("link");c.href=o,c.rel="stylesheet",c.type="text/css",document.getElementsByTagName("head")[0].appendChild(c),document.cookie="font_css_cache"}}function a(e){var t=document.createElement("style");t.innerHTML=e,document.getElementsByTagName("head")[0].appendChild(t)}var o="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/stylesheets/webfonts.min.css?ver=1.1.0";window.localStorage&&localStorage.font_css_cache||document.cookie.indexOf("font_css_cache")>-1?n():e(window,"load",n)}();</script> <!--[if IE 8]><script type="text/javascript" src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><link href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/stylesheets/ie8-nu.css" media="all" rel="stylesheet" type="text/css" /><![endif]--> <noscript><link href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/stylesheets/main.min.css?ver=2014.14.0" rel="stylesheet" media="all" type="text/css" /></noscript> </head> <body class="single single-post postid-111255 single-format-standard www-section"> <nav id="top" class="tn clearfix"> <div class="mini"> <h1><span class="sr">Smashing Magazine</span><a href="http://www.smashingmagazine.com/"><img src="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/logo.png" alt="Smashing Magazine" title="Jump to the front page" /></a></h1> </div> <div class="mnb"> <a href="#mn" class="ntb">Menu</a> <a href="#ms" class="stb">Search</a> </div> <ul id="menu-network-menu" class="nw clearfix"><li class="current"><a href="http://www.smashingmagazine.com"><img src="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/logo.png" alt="Smashing Magazine" title="Jump to the front page" /></a></li><li id="menu-item-77918" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-77918 menu-item-books"><a href="http://www.smashingmagazine.com/books/">Books</a></li> <li id="menu-item-78659" class="cody menu-item menu-item-type-post_type menu-item-object-page menu-item-78659 menu-item-ebooks"><a href="http://www.smashingmagazine.com/ebooks/">eBooks</a></li> <li id="menu-item-85386" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-85386 menu-item-workshops"><a href="http://www.smashingmagazine.com/smashing-workshops/">Workshops</a></li> <li id="menu-item-2" class="menu-item menu-item-type-custom menu-item-object-custom menu-item-2 menu-item-job-board"><a href="http://jobs.smashingmagazine.com/">Job Board</a></li> </ul> <ul class="ch"> <li class="rss"><a href="http://www.smashingmagazine.com/feed/" title="Subscribe to our RSS-feed (120K)">RSS</a></li> <li class="fb"><a href="http://www.facebook.com/smashmag" title="Join our Facebook page! (221k)">Facebook</a></li> <li class="tw"><a href="http://twitter.com/smashingmag" title="Follow us on Twitter! (811k)">Twitter</a></li> <li class="nl"><a href="http://www.smashingmagazine.com/the-smashing-newsletter/" title="Subscribe to our Email Newsletter (180k)">Newsletter</a></li> </ul></nav> <div class="cc"><div class="fluid clearfix"><div class="grid clearfix"> <div class="mise sf clearfix" > <form id="search" method="get" action="http://www.smashingmagazine.com/search-results/" target="_top"> <input name="q" type="text" placeholder="e.g. JavaScript" /> <button class="search_submit" type="submit">Search</button> <input type="hidden" name="cx" value="partner-pub-6779860845561969:5884617103"> <input type="hidden" name="cof" value="FORID:10"> <input type="hidden" name="ie" value="UTF-8"> </form> </div><div class="col sn"> <nav class="sct"><ul id="menu-category-menu" class="clearfix"><li id="menu-item-116" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-has-children menu-item-116 menu-item-coding"><a href="http://www.smashingmagazine.com/category/coding/">Coding</a> <ul class="sub-menu"> <li id="menu-item-2014" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2014 menu-item-css"><a href="http://www.smashingmagazine.com/tag/css/">CSS</a></li> <li id="menu-item-134810" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-134810 menu-item-html"><a href="http://www.smashingmagazine.com/tag/html/">HTML</a></li> <li id="menu-item-2015" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2015 menu-item-javascript"><a href="http://www.smashingmagazine.com/tag/javascript/">JavaScript</a></li> <li id="menu-item-2016" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2016 menu-item-techniques"><a href="http://www.smashingmagazine.com/tag/techniques/">Techniques</a></li> </ul> </li> <li id="menu-item-117" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-has-children menu-item-117 menu-item-design"><a href="http://www.smashingmagazine.com/category/design/">Design</a> <ul class="sub-menu"> <li id="menu-item-2017" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2017 menu-item-web-design"><a href="http://www.smashingmagazine.com/tag/web-design/">Web Design</a></li> <li id="menu-item-2032" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2032 menu-item-typography"><a href="http://www.smashingmagazine.com/tag/typography/">Typography</a></li> <li id="menu-item-2063" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2063 menu-item-inspiration"><a href="http://www.smashingmagazine.com/tag/inspiration/">Inspiration</a></li> <li id="menu-item-2120" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2120 menu-item-business"><a href="http://www.smashingmagazine.com/tag/business/">Business</a></li> </ul> </li> <li id="menu-item-119" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-has-children menu-item-119 menu-item-mobile"><a href="http://www.smashingmagazine.com/category/mobile/">Mobile</a> <ul class="sub-menu"> <li id="menu-item-142132" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-142132 menu-item-iphone-ipad"><a href="http://www.smashingmagazine.com/tag/ios/">iPhone & iPad</a></li> <li id="menu-item-143596" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143596 menu-item-android"><a href="http://www.smashingmagazine.com/tag/android/">Android</a></li> <li id="menu-item-143608" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143608 menu-item-design-patterns"><a href="http://www.smashingmagazine.com/tag/design-patterns/">Design Patterns</a></li> </ul> </li> <li id="menu-item-118" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-has-children menu-item-118 menu-item-graphics"><a href="http://www.smashingmagazine.com/category/graphics/">Graphics</a> <ul class="sub-menu"> <li id="menu-item-2264" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2264 menu-item-photoshop"><a href="http://www.smashingmagazine.com/tag/photoshop/">Photoshop</a></li> <li id="menu-item-160" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-160 menu-item-fireworks"><a href="http://www.smashingmagazine.com/category/fireworks/">Fireworks</a></li> <li id="menu-item-2283" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2283 menu-item-wallpapers"><a href="http://www.smashingmagazine.com/tag/wallpapers/">Wallpapers</a></li> <li id="menu-item-2305" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2305 menu-item-freebies"><a href="http://www.smashingmagazine.com/tag/freebies/">Freebies</a></li> </ul> </li> <li id="menu-item-120" class="menu-item-uxdesign menu-item menu-item-type-taxonomy menu-item-object-category menu-item-has-children menu-item-120 menu-item-ux-design"><a href="http://www.smashingmagazine.com/category/uxdesign/">UX Design</a> <ul class="sub-menu"> <li id="menu-item-143609" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143609 menu-item-usability"><a href="http://www.smashingmagazine.com/tag/usability/">Usability</a></li> <li id="menu-item-143610" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143610 menu-item-user-experience"><a href="http://www.smashingmagazine.com/tag/user-experience/">User Experience</a></li> <li id="menu-item-143611" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143611 menu-item-ui-design"><a href="http://www.smashingmagazine.com/tag/ui/">UI Design</a></li> <li id="menu-item-143612" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143612 menu-item-e-commerce"><a href="http://www.smashingmagazine.com/tag/e-commerce/">E-Commerce</a></li> </ul> </li> <li id="menu-item-121" class="menu-item menu-item-type-taxonomy menu-item-object-category current-post-ancestor current-menu-parent current-post-parent menu-item-has-children menu-item-121 menu-item-wordpress"><a href="http://www.smashingmagazine.com/category/wordpress/"><span class="long"><span>Word</span><span>Press</span></span><span class="short">WP</span></a> <ul class="sub-menu"> <li id="menu-item-143677" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143677 menu-item-essentials"><a href="http://www.smashingmagazine.com/tag/essentials/">Essentials</a></li> <li id="menu-item-143678" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143678 menu-item-techniques"><a href="http://www.smashingmagazine.com/tag/techniques-wp/">Techniques</a></li> <li id="menu-item-143679" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143679 menu-item-plugins"><a href="http://www.smashingmagazine.com/tag/plugins/">Plugins</a></li> <li id="menu-item-143680" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143680 menu-item-themes"><a href="http://www.smashingmagazine.com/tag/themes/">Themes</a></li> </ul> </li> </ul></nav></div> <div class="col main single"> <article class="post-111255 post type-post status-publish format-standard has-post-thumbnail hentry category-wordpress tag-essentials tag-php tag-plugins tag-techniques-wp post"> <h2><a href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/" rel="bookmark" title="Read 'Ten Things Every WordPress Plugin Developer Should Know'">Ten Things Every WordPress Plugin Developer Should Know</a></h2> <ul class="pmd clearfix"> <li class="a">By <a rel="author" class="poa" href="http://www.smashingmagazine.com/author/dave-donaldson/?rel=author" title="Posts by Dave Donaldson">Dave Donaldson</a></li> <li class="date">March 8th, 2011</li> <li class="tags"><a href="http://www.smashingmagazine.com/tag/essentials/">Essentials</a><a href="http://www.smashingmagazine.com/tag/php/">PHP</a><a href="http://www.smashingmagazine.com/tag/plugins/">Plugins</a></li> <li class="comments"><a href="#comments" title="Comment on Ten Things Every WordPress Plugin Developer Should Know">94 Comments</a> </li> </ul> <div class="ad ed"> <span class="declare">Advertisement</span> <div id="cad"></div> </div> <p>Plugins are a major part of why WordPress powers millions of blogs and websites around the world. The ability to extend WordPress to meet just about any need is a powerful motivator for choosing WordPress over other alternatives. Having written several plugins myself, I’ve come to learn many (but certainly not all) of the ins-and-outs of <strong>WordPress plugin development</strong>, and this article is a culmination of the things I think every WordPress plugin developer should know. Oh, and keep in mind everything you see here is compatible with WordPress 3.0+.</p> <h3>Don’t Develop Without Debugging</h3> <p>The first thing you should do when developing a WordPress plugin is to enable debugging, and I suggest leaving it on the entire time you’re writing plugin code. When things go wrong, WordPress raises warnings and error messages, but if you can’t see them then they might as well have not been raised at all. <p><a href="http://www.smashingmagazine.com/wp-content/uploads/2011/03/wordpress_plugin.jpg"><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/03/wordpress_plugin.jpg" alt="Screenshot" title="WordPress_Plugins" width="500" /></a><sup class="po" id="note-1"><a href="#1">1</a></sup></p> <p>Enabling debugging also turns on WordPress notices, which is important because that’s how you’ll know if you’re using any deprecated functions. Deprecated functions may be removed from future versions of WordPress, and just about every WordPress release contains functions slated to die at a later date. If you see that you are using a deprecated function, it’s best to find its replacement and use that instead.</p> <h4>How to Enable Debugging</h4> <p>By default, WordPress debugging is turned off, so to enable it, open <strong>wp-config.php</strong> (tip: make a backup copy of this file that you can revert to later if needed) in the root of your WordPress installation and look for this line:</p> <pre><code class="language-php">define('WP_DEBUG', false);</code></pre> <p>Replace that line with the following:</p> <pre><code class="language-php">// Turns WordPress debugging on define('WP_DEBUG', true); // Tells WordPress to log everything to the /wp-content/debug.log file define('WP_DEBUG_LOG', true); // Doesn't force the PHP 'display_errors' variable to be on define('WP_DEBUG_DISPLAY', false); // Hides errors from being displayed on-screen @ini_set('display_errors', 0);</code></pre> <p>With those lines added to your wp-config.php file, debugging is fully enabled. Here’s an example of a notice that got logged to /wp-content/debug.log for using a deprecated function:</p> <p><em>[15-Feb-2011 20:09:14] PHP Notice: get_usermeta is <strong>deprecated</strong> since version 3.0! Use get_user_meta() instead. in C:CodePluginswordpresswp-includesfunctions.php on line 3237</em></p> <p>With debugging enabled, <strong>keep a close eye on /wp-content/debug.log</strong> as you develop your plugin. Doing so will save you, your users, and other plugin developers a lot of headaches.</p> <h4>How to Log Your Own Debug Statements</h4> <p>So what about logging your own debug statements? Well, the simplest way is to use <code>echo</code> and see the message on the page. It’s the quick-and-dirty-hack way to debug, but everyone has done it one time or another. A better way would be to create a function that does this for you, and then you can see all of your own debug statements in the debug.log file with everything else.</p> <p>Here’s a function you can use; notice that it only logs the message if WP_DEBUG is enabled:</p> <pre><code class="language-php">function log_me($message) { if (WP_DEBUG === true) { if (is_array($message) || is_object($message)) { error_log(print_r($message, true)); } else { error_log($message); } } }</code></pre> <p>And then you can call the <code>log_me</code> function like this:</p> <pre><code class="language-php">log_me(array('This is a message' => 'for debugging purposes')); log_me('This is a message for debugging purposes');</code></pre> <h4>Use the BlackBox Debug Bar Plugin</h4> <p>I only recently discovered this plugin, but it’s already been a huge help as I work on my own plugins. The <a href="http://ditio.net/2011/01/29/wordpress-debug-bar-plugin-blackbox/">BlackBox</a><sup class="po" id="note-2"><a href="#2">2</a></sup> plugin adds a thin black bar to the top of any WordPress post or page, and provides quick access to errors, global variables, profile data, and SQL queries.</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-black1.jpg" alt="" title="debug-bar-black" width="525" height="27" class="alignnone size-full wp-image-90255" /></p> <p>Clicking on the Globals tab in the bar shows all of the global variables and their values that were part of the request, essentially everything in the $_GET, $_POST, $_COOKIE, $_SESSION, and $_SERVER variables:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-globals1.jpg" alt="" title="debug-bar-globals" width="525" height="353" class="alignnone size-full wp-image-90251" /></p> <p>The next tab is the Profiler, which displays the time that passed since the profiler was started and the total memory WordPress was using when the checkpoint was reached:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-profiler1.jpg" alt="" title="debug-bar-profiler" width="525" height="98" class="alignnone size-full wp-image-90252" /></p> <p>You can add your own checkpoints to the Profiler by putting this line of code anywhere in your plugin where you want to capture a measurement:</p> <pre><code class="language-php">apply_filters('debug', 'This is a checkpoint');</code></pre> <p>Perhaps the most valuable tab in the BlackBox plugin is the SQL tab, which shows you all of the database queries that executed as part of the request. Very useful for determining long-running database calls:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-sql1.jpg" alt="" title="debug-bar-sql" width="525" height="176" class="alignnone size-full wp-image-90253" /></p> <p>And finally we have the Errors tab, which lists all of the notices, warnings, and errors that occurred during the request:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-errors1.jpg" alt="" title="debug-bar-errors" width="525" height="111" class="alignnone size-full wp-image-90250" /></p> <p>By providing quick access to essential debug information, the BlackBox plugin is a big-timer when it comes to debugging your WordPress plugin.</p> <h3>Prefix Your Functions</h3> <p>One of the first things that bit me when I started developing WordPress plugins was finding out that other plugin developers sometimes use the same names for functions that I use. For example, function names like <code>copy_file()</code>, <code>save_data()</code>, and <code>database_table_exists()</code> have a decent chance of being used by other plugins in addition to yours.</p> <p>The reason for this is because when WordPress activates a plugin, PHP loads the functions from the plugin into the WordPress execution space, where all functions from all plugins live together. There is no separation or isolation of functions for each plugin, which means that <strong>each function must be uniquely named</strong>.</p> <p>Fortunately, there is an easy way around this, and it’s to name all of your plugin functions with a prefix. For example, the common functions I mentioned previously might now look like this:</p> <pre><code class="language-php">function myplugin_copy_file() { } function myplugin_save_data() { } function myplugin_database_table_exists() { }</code></pre> <p>Another common naming convention is to use a prefix that is an abbreviation of your plugin’s name, such as “My Awesome WordPress Plugin”, in which case the function names would be:</p> <pre><code class="language-php">function mawp_copy_file() { } function mawp_save_data() { } function mawp_database_table_exists() { }</code></pre> <p>There is one caveat to this, however. If you use PHP classes that contain your functions (which in many cases is a good idea), you don’t really have to worry about clashing with functions defined elsewhere. For example, let’s say you have a class in your plugin named “CommonFunctions” with a <code>copy_file()</code> function, and another plugin has the same <code>copy_file()</code> function defined, but not in a class. Invoking the two functions would look similar to this:</p> <pre><code class="language-php">// Calls the copy_file() function from your class $common = new CommonFunctions(); $common->copy_file(); // Calls the copy_file() function from the other plugin copy_file();</code></pre> <p><strong>By using classes, the need to explicitly prefix your functions goes away.</strong> Just keep in mind that WordPress will raise an error if you use a function name that’s already taken, so keep an eye on the debug.log file to know if you’re in the clear or not.</p> <h3>Global Paths Are Handy</h3> <p>Writing the PHP code to make your plugin work is one thing, but if you want to make it look and feel good at the same time, you’ll need to include some images, CSS, and perhaps a little JavaScript as well (maybe in the form of a jQuery plugin). And in typical fashion, you’ll most likely organize these files into their own folders, such as “images”, “css”, and “js”.</p> <p>That’s all well and good, but how should you code your plugin so that it can always find those files, no matter what domain the plugin is running under? The best way that I’ve found is to <strong>create your own global paths</strong> that can be used anywhere in your plugin code.</p> <p>For example, I always create four global variables for my plugins, one each for the following:</p> <ul> <li>The path to the theme directory</li> <li>The name of the plugin</li> <li>The path to the plugin directory</li> <li>The url of the plugin</li> </ul> <p>For which the code looks like this:</p> <pre><code class="language-php">if (!defined('MYPLUGIN_THEME_DIR')) define('MYPLUGIN_THEME_DIR', ABSPATH . 'wp-content/themes/' . get_template()); if (!defined('MYPLUGIN_PLUGIN_NAME')) define('MYPLUGIN_PLUGIN_NAME', trim(dirname(plugin_basename(__FILE__)), '/')); if (!defined('MYPLUGIN_PLUGIN_DIR')) define('MYPLUGIN_PLUGIN_DIR', WP_PLUGIN_DIR . '/' . MYPLUGIN_PLUGIN_NAME); if (!defined('MYPLUGIN_PLUGIN_URL')) define('MYPLUGIN_PLUGIN_URL', WP_PLUGIN_URL . '/' . MYPLUGIN_PLUGIN_NAME);</code></pre> <p>Having these global paths defined lets me write the code below in my plugin anywhere I need to, and I know it will resolve correctly for any website that uses the plugin:</p> <pre><code class="language-php">$image = MYPLUGIN_PLUGIN_URL . '/images/my-image.jpg'; $style = MYPLUGIN_PLUGIN_URL . '/css/my-style.css'; $script = MYPLUGIN_PLUGIN_URL . '/js/my-script.js';</code></pre> <h3>Store the Plugin Version for Upgrades</h3> <p>When it comes to WordPress plugins, one of the things you’ll have to deal with sooner or later is upgrades. For instance, let’s say the first version of your plugin required one database table, but the next version requires another table. How do you know if you should run the code that creates the second database table?</p> <p>I suggest storing the plugin version in the WordPress database so that you can read it later to decide certain upgrade actions your plugin should take. To do this, you’ll need to create a couple more global variables and invoke the <code>add_option()</code> function:</p> <pre><code class="language-php">if (!defined('MYPLUGIN_VERSION_KEY')) define('MYPLUGIN_VERSION_KEY', 'myplugin_version'); if (!defined('MYPLUGIN_VERSION_NUM')) define('MYPLUGIN_VERSION_NUM', '1.0.0'); add_option(MYPLUGIN_VERSION_KEY, MYPLUGIN_VERSION_NUM);</code></pre> <p>I certainly could have simply called <code>add_option('myplugin_version', '1.0.0');</code> without the need for the global variables, but like the global path variables, I’ve found these just as handy for using in other parts of a plugin, such as a Dashboard or About page.</p> <p>Also note that <code>update_option()</code> could have been used instead of <code>add_option()</code>. The difference is that <code>add_option()</code> does nothing if the option already exists, whereas <code>update_option()</code> checks to see if the option already exists, and if it doesn’t, it will add the option to the database using <code>add_option()</code>; otherwise, it updates the option with the value provided.</p> <p>Then, when it comes time to check whether or not to perform upgrade actions, your plugin will end up with code that looks similar to this:</p> <pre><code class="language-php">$new_version = '2.0.0'; if (get_option(MYPLUGIN_VERSION_KEY) != $new_version) { // Execute your upgrade logic here // Then update the version value update_option(MYPLUGIN_VERSION_KEY, $new_version); }</code></pre> <h3>Use dbDelta() to Create/Update Database Tables</h3> <p>If your plugin requires its own database tables, you will inevitably need to modify those tables in future versions of your plugin. This can get a bit tricky to manage if you’re not careful, but WordPress helps alleviate this problem by providing the <code>dbDelta()</code> function.</p> <p>A useful feature of the <code>dbDelta()</code> function is that it can be used for both creating and updating tables, but according to the WordPress codex page <a href="http://codex.wordpress.org/Creating_Tables_with_Plugins">“Creating Tables with Plugins”</a><sup class="po" id="note-3"><a href="#3">3</a></sup>, it’s a little picky:</p> <ul> <li>You have to put each field on its own line in your SQL statement.</li> <li>You have to have two spaces between the words PRIMARY KEY and the definition of your primary key.</li> <li>You must use the keyword KEY rather than its synonym INDEX and you must include at least one KEY.</li> </ul> <p>Knowing these rules, we can use the function below to create a table that contains an ID, a name, and an email:</p> <pre><code class="language-php">function myplugin_create_database_table() { global $wpdb; $table = $wpdb->prefix . 'myplugin_table_name'; $sql = "CREATE TABLE " . $table . " ( id INT NOT NULL AUTO_INCREMENT, name VARCHAR(100) NOT NULL DEFAULT '', email VARCHAR(100) NOT NULL DEFAULT '', UNIQUE KEY id (id) );"; require_once(ABSPATH . 'wp-admin/includes/upgrade.php'); dbDelta($sql); }</code></pre> <p><em><strong>Important:</strong> The <code>dbDelta()</code> function is found in <strong>wp-admin/includes/upgrade.php</strong>, but it has to be included manually because it’s not loaded by default.</em></p> <p>So now we have a table, but in the next version we need to expand the size of the name column from 100 to 250. Fortunately <code>dbDelta()</code> makes this straightforward, and using our upgrade logic previously, the next version of the plugin will have code similar to this:</p> <pre><code class="language-php">$new_version = '2.0.0'; if (get_option(MYPLUGIN_VERSION_KEY) != $new_version) { myplugin_update_database_table(); update_option(MYPLUGIN_VERSION_KEY, $new_version); } function myplugin_update_database_table() { global $wpdb; $table = $wpdb->prefix . 'myplugin_table_name'; $sql = "CREATE TABLE " . $table . " ( id INT NOT NULL AUTO_INCREMENT, name VARCHAR(250) NOT NULL DEFAULT '', // Bigger name column email VARCHAR(100) NOT NULL DEFAULT '', UNIQUE KEY id (id) );"; require_once(ABSPATH . 'wp-admin/includes/upgrade.php'); dbDelta($sql); }</code></pre> <p>While there are other ways to create and update database tables for your WordPress plugin, it’s hard to ignore the flexibility of the <code>dbDelta()</code> function.</p> <h3>Know the Difference Between include, include_once, require, and require_once</h3> <p>There will come a time during the development of your plugin where you will want to put code into other files so that maintaining your plugin is a bit easier. For instance, a common practice is to create a functions.php file that contains all of the shared functions that all of the files in your plugin can use.</p> <p>Let’s say your main plugin file is named myplugin.php and you want to include the functions.php file. You can use any of these lines of code to do it:</p> <pre><code class="language-php">include 'functions.php'; include_once 'functions.php'; require 'functions.php'; require_once 'functions.php';</code></pre> <p>But which should you use? It mostly depends on your expected outcome of the file not being there.</p> <ul> <li><strong>include:</strong> Includes and evaluates the specified file, throwing a warning if the file can’t be found.</li> <li><strong>include_once:</strong> Same as include, but if the file has already been included it will not be included again.</li> <li><strong>require:</strong> Includes and evaluates the specified file (same as include), but instead of a warning, throws a fatal error if the file can’t be found.</li> <li><strong>require_once:</strong> Same as require, but if the file has already been included it will not be included again.</li> </ul> <p>My experience has been to always use <code>include_once</code> because a) how I structure and use my files usually requires them to be included once and only once, and b) if a required file can’t be found I don’t expect parts of the plugin to work, but it doesn’t need to break anything else either.</p> <p>Your expectations may vary from mine, but it’s important to know the subtle differences between the four ways of including files.</p> <h3>Use bloginfo(‘wpurl’) Instead of bloginfo(‘url’)</h3> <p>By and large, WordPress is installed in the root folder of a website; it’s standard operating procedure. However, every now and then you’ll come across websites that install WordPress into a separate subdirectory under the root. Seems innocent enough, but the location of WordPress is critically important.</p> <p>To demonstrate, in the “General Settings” section of the WordPress admin panel, you’ll find the “WordPress address (URL)” and “Site address (URL)” settings, and for sites where WordPress is installed into the root directory, they will have the exact same values:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/general-settings-same-url.jpg" alt="" title="general-settings-same-url" width="525" height="84" class="alignnone size-full wp-image-90926" /></p> <p>But for sites where WordPress is installed into a subdirectory under the root (in this case a “wordpress” subdirectory), their values will be different:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/general-settings-different-url.jpg" alt="" title="general-settings-different-url" width="525" height="84" class="alignnone size-full wp-image-90925" /></p> <p>At this stage it’s important to know the following:</p> <ul> <li><strong>bloginfo(‘wpurl’)</strong> equals the “WordPress address (URL)” setting</li> <li><strong>bloginfo(‘url’)</strong> equals the “Site address (URL)” setting</li> </ul> <p>Where this matters is when you need to build URLs to certain resources or pages. For example, if you want to provide a link to the WordPress login screen, you could do this:</p> <pre><code class="language-php">// URL will be http://mydomain.com/wp-login.php <a href="<?php bloginfo('url') ?>/wp-login.php">Login</a></code></pre> <p>But that won’t resolve to the correct URL in the scenario such as the one above where WordPress is installed to the “wordpress” subdirectory. To do this correctly, you must use <code>bloginfo('wpurl')</code> instead:</p> <pre><code class="language-php">// URL will be http://mydomain.com/wordpress/wp-login.php <a href="<?php bloginfo('wpurl') ?>/wp-login.php">Login</a></code></pre> <p>Using <code>bloginfo('wpurl')</code> instead of <code>bloginfo('url')</code> is the safest way to go when building links and URLs inside your plugin because it works in both scenarios: when WordPress is installed in the root of a website and also when it’s installed in a subdirectory. Using <code>bloginfo('url')</code> only gets you the first one.</p> <h3>How and When to Use Actions and Filters</h3> <p>WordPress allows developers to add their own code during the execution of a request by providing various hooks. These hooks come in the form of actions and filters:</p> <ul> <li><strong>Actions</strong>: WordPress invokes actions at certain points during the execution request and when certain events occur.</li> <li><strong>Filters</strong>: WordPress uses filters to modify text before adding it to the database and before displaying it on-screen.</li> </ul> <p>The number of actions and filters is quite large, so we can’t get into them all here, but let’s at least take a look at how they are used.</p> <p>Here’s an example of how to use the <code>admin_print_styles</code> action, which allows you to add your own stylesheets to the WordPress admin pages:</p> <pre><code class="language-php">add_action('admin_print_styles', 'myplugin_admin_print_styles'); function myplugin_admin_print_styles() { $handle = 'myplugin-css'; $src = MYPLUGIN_PLUGIN_URL . '/styles.css'; wp_register_style($handle, $src); wp_enqueue_style($handle); }</code></pre> <p>And here’s how you would use the <code>the_content</code> filter to add a “Follow me on Twitter!” link to the bottom of every post:</p> <pre><code class="language-php">add_filter('the_content', 'myplugin_the_content'); function myplugin_the_content($content) { $output = $content; $output .= '<p>'; $output .= '<a href="http://twitter.com/username">Follow me on Twitter!</a>'; $output .= '</p>'; return $output; }</code></pre> <p>It’s impossible to write a WordPress plugin without actions and filters, and knowing what’s available to use and when to use them can make a big difference. See the WordPress codex page <a href="http://codex.wordpress.org/Plugin_API/Action_Reference">“Plugin API/Action Reference”</a><sup class="po" id="note-4"><a href="#4">4</a></sup> for the complete list of actions and the page <a href="http://codex.wordpress.org/Plugin_API/Filter_Reference">“Plugin API/Filter Reference”</a><sup class="po" id="note-5"><a href="#5">5</a></sup> for the complete list of filters.</p> <p><em><strong>Tip:</strong> Pay close attention to the order in which the actions are listed on its codex page. While not an exact specification, my experimentation and trial-and-error has shown it to be pretty close to the order in which actions are invoked during the WordPress request pipeline.</em></p> <h3>Add Your Own Settings Page or Admin Menu</h3> <p>Many WordPress plugins require users to enter settings or options for the plugin to operate properly, and the way plugin authors accomplish this is by either adding their own settings page to an existing menu or by adding their own new top-level admin menu to WordPress.</p> <h4>How to Add a Settings Page</h4> <p>A common practice for adding your own admin settings page is to use the <code>add_menu()</code> hook to call the <code>add_options_page()</code> function:</p> <pre><code class="language-php">add_action('admin_menu', 'myplugin_admin_menu'); function myplugin_admin_menu() { $page_title = 'My Plugin Settings'; $menu_title = 'My Plugin'; $capability = 'manage_options'; $menu_slug = 'myplugin-settings'; $function = 'myplugin_settings'; add_options_page($page_title, $menu_title, $capability, $menu_slug, $function); } function myplugin_settings() { if (!current_user_can('manage_options')) { wp_die('You do not have sufficient permissions to access this page.'); } // Here is where you could start displaying the HTML needed for the settings // page, or you could include a file that handles the HTML output for you. }</code></pre> <p>By invoking the <code>add_options_page()</code> function, we see that the “My Plugin” option has been added to the built-in <strong>Settings</strong> menu in the WordPress admin panel:</p> <p class="showcase"><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/admin-menu-options-page.jpg" alt="" title="admin-menu-options-page" width="147" height="207" class="alignnone size-full wp-image-91029" /></p> <p>The <code>add_options_page()</code> function is really just a wrapper function on top of the <code>add_submenu_page()</code> function, and there are other wrapper functions that do similar work for the other sections of the WordPress admin panel:</p> <ul> <li>add_dashboard_page()</li> <li>add_posts_page()</li> <li>add_media_page()</li> <li>add_links_page()</li> <li>add_pages_page()</li> <li>add_comments_page()</li> <li>add_theme_page()</li> <li>add_plugins_page()</li> <li>add_users_page()</li> <li>add_management_page()</li> </ul> <h4>How to Add a Custom Admin Menu</h4> <p>Those wrapper functions work great, but what if you wanted to create your own admin menu section for your plugin? For example, what if you wanted to create a “My Plugin” admin section with more than just the Settings page, such as a Help page? This is how you would do that:</p> <pre><code class="language-php">add_action('admin_menu', 'myplugin_menu_pages'); function myplugin_menu_pages() { // Add the top-level admin menu $page_title = 'My Plugin Settings'; $menu_title = 'My Plugin'; $capability = 'manage_options'; $menu_slug = 'myplugin-settings'; $function = 'myplugin_settings'; add_menu_page($page_title, $menu_title, $capability, $menu_slug, $function); // Add submenu page with same slug as parent to ensure no duplicates $sub_menu_title = 'Settings'; add_submenu_page($menu_slug, $page_title, $sub_menu_title, $capability, $menu_slug, $function); // Now add the submenu page for Help $submenu_page_title = 'My Plugin Help'; $submenu_title = 'Help'; $submenu_slug = 'myplugin-help'; $submenu_function = 'myplugin_help'; add_submenu_page($menu_slug, $submenu_page_title, $submenu_title, $capability, $submenu_slug, $submenu_function); } function myplugin_settings() { if (!current_user_can('manage_options')) { wp_die('You do not have sufficient permissions to access this page.'); } // Render the HTML for the Settings page or include a file that does } function myplugin_help() { if (!current_user_can('manage_options')) { wp_die('You do not have sufficient permissions to access this page.'); } // Render the HTML for the Help page or include a file that does }</code></pre> <p>Notice that this code doesn’t use any of the wrapper functions. Instead, it calls <code>add_menu_page()</code> (for the parent menu page) and <code>add_submenu_page()</code> (for the child pages) to create a separate “My Plugin” admin menu that contains the Settings and Help pages:</p> <p class="showcase"><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/admin-menu-custom.jpg" alt="" title="admin-menu-custom" width="147" height="233" class="alignnone size-full wp-image-91091" /></p> <p>One advantage of adding your own custom menu is that <strong>it’s easier for users to find the settings for your plugin</strong> because they aren’t buried within one of the built-in WordPress admin menus. Keeping that in mind, if your plugin is simple enough to only require a single admin page, then using one of the wrapper functions might make the most sense. But if you need more than that, creating a custom admin menu is the way to go.</p> <h3>Provide a Shortcut to Your Settings Page with Plugin Action Links</h3> <p>In much the same way that adding your own custom admin menu helps give the sense of a well-rounded plugin, plugin action links work in the same fashion. So what are plugin action links? It’s best to start with a picture:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/plugin-action-links-none.jpg" alt="" title="plugin-action-links-none" width="525" height="118" class="alignnone size-full wp-image-91097" /></p> <p>See the “Deactivate” and “Edit” links underneath the name of the plugin? Those are plugin action links, and WordPress provides a filter named <code>plugin_action_links</code> for you to add more. Basically, <strong>plugin action links are a great way to add a quick shortcut to your most commonly used admin menu page</strong>.</p> <p>Keeping with our Settings admin page, here’s how we would add a plugin action link for it:</p> <pre><code class="language-php">add_filter('plugin_action_links', 'myplugin_plugin_action_links', 10, 2); function myplugin_plugin_action_links($links, $file) { static $this_plugin; if (!$this_plugin) { $this_plugin = plugin_basename(__FILE__); } if ($file == $this_plugin) { // The "page" query string value must be equal to the slug // of the Settings admin page we defined earlier, which in // this case equals "myplugin-settings". $settings_link = '<a href="' . get_bloginfo('wpurl') . '/wp-admin/admin.php?page=myplugin-settings">Settings</a>'; array_unshift($links, $settings_link); } return $links; }</code></pre> <p>With this code in place, now when you view your plugins list you’ll see this:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/plugin-action-links-settings.jpg" alt="" title="plugin-action-links-settings" width="550" height="118" class="alignnone size-full wp-image-91112" /></p> <p>Here we provided a plugin action link to the Settings admin page, which is the same thing as clicking on Settings from our custom admin menu. The benefit of the plugin action link is that <strong>users see it immediately after they activate the plugin</strong>, thus adding to the overall experience.</p> <h3>Additional Resources</h3> <p>I’ve covered a lot in this article, but there’s plenty more out there to keep you busy awhile. The most comprehensive documentation for WordPress plugin development can be found on the <a href="http://codex.wordpress.org/">WordPress Codex</a><sup class="po" id="note-6"><a href="#6">6</a></sup>, a huge collection of pages documenting everything that is WordPress. Below are some of the more pertinent links from the codex you’ll need:</p> <ul> <li><a href="http://codex.wordpress.org/Writing_a_Plugin">Writing a Plugin</a><sup class="po" id="note-7"><a href="#7">7</a></sup> – If you’re brand new to WordPress plugin development, start here.</li> <li><a href="http://codex.wordpress.org/Plugin_API/Action_Reference">Plugin API – Action Reference</a><sup class="po" id="note-8"><a href="#8">8</a></sup></li> <li><a href="http://codex.wordpress.org/Plugin_API/Filter_Reference">Plugin API – Filter Reference</a><sup class="po" id="note-9"><a href="#9">9</a></sup></li> <li><a href="http://codex.wordpress.org/Pluggable_Functions">Pluggable Functions</a><sup class="po" id="note-10"><a href="#10">10</a></sup></li> <li><a href="http://codex.wordpress.org/Data_Validation">Data Validation</a><sup class="po" id="note-11"><a href="#11">11</a></sup></li> </ul> <p>I also suggest reading Joost de Valk’s article “<a href="http://www.smashingmagazine.com/2010/07/30/lessons-learned-from-maintaining-a-wordpress-plug-in/">Lessons Learned From Maintaining a WordPress Plug-In</a><sup class="po" id="note-12"><a href="#12">12</a></sup>“, which provides more good tips on WordPress plugin development.</p> <p><em>(vf) (ik)</em></p> <h4 class="po">Footnotes</h4><ol class="po"><li id="#1"><a href="#note-1">1 http://www.smashingmagazine.com/wp-content/uploads/2011/03/wordpress_plugin.jpg</a></li><li id="#2"><a href="#note-2">2 http://ditio.net/2011/01/29/wordpress-debug-bar-plugin-blackbox/</a></li><li id="#3"><a href="#note-3">3 http://codex.wordpress.org/Creating_Tables_with_Plugins</a></li><li id="#4"><a href="#note-4">4 http://codex.wordpress.org/Plugin_API/Action_Reference</a></li><li id="#5"><a href="#note-5">5 http://codex.wordpress.org/Plugin_API/Filter_Reference</a></li><li id="#6"><a href="#note-6">6 http://codex.wordpress.org/</a></li><li id="#7"><a href="#note-7">7 http://codex.wordpress.org/Writing_a_Plugin</a></li><li id="#8"><a href="#note-8">8 http://codex.wordpress.org/Plugin_API/Action_Reference</a></li><li id="#9"><a href="#note-9">9 http://codex.wordpress.org/Plugin_API/Filter_Reference</a></li><li id="#10"><a href="#note-10">10 http://codex.wordpress.org/Pluggable_Functions</a></li><li id="#11"><a href="#note-11">11 http://codex.wordpress.org/Data_Validation</a></li><li id="#12"><a href="#note-12">12 http://www.smashingmagazine.com/2010/07/30/lessons-learned-from-maintaining-a-wordpress-plug-in/</a></li></ol> <div id="textadtarget"></div> <div class="lt"> <a href="http://www.smashingmagazine.com/tag/essentials/">Essentials</a><a href="http://www.smashingmagazine.com/tag/php/">PHP</a><a href="http://www.smashingmagazine.com/tag/plugins/">Plugins</a> </div> <p><a href="#top" class="top single" title="Jump to the top of the page">↑ Back to top</a><a class="sot single" href="https://twitter.com/intent/tweet?original_referer=http%3A%2F%2Fwww.smashingmagazine.com%2F2011%2F03%2F08%2Ften-things-every-wordpress-plugin-developer-should-know%2F&source=tweetbutton&text=Ten%20Things%20Every%20WordPress%20Plugin%20Developer%20Should%20Know&url=http%3A%2F%2Fwww.smashingmagazine.com%2F2011%2F03%2F08%2Ften-things-every-wordpress-plugin-developer-should-know%2F&via=smashingmag" title="Share on Twitter!">Share on Twitter</a></p> </article> <div class="bio clearfix"> <div class="grv"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/5d1c4c4bffa1f1133b17dc54f7bf40d1?s=78&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D78&r=G" class="avatar avatar-78 photo" height="78" width="78" /> </div> <div class="about"> <a rel="author" class="poa" href="http://www.smashingmagazine.com/author/dave-donaldson/?rel=author" title="Posts by Dave Donaldson">Dave Donaldson</a> <p>Dave lives in Columbus, OH and is one of the founders of <a href="http://maxfoundry.com/">Max Foundry</a>, a company that makes WordPress plugins for <a href="http://maxfoundry.com/plugins/maxlanding/">landing pages</a>, <a href="http://maxfoundry.com/plugins/maxsqueeze/">squeeze pages</a>, <a href="http://maxfoundry.com/plugins/maxsales/">sales pages</a>, and <a href="http://maxfoundry.com/plugins/maxab/">A/B testing</a>. You can <a href="http://twitter.com/arcware">follow Dave on Twitter</a> and <a href="http://arcware.net">on his blog</a>, where he writes about living the bootstrapped startup life.</p> </div> </div> <div class="ras clearfix"> <h2>Related Articles</h2> <div class="ra clearfix"> <a class="pp" href="http://www.smashingmagazine.com/2014/09/25/the-ultimate-guide-to-choosing-a-wordpress-host/"><img width="84" height="84" src="http://www.smashingmagazine.com/wp-content/uploads/2014/09/illu-wp-14.jpg" class="attachment-related-thumb wp-post-image" alt="illu-wp-14" /></a> <h3><a href="http://www.smashingmagazine.com/2014/09/25/the-ultimate-guide-to-choosing-a-wordpress-host/">The Ultimate Guide To Choosing A WordPress Host</a></h3> </div> <div class="ra clearfix"> <a class="pp" href="http://www.smashingmagazine.com/2014/08/27/customizing-wordpress-archives-categories-terms-taxonomies/"><img width="84" height="84" src="http://www.smashingmagazine.com/wp-content/uploads/2014/08/wordpress-blue-illu.jpg" class="attachment-related-thumb wp-post-image" alt="wordpress-blue-illu" /></a> <h3><a href="http://www.smashingmagazine.com/2014/08/27/customizing-wordpress-archives-categories-terms-taxonomies/">Customizing WordPress Archives For Categories, Tags And Other Taxonomies</a></h3> </div> <div class="ra clearfix"> <a class="pp" href="http://www.smashingmagazine.com/2014/08/27/a-tour-of-wordpress-4-0/"><img width="84" height="84" src="http://www.smashingmagazine.com/wp-content/uploads/2014/08/wp-logo-4-0-illu.png" class="attachment-related-thumb wp-post-image" alt="wp-logo-4-0-illu" /></a> <h3><a href="http://www.smashingmagazine.com/2014/08/27/a-tour-of-wordpress-4-0/">A Quick Tour Of WordPress 4.0</a></h3> </div> </div> <div class="adv"> <span class="declare">Advertising</span> <div id="commentspnsrtarget"></div> </div> <ul id="comments" class="sub-tabs clearfix"> <li><a href="#show-comments" class="active">94 Comments</a></li> </ul> <div id="discussion" class="subtab-pages"> <div id="show-comments"> <ol id="comments-overview" class="cl"> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">1</span> <div class="c" id="comment-169926"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/b473ef78b653e5aa33656f54f7f090bc?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Eddie Gear</h3> <span class="dati"> <a title="Commentlink #1" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169926"> March 8, 2011 5:48 am </a> </span> </div> </div> <div class="ctx"> <p>Great insights Dave. I loved the way you have pointed out the things that any developer that needs to keep track of. Thanks for sharing.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169926" class="inpsyde_extended_comments_rate positive">3</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169926" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">2</span> <div class="c" id="comment-169927"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/be19e396141c6328782a2852844d58f1?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Frederick Luna</h3> <span class="dati"> <a title="Commentlink #2" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169927"> March 8, 2011 6:07 am </a> </span> </div> </div> <div class="ctx"> <p>Intersting stuff about adding a custom menu and a settings page :D great post Dave.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169927" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169927" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">3</span> <div class="c" id="comment-169928"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/53c424111bd9e2571763aed8c55c3745?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Matt Rittman</h3> <span class="dati"> <a title="Commentlink #3" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169928"> March 8, 2011 6:26 am </a> </span> </div> </div> <div class="ctx"> <p>Great article Dave! This will really help out my future endeavors with WordPress plugin development. Thanks for sharing!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169928" class="inpsyde_extended_comments_rate positive">3</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169928" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">4</span> <div class="c" id="comment-169929"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/0b95637f2168ded35b2d9812f3fbaf9f?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>David</h3> <span class="dati"> <a title="Commentlink #4" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169929"> March 8, 2011 6:27 am </a> </span> </div> </div> <div class="ctx"> <p>This is brilliant, thanks for the write up. Bookmarked! I see that you recommend the Blackbox debug plugin. Having just started creating my own plugins, why this and not the DebugBar plugin (<a href="http://wordpress.org/extend/plugins/debug-bar/" rel="nofollow">http://wordpress.org/extend/plugins/debug-bar/</a>)? What’s the primary difference?</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169929" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169929" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">5</span> <div class="c" id="comment-169959"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #5" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169959"> March 8, 2011 3:31 pm </a> </span> </div> </div> <div class="ctx"> <p>@David – I didn’t include the DebugBar plugin because it requires WordPress 3.1, which was only in Release Candidate mode at the time of writing. Both plugins provide similar debug info, so I suggest trying both and going with the one you like best.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169959" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169959" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">6</span> <div class="c" id="comment-169930"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/fd58a5b6b89266f6095d15566f290ecd?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Chris</h3> <span class="dati"> <a title="Commentlink #6" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169930"> March 8, 2011 6:35 am </a> </span> </div> </div> <div class="ctx"> <p>Great advices! I wish it would have been released much earlier – could have saved me a lot of time and trouble :)</p> <p>Regarding bloginfo(wpurl): The codex says to use site_url() instead, for it also supports https, eg. if is_ssl() is true.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169930" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169930" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">7</span> <div class="c" id="comment-169935"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #7" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169935"> March 8, 2011 7:09 am </a> </span> </div> </div> <div class="ctx"> <p>@Chris – I can’t find the codex article that says to use site_url() instead of bloginfo(‘wpurl’), but yes, I suppose you could do that. There seems to be some confusion about whether or not site_url() includes the install directory of WordPress (if installed in a subdirectory), but looking at the core WordPress code it looks like it does.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169935" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169935" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-3 clearfix"> <span class="cn">8</span> <div class="c" id="comment-169995"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/46e57cfd694f0c9c91737a14e4913af8?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Christofer</h3> <span class="dati"> <a title="Commentlink #8" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169995"> March 15, 2011 12:03 am </a> </span> </div> </div> <div class="ctx"> <p>@Dave — Maybe, this is the page Chris referred to:<br /> <a href="http://codex.wordpress.org/Function_Reference/get_bloginfo" rel="nofollow">http://codex.wordpress.org/Function_Reference/get_bloginfo</a></p> <p>“‘wpurl’ / ‘siteurl’ – Returns the ‘WordPress address (URI)’ [..] Consider using site_url() instead.”</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169995" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169995" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">9</span> <div class="c" id="comment-169931"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/c41cbd0f894f1c1d570ab99a568e41d2?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Pete</h3> <span class="dati"> <a title="Commentlink #9" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169931"> March 8, 2011 6:38 am </a> </span> </div> </div> <div class="ctx"> <p>Nice article, thanks for sharing. I especially like the notes on debugging & function prefixes. Hopefully this will change the coding habits of some Developers when writing a WP plugin.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169931" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169931" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">10</span> <div class="c" id="comment-169932"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/1486cf246811f6cdaa9894d7f9ede233?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Donna Vitan</h3> <span class="dati"> <a title="Commentlink #10" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169932"> March 8, 2011 6:48 am </a> </span> </div> </div> <div class="ctx"> <p>Another awesome and well described tutorial Dave! I especially love how concise the part about creating admin settings panel and menu.</p> <p>Cheers,</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169932" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169932" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">11</span> <div class="c" id="comment-169933"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/9c97d846b29e7a50e82af8ab40225023?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Thomas Bachmann</h3> <span class="dati"> <a title="Commentlink #11" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169933"> March 8, 2011 6:55 am </a> </span> </div> </div> <div class="ctx"> <p>thanks!<br /> … if you are a trained professional developer and familiar with PHP only half of it should be new (wordpress specifics)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169933" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169933" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">12</span> <div class="c" id="comment-169934"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/e06e23e82d25e39ae6e04e77a3aad1a2?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Hung Bui</h3> <span class="dati"> <a title="Commentlink #12" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169934"> March 8, 2011 7:04 am </a> </span> </div> </div> <div class="ctx"> <p>Great stuff! Very useful thought.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169934" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169934" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">13</span> <div class="c" id="comment-169936"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/ae17fd59d1f4261b04860e1a8997892c?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>kwasseem</h3> <span class="dati"> <a title="Commentlink #13" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169936"> March 8, 2011 7:30 am </a> </span> </div> </div> <div class="ctx"> <p>Precise and short; good, clear checkpoints!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169936" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169936" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">14</span> <div class="c" id="comment-169937"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/8f80a2914655c2dddf59bddd8af8e62d?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Samundra Shrestha</h3> <span class="dati"> <a title="Commentlink #14" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169937"> March 8, 2011 7:33 am </a> </span> </div> </div> <div class="ctx"> <p>Really loved the way you have mentioned the tricks for wordpress developer. I liked the way you described the usuage of require, require_once, include and include_once. All most of us use them but never seem to care since we all use include_once most of the time :).</p> <p>I have already been using some of the tricks you have mentioned.</p> <p>Great Article.</p> <p>best regards,<br /> Samundra Shrestha<br /> Realtime Solutions, Nepal</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169937" class="inpsyde_extended_comments_rate negative">-3</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169937" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">15</span> <div class="c" id="comment-169938"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7ba0e1a12efe734f77b4fba4d97dd8ef?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Pieter Carette</h3> <span class="dati"> <a title="Commentlink #15" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169938"> March 8, 2011 7:35 am </a> </span> </div> </div> <div class="ctx"> <p>Great post. It makes me want to write a plugin! :)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169938" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169938" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">16</span> <div class="c" id="comment-169939"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/21fc7f3431b9b07560c2bdbd6b0389e2?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Joseph Carrington</h3> <span class="dati"> <a title="Commentlink #16" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169939"> March 8, 2011 7:37 am </a> </span> </div> </div> <div class="ctx"> <p>Good stuff. I’d point out that using a class as a fill-in for a namespace is not exactly the intention of OOP however.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169939" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169939" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">17</span> <div class="c" id="comment-169940"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #17" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169940"> March 8, 2011 7:53 am </a> </span> </div> </div> <div class="ctx"> <p>@Joseph Carrington – You’re right, using classes as a namespace fill-in is not the intention of OOP, but it is a common practice for avoiding function name collisions in PHP and WordPress.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169940" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169940" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">18</span> <div class="c" id="comment-169941"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/41d0698209bfdc9cb69b31e8fccd1459?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Josh Hartman</h3> <span class="dati"> <a title="Commentlink #18" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169941"> March 8, 2011 7:54 am </a> </span> </div> </div> <div class="ctx"> <p>Great info! I wasn’t aware of the bloginfo(‘wpurl’) vs. bloginfo(‘url’) difference.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169941" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169941" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">19</span> <div class="c" id="comment-169942"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/aee526984fe85082c6a902d028806522?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>David</h3> <span class="dati"> <a title="Commentlink #19" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169942"> March 8, 2011 7:54 am </a> </span> </div> </div> <div class="ctx"> <p>Really enjoyed this. It was encouraging that I found I was already doing most of these things. Some good tips, though, and I’ve updated my plugin with some of these suggestions.</p> <p>I tried blackbar, but got tons of deprecated errors, which kind of made me laugh…</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169942" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169942" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-2 clearfix"> <span class="cn">20</span> <div class="c" id="comment-169943"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #20" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169943"> March 8, 2011 7:57 am </a> </span> </div> </div> <div class="ctx"> <p>@David – Hehe, yea, the irony of that was not lost on me :-)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169943" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169943" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">21</span> <div class="c" id="comment-169944"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/907728625b3b0f36cfc56582a736d10a?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Vivek Parmar</h3> <span class="dati"> <a title="Commentlink #21" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169944"> March 8, 2011 8:12 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks for so much, getitng started with plugin development and wordpress theme development, and this article help me a lot in knowing many things that i do not know</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169944" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169944" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">22</span> <div class="c" id="comment-169945"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/03e89dba5cb218b78f43ac4ca2a6aec7?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>scasmflop</h3> <span class="dati"> <a title="Commentlink #22" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169945"> March 8, 2011 8:53 am </a> </span> </div> </div> <div class="ctx"> <p>Great article, very informative without straying too far down rabbit trails. Thanks.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169945" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169945" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">23</span> <div class="c" id="comment-169946"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/429e15ea1f962e579cd1d59b0f0e6d37?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Raherian</h3> <span class="dati"> <a title="Commentlink #23" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169946"> March 8, 2011 9:25 am </a> </span> </div> </div> <div class="ctx"> <p>Hi,<br /> Using blackbox-debug-bar with wp_debug on true display a bunch of notices, not very good for developping :/</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169946" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169946" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-2 clearfix"> <span class="cn">24</span> <div class="c" id="comment-169947"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #24" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169947"> March 8, 2011 9:28 am </a> </span> </div> </div> <div class="ctx"> <p>@Raherian – But that’s kind of the point of enabling debugging in the first place, to see all of the notices you wouldn’t have otherwise known were there.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169947" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169947" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-3 clearfix"> <span class="cn">25</span> <div class="c" id="comment-169955"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/429e15ea1f962e579cd1d59b0f0e6d37?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Raherian</h3> <span class="dati"> <a title="Commentlink #25" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169955"> March 8, 2011 12:14 pm </a> </span> </div> </div> <div class="ctx"> <p>Yes but this plugin is usefull for developping, and i develop with wp_debug true, so having a bunch of notices while developping isn’t good.<br /> It were a good idea to make a plugin available on repository only if he doesn’t have any notices, like themes ^^</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169955" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169955" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">26</span> <div class="c" id="comment-169948"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/ec905543ea918ee9546033a8ec2bfca9?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>aurel</h3> <span class="dati"> <a title="Commentlink #26" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169948"> March 8, 2011 9:32 am </a> </span> </div> </div> <div class="ctx"> <p>So far I developed only two themes, both of them using different methods (or no method apart from “hope it will work”)</p> <p>it seems that these 10 plugins will make the process much easier to manage and hopefully to be able to understand by things work – that way things could stick in the head when developing the next theme</p> <p>thanks</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169948" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169948" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">27</span> <div class="c" id="comment-169949"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/fc6a528fe2b60482971b1642577ae43d?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Alan Stevens</h3> <span class="dati"> <a title="Commentlink #27" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169949"> March 8, 2011 9:32 am </a> </span> </div> </div> <div class="ctx"> <p>Nice article, Dave. I don’t know if there is a codex article on using site_url() but this article has some good tips on guarding for ssl: <a href="http://blogs.sitepoint.com/2011/02/22/crimes-against-wordpress/" rel="nofollow">http://blogs.sitepoint.com/2011/02/22/crimes-against-wordpress/</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169949" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169949" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">28</span> <div class="c" id="comment-169950"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/1f7d16fe6425d85f05aa229464b49843?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Thai Bui</h3> <span class="dati"> <a title="Commentlink #28" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169950"> March 8, 2011 9:35 am </a> </span> </div> </div> <div class="ctx"> <p>Great article. One of my biggest hurdles is debugging my plugins properly and these tips are outstanding. I usually use firephp to see what’s going on with the variables being passed back and fourth. Such an invaluable tool.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169950" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169950" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">29</span> <div class="c" id="comment-169951"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/0f0319b397cd2a0443f73a94ab6934cf?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Conrad Muan</h3> <span class="dati"> <a title="Commentlink #29" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169951"> March 8, 2011 10:16 am </a> </span> </div> </div> <div class="ctx"> <p>Great post. I’ll have to try blackbar in my future projects.</p> <p>I was also _just_ looking for a tutorial on adding menu items when I found this gem.</p> <p>Thanks again,<br /> Conrad</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169951" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169951" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">30</span> <div class="c" id="comment-169952"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/aac7e0386facd070f6d4b817c257a958?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Zé</h3> <span class="dati"> <a title="Commentlink #30" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169952"> March 8, 2011 10:55 am </a> </span> </div> </div> <div class="ctx"> <p>Great article, but I am a little sad that i18n wasn’t contemplated from the beginning for all those strings, i.e.</p> <p><code>$page_title = __('My Plugin Settings', 'myplugin_textdomain');</code><br /> instead of<br /> <code>$page_title = 'My Plugin Settings';</code></p> <p>It’s great for all other languages to have plugins that are translatable from the get go.<br /> <a href="http://codex.wordpress.org/I18n_for_WordPress_Developers" rel="nofollow">http://codex.wordpress.org/I18n_for_WordPress_Developers</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169952" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169952" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">31</span> <div class="c" id="comment-169957"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #31" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169957"> March 8, 2011 2:55 pm </a> </span> </div> </div> <div class="ctx"> <p>@Ze – I mentioned on another comment that I thought about including internationalization but decided against it for this article. The topic is probably big enough for another article on its own, so maybe I’ll write that one next.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169957" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169957" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">32</span> <div class="c" id="comment-169953"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/95c934fa2c3362794bf62ff8c59ada08?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Drew</h3> <span class="dati"> <a title="Commentlink #32" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169953"> March 8, 2011 11:48 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks for the lead on Blackbox!. I installed it mid-read on your post and played with it for 30 minutes on three of my sites. Then I remember I was reading your post so I came back to finish. Great roundup!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169953" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169953" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">33</span> <div class="c" id="comment-169954"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/1a659e051ae2d889b0e4421408b6ff34?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Tomáš Kapler</h3> <span class="dati"> <a title="Commentlink #33" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169954"> March 8, 2011 12:12 pm </a> </span> </div> </div> <div class="ctx"> <p>one very common problem from US writers missing – forgotting internationalization so __(), _x(), _e() functions etc.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169954" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169954" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-2 clearfix"> <span class="cn">34</span> <div class="c" id="comment-169956"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #34" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169956"> March 8, 2011 12:29 pm </a> </span> </div> </div> <div class="ctx"> <p>@Tomas – I thought about including a section on internationalization, but decided against it for this article. Maybe I’ll write another article just for that.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169956" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169956" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">35</span> <div class="c" id="comment-169958"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/815d913154a591f2c2b4718ef6003d98?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Brett Lewis</h3> <span class="dati"> <a title="Commentlink #35" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169958"> March 8, 2011 3:23 pm </a> </span> </div> </div> <div class="ctx"> <p>This is great :)</p> <p>Thank you so much.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169958" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169958" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">36</span> <div class="c" id="comment-169960"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/d0517bf908028685b3b25b815ef75068?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Phuoc Huynh</h3> <span class="dati"> <a title="Commentlink #36" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169960"> March 8, 2011 6:24 pm </a> </span> </div> </div> <div class="ctx"> <p>Thanks for this great. This is awesome !</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169960" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169960" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">37</span> <div class="c" id="comment-169961"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/909cdcfc310e3cdab83586232d6e81f8?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Patent Litigation</h3> <span class="dati"> <a title="Commentlink #37" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169961"> March 8, 2011 10:03 pm </a> </span> </div> </div> <div class="ctx"> <p>Here is a similar story</p> <p>Until recently, migrating all your blogs to a single multisite blog was a massive task because of the need to resolve conflicting IDs across different tables. Fortunately, newer WordPress versions have built-in functions to make life a bit easier for all of us.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169961" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169961" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">38</span> <div class="c" id="comment-169962"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/30b5f53666c7c520e8142a372f8a54f6?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Steve mg</h3> <span class="dati"> <a title="Commentlink #38" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169962"> March 8, 2011 11:02 pm </a> </span> </div> </div> <div class="ctx"> <p>As a customer of WordPress plugins, my biggest gripe is the lack of screenshots displaying what the plugin does. Is it really that hard to grab screens? Great you’ve made this fantastic plugin, and also great that you’ve put it up for free, just telling me what it does, isn’t going to completely sell me on it.<br /> Screenshots, do it.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169962" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169962" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">39</span> <div class="c" id="comment-169963"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/6666ae2b2012ee49fe01c5e18ebfe2d0?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Mick</h3> <span class="dati"> <a title="Commentlink #39" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169963"> March 8, 2011 11:42 pm </a> </span> </div> </div> <div class="ctx"> <p>I wish every single plugin developer followed these simple rules!<br /> It would make life a little bit easier</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169963" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169963" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">40</span> <div class="c" id="comment-169964"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/115ee6ccc6f3375410990a387bf5c0bb?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Justin</h3> <span class="dati"> <a title="Commentlink #40" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169964"> March 9, 2011 12:43 am </a> </span> </div> </div> <div class="ctx"> <p>This is a great article. Thanks for consolidating all of this information instead of making me search everywhere for it!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169964" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169964" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">41</span> <div class="c" id="comment-169965"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/61ad912b724a2554976edd74ee6e0266?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Jerry</h3> <span class="dati"> <a title="Commentlink #41" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169965"> March 9, 2011 12:45 am </a> </span> </div> </div> <div class="ctx"> <p>Dave, Awesome post. Pretty helpful for green-hands like me for wordpress.<br /> Usually we use netbeans and X-debug for debugging. This time we could try blackbox for help :)</p> <p>One question: How do you do unit test for new built WP plugin? Use PHPUnit or something else? I am quite new to the test procedure of PHP, any help will be much appreciated.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169965" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169965" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">42</span> <div class="c" id="comment-169966"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/8327520245e97889fca3b0270d69acc8?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>jeFFF</h3> <span class="dati"> <a title="Commentlink #42" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169966"> March 9, 2011 12:59 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks a lot for this great article Dave !</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169966" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169966" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">43</span> <div class="c" id="comment-169967"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/8291ab5d74a9f6d7b8a98ed62ad1709e?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Ruslan</h3> <span class="dati"> <a title="Commentlink #43" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169967"> March 9, 2011 1:29 am </a> </span> </div> </div> <div class="ctx"> <p>One thing that you have understand about include vs include_once, require vs require_once is performance penalty.</p> <p>If you develop your code, and you are 100% for sure, that after you included your file in following code it wont be included again, never use *_once functions. They are more resource eating that simple include or require.</p> <p>Read this article to understand difference in C level:<br /> <a href="http://www.techyouruniverse.com/software/php-performance-tip-require-versus-require_once" rel="nofollow">http://www.techyouruniverse.com/software/php-performance-tip-require-versus-require_once</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169967" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169967" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">44</span> <div class="c" id="comment-169968"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/26c5bc5b88075a54b55ae54e98be2c09?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Fernando Agüero</h3> <span class="dati"> <a title="Commentlink #44" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169968"> March 9, 2011 1:42 am </a> </span> </div> </div> <div class="ctx"> <p>One of the best post written in Smashing Magazine. Now I have no doubts.</p> <p>Thank you!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169968" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169968" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">45</span> <div class="c" id="comment-169969"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/00abc2999b2a32f9072fc8b9ae2ccfe9?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Baltech</h3> <span class="dati"> <a title="Commentlink #45" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169969"> March 9, 2011 2:13 am </a> </span> </div> </div> <div class="ctx"> <p>Great you’ve made this fantastic plugin, and also great that you’ve put it up for free.It seems that these 10 plugins will make the process much easier to manage and hopefully to be able to understand by things. Thanks for give us this information.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169969" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169969" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">46</span> <div class="c" id="comment-169970"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/00abc2999b2a32f9072fc8b9ae2ccfe9?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Baltech</h3> <span class="dati"> <a title="Commentlink #46" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169970"> March 9, 2011 2:14 am </a> </span> </div> </div> <div class="ctx"> <p>Great you’ve made this fantastic plugin, and also great that you’ve put it up for free.It seems that these 10 plugins will make the process much easier to manage and hopefully to be able to understand by things. Thanks for this useful knowledge..</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169970" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169970" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">47</span> <div class="c" id="comment-169971"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/48c28e5f2f6f1b32dd7beb2d9bb63d17?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Thorsten</h3> <span class="dati"> <a title="Commentlink #47" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169971"> March 9, 2011 2:36 am </a> </span> </div> </div> <div class="ctx"> <p>A very important topic that is missing here is Data Validation.<br /> <a href="http://codex.wordpress.org/Data_Validation" rel="nofollow">http://codex.wordpress.org/Data_Validation</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169971" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169971" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">48</span> <div class="c" id="comment-169972"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/b8cefc2f7b65fd5e4204711ee5fc3d42?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Max</h3> <span class="dati"> <a title="Commentlink #48" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169972"> March 9, 2011 3:05 am </a> </span> </div> </div> <div class="ctx"> <p>One bad thing was described above.<br /> When webmaster changes <em>wp-content</em> directory name, following code will break the site:<br /> <code>define('MYPLUGIN_THEME_DIR', ABSPATH . 'wp-content/themes/' . get_template());</code><br /> You should use following code instead wrong one:<br /> <code>define('MYPLUGIN_THEME_DIR', WP_CONTENT_DIR . 'themes/' . get_template());</code></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169972" class="inpsyde_extended_comments_rate positive">2</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169972" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">49</span> <div class="c" id="comment-169976"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #49" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169976"> March 9, 2011 6:10 am </a> </span> </div> </div> <div class="ctx"> <p>@Max – Good point, thanks for catching that. Using WP_CONTENT_DIR instead of a hardcoded ‘wp-content’ string would be better.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169976" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169976" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt depth-2 clearfix"> <span class="cn">50</span> <div class="c" id="comment-169998"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/41a7bd5fd7e182e3705c51338285f2a8?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>YellowShark</h3> <span class="dati"> <a title="Commentlink #50" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169998"> March 15, 2011 9:53 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks for pointing this out, I 100% concur – every WP install I do, I move the wp-content to site root, so i wind up with a nice structure like:<br /> /themes<br /> /plugins<br /> /wordpress<br /> /index.php</p> <p>Developers should definitely utilize WP_PLUGIN_DIR and WP_CONTENT_DIR. Google either of those terms for more info on how to leverage them.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169998" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169998" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">51</span> <div class="c" id="comment-169973"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/f439b5e33c6a8bf37337611cb6a9b283?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>STPo</h3> <span class="dati"> <a title="Commentlink #51" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169973"> March 9, 2011 4:17 am </a> </span> </div> </div> <div class="ctx"> <p>And please: do NOT fill the front-end HTML with plugin-specific CSS/jQuery/meta crap without a way to properly erase them if it is not required. I code my own front-end markup and i’m tired to see jQuery/Prototype/Mootools included everytime I use a plugin…</p> <p>PLEASE!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169973" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169973" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">52</span> <div class="c" id="comment-169974"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/8a01f1cc43100cc77bf7fa249f3486db?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>catalin cimpanu</h3> <span class="dati"> <a title="Commentlink #52" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169974"> March 9, 2011 4:49 am </a> </span> </div> </div> <div class="ctx"> <p>Hell of a job on this article.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169974" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169974" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">53</span> <div class="c" id="comment-169975"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/771eb1edb297f17b15e0efde616a840b?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>wparena</h3> <span class="dati"> <a title="Commentlink #53" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169975"> March 9, 2011 5:36 am </a> </span> </div> </div> <div class="ctx"> <p>Although my current WordPress blogs have some of the SeO plugins installed I have found a good tips on your list that I must to follow</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169975" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169975" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">54</span> <div class="c" id="comment-169977"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/a89d26529cebfe446596439bfe4cc74a?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>djavupixel</h3> <span class="dati"> <a title="Commentlink #54" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169977"> March 9, 2011 10:56 am </a> </span> </div> </div> <div class="ctx"> <p>Good WordPress summary to develop a WordPress plugin.<br /> Great work and good explanations!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169977" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169977" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">55</span> <div class="c" id="comment-169978"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/628dfd9e3e905064c09ae089f60b2595?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Douglas Bonneville</h3> <span class="dati"> <a title="Commentlink #55" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169978"> March 9, 2011 11:47 am </a> </span> </div> </div> <div class="ctx"> <p>Dave: Great article – I’m going to give making a plugin a shot pretty soon and I’ll start here. I’ve edited a few, but this outline really lowers the threshold to new development. This is one of the best WordPress articles I’ve seen in a while, and certainly on my list of top articles at Smashing!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169978" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169978" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">56</span> <div class="c" id="comment-169979"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/5dfcd8fbb95d1a7cf5ef40eab3ba0611?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>darell</h3> <span class="dati"> <a title="Commentlink #56" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169979"> March 9, 2011 4:36 pm </a> </span> </div> </div> <div class="ctx"> <p>Thanks for your post, it’s very helpful for my daily work and thoughts.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169979" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169979" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">57</span> <div class="c" id="comment-169980"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/a91236f90b1063e60ad30e7c5f9e30bd?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Jurdefur</h3> <span class="dati"> <a title="Commentlink #57" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169980"> March 10, 2011 1:38 am </a> </span> </div> </div> <div class="ctx"> <p>Seriously why is everybody still using wordpress its the biggest crap of code i ever seen, its like IE6 under the browsers…</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169980" class="inpsyde_extended_comments_rate negative">-1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169980" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">58</span> <div class="c" id="comment-169981"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/922a5911c9e2bba510333139d9f08122?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Christian K. Nordtømme</h3> <span class="dati"> <a title="Commentlink #58" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169981"> March 10, 2011 2:29 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks for this. I’m just now learning how to develop my own plugins, and have bookmarked this post.</p> <p>I also wish more plugin developers made the plugin’s documentation and help easier accessible, though.</p> <p>I don’t think digging up readme files from the plugin folder, rummaging through every page on the author’s website or trying to decipher the code in search of basic answers should be neccessary. Instead, a “Quick Start” action link (either to 100% self-explanatory settings or to a readme file) should be standard.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169981" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169981" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">59</span> <div class="c" id="comment-169982"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/2901240fe75416f14f03fbdd82c00f87?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>jakub</h3> <span class="dati"> <a title="Commentlink #59" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169982"> March 10, 2011 2:42 am </a> </span> </div> </div> <div class="ctx"> <p>This is superuseful article! In-depth yet still accessible for occassional developers. Much better than “25 nice inspirational designs in pink” or “100 beautiful photos of furry pets” type stuff…</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169982" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169982" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">60</span> <div class="c" id="comment-169983"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/41e4c684ba730c88e05fc9bdf563cbc2?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Marty</h3> <span class="dati"> <a title="Commentlink #60" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169983"> March 10, 2011 3:08 pm </a> </span> </div> </div> <div class="ctx"> <p>excellent post… stumbled.. :)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169983" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169983" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">61</span> <div class="c" id="comment-169984"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/403337506ddc11158cad4b76d304fbe7?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>seedy</h3> <span class="dati"> <a title="Commentlink #61" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169984"> March 10, 2011 11:38 pm </a> </span> </div> </div> <div class="ctx"> <p>these articles are getting lamer and lamer</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169984" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169984" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">62</span> <div class="c" id="comment-169985"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/de87d78c47a8f6e6802c23544ef4bd90?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>web3mantra</h3> <span class="dati"> <a title="Commentlink #62" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169985"> March 11, 2011 3:18 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks for sharing this post.I like this post.It contains good examples of wordpress plugin developer should know.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169985" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169985" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">63</span> <div class="c" id="comment-169986"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/dd2e765b964f9f3887c4518b294e42ac?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>ig-ffm</h3> <span class="dati"> <a title="Commentlink #63" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169986"> March 12, 2011 11:16 am </a> </span> </div> </div> <div class="ctx"> <p>I really appreciate your posting. Thanks.</p> <p>There is one issue I’ld like to add: localization.<br /> I have to translate all kinds of plugins and that can be a really annoying waste of time, if a plugin is not meant to be localized.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169986" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169986" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">64</span> <div class="c" id="comment-169987"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/70325f2bf83316d1ba0c44bbc9bc2b1e?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Rahul</h3> <span class="dati"> <a title="Commentlink #64" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169987"> March 13, 2011 10:23 am </a> </span> </div> </div> <div class="ctx"> <p>Great post. Really helps a lot. But need to ask something. I saw this effect on a recently launched blog with wp posts coming in like a js gallery slider.</p> <p><a href="http://sputznik.com/" rel="nofollow">http://sputznik.com/</a></p> <p>How have they achieved this transition and post thing? Is there a plugin that I could use? Thanks for the help.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169987" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169987" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">65</span> <div class="c" id="comment-169991"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #65" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169991"> March 14, 2011 4:07 am </a> </span> </div> </div> <div class="ctx"> <p>@Rahul – It looks like that transition is done with jQuery and the easing plugin for jQuery. Just give it a quick Google and you’ll find what you need.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169991" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169991" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-3 clearfix"> <span class="cn">66</span> <div class="c" id="comment-170002"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/70325f2bf83316d1ba0c44bbc9bc2b1e?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Rahul</h3> <span class="dati"> <a title="Commentlink #66" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170002"> March 24, 2011 11:23 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks a ton. Is there any plugin for this?</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170002" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170002" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">67</span> <div class="c" id="comment-169988"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/281d234ca83251614a66121a05cb8fad?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Manny Fleurmond</h3> <span class="dati"> <a title="Commentlink #67" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169988"> March 13, 2011 9:26 pm </a> </span> </div> </div> <div class="ctx"> <p>I also recommend using the plugins_url() function to find your plugins base directory:<br /> <a href="http://codex.wordpress.org/Function_Reference/plugins_url" rel="nofollow">http://codex.wordpress.org/Function_Reference/plugins_url</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169988" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169988" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">68</span> <div class="c" id="comment-169989"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/f3fc67a71bef1394539fd4be794cb73e?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dax Davis</h3> <span class="dati"> <a title="Commentlink #68" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169989"> March 13, 2011 9:52 pm </a> </span> </div> </div> <div class="ctx"> <p>This is a great post. Thanks for bringing it all together in one place.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169989" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169989" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">69</span> <div class="c" id="comment-169990"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/f8393ef67ed5144e15890d60eaa2289e?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Valentinas</h3> <span class="dati"> <a title="Commentlink #69" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169990"> March 14, 2011 1:28 am </a> </span> </div> </div> <div class="ctx"> <p>Great article! Particularly the part about using wp_debug is a must-read for every plugin developer.<br /> By the way, just wanted to point out that there is a function wp_login_url() for login url. People should use this, because some plugins may modify it with filter that is inside it and bloginfo(‘wpurl’) . “/wp-login.php” is not necessary the right login URL.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169990" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169990" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-2 clearfix"> <span class="cn">70</span> <div class="c" id="comment-169992"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #70" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169992"> March 14, 2011 4:08 am </a> </span> </div> </div> <div class="ctx"> <p>@Valentinas – Good catch about the wp_login_url() function, thanks for pointing that out.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169992" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169992" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">71</span> <div class="c" id="comment-169993"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/61a894194ade535460a0e34ed4b56c31?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Gavin Potts</h3> <span class="dati"> <a title="Commentlink #71" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169993"> March 14, 2011 7:34 am </a> </span> </div> </div> <div class="ctx"> <p>Awesome post. 9 of 10 i’ve found extremely interesting and enlightening…</p> <p>I’d just like to query the tip: “Use bloginfo(‘wpurl’) Instead of bloginfo(‘url’)”. I believe this is bad advice.</p> <p>When developing a WordPress website, developers may be forced to work in a live environment with a holding page in place. If you use ‘wpurl’ in your themes/plugins, this will fail, as you will need to rename index.php and point ‘siteurl’ to the index page to have the website up for development.</p> <p>If all of your internal links are output with the ‘wpurl’ parameter, these will link to your holding page and you will have to type permalinks into your browser manually instead of clicking on links within the website.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169993" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169993" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">72</span> <div class="c" id="comment-169994"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/c92d3f3fe8e5b19bd7dc3d08142b400e?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Jim Krill</h3> <span class="dati"> <a title="Commentlink #72" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169994"> March 14, 2011 6:54 pm </a> </span> </div> </div> <div class="ctx"> <p>This is a great article for anyone wanting to develop a WordPress plugin. Hopefully it will lead to some brilliant plug-ins which will enrich the WordPress community even more.</p> <p>Thanks Dave!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169994" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169994" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">73</span> <div class="c" id="comment-169996"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/e94a2e120ad98cc9d2708b156c6a1c69?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Philip Norton</h3> <span class="dati"> <a title="Commentlink #73" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169996"> March 15, 2011 1:58 am </a> </span> </div> </div> <div class="ctx"> <p>This is a great list, but one thing that every WordPress developer should know about (more important than knowing about require_once() etc) is nonces. Nonces are a very important part of WordPress that help to combat security problems and should definitely be on this list.<br /> <a href="http://codex.wordpress.org/WordPress_Nonces" rel="nofollow">http://codex.wordpress.org/WordPress_Nonces</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169996" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169996" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">74</span> <div class="c" id="comment-169997"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7ac2e44aeff39f6df1187cb0e4f7fb92?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Jason LaRose</h3> <span class="dati"> <a title="Commentlink #74" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169997"> March 15, 2011 9:15 am </a> </span> </div> </div> <div class="ctx"> <p>One thing every WordPress plugin developer should do is NOT include default styles for their generated HTML. Doing so means reverse engineering for other WordPress developers. If you do add default styles, add in the option to deactivate the CSS.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169997" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169997" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">75</span> <div class="c" id="comment-169999"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/25c608d2c1b076011369920bfcd889a3?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dan Coulter</h3> <span class="dati"> <a title="Commentlink #75" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169999"> March 15, 2011 12:12 pm </a> </span> </div> </div> <div class="ctx"> <p>Nothing about wp_enqueue_script()?</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169999" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169999" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">76</span> <div class="c" id="comment-170000"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/5c65fecb4e4179a59ebecb18034dcb64?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Permana Jayanta</h3> <span class="dati"> <a title="Commentlink #76" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170000"> March 15, 2011 6:40 pm </a> </span> </div> </div> <div class="ctx"> <p>Really helpful post as I’m writing WordPress plugin now. Maybe should added list of functions that can help plugin development, instead of writing a functions again.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170000" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170000" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">77</span> <div class="c" id="comment-170001"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/0445bfc3e671c35b39d6036658c57a0e?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Kyathi</h3> <span class="dati"> <a title="Commentlink #77" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170001"> March 16, 2011 10:24 pm </a> </span> </div> </div> <div class="ctx"> <p>Thank you.. superb.. !!! its really helpful…</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170001" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170001" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">78</span> <div class="c" id="comment-170003"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/b80742b6d859d848f839c270c2543f3c?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Sterling Hamilton</h3> <span class="dati"> <a title="Commentlink #78" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170003"> April 9, 2011 11:15 am </a> </span> </div> </div> <div class="ctx"> <p>Hey there!</p> <p>A few things…</p> <p>In regards to dbDelta:<br /> “require_once(ABSPATH . ‘wp-admin/includes/upgrade.php’);”</p> <p>That means you are now including a core WP file into your plugin…not really recommended. Further more, by doing that – it will start throwing aggressive cache busting headers. This will get in the way of caching plugins and proxies.</p> <p>Also – rather than prefixing every function, it’s better to just do an Object in PHP and give that a unique name. That way prefixing is not needed – just a unique object name.</p> <p>And the BlackBox plugin has been known to drastically slow down servers, so it should not be used in any sort of production environment.</p> <p>Also – you want to load your plugins meta data rather than creating your own. So version number/plugin path/etc are able to be loaded like this: <a href="https://gist.github.com/911684" rel="nofollow">https://gist.github.com/911684</a></p> <p>Another really good tip…do NOT rely on environment variables like HTTP_HOST, REQUEST_URI and such.</p> <p>These tend to be unreliable – its best to use the wordpress variables for determining locations and what not.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170003" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170003" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">79</span> <div class="c" id="comment-170004"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7a831efd240c56f74f4c4f2618d9a51a?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>cogmios`</h3> <span class="dati"> <a title="Commentlink #79" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170004"> May 6, 2011 10:30 am </a> </span> </div> </div> <div class="ctx"> <p>Because of the topic the “Objective Best Practices for Plugin Development?” on <a href="http://wordpress.stackexchange.com/questions/715/objective-best-practices-for-plugin-development" rel="nofollow">http://wordpress.stackexchange.com/questions/715/objective-best-practices-for-plugin-development</a> is also a good addition.</p> <p>Maybe to add to the debugging part: I also found using Zend Server community edition together with PHP PDT increase my debugging abilities (I dumped xampp for it).</p> <p> For making names unique well… I use php 5.3 with namespaces -end of problem- the language solves it for me. So I just state “this plugin is only for php 5.3 onwards” (although some discussion exist on “only 5.3″ <a href="http://groups.google.com/group/wp-hackers/browse_thread/thread/19dc7c7197f66754/9a60ad0b37ccaf1b?show_docid=9a60ad0b37ccaf1b&pli=1" rel="nofollow">http://groups.google.com/group/wp-hackers/browse_thread/thread/19dc7c7197f66754/9a60ad0b37ccaf1b?show_docid=9a60ad0b37ccaf1b&pli=1</a>)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170004" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170004" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">80</span> <div class="c" id="comment-170005"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/8c06582f15e2a41ca172044202c426eb?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>anyon</h3> <span class="dati"> <a title="Commentlink #80" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170005"> May 7, 2011 2:25 pm </a> </span> </div> </div> <div class="ctx"> <p>rule #1 wordpress is coded badly you will not learn anything about design patterns or best practices from looking at the wordpress source code, use your initiative ;)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170005" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170005" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">81</span> <div class="c" id="comment-170006"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/216c409be1cbf323cbd714f4010e6797?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Brett Widmann</h3> <span class="dati"> <a title="Commentlink #81" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170006"> May 10, 2011 7:22 pm </a> </span> </div> </div> <div class="ctx"> <p>Thanks for these really awesome tips! They will be really helpful.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170006" class="inpsyde_extended_comments_rate negative">-2</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170006" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">82</span> <div class="c" id="comment-170007"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/827b430098defd203fa74ed9ce92e0d9?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>mikaweb</h3> <span class="dati"> <a title="Commentlink #82" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170007"> September 11, 2011 2:28 am </a> </span> </div> </div> <div class="ctx"> <p>Nice tips. I’m currently writing my first plugin and it helped me a lot especially for the upgrade system.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170007" class="inpsyde_extended_comments_rate positive">2</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170007" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">83</span> <div class="c" id="comment-170008"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/78d5156936de65aac7e00ea273db82e7?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>liskel</h3> <span class="dati"> <a title="Commentlink #83" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170008"> August 25, 2012 4:22 am </a> </span> </div> </div> <div class="ctx"> <p>Really nice things to keep in mind and great for beginners exploring the deep depths of wordpress plugin development!<br /> Thanks!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170008" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170008" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">84</span> <div class="c" id="comment-170009"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/0fa974dbdfd8afc7390131f9fd4c097c?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Ryan S</h3> <span class="dati"> <a title="Commentlink #84" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170009"> September 14, 2012 12:09 am </a> </span> </div> </div> <div class="ctx"> <p>Hi thanks for the tip, I just notice in Settings link, I think there is the better way to declare setting link.</p> <p>something like this<br /> $settings_link = ‘<a href="'.admin_url('admin.php?page=plugin-settings').'" rel="nofollow">Settings</a>‘;</p> <p>Ryan S</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170009" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170009" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">85</span> <div class="c" id="comment-170010"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/0fa974dbdfd8afc7390131f9fd4c097c?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Ryan S</h3> <span class="dati"> <a title="Commentlink #85" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170010"> September 14, 2012 12:10 am </a> </span> </div> </div> <div class="ctx"> <p>Oops sorry for this second comment, it does not look good on my previous comment.</p> <p><code>$settings_link = '<a href="'.admin_url('admin.php?page=cx-events').'" rel="nofollow">Settings</a>';</code></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170010" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170010" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">86</span> <div class="c" id="comment-170011"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/98d0a24074949185147845293651e72c?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Arch!tect</h3> <span class="dati"> <a title="Commentlink #86" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170011"> January 7, 2013 11:27 pm </a> </span> </div> </div> <div class="ctx"> <p>thanks dude!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170011" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170011" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">87</span> <div class="c" id="comment-170012"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/1cde71fd2000a3649df05c3be7fd7ba9?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>David Hazelden</h3> <span class="dati"> <a title="Commentlink #87" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170012"> February 17, 2013 8:04 am </a> </span> </div> </div> <div class="ctx"> <p>Good stuff!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170012" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170012" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">88</span> <div class="c" id="comment-170013"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/2af83baa1864c442b08865d2f9ed8223?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Byron Dunn</h3> <span class="dati"> <a title="Commentlink #88" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170013"> February 28, 2013 7:50 am </a> </span> </div> </div> <div class="ctx"> <p>Great article. Being new to WP development, this is really helpful. Even for those of us struggling to tweak plugins we use.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170013" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170013" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">89</span> <div class="c" id="comment-170014"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/1441f3f17c4f72a0153415048e442bf0?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Manuel Marquez</h3> <span class="dati"> <a title="Commentlink #89" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170014"> March 21, 2013 1:43 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks Dave,</p> <p>These are fantastic tips to start quality plugin development. Please keep up the good work!<br /> Much appreciated.</p> <p>Cheers,<br /> Manuel</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170014" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170014" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">90</span> <div class="c" id="comment-170019"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/ad64f6ef4b9c5b4f8b3c90be203be4d2?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Alex Buri</h3> <span class="dati"> <a title="Commentlink #90" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170019"> June 28, 2013 3:04 am </a> </span> </div> </div> <div class="ctx"> <p>Clear and well-written – you’ve allowed me to understand php even in the middle of the night….<br /> thanks</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170019" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170019" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">91</span> <div class="c" id="comment-170018"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7807fb5b55bfd79bc0c36c307b3a4bd8?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Juergen</h3> <span class="dati"> <a title="Commentlink #91" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170018"> October 14, 2013 11:31 pm </a> </span> </div> </div> <div class="ctx"> <p>Hello,<br /> a really really good tutorial.<br /> Thanks</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170018" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170018" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">92</span> <div class="c" id="comment-170017"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/c1b4eb8751a973da835b8fb6588586aa?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Will</h3> <span class="dati"> <a title="Commentlink #92" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170017"> January 3, 2014 12:10 pm </a> </span> </div> </div> <div class="ctx"> <p>Thanks for the article. The menu stuff in particular was very helpful. </p> <p>I’d add 11): Understand how/when WordPress loads things. This flow chart of what happens during a WP request cycle is pretty illuminating: <a href="http://www.rarst.net/script/wordpress-core-load/" rel="nofollow">http://www.rarst.net/script/wordpress-core-load/</a> </p> <p>Couple of other handy flow charts linked from that page as well in particular this chart that explains WP Query Functions <a href="http://www.rarst.net/script/wordpress-query-functions/" rel="nofollow">http://www.rarst.net/script/wordpress-query-functions/</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170017" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170017" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">93</span> <div class="c" id="comment-170015"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/e85eff52524a64e38ddc4316fb079c22?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>jack</h3> <span class="dati"> <a title="Commentlink #93" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170015"> January 20, 2014 12:02 am </a> </span> </div> </div> <div class="ctx"> <p>i have developed a plugin for paggination along with a shortcode but the output is showing in dashboad and when adding shortcode in any pages then it displays output in pages.<br /> Kindly suggest how to hide the output from dashbord.</p> <p>Thank You in advance</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170015" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170015" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">94</span> <div class="c" id="comment-170016"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/6c94850a0051b2ab23ab7a18c7d4d181?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Wordpress plugins</h3> <span class="dati"> <a title="Commentlink #94" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170016"> February 20, 2014 10:04 pm </a> </span> </div> </div> <div class="ctx"> <p>Good post. I learn something totally new and challenging on blogs I stumbleupon on a daily basis. It will always be helpful to read through content from other authors and use something from their sites.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170016" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170016" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ol> </div> </div> </div></div><p><a href="#top" class="top" title="Jump to the top of the page">↑ Back to top</a></p> </div><div class="fo-na"> <div class="mn" id="mn"> <ul id="menu-smashing-mobile-network" class="mnu"><li class="mnh">Smashing Pages:</li><li id="menu-item-188956" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-188956 menu-item-books"><a href="http://www.smashingmagazine.com/books/">Books</a></li> <li id="menu-item-188957" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-188957 menu-item-ebooks"><a href="http://www.smashingmagazine.com/ebooks/">eBooks</a></li> <li id="menu-item-188955" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-188955 menu-item-workshops"><a href="http://www.smashingmagazine.com/smashing-workshops/">Workshops</a></li> <li id="menu-item-188959" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-188959 menu-item-email-newsletter"><a href="http://www.smashingmagazine.com/the-smashing-newsletter/">Email Newsletter</a></li> <li id="menu-item-188961" class="menu-item menu-item-type-custom menu-item-object-custom menu-item-188961 menu-item-job-board"><a href="http://jobs.smashingmagazine.com">Job Board</a></li> <li id="menu-item-188958" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-188958 menu-item-about-us-impressum"><a href="http://www.smashingmagazine.com/about/">About us / Impressum</a></li> </ul> <ul id="menu-mobile-categories" class="mnu"><li class="mnh">Categories:</li><li id="menu-item-181575" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-181575 menu-item-coding"><a href="http://www.smashingmagazine.com/category/coding/">Coding</a></li> <li id="menu-item-181576" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-181576 menu-item-design"><a href="http://www.smashingmagazine.com/category/design/">Design</a></li> <li id="menu-item-181580" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-181580 menu-item-mobile"><a href="http://www.smashingmagazine.com/category/mobile/">Mobile</a></li> <li id="menu-item-181579" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-181579 menu-item-graphics"><a href="http://www.smashingmagazine.com/category/graphics/">Graphics</a></li> <li id="menu-item-181577" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-181577 menu-item-ux-design"><a href="http://www.smashingmagazine.com/category/uxdesign/">UX Design</a></li> <li id="menu-item-181578" class="menu-item menu-item-type-taxonomy menu-item-object-category current-post-ancestor current-menu-parent current-post-parent menu-item-181578 menu-item-wordpress"><a href="http://www.smashingmagazine.com/category/wordpress/"><span class="long"><span>Word</span><span>Press</span></span><span class="short">WP</span></a></li> </ul> <a href="#top" class="top" title="Jump to the top of the page">↑ Back to top</a> </div><div class="ms" id="ms"> <form id="searching" class="sfm" method="get" action="http://www.smashingmagazine.com/search-results/" target="_top"> <div class="clearfix"> <input name="q" id="mobile-search-input" type="text" placeholder="e.g. CSS" /> <button class="search_submit" type="submit">Search</button> <input type="hidden" name="cx" value="partner-pub-6779860845561969:5884617103"> <input type="hidden" name="cof" value="FORID:10"> <input type="hidden" name="ie" value="UTF-8"> </div> </form> <a href="#top" class="top" title="Jump to the top of the page">↑ Back to top</a> </div> <!-- Search form --></div> </div><div id="wpsidebar" class="sb"> <div class="col side"> <div class="sf"> <form method="get" action="http://www.smashingmagazine.com/search-results/" target="_top"> <label for="magazine-search">Search on Smashing Magazine</label> <input id="magazine-search" name="q" type="text" placeholder="e.g. Responsive design" /> <button type="submit">Search</button> <input type="hidden" name="cx" value="partner-pub-6779860845561969:5884617103"> <input type="hidden" name="cof" value="FORID:10"> <input type="hidden" name="ie" value="UTF-8"> </form> </div> <div class="bw faw"> <span class="declare">Advertisement</span> <span class="awithus"><a class="sprite ed-us" href="mailto:advertising@smashingmagazine.com" title="Advertise with us!">Advertise with us!</a></span> <div id="spnsrlist-a"></div> </div> <div class="sf wg"> <h3> <a href="http://www.smashingmagazine.com/the-smashing-newsletter/"> <img src="http://www.smashingmagazine.com/files/smashing-widget/v006/img/smnl.png" alt="Smashing Newsletter" /> Smashing Newsletter </a> </h3> <p>Subscribe to our email newsletter for useful tips and valuable resources, sent out every second Tuesday.</p> <form action="http://smashingmagazine.us1.list-manage1.com/subscribe/post?u=16b832d9ad4b28edf261f34df&id=a1666656e0" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate"> <input name="EMAIL" type="text" placeholder="email address" /> <button class="search_submit" type="submit">Subscribe</button> </form> </div> <div class="bw"> <div id="spnsrlist-b"></div> </div> <div class="so wg"> <div class="fir"> <a href="http://www.smashingmagazine.com/books/#digital-adaptation" style="border: none;"> <img src="http://www.smashingmagazine.com/wp-content/uploads/2013/04/sidebar-digital-adaptation-paul-boag-v5-opt.png" alt="Digital Adaptation by Paul Boag"> </a> <p>Nothing is more frustrating than <strong>stubborn management</strong>. That's why we have published <a href="http://www.smashingmagazine.com/books/#digital-adaptation">Digital Adaptation</a>, a new book by Paul Boag on how to help management overcome legacy practices - for good.</p> </div> <div class="sec"> <a href="http://www.smashingmagazine.com/smashing-book-4-new-perspectives/?pk_campaign=sb4-sidebar"><img src="http://www.smashingmagazine.com/wp-content/uploads/2013/04/Smashing-Book-4-sidebar-transparent-opt.png" alt="Smashing Book #4"></a> <p>It's done. The <a href="http://www.smashingmagazine.com/smashing-book-4-new-perspectives/?pk_campaign=sb4-sidebar">Smashing Book #4</a>, our brand new book with smart <strong>front-end techniques</strong> and design approaches. Written by respected designers and developers, neatly packed in a gorgeous hardcover.</p> </div> <div class="thi"> <a href="http://www.smashingmagazine.com/ebooks/?pk_campaign=sb4-sidebar"> <img src="http://www.smashingmagazine.com/wp-content/uploads/2014/08/sidebar-smashing-library.png" alt="Smashing Library"> </a> <p>Hungry for more content? Over 60 <strong>eBooks</strong> are waiting to be discovered in our lovely <a href="http://www.smashingmagazine.com/ebooks/?pk_campaign=sb4-sidebar">Smashing Library</a>. And guess what? You can watch Smashing Conference talks there, too.</p> </div> </div> <div class="bw"> <div id="spnsrlist-c"></div> </div> <div class="wg"> <div id="jobs"> <h3> <a href="http://jobs.smashingmagazine.com/?pk_campaign=sm&piwik_kwd=widget"> <span>Smashing Job Board</span> <img src="http://www.smashingmagazine.com/files/smashing-widget/v006/img/sm-jobs.png" alt="Smashing Jobs"> </a> </h3> <ul class="tl"> <li style="display:none;"></li> <ul class="tl"><li class="clearfix"><a href="http://feedproxy.google.com/~r/smjobs/~3/l1iopv9T-xg/2415960">Senior Web/Graphic Designer - RateHub - (Toronto, ON) - FullTime</a><p>Position for hire: Senior Web / Graphic designer Location: Downtown Toronto, ON Start Date: As soon as possible About us We’re a talen...</p></li><li class="clearfix"><a href="http://feedproxy.google.com/~r/smjobs/~3/ODntye-bheY/2415959">Senior Front-End Engineer (Yes, You can Work from Home) - Twin Technologies - (Altamont, New York) - FullTime</a><p>About the Opportunity We are seeking a few good men and women to help build a “best of breed” eCommerce platform that supports the creation, maintenance...</p></li></ul> </ul> <a class="cr" href="http://jobs.smashingmagazine.com?pk_campaign=sm&piwik_kwd=widget">View more job openings…</a> </div> </div> <div id="sidebar_special-1"></div> <div id="sidebar_special-2"></div> <div class="sidebar_sky" id="sidebar_sky-1"></div> <div class="sidebar_sky" id="sidebar_sky-2"></div> </div> </div><div id="footer">
<div class="fp clearfix"> <a class="pi" href="http://www.smashingmagazine.com/smashing-book-4-new-perspectives/?pk_campaign=sb4-footer"><img src="http://www.smashingmagazine.com/wp-content/uploads/2013/10/smashing-book-4-footer-opt.png" alt="Smashing Book #4"></a> <p class="pd"> <a href="http://www.smashingmagazine.com/smashing-book-4-new-perspectives/?pk_campaign=sb4-footer"><strong>Smashing Book #4</strong></a><br />Get our brand new Smashing Book #4, available as print and eBook. <a href="http://www.smashingmagazine.com/smashing-book-4-new-perspectives/?pk_campaign=sb4-footer">Learn more...</a> </p> </div> <div class="fp clearfix"> <a class="pi" href="https://shop.smashingmagazine.com/smashing-library-complete.html?pk_campaign=smashingmagazine-footer"><img src="http://www.smashingmagazine.com/wp-content/uploads/2013/10/smashing-library-footer-new-opt.png" alt="The Smashing Library"></a> <p class="pd"> <a href="https://shop.smashingmagazine.com/smashing-library-complete.html?pk_campaign=smashingmagazine-footer"><strong>The Smashing Library</strong></a><br />Grab all published and upcoming Smashing eBooks, in one swoop. <a href="https://shop.smashingmagazine.com/smashing-library-complete.html?pk_campaign=smashingmagazine-footer">Learn more...</a> </p> </div> <div class="fp clearfix"> <a class="pi" href="http://www.smashingmagazine.com/smashing-workshops/"><img src="http://www.smashingmagazine.com/wp-content/uploads/2013/08/footer-brad-frost-opt.jpg" alt="Smashing Workshops"></a> <p class="pd"> <a href="http://www.smashingmagazine.com/smashing-workshops/"><strong>Smashing Workshops</strong></a><br />Join our hands-on full-day workshops, run by experts of the industry. Good stuff. <a href="http://www.smashingmagazine.com/smashing-workshops/">Learn more...</a> </p> </div><p class="stmt"><em>With a commitment to quality content for the design community.</em><br />Founded by Vitaly Friedman and Sven Lennartz. 2006-2014.<br />Made in Germany. ? <a href="http://www.smashingmagazine.com/write-for-us/">Write for us</a> - <a href="http://www.smashingmagazine.com/contact/">Contact us</a> - <a href="http://www.smashingmagazine.com/about/">Impressum</a>.</p> </div> <script type="text/javascript">var clicky_site_ids=clicky_site_ids||[];clicky_site_ids.push(2727),function(){var e=document.createElement("script");e.type="text/javascript",e.async=!0,e.src="//static.getclicky.com/js",(document.getElementsByTagName("head")[0]||document.getElementsByTagName("body")[0]).appendChild(e)}();</script><noscript><p><img alt="Clicky" width="1" height="1" src="//in.getclicky.com/2727ns.gif" /></p></noscript>
<script type='text/javascript' src='http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/javascripts/ads.min.js?ver=2014.1.3'></script> <script type="text/javascript">var elements=["http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/javascripts/onload.min.js?ver=2014.12.0","http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/javascripts/prism.js"],downloadJSAtOnload=function(n){if("[object Array]"!==Object.prototype.toString.call(n))return 0;var t,e;for(t=0;t<n.length;t++)e=document.createElement("script"),e.src=n[t],document.body.appendChild(e);return !0};window.addEventListener ? window.addEventListener("load",function(){downloadJSAtOnload(elements)},!1):window.attachEvent ? window.attachEvent("onload",function(){downloadJSAtOnload(elements)}):window.onload=function(){downloadJSAtOnload(elements)};window.onload=function(){var avatars=document.querySelectorAll('.avatar');for(var i=0,length=avatars.length;i<length;i++){var gravatar_url=avatars[i].getAttribute('data-gravatar-url');avatars[i].src=gravatar_url;}};</script> <script type='text/javascript'>/* <![CDATA[ */ SmashingAds.load(); /* ]]> */</script><script type='text/javascript'>/* <![CDATA[ */ SmashingAds.postLoad(); /* ]]> */</script><script type='text/javascript'>/* <![CDATA[ */ SmashingAds.postPostLoad(); /* ]]> */</script> <script type="text/javascript">(function(){"use strict";if("querySelector" in document){var forEach=function(array,callback,scope){for(var i=0;i<array.length;i++){callback.call(scope,i,array[i]);}};var articles=document.getElementsByTagName("article");forEach(articles,function(i,el){var tagElements=el.querySelectorAll("li.tags a");var tags=[];forEach(tagElements,function(i,el){var content=el.innerText||el.textContent;tags.push(content.toLowerCase());});var image=el.querySelector(".at");if(image)image.setAttribute("data-adt-keywords",tags);});adtile("[data-adt-keywords]",{apiKey:"4624ca9f-0982-442f-b691-bb5f04643a74",channel:"technology",keywords:["Smashing Conference","Smashingconf","Whistler","Front-end","CSS","Javascript"],taglineFontFamily:"'Proxima Nova Bold','Helvetica Neue',Helvetica,Arial,sans-serif",taglineBorderRadius:"1.25em",colors:{iconBackground:"#e53b2c",closeButtonBackground:"#e53b2c"}});}})();</script> </body></html> <end node> 5P9i0s8y19Z dt= <node>WARNINGS 1 [FORMS] DO not use name="name" into inputs. RETURNS PAGE NOT FOUND <end node> 5P9i0s8y19Z
<node>cheat sheets <node>constants <node>directory <node>example <node>hooks <node>SESSIONS <node>html5 <node>reserved words <node>Settings <node>Upgrades <node>uploads <node>urls <node>How to Include a WordPress Page <node>Stupid WordPress Tricks <node>Ten Things Every WordPress Plugin Developer Should Know <node>WARNINGS <Treepad version 3.0> dt= <node>cheat sheets 0 http://www.buildyourownblog.net/blog/time-saving-copypaste-wordpress-cheat-sheet/The Time Saving Copy/Paste WordPress Cheat Sheet while(have_posts()) { the_post(); }
Use this WordPress Cheat Sheet page for a quick, categorized list of WordPress functions that are commonly used when building, updating and maintaining templates. Simple, Easy, Copy-Paste. The quick guide to common WordPress > Template functions. Pdf Icon
-------------------------------------------------------------------------------- Basic Template Files File Name Description style.css style sheet file index.php home page file header.php header content file single.php single post page file archive.php archive/category file searchform.php search form file search.php search content file 404.php error page file comments.php comments template file footer.php footer content file sidebar.php sidebar content file page.php single page file front-page.php latest posts or static page tag.php display tags in archive format category.php display categories in archive format Header Functions Function Description <?php site_url(); ?> root url for website <?php wp_title(); ?> title of specific post/page <?php bloginfo('name'); ?> title of site <?php bloginfo('description'); ?> site description <?php get_stylesheet_directory(); ?> stylesheet folder location <?php bloginfo('stylesheet_url'); ?> style.css file location <?php bloginfo('pingback_url'); ?> pingback url <?php bloginfo('template_url'); ?> template folder path <?php bloginfo('version'); ?> wordpress blog version <?php bloginfo('atom_url'); ?> atom url <?php bloginfo('rss2_url'); ?> rss2 url <?php bloginfo('url'); ?> root url for website <?php bloginfo('html_type'); ?> html version <?php bloginfo('charset'); ?> charset parameter Navigation Menu Default Navigation Menu <?php wp_nav_menu(); ?> Specific Navigation Menu <?php wp_nav_menu( array('menu' => 'Project Nav' )); ?> Category Based Navigation <ul id="menu"> <li <?php if(is_home()) { ?> class="current-cat" <?php } ?>> <a href="<?php bloginfo('home'); ?>">Home</a></li> <?php wp_list_categories('title_li=&orderby=id');?> </ul> Page Based Navigation <ul id="menu"> <li <?php if(is_home()) { ?> class="current-page-item" <?php } ?>> <a href="<?php bloginfo('home'); ?>">Home</a></li> <?php wp_list_pages('sort_column=menu_order&depth=1&title_li=');?> </ul> -------------------------------------------------------------------------------- Template Functions Function Description <?php the_content(); ?> content of posts/pages <?php if(have_posts()): ?> check if there are posts <?php while(have_posts()): the_post(); ?> shows posts <?php endwhile; ?> closes loop <?php endif; ?> closes if <?php get_header(); ?> header.php file contents <?php get_sidebar(); ?> sidebar.php file contents <?php get_footer(); ?> footer.php file contents <?php the_time('m-d-y'); ?> the date is ’08-18-07' <?php comments_popup_link(); ?> link to comments of post <?php the_title(); ?> title of post/page <?php the_permalink(); ?> url of post/page <?php the_category(); ?> category of post/page <?php the_author(); ?> author of post/page <?php the_ID(); ?> id of post/page <?php edit_post_link(); ?> edit link of post/page <?php wp_list_bookmarks(); ?> links from blogroll <?php comments_template(); ?> comment.php file contents <?php wp_list_pages(); ?> list all pages <?php wp_list_categories(); ?> list all categories <?php next_post_link('%link'); ?> url to next post <?php previous_post_list('%link'); ?> url to previous post <?php get_calendar(); ?> show post calendar <?php wp_get_archives(); ?> list of archive urls <?php posts_nav_link(); ?> next and previous post link <?php rewind_posts(); ?> rewinds post for a second loop The Loop Basic Loop <?php if(have_posts()) { ?> <?php while(have_posts()) { ?> <?php the_post(); ?> <?php // custom post content code for title, excerpt and featured image ?> <?php } // end while ?> <?php } // end if ?> Extra Functions Function Description /%postname%/ custom permalinks <?php include(TEMPLATEPATH . '/x'); ?> include file from template folder <?php the_search_query(); ?> value returned from search from <?php _e('Message'); ?> return translated text from translate() <?php wp_register(); ?> register link <?php wp_loginout(); ?> login/logout link <!--nextpage--> divide content into pages <!--more--> cut off content and create link to full post <?php wp_meta(); ?> admin meta data <?php timer_start(); ?> start page timer (header.php) <?php timer_stop(1); ?> time to load the page (footer.php) <?php echo get_num_queries(); ?> show queries executed to generate page <end node> 5P9i0s8y19Z dt= <node>constants 1 get_site_url() get_theme_root_uri(), get_stylesheet(), get_stylesheet_uri(), get_stylesheet_directory(), get_stylesheet_directory_uri(), get_bloginfo() WordPress Directories: home_url() Home URL http://www.example.com site_url() Site directory URL http://www.example.com or http://www.example.com/wordpress admin_url() Admin directory URL http://www.example.com/wp-admin includes_url() Includes directory URL http://www.example.com/wp-includes content_url() Content directory URL http://www.example.com/wp-content plugins_url() Plugins directory URL http://www.example.com/wp-content/plugins theme_url() Themes directory URL (#18302) http://www.example.com/wp-content/themes wp_upload_dir() Upload directory URL (returns an array) http://www.example.com/wp-content/uploads
Categories: WordPress Constants Here are some of the constants and how they are used. There are probably a few that I missed. I’ll add to this as I find more. Security Constants These constants are declared in wp-config.php and are required for the normal operation of WordPress. All of these constants are 64 character random strings and are used for hashes, nonces and other security purposes. Each installation of WordPress should use different strings to ensure that your site is harder to “hack.” If you haven’t already changed your security keys, you can use WordPress’s online security key generator. AUTH_KEY - Used for authenticating a user and setting cookies. SECURE_AUTH_KEY - Used for authenticating a user and setting cookies under the https protocol. LOGGED_IN_KEY - Used for marking a user’s cookie data as logged in. NONCE_KEY - Used for creating Nonces, which are used as one-time values to ensure that humans are entering data in forms. AUTH_SALT - Used to “salt” the authentication data. Salts are random data added to passwords, keys and other data to make them harder to guess. SECURE_AUTH_SALT - Used to “salt” the secure authentication data. LOGGED_IN_SALT - Used to “salt” the logged in cookie data. NONCE_SALT - Used to “salt” the nonce data. Database Constants These are used to declare your database connection information. If you ever need to change your database password or location, you can effect this by editing your wp-config.php file and change these values: DB_NAME - The name of your database. DB_USER - The user name for your database connection. DB_PASSWORD - The password for your database connection. DB_HOST - The host name, or computer name where your database server is located. DB_CHARSET - The character set used when creating tables in your database. Unless you have a specific requirement for something else, this should have a value of ‘utf8?. DB_COLLATE - The collation (sorting) type to use for indexed data in your tables. This should be left empty unless you have a specific requirement otherwise. Other wp-config.php Constants These are the last few constants that are normally declared in wp-config.php: COOKIE_DOMAIN - Specifies the domain set in cookies for those with unusual domain configurations. This can help to prevent cookies being sent with requests for static content. Example: define(‘COOKIE_DOMAIN’, ‘www.staticdomain.com’);. WP_DEBUG - Sets WordPress’s “debug” mode on or off. Normally, this is set to false. Changing it to define(‘WP_DEBUG’, true); will turn on debug mode. This can be useful if you need to track down errors. WP_HOME - This overrides the configuration setting for the home url, but doesn’t change it permanently. This should include the http:// prefix, as in: define(‘WP_HOME’, ‘http://domain.com/optionalsubdirectory’);. WP_SITEURL - Declares the site’s URL. This defines the address where your WordPress code files reside. It should include the http:// prefix. An example would be: define(‘WP_SITEURL’, ‘http://mydomain.com’);. WPLANG - Used to localize your WordPress install. This should be left empty for a default language of American English. If you need to localize your WordPress installation, you need to change this and install a corresponding MO file for your language. For example, changing this to: define(‘WPLANG’, ‘de_DE’); will set your language to German. DISABLE_WP_CRON - Used to turn off WP Cron tasks that are initiated y a page load. When this is disabled, it is recommended to set up a separate Cron job to run the wp-cron.php script on a regular basis in order to still have cron-related operations run. System Constants These constants are set to describe the state of how WordPress handles various requests. APP_REQUEST - Set within wp-app.php to indicate that WordPress is handling an Atom Publishing Protocol request. Default Constants These values are declared in the wp-includes/default-constants.php file. You to change these settings, add them to your wp-config.php file so they are declared before the wp-includes/default-constants.php file is loaded. ADMIN_COOKIE_PATH - Sets the cookie path for admin-based cookies. If not already defined, this will take the value: define(‘ADMIN_COOKIE_PATH’, SITECOOKIEPATH . ‘wp-admin’); AUTH_COOKIE - Sets the authentication cookie name. If not already set, will be: define(‘AUTH_COOKIE’, ‘wordpress_’ . COOKIEHASH); COOKIEHASH - Defines an MD5 hash of the site’s domain name for use in user and password cookie names. COOKIEPATH - Defines the path name to be used in setting and retrieving cookies. If not already set, will be the domain name in which WordPress is installed. On MultiSite installs, will be the subdomain name, or the domain name including the directory of the Site. FORCE_SSL_ADMIN - Enforces the use of SSL for Admin access. Normally, this is disabled. To force SSL for all Admin pages, you can: define(‘FORCE_SSL_ADMIN’, true); FORCE_SSL_LOGIN - Enforces the use of SSL for site logins. Normally, this is disabled. To force SSL for login requests, you can: define(‘FORCE_SSL_LOGIN’, true); SITECOOKIEPATH - Sets the cookie path for normal site cookies. If not set, this will take the value define(‘SITECOOKIEPATH’, preg_replace(‘|https?://[^/]+|i’, ”, get_option(‘siteurl’) . ‘/’ ) ); WP_CONTENT_DIR - Sets the name of the content directory. Normally, this is ‘wp-content’. To change this, you can: define(‘WP_CONTENT_DIR’, ‘mycontentdirectory’); This can also be obtained by using plugin_dir_path() WP_CONTENT_URL - Sets the URL for the content directory references. if you change the WP_CONTENT_DIR, you will also need to change this to match the directory name for http requests. WP_DEBUG_DISPLAY - Controls display of errors. The default is to use the display_errors setting and not force errors to be displayed. To force errors to display, you can: define(‘WP_DEBUG_DISPLAY’, true); WP_DEBUG_LOG - Controls error logging to the file wp-content/debug.log. The default is no logging. To change this, you can: define(‘WP_DEBUG_LOG’, true); WP_DEFAULT_THEME - Sets the default theme. The current version of WordPress assumes a default theme of ‘twentyeleven’. If you want to change this, you can: define(‘WP_DEFAULT_THEME’, ‘mydefaulttheme’); WP_PLUGIN_DIR - Sets the directory for plugin files. The default is ‘plugins’. To change this, you can: define(‘WP_PLUGIN_DIR’, ‘/newplugindir’); WP_PLUGIN_URL - Sets the URL for the plugin directory. If you change the WP_PLUGIN_DIR, you will also need to change this to match the directory name for http requests. If you have compatibility issues with some plugins, you can set an additional value, as in: define(‘PLUGINDIR’, ‘/wpdir/wp-content/plugins’);. WPMU_PLUGIN_DIR - Sets the directory to store the Must Use plugins. The default location is /mu-plugins. To change this, you can: define(‘WPMU_PLUGIN_DIR’, ‘/requiredplugins’); WPMU_PLUGIN_URL - Sets the URL for the Must Use plugin directory. If you change the WPMU_PLUGIN_DIR, you will also need to change this to match the directory name for http requests. Capability Settings These can be used to control certain behaviors that users are allowed to perform. Some of these are confusing because you are turning “on” the ability to “disallow” a feature. So be careful on how you’re declaring these values. Most of these are used in the wp-includes/capabilities.php file, but if you want to change the settings, you should add your settings to your wp-config.php file. ALLOW_UNFILTERED_UPLOADS - Allows unfiltered uploads. You can: define(‘ALLOW_UNFILTERED_UPLOADS’, true); to enable users to upload files without filtering. Be careful: this is a potential security risk. DISALLOW_FILE_EDIT - Allows users to edit theme and plugin files. If you do not want your users to be able to edit these files, you can change this: define(‘DISALLOW_FILE_EDIT’, true); DISALLOW_FILE_MODS - Allows users to update theme and plugin files via the WordPress Repository. If you do not want your users to be able to update their WordPress install, you can change this: define(‘DISALLOW_FILE_MODS’, true); DISALLOW_UNFILTERED_HTML - Disables the ability to allow unfiltered HTML. Using define(‘DISALLOW_UNFILTERED_HTML’, false); will turn off the ability to allow unfiltered HTML. WP_CACHE - Enables the built-in WordPress caching capability. If you want to enable this caching, you can: define(‘WP_CACHE’, true); WP_USE_THEMES - Declared in /index.php. Tells WordPress whether or not use load it’s template engine. If you want access to WordPress APIs but don’t want or need the overhead of the template engine, define this to false: define(‘WP_USE_THEMES’, false); Script Control These settings control how scripts (Javascript and CSS) are handled by the system. COMPRESS_CSS - Compresses CSS. To enable CSS compression, you can: define(‘COMPRESS_CSS’, true); COMPRESS_SCRIPTS - Compresses scripts. To enable compression, you can: define(‘COMPRESS_SCRIPTS’, true); CONCATENATE_SCRIPTS - Concatenates Javascript and CSS files. To enable, you can define(‘CONCATENATE_SCRIPTS’, true); ENFORCE_GZIP - Forces gzip for compressoin of data sent to browsers. The default setting is to use the mod_deflate Apache module. If your host does not have this installed, you can: SCRIPT_DEBUG - Include the development (or non-minified) versions of all Javascript and CSS files. It also disabled compression and concatenation. To enable, you can: define(‘SCRIPT_DEBUG’, true); Optimization Settings These values can be used to control and optimize your WordPress install. AUTOSAVE_INTERVAL - Sets the interval for saving revisions while editing posts. CORE_UPGRADE_SKIP_NEW_BUNDLED - Enables skipping of theme and plugin updates when upgrading WordPress. DOING_AJAX - Set to TRUE when processing an AJAX request. EMPTY_TRASH_DAYS - Sets the number of days before trashed items are removed. IMAGE_EDIT_OVERWRITE - Allows overwriting images when editing them. MEDIA_TRASH - Enables the trash function for Media files. WP_MEMORY_LIMIT - Sets the memory limit used. WP_MAX_MEMORY_LIMIT - Controls the maximum memory size used. Some WordPress processes require more memory. This setting controls the upper limit used by these high memory use procedures. SHORTINIT - Turns on only the core WordPress functions. Often used when interfacing to other platforms. WP_POST_REVISIONS - Sets the maximum number of revisions to save. If set to FALSE it will be unlimited, an integer set the maximum number of revisions to save. MultiSite Settings These values control how WordPress MultiSite behaves. NOBLOGREDIRECT - Sets the URL to redirect visitors to when they request a non-existent MultiSite blog. The default is ‘%siteurl%’, which is the default site. If you wish to use a different location, you can: define(‘NOBLOGREDIRECT’, ‘mynewdomain.com’); WP_ALLOW_MULTISITE - Turns on MultiSite. Just enabling this using define(‘WP_ALLOW_MULTISITE’, true); does not by itself make your WordPress install a MultiSite install. It just starts the process. When you add this to your wp-config.php file, it turns on the Network menu in the Admin. This allows you to make certain choices and continue the setup process for your MultiSite install. WPMU_ACCEL_REDIRECT - When using Apache X-Sendfile for quicker loading, this helps you turn it on natively in WordPress for MultiSites. To enable, you can: define(‘WPMU_ACCEL_REDIRECT’, true); ABSPATH Definitions: 5 References: 597 ADMIN_COOKIE_PATH Definitions: 3 References: 8 AKISMET_DELETE_LIMIT Definitions: 1 References: 3 AKISMET_VERSION Definitions: 1 References: 8 AKISMET__MINIMUM_WP_VERSION Definitions: 1 References: 3 AKISMET__PLUGIN_DIR Definitions: 1 References: 7 AKISMET__PLUGIN_URL Definitions: 1 References: 5 ARRAY_A Definitions: 1 References: 71 ARRAY_N Definitions: 1 References: 16 ATOM Definitions: 1 References: 10 AUTH_COOKIE Definitions: 1 References: 12 AUTH_KEY Definitions: 1 References: 4 AUTH_SALT Definitions: 1 References: 3 AUTOSAVE_INTERVAL Definitions: 1 References: 3 BACKGROUND_COLOR Definitions: 1 References: 3 BACKGROUND_IMAGE Definitions: 1 References: 3 BLOGUPLOADDIR Definitions: 1 References: 5 BLOG_ID_CURRENT_SITE Definitions: 1 References: 3 COMMENTS_TEMPLATE Definitions: 1 References: 2 COOKIEHASH Definitions: 2 References: 29 COOKIEPATH Definitions: 2 References: 17 COOKIE_DOMAIN Definitions: 3 References: 28 CRLF Definitions: 1 References: 37 CUSTOM_TAGS Definitions: 1 References: 3 DAY_IN_SECONDS Definitions: 1 References: 33 DB_CHARSET Definitions: 1 References: 3 DB_COLLATE Definitions: 1 References: 6 DB_HOST Definitions: 2 References: 4 DB_NAME Definitions: 2 References: 5 DB_PASSWORD Definitions: 2 References: 4 DB_USER Definitions: 2 References: 4 DOING_AJAX Definitions: 2 References: 34 DOING_AUTOSAVE Definitions: 1 References: 4 DOING_CRON Definitions: 1 References: 24 DOMAIN_CURRENT_SITE Definitions: 1 References: 3 EBML_ID_ASPECTRATIOTYPE Definitions: 1 References: 3 EBML_ID_ATTACHEDFILE Definitions: 1 References: 3 EBML_ID_ATTACHMENTLINK Definitions: 1 References: 2 EBML_ID_ATTACHMENTS Definitions: 1 References: 3 EBML_ID_AUDIO Definitions: 1 References: 4 EBML_ID_BITDEPTH Definitions: 1 References: 3 EBML_ID_CHANNELPOSITIONS Definitions: 1 References: 3 EBML_ID_CHANNELS Definitions: 1 References: 3 EBML_ID_CHAPCOUNTRY Definitions: 1 References: 3 EBML_ID_CHAPLANGUAGE Definitions: 1 References: 3 EBML_ID_CHAPPROCESS Definitions: 1 References: 2 EBML_ID_CHAPPROCESSCODECID Definitions: 1 References: 2 EBML_ID_CHAPPROCESSCOMMAND Definitions: 1 References: 2 EBML_ID_CHAPPROCESSDATA Definitions: 1 References: 2 EBML_ID_CHAPPROCESSPRIVATE Definitions: 1 References: 2 EBML_ID_CHAPPROCESSTIME Definitions: 1 References: 2 EBML_ID_CHAPSTRING Definitions: 1 References: 3 EBML_ID_CHAPTERATOM Definitions: 1 References: 4 EBML_ID_CHAPTERDISPLAY Definitions: 1 References: 4 EBML_ID_CHAPTERFLAGENABLED Definitions: 1 References: 3 EBML_ID_CHAPTERFLAGHIDDEN Definitions: 1 References: 3 EBML_ID_CHAPTERPHYSICALEQUIV Definitions: 1 References: 2 EBML_ID_CHAPTERS Definitions: 1 References: 3 EBML_ID_CHAPTERSEGMENTEDITIONUID Definitions: 1 References: 3 EBML_ID_CHAPTERSEGMENTUID Definitions: 1 References: 3 EBML_ID_CHAPTERTIMEEND Definitions: 1 References: 3 EBML_ID_CHAPTERTIMESTART Definitions: 1 References: 3 EBML_ID_CHAPTERTRACK Definitions: 1 References: 4 EBML_ID_CHAPTERTRACKNUMBER Definitions: 1 References: 3 EBML_ID_CHAPTERTRANSLATE Definitions: 1 References: 3 EBML_ID_CHAPTERTRANSLATECODEC Definitions: 1 References: 3 EBML_ID_CHAPTERTRANSLATEEDITIONUID Definitions: 1 References: 3 EBML_ID_CHAPTERTRANSLATEID Definitions: 1 References: 3 EBML_ID_CHAPTERUID Definitions: 1 References: 3 EBML_ID_CLUSTER Definitions: 1 References: 5 EBML_ID_CLUSTERBLOCK Definitions: 1 References: 5 EBML_ID_CLUSTERBLOCKADDID Definitions: 1 References: 2 EBML_ID_CLUSTERBLOCKADDITIONAL Definitions: 1 References: 2 EBML_ID_CLUSTERBLOCKADDITIONID Definitions: 1 References: 2 EBML_ID_CLUSTERBLOCKADDITIONS Definitions: 1 References: 2 EBML_ID_CLUSTERBLOCKDURATION Definitions: 1 References: 3 EBML_ID_CLUSTERBLOCKGROUP Definitions: 1 References: 4 EBML_ID_CLUSTERBLOCKMORE Definitions: 1 References: 2 EBML_ID_CLUSTERBLOCKVIRTUAL Definitions: 1 References: 2 EBML_ID_CLUSTERCODECSTATE Definitions: 1 References: 3 EBML_ID_CLUSTERDELAY Definitions: 1 References: 2 EBML_ID_CLUSTERDURATION Definitions: 1 References: 2 EBML_ID_CLUSTERENCRYPTEDBLOCK Definitions: 1 References: 2 EBML_ID_CLUSTERFRAMENUMBER Definitions: 1 References: 2 EBML_ID_CLUSTERLACENUMBER Definitions: 1 References: 2 EBML_ID_CLUSTERPOSITION Definitions: 1 References: 3 EBML_ID_CLUSTERPREVSIZE Definitions: 1 References: 3 EBML_ID_CLUSTERREFERENCEBLOCK Definitions: 1 References: 3 EBML_ID_CLUSTERREFERENCEPRIORITY Definitions: 1 References: 3 EBML_ID_CLUSTERREFERENCEVIRTUAL Definitions: 1 References: 2 EBML_ID_CLUSTERSILENTTRACKNUMBER Definitions: 1 References: 3 EBML_ID_CLUSTERSILENTTRACKS Definitions: 1 References: 4 EBML_ID_CLUSTERSIMPLEBLOCK Definitions: 1 References: 7 EBML_ID_CLUSTERSLICES Definitions: 1 References: 2 EBML_ID_CLUSTERTIMECODE Definitions: 1 References: 3 EBML_ID_CLUSTERTIMESLICE Definitions: 1 References: 2 EBML_ID_CODECDECODEALL Definitions: 1 References: 3 EBML_ID_CODECDOWNLOADURL Definitions: 1 References: 2 EBML_ID_CODECID Definitions: 1 References: 3 EBML_ID_CODECINFOURL Definitions: 1 References: 2 EBML_ID_CODECNAME Definitions: 1 References: 3 EBML_ID_CODECPRIVATE Definitions: 1 References: 4 EBML_ID_CODECSETTINGS Definitions: 1 References: 2 EBML_ID_COLOURSPACE Definitions: 1 References: 3 EBML_ID_CONTENTCOMPALGO Definitions: 1 References: 3 EBML_ID_CONTENTCOMPRESSION Definitions: 1 References: 4 EBML_ID_CONTENTCOMPSETTINGS Definitions: 1 References: 3 EBML_ID_CONTENTENCALGO Definitions: 1 References: 3 EBML_ID_CONTENTENCKEYID Definitions: 1 References: 3 EBML_ID_CONTENTENCODING Definitions: 1 References: 3 EBML_ID_CONTENTENCODINGORDER Definitions: 1 References: 3 EBML_ID_CONTENTENCODINGS Definitions: 1 References: 4 EBML_ID_CONTENTENCODINGSCOPE Definitions: 1 References: 3 EBML_ID_CONTENTENCODINGTYPE Definitions: 1 References: 3 EBML_ID_CONTENTENCRYPTION Definitions: 1 References: 4 EBML_ID_CONTENTSIGALGO Definitions: 1 References: 3 EBML_ID_CONTENTSIGHASHALGO Definitions: 1 References: 3 EBML_ID_CONTENTSIGKEYID Definitions: 1 References: 3 EBML_ID_CONTENTSIGNATURE Definitions: 1 References: 3 EBML_ID_CRC32 Definitions: 1 References: 3 EBML_ID_CUEBLOCKNUMBER Definitions: 1 References: 3 EBML_ID_CUECLUSTERPOSITION Definitions: 1 References: 3 EBML_ID_CUECODECSTATE Definitions: 1 References: 3 EBML_ID_CUEPOINT Definitions: 1 References: 3 EBML_ID_CUEREFCLUSTER Definitions: 1 References: 2 EBML_ID_CUEREFCODECSTATE Definitions: 1 References: 2 EBML_ID_CUEREFERENCE Definitions: 1 References: 2 EBML_ID_CUEREFNUMBER Definitions: 1 References: 2 EBML_ID_CUEREFTIME Definitions: 1 References: 2 EBML_ID_CUES Definitions: 1 References: 3 EBML_ID_CUETIME Definitions: 1 References: 3 EBML_ID_CUETRACK Definitions: 1 References: 3 EBML_ID_CUETRACKPOSITIONS Definitions: 1 References: 4 EBML_ID_DATEUTC Definitions: 1 References: 3 EBML_ID_DEFAULTDURATION Definitions: 1 References: 3 EBML_ID_DISPLAYHEIGHT Definitions: 1 References: 3 EBML_ID_DISPLAYUNIT Definitions: 1 References: 3 EBML_ID_DISPLAYWIDTH Definitions: 1 References: 3 EBML_ID_DOCTYPE Definitions: 1 References: 3 EBML_ID_DOCTYPEREADVERSION Definitions: 1 References: 3 EBML_ID_DOCTYPEVERSION Definitions: 1 References: 3 EBML_ID_DURATION Definitions: 1 References: 3 EBML_ID_EBML Definitions: 1 References: 3 EBML_ID_EBMLMAXIDLENGTH Definitions: 1 References: 3 EBML_ID_EBMLMAXSIZELENGTH Definitions: 1 References: 3 EBML_ID_EBMLREADVERSION Definitions: 1 References: 3 EBML_ID_EBMLVERSION Definitions: 1 References: 3 EBML_ID_EDITIONENTRY Definitions: 1 References: 3 EBML_ID_EDITIONFLAGDEFAULT Definitions: 1 References: 3 EBML_ID_EDITIONFLAGHIDDEN Definitions: 1 References: 3 EBML_ID_EDITIONFLAGORDERED Definitions: 1 References: 3 EBML_ID_EDITIONUID Definitions: 1 References: 3 EBML_ID_FILEDATA Definitions: 1 References: 4 EBML_ID_FILEDESCRIPTION Definitions: 1 References: 3 EBML_ID_FILEMIMETYPE Definitions: 1 References: 3 EBML_ID_FILENAME Definitions: 1 References: 3 EBML_ID_FILEREFERRAL Definitions: 1 References: 2 EBML_ID_FILEUID Definitions: 1 References: 3 EBML_ID_FLAGDEFAULT Definitions: 1 References: 3 EBML_ID_FLAGENABLED Definitions: 1 References: 3 EBML_ID_FLAGFORCED Definitions: 1 References: 3 EBML_ID_FLAGINTERLACED Definitions: 1 References: 3 EBML_ID_FLAGLACING Definitions: 1 References: 3 EBML_ID_GAMMAVALUE Definitions: 1 References: 3 EBML_ID_INFO Definitions: 1 References: 3 EBML_ID_LANGUAGE Definitions: 1 References: 3 EBML_ID_MAXBLOCKADDITIONID Definitions: 1 References: 3 EBML_ID_MAXCACHE Definitions: 1 References: 3 EBML_ID_MINCACHE Definitions: 1 References: 3 EBML_ID_MUXINGAPP Definitions: 1 References: 3 EBML_ID_NAME Definitions: 1 References: 3 EBML_ID_NEXTFILENAME Definitions: 1 References: 3 EBML_ID_NEXTUID Definitions: 1 References: 3 EBML_ID_OLDSTEREOMODE Definitions: 1 References: 3 EBML_ID_OUTPUTSAMPLINGFREQUENCY Definitions: 1 References: 3 EBML_ID_PIXELCROPBOTTOM Definitions: 1 References: 3 EBML_ID_PIXELCROPLEFT Definitions: 1 References: 3 EBML_ID_PIXELCROPRIGHT Definitions: 1 References: 3 EBML_ID_PIXELCROPTOP Definitions: 1 References: 3 EBML_ID_PIXELHEIGHT Definitions: 1 References: 3 EBML_ID_PIXELWIDTH Definitions: 1 References: 3 EBML_ID_PREVFILENAME Definitions: 1 References: 3 EBML_ID_PREVUID Definitions: 1 References: 3 EBML_ID_SAMPLINGFREQUENCY Definitions: 1 References: 3 EBML_ID_SEEK Definitions: 1 References: 3 EBML_ID_SEEKHEAD Definitions: 1 References: 3 EBML_ID_SEEKID Definitions: 1 References: 3 EBML_ID_SEEKPOSITION Definitions: 1 References: 3 EBML_ID_SEGMENT Definitions: 1 References: 3 EBML_ID_SEGMENTFAMILY Definitions: 1 References: 3 EBML_ID_SEGMENTFILENAME Definitions: 1 References: 3 EBML_ID_SEGMENTUID Definitions: 1 References: 3 EBML_ID_SIMPLETAG Definitions: 1 References: 5 EBML_ID_STEREOMODE Definitions: 1 References: 3 EBML_ID_TAG Definitions: 1 References: 3 EBML_ID_TAGATTACHMENTUID Definitions: 1 References: 3 EBML_ID_TAGBINARY Definitions: 1 References: 3 EBML_ID_TAGCHAPTERUID Definitions: 1 References: 3 EBML_ID_TAGDEFAULT Definitions: 1 References: 3 EBML_ID_TAGEDITIONUID Definitions: 1 References: 3 EBML_ID_TAGLANGUAGE Definitions: 1 References: 3 EBML_ID_TAGNAME Definitions: 1 References: 3 EBML_ID_TAGS Definitions: 1 References: 3 EBML_ID_TAGSTRING Definitions: 1 References: 3 EBML_ID_TAGTRACKUID Definitions: 1 References: 3 EBML_ID_TARGETS Definitions: 1 References: 3 EBML_ID_TARGETTYPE Definitions: 1 References: 3 EBML_ID_TARGETTYPEVALUE Definitions: 1 References: 3 EBML_ID_TIMECODESCALE Definitions: 1 References: 3 EBML_ID_TITLE Definitions: 1 References: 3 EBML_ID_TRACKENTRY Definitions: 1 References: 3 EBML_ID_TRACKNUMBER Definitions: 1 References: 3 EBML_ID_TRACKOFFSET Definitions: 1 References: 2 EBML_ID_TRACKOVERLAY Definitions: 1 References: 2 EBML_ID_TRACKS Definitions: 1 References: 3 EBML_ID_TRACKTIMECODESCALE Definitions: 1 References: 3 EBML_ID_TRACKTRANSLATE Definitions: 1 References: 2 EBML_ID_TRACKTRANSLATECODEC Definitions: 1 References: 2 EBML_ID_TRACKTRANSLATEEDITIONUID Definitions: 1 References: 2 EBML_ID_TRACKTRANSLATETRACKID Definitions: 1 References: 2 EBML_ID_TRACKTYPE Definitions: 1 References: 3 EBML_ID_TRACKUID Definitions: 1 References: 3 EBML_ID_VIDEO Definitions: 1 References: 4 EBML_ID_VOID Definitions: 1 References: 3 EBML_ID_WRITINGAPP Definitions: 1 References: 3 EMPTY_TRASH_DAYS Definitions: 1 References: 28 EP_ALL Definitions: 1 References: 1 EP_ALL_ARCHIVES Definitions: 1 References: 2 EP_ATTACHMENT Definitions: 1 References: 3 EP_AUTHORS Definitions: 1 References: 3 EP_CATEGORIES Definitions: 1 References: 3 EP_COMMENTS Definitions: 1 References: 3 EP_DATE Definitions: 1 References: 3 EP_DAY Definitions: 1 References: 3 EP_MONTH Definitions: 1 References: 3 EP_NONE Definitions: 1 References: 6 EP_PAGES Definitions: 1 References: 4 EP_PERMALINK Definitions: 1 References: 5 EP_ROOT Definitions: 1 References: 4 EP_SEARCH Definitions: 1 References: 3 EP_TAGS Definitions: 1 References: 3 EP_YEAR Definitions: 1 References: 3 EZSQL_VERSION Definitions: 1 References: 1 FORCE_SSL_ADMIN Definitions: 1 References: 3 FORCE_SSL_LOGIN Definitions: 1 References: 3 FS_CHMOD_DIR Definitions: 1 References: 17 FS_CHMOD_FILE Definitions: 1 References: 21 FS_CONNECT_TIMEOUT Definitions: 1 References: 5 FS_TIMEOUT Definitions: 2 References: 8 FTP_ASCII Definitions: 1 References: 21 FTP_AUTOASCII Definitions: 1 References: 9 FTP_BINARY Definitions: 1 References: 19 FTP_FORCE Definitions: 1 References: 3 GETID3_FLV_TAG_AUDIO Definitions: 1 References: 2 GETID3_FLV_TAG_META Definitions: 1 References: 2 GETID3_FLV_TAG_VIDEO Definitions: 1 References: 2 GETID3_FLV_VIDEO_H263 Definitions: 1 References: 3 GETID3_FLV_VIDEO_H264 Definitions: 1 References: 3 GETID3_FLV_VIDEO_SCREEN Definitions: 1 References: 2 GETID3_FLV_VIDEO_SCREENV2 Definitions: 1 References: 2 GETID3_FLV_VIDEO_VP6FLV Definitions: 1 References: 2 GETID3_FLV_VIDEO_VP6FLV_ALPHA Definitions: 1 References: 2 GETID3_HELPERAPPSDIR Definitions: 1 References: 11 GETID3_INCLUDEPATH Definitions: 1 References: 24 GETID3_MP3_VALID_CHECK_FRAMES Definitions: 1 References: 4 GETID3_OS_ISWINDOWS Definitions: 1 References: 7 GETID3_TEMP_DIR Definitions: 1 References: 6 H264_AVC_SEQUENCE_HEADER Definitions: 1 References: 2 H264_PROFILE_BASELINE Definitions: 1 References: 1 H264_PROFILE_EXTENDED Definitions: 1 References: 1 H264_PROFILE_HIGH Definitions: 1 References: 2 H264_PROFILE_HIGH10 Definitions: 1 References: 2 H264_PROFILE_HIGH422 Definitions: 1 References: 2 H264_PROFILE_HIGH444 Definitions: 1 References: 2 H264_PROFILE_HIGH444_PREDICTIVE Definitions: 1 References: 2 H264_PROFILE_MAIN Definitions: 1 References: 1 HEADER_IMAGE Definitions: 3 References: 5 HEADER_IMAGE_HEIGHT Definitions: 3 References: 7 HEADER_IMAGE_WIDTH Definitions: 3 References: 10 HEADER_TEXTCOLOR Definitions: 3 References: 7 HOUR_IN_SECONDS Definitions: 1 References: 45 IFRAME_REQUEST Definitions: 8 References: 12 IS_PROFILE_PAGE Definitions: 2 References: 24 LANGDIR Definitions: 2 References: 4 LOGGED_IN_COOKIE Definitions: 1 References: 12 LOGGED_IN_KEY Definitions: 1 References: 3 LOGGED_IN_SALT Definitions: 1 References: 3 MAGPIE_CACHE_AGE Definitions: 1 References: 3 MAGPIE_CACHE_DIR Definitions: 1 References: 3 MAGPIE_CACHE_FRESH_ONLY Definitions: 1 References: 2 MAGPIE_CACHE_ON Definitions: 1 References: 4 MAGPIE_DEBUG Definitions: 1 References: 10 MAGPIE_FETCH_TIME_OUT Definitions: 1 References: 3 MAGPIE_INITALIZED Definitions: 1 References: 2 MAGPIE_USER_AGENT Definitions: 2 References: 3 MAGPIE_USE_GZIP Definitions: 1 References: 2 MEDIA_TRASH Definitions: 1 References: 13 MINUTE_IN_SECONDS Definitions: 1 References: 9 MULTISITE Definitions: 2 References: 12 MUPLUGINDIR Definitions: 1 References: 2 NONCE_KEY Definitions: 1 References: 3 NONCE_SALT Definitions: 1 References: 3 NO_HEADER_TEXT Definitions: 2 References: 4 OBJECT Definitions: 1 References: 44 OBJECT_K Definitions: 1 References: 4 PASS_COOKIE Definitions: 1 References: 4 PATH_CURRENT_SITE Definitions: 1 References: 3 PCLZIP_ATT_FILE_COMMENT Definitions: 1 References: 4 PCLZIP_ATT_FILE_CONTENT Definitions: 1 References: 4 PCLZIP_ATT_FILE_MTIME Definitions: 1 References: 4 PCLZIP_ATT_FILE_NAME Definitions: 1 References: 6 PCLZIP_ATT_FILE_NEW_FULL_NAME Definitions: 1 References: 4 PCLZIP_ATT_FILE_NEW_SHORT_NAME Definitions: 1 References: 4 PCLZIP_CB_POST_ADD Definitions: 1 References: 7 PCLZIP_CB_POST_DELETE Definitions: 1 References: 2 PCLZIP_CB_POST_EXTRACT Definitions: 1 References: 13 PCLZIP_CB_POST_LIST Definitions: 1 References: 2 PCLZIP_CB_PRE_ADD Definitions: 1 References: 7 PCLZIP_CB_PRE_DELETE Definitions: 1 References: 2 PCLZIP_CB_PRE_EXTRACT Definitions: 1 References: 13 PCLZIP_CB_PRE_LIST Definitions: 1 References: 2 PCLZIP_ERROR_EXTERNAL Definitions: 1 References: 6 PCLZIP_ERR_ALREADY_A_DIRECTORY Definitions: 1 References: 2 PCLZIP_ERR_BAD_CHECKSUM Definitions: 1 References: 3 PCLZIP_ERR_BAD_EXTENSION Definitions: 1 References: 3 PCLZIP_ERR_BAD_EXTRACTED_FILE Definitions: 1 References: 3 PCLZIP_ERR_BAD_FORMAT Definitions: 1 References: 14 PCLZIP_ERR_DELETE_FILE_FAIL Definitions: 1 References: 3 PCLZIP_ERR_DIRECTORY_RESTRICTION Definitions: 1 References: 4 PCLZIP_ERR_DIR_CREATE_FAIL Definitions: 1 References: 4 PCLZIP_ERR_FILENAME_TOO_LONG Definitions: 1 References: 3 PCLZIP_ERR_INVALID_ARCHIVE_ZIP Definitions: 1 References: 8 PCLZIP_ERR_INVALID_ATTRIBUTE_VALUE Definitions: 1 References: 11 PCLZIP_ERR_INVALID_OPTION_VALUE Definitions: 1 References: 11 PCLZIP_ERR_INVALID_PARAMETER Definitions: 1 References: 24 PCLZIP_ERR_INVALID_ZIP Definitions: 1 References: 3 PCLZIP_ERR_MISSING_FILE Definitions: 1 References: 8 PCLZIP_ERR_MISSING_OPTION_VALUE Definitions: 1 References: 12 PCLZIP_ERR_NO_ERROR Definitions: 1 References: 6 PCLZIP_ERR_READ_OPEN_FAIL Definitions: 1 References: 16 PCLZIP_ERR_RENAME_FILE_FAIL Definitions: 1 References: 3 PCLZIP_ERR_UNSUPPORTED_COMPRESSION Definitions: 1 References: 4 PCLZIP_ERR_UNSUPPORTED_ENCRYPTION Definitions: 1 References: 5 PCLZIP_ERR_USER_ABORTED Definitions: 1 References: 7 PCLZIP_ERR_WRITE_OPEN_FAIL Definitions: 1 References: 7 PCLZIP_OPT_ADD_COMMENT Definitions: 1 References: 5 PCLZIP_OPT_ADD_PATH Definitions: 1 References: 14 PCLZIP_OPT_ADD_TEMP_FILE_OFF Definitions: 1 References: 1 PCLZIP_OPT_ADD_TEMP_FILE_ON Definitions: 1 References: 1 PCLZIP_OPT_ADD_TEMP_FILE_THRESHOLD Definitions: 1 References: 1 PCLZIP_OPT_BY_EREG Definitions: 1 References: 4 PCLZIP_OPT_BY_INDEX Definitions: 1 References: 23 PCLZIP_OPT_BY_NAME Definitions: 1 References: 21 PCLZIP_OPT_BY_PREG Definitions: 1 References: 11 PCLZIP_OPT_COMMENT Definitions: 1 References: 10 PCLZIP_OPT_EXTRACT_AS_STRING Definitions: 1 References: 10 PCLZIP_OPT_EXTRACT_DIR_RESTRICTION Definitions: 1 References: 7 PCLZIP_OPT_EXTRACT_IN_OUTPUT Definitions: 1 References: 5 PCLZIP_OPT_NO_COMPRESSION Definitions: 1 References: 8 PCLZIP_OPT_PATH Definitions: 1 References: 8 PCLZIP_OPT_PREPEND_COMMENT Definitions: 1 References: 5 PCLZIP_OPT_REMOVE_ALL_PATH Definitions: 1 References: 15 PCLZIP_OPT_REMOVE_PATH Definitions: 1 References: 14 PCLZIP_OPT_REPLACE_NEWER Definitions: 1 References: 7 PCLZIP_OPT_SET_CHMOD Definitions: 1 References: 6 PCLZIP_OPT_STOP_ON_ERROR Definitions: 1 References: 14 PCLZIP_OPT_TEMP_FILE_OFF Definitions: 1 References: 13 PCLZIP_OPT_TEMP_FILE_ON Definitions: 1 References: 10 PCLZIP_OPT_TEMP_FILE_THRESHOLD Definitions: 1 References: 17 PCLZIP_READ_BLOCK_SIZE Definitions: 1 References: 34 PCLZIP_SEPARATOR Definitions: 1 References: 4 PCLZIP_TEMPORARY_DIR Definitions: 1 References: 7 PCLZIP_TEMPORARY_FILE_RATIO Definitions: 1 References: 3 PHP_INT_MIN Definitions: 1 References: 3 PLUGINDIR Definitions: 1 References: 2 PLUGINS_COOKIE_PATH Definitions: 1 References: 5 PO_MAX_LINE_LEN Definitions: 1 References: 2 RSS Definitions: 1 References: 33 SCRIPT_DEBUG Definitions: 2 References: 14 SECURE_AUTH_COOKIE Definitions: 1 References: 12 SECURE_AUTH_KEY Definitions: 1 References: 3 SECURE_AUTH_SALT Definitions: 1 References: 3 SERVICES_JSON_IN_ARR Definitions: 1 References: 10 SERVICES_JSON_IN_CMT Definitions: 1 References: 3 SERVICES_JSON_IN_OBJ Definitions: 1 References: 10 SERVICES_JSON_IN_STR Definitions: 1 References: 4 SERVICES_JSON_LOOSE_TYPE Definitions: 1 References: 4 SERVICES_JSON_SLICE Definitions: 1 References: 7 SERVICES_JSON_SUPPRESS_ERRORS Definitions: 1 References: 3 SERVICES_JSON_USE_TO_JSON Definitions: 1 References: 2 SHORTINIT Definitions: 2 References: 4 SIMPLEPIE_BUILD Definitions: 1 References: 6 SIMPLEPIE_CONSTRUCT_ALL Definitions: 1 References: 1 SIMPLEPIE_CONSTRUCT_BASE64 Definitions: 1 References: 5 SIMPLEPIE_CONSTRUCT_HTML Definitions: 1 References: 18 SIMPLEPIE_CONSTRUCT_IRI Definitions: 1 References: 60 SIMPLEPIE_CONSTRUCT_MAYBE_HTML Definitions: 1 References: 18 SIMPLEPIE_CONSTRUCT_NONE Definitions: 1 References: 5 SIMPLEPIE_CONSTRUCT_TEXT Definitions: 1 References: 258 SIMPLEPIE_CONSTRUCT_XHTML Definitions: 1 References: 8 SIMPLEPIE_FILE_SOURCE_CURL Definitions: 1 References: 2 SIMPLEPIE_FILE_SOURCE_FILE_GET_CONTENTS Definitions: 1 References: 2 SIMPLEPIE_FILE_SOURCE_FSOCKOPEN Definitions: 1 References: 2 SIMPLEPIE_FILE_SOURCE_LOCAL Definitions: 1 References: 3 SIMPLEPIE_FILE_SOURCE_NONE Definitions: 1 References: 2 SIMPLEPIE_FILE_SOURCE_REMOTE Definitions: 1 References: 11 SIMPLEPIE_IANA_LINK_RELATIONS_REGISTRY Definitions: 1 References: 19 SIMPLEPIE_LINKBACK Definitions: 1 References: 1 SIMPLEPIE_LOCATOR_ALL Definitions: 1 References: 4 SIMPLEPIE_LOCATOR_AUTODISCOVERY Definitions: 1 References: 2 SIMPLEPIE_LOCATOR_LOCAL_BODY Definitions: 1 References: 3 SIMPLEPIE_LOCATOR_LOCAL_EXTENSION Definitions: 1 References: 3 SIMPLEPIE_LOCATOR_NONE Definitions: 1 References: 2 SIMPLEPIE_LOCATOR_REMOTE_BODY Definitions: 1 References: 3 SIMPLEPIE_LOCATOR_REMOTE_EXTENSION Definitions: 1 References: 3 SIMPLEPIE_LOWERCASE Definitions: 1 References: 1 SIMPLEPIE_NAME Definitions: 1 References: 5 SIMPLEPIE_NAMESPACE_ATOM_03 Definitions: 1 References: 79 SIMPLEPIE_NAMESPACE_ATOM_10 Definitions: 1 References: 89 SIMPLEPIE_NAMESPACE_DC_10 Definitions: 1 References: 21 SIMPLEPIE_NAMESPACE_DC_11 Definitions: 1 References: 21 SIMPLEPIE_NAMESPACE_GEORSS Definitions: 1 References: 7 SIMPLEPIE_NAMESPACE_ITUNES Definitions: 1 References: 24 SIMPLEPIE_NAMESPACE_MEDIARSS Definitions: 1 References: 116 SIMPLEPIE_NAMESPACE_MEDIARSS_WRONG Definitions: 1 References: 2 SIMPLEPIE_NAMESPACE_MEDIARSS_WRONG2 Definitions: 1 References: 2 SIMPLEPIE_NAMESPACE_MEDIARSS_WRONG3 Definitions: 1 References: 2 SIMPLEPIE_NAMESPACE_MEDIARSS_WRONG4 Definitions: 1 References: 2 SIMPLEPIE_NAMESPACE_MEDIARSS_WRONG5 Definitions: 1 References: 2 SIMPLEPIE_NAMESPACE_RDF Definitions: 1 References: 20 SIMPLEPIE_NAMESPACE_RSS_090 Definitions: 1 References: 23 SIMPLEPIE_NAMESPACE_RSS_10 Definitions: 1 References: 23 SIMPLEPIE_NAMESPACE_RSS_20 Definitions: 1 References: 50 SIMPLEPIE_NAMESPACE_W3C_BASIC_GEO Definitions: 1 References: 10 SIMPLEPIE_NAMESPACE_XHTML Definitions: 1 References: 3 SIMPLEPIE_NAMESPACE_XML Definitions: 1 References: 5 SIMPLEPIE_PCRE_HTML_ATTRIBUTE Definitions: 1 References: 4 SIMPLEPIE_PCRE_XML_ATTRIBUTE Definitions: 1 References: 3 SIMPLEPIE_SAME_CASE Definitions: 1 References: 1 SIMPLEPIE_TYPE_ALL Definitions: 1 References: 2 SIMPLEPIE_TYPE_ATOM_03 Definitions: 1 References: 3 SIMPLEPIE_TYPE_ATOM_10 Definitions: 1 References: 3 SIMPLEPIE_TYPE_ATOM_ALL Definitions: 1 References: 2 SIMPLEPIE_TYPE_NONE Definitions: 1 References: 3 SIMPLEPIE_TYPE_RSS_090 Definitions: 1 References: 4 SIMPLEPIE_TYPE_RSS_091 Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_091_NETSCAPE Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_091_USERLAND Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_092 Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_093 Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_094 Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_10 Definitions: 1 References: 4 SIMPLEPIE_TYPE_RSS_20 Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_ALL Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_RDF Definitions: 1 References: 2 SIMPLEPIE_TYPE_RSS_SYNDICATION Definitions: 1 References: 7 SIMPLEPIE_UPPERCASE Definitions: 1 References: 1 SIMPLEPIE_URL Definitions: 1 References: 3 SIMPLEPIE_USERAGENT Definitions: 1 References: 4 SIMPLEPIE_VERSION Definitions: 1 References: 4 SITECOOKIEPATH Definitions: 2 References: 20 SITE_ID_CURRENT_SITE Definitions: 1 References: 3 STYLESHEETPATH Definitions: 1 References: 8 SUBDOMAIN_INSTALL Definitions: 3 References: 13 TEMPLATEPATH Definitions: 1 References: 9 TEST_COOKIE Definitions: 1 References: 5 UPLOADBLOGSDIR Definitions: 1 References: 5 UPLOADS Definitions: 1 References: 7 USER_COOKIE Definitions: 1 References: 4 VHOST Definitions: 2 References: 11 WEEK_IN_SECONDS Definitions: 1 References: 6 WPINC Definitions: 5 References: 204 WPLANG Definitions: 1 References: 22 WPMU_ACCEL_REDIRECT Definitions: 1 References: 3 WPMU_PLUGIN_DIR Definitions: 1 References: 20 WPMU_PLUGIN_URL Definitions: 1 References: 3 WPMU_SENDFILE Definitions: 1 References: 3 WP_ADMIN Definitions: 4 References: 10 WP_ALLOW_REPAIR Definitions: 2 References: 3 WP_BLOG_ADMIN Definitions: 1 References: 3 WP_CACHE Definitions: 1 References: 6 WP_CONTENT_DIR Definitions: 3 References: 95 WP_CONTENT_URL Definitions: 1 References: 10 WP_CRON_LOCK_TIMEOUT Definitions: 1 References: 4 WP_DEBUG Definitions: 3 References: 26 WP_DEBUG_DISPLAY Definitions: 1 References: 5 WP_DEBUG_LOG Definitions: 1 References: 5 WP_DEFAULT_THEME Definitions: 1 References: 19 WP_IMPORTING Definitions: 1 References: 7 WP_INSTALLING Definitions: 5 References: 37 WP_INSTALLING_NETWORK Definitions: 2 References: 9 WP_LANG_DIR Definitions: 2 References: 32 WP_LOAD_IMPORTERS Definitions: 2 References: 3 WP_MAIL_INTERVAL Definitions: 1 References: 3 WP_MAX_MEMORY_LIMIT Definitions: 1 References: 8 WP_MEMORY_LIMIT Definitions: 2 References: 7 WP_NETWORK_ADMIN Definitions: 2 References: 9 WP_PLUGIN_DIR Definitions: 1 References: 58 WP_PLUGIN_URL Definitions: 1 References: 4 WP_POST_REVISIONS Definitions: 1 References: 3 WP_REPAIRING Definitions: 1 References: 4 WP_SETUP_CONFIG Definitions: 1 References: 5 WP_UNINSTALL_PLUGIN Definitions: 1 References: 1 WP_USER_ADMIN Definitions: 2 References: 9 WP_USE_THEMES Definitions: 1 References: 6 WXR_VERSION Definitions: 1 References: 1 XMLRPC_REQUEST Definitions: 1 References: 8 YEAR_IN_SECONDS Definitions: 1 References: 21
If done correctly your functions.php file should now look like this at the top. add_action('init', 'start_session', 1); function start_session() { if(!session_id()) { session_start(); } add_action(‘wp_logout’, ‘end_session’); add_action(‘wp_login’, ‘end_session’); add_action(‘end_session_action’, ‘end_session’); function end_session() { session_destroy (); } You can now add data to the global $_SESSION variable that will be accessible at any point within the application during a user session by accessing the $_SESSION variable. The variable is an array; below is an example of adding data to the session array. $foo = ‘Foo Data’; $_SESSION[‘foo’] = $foo; Something to think about: If you are building a scalable or load balanced website, you may not want to use sessions. HTTP is Stateless and PHP SESSIONS are State driven. Sessions are stored and handled by the server. Routing each session to the proper server requires more complex configuration and creates a single point of failure for the users who’s sessions are stored on that server. When possible, it is best to store session information in the client’s browser. Though it may not be extremely expensive to the server resources to query session objects, it is always wise to reduce overhead whenever possible. Thank you for reading. I hope you find this article helpful and please comment below with any questions. Happy coding! ?? <end node> 5P9i0s8y19Z dt= <node>html5 1 <input required min='' max='' placeholder='' > <input type="number" min="0" max="100" step="5"> accept audio/* video/* image/* MIME_type Specifies the types of files that the server accepts (only for type="file") align left right top middle bottom Not supported in HTML5. Deprecated in HTML 4.01. Specifies the alignment of an image input (only for type="image") alt text Specifies an alternate text for images (only for type="image") autocompleteNew on off Specifies whether an <input> element should have autocomplete enabled autofocusNew autofocus Specifies that an <input> element should automatically get focus when the page loads checked checked Specifies that an <input> element should be pre-selected when the page loads (for type="checkbox" or type="radio") disabled disabled Specifies that an <input> element should be disabled formNew form_id Specifies one or more forms the <input> element belongs to formactionNew URL Specifies the URL of the file that will process the input control when the form is submitted (for type="submit" and type="image") formenctypeNew application/x-www-form-urlencoded multipart/form-data text/plain Specifies how the form-data should be encoded when submitting it to the server (for type="submit" and type="image") formmethodNew get post Defines the HTTP method for sending data to the action URL (for type="submit" and type="image") formnovalidateNew formnovalidate Defines that form elements should not be validated when submitted formtargetNew _blank _self _parent _top framename Specifies where to display the response that is received after submitting the form (for type="submit" and type="image") heightNew pixels Specifies the height of an <input> element (only for type="image") listNew datalist_id Refers to a <datalist> element that contains pre-defined options for an <input> element max New number date Specifies the maximum value for an <input> element maxlength number Specifies the maximum number of characters allowed in an <input> element min New number date Specifies a minimum value for an <input> element multiple New multiple Specifies that a user can enter more than one value in an <input> element name text Specifies the name of an <input> element patternNew regexp Specifies a regular expression that an <input> element's value is checked against placeholder New text Specifies a short hint that describes the expected value of an <input> element readonly readonly Specifies that an input field is read-only required New required Specifies that an input field must be filled out before submitting the form size number Specifies the width, in characters, of an <input> element src URL Specifies the URL of the image to use as a submit button (only for type="image") stepNew number Specifies the legal number intervals for an input field HTML5 Input Types checkbox color date datetime datetime-local email file hidden image month number password radio range reset search submit tel text time url week Specifies the type <input> element to display value text Specifies the value of an <input> element
width New pixels Specifies the width of an <input> element (only for type="image") <end node> 5P9i0s8y19Z dt= <node>reserved words 1 List of reserved names in $_POST and $_REQUEST used by WordPress 3.5 _ajax_nonce _page _per_page _signup_form _total _url _wp_http_referer _wp_original_http_referer _wp_unfiltered_html_comment _wpnonce _wpnonce-custom-header-upload aa action action2 active_post_lock add_new add_new_users addmeta admin_bar_front admin_color admin_email admin_password admin_password2 ajax align allblogs allusers alt approve_parent approved attachment attachment_id attachments auth_cookie author author_name autocomplete_type auto_draft auto-add-pages autosave background-attachment background-color background-position-x background-repeat banned_email_domains blog blog_name blog_public blog_upload_space blogname bulk_edit c calendar cat category_base category_name catslist changeit changes charset checkbox checked clear-recent-list closed comment comment_approved comment_author comment_author_email comment_author_url comment_content comment_date comment_ID comment_parent comment_post_ID comment_shortcuts comment_status comments_listing comments_popup confirmdelete connection_type content context cpage create-new-attachment createuser customize_messenger_channel customized customlink-tab date date_format date_format_custom day default-header delete delete_all delete_all2 delete_comments delete_option delete_tags delete_widget deletebookmarks deletecomment deleted deletemeta deletepost description detached dismiss display_name do edit_date email error exact excerpt features feed fetch fheight file fileupload_maxk filter find_detached first_comment first_comment_author first_comment_url first_name first_page first_post found_post_id fwidth global_terms_enabled GLOBALS gmt_offset guid height hh hidden hidden_aa hidden_jj hidden_mm hidden_mn hidden_hh history hostname hour html-upload id ID ids id_base illegal_names insert-gallery insertonlybutton interim-login item-object item-type jj json json_data key last_name limited_email_domains link_id link_image link_name link_rss link_url link_visible linkcheck locale locked log logged_in_cookie m media media_type menu menu_items menu-item menu-item-attr-title menu-item-classes menu-item-db-id menu-item-description menu-item-object menu-item-object-id menu-item-parent-id menu-item-position menu-item-target menu-item-title menu-item-type menu-item-url menu-item-xfn menu-locations menu-name message meta metakeyinput metakeyselect metavalue minute mm mn mode monthnum more move multi_number name nav-menu-locations new new_role new_slug new_title newcat newcomment_author newcomment_author_email newcomment_author_url newcontent newuser nickname no_placeholder noapi noconfirmation noredir number offset oitar option option_page order orderby p pb page page_columns page_id page_options paged pagegen_timestamp pagename parent_id pass1 pass2 password permalink_structure photo_description photo_src phperror ping_status plugin plugin_status pointer position post post_category post_data post_format post_ID post_id post_mime_type post_password post_status post_title post_type post_view postid posts preview primary_blog private_key ps public_key publish pwd query reassign_user reauth redirect redirect_to ref referredby registration registrationnotification rememberme remove-background removeheader removewidget reset-background resetheader review rich_editing robots role s same save savewidget savewidgets screen scrollto search second section selectall selection send send_password sentence short show_sticky sidebar sidebars signup_for signup_form_id site_id site_name sitename size skip-cropping spam spammed src ss stage start static status sticky subdomain_install submit subpost subpost_id super_admin tab tag tag_ID tag-name tag_base tags_input tax tax_input tag-name target taxonomy tb term text-color the-widget-id theme theme_status thumb timezone_string time_format time_format_custom title thumbnail_id trash trashed type undismiss unspam unspammed untrash untrashed url update_home_url updated upgrade upload_filetypes upload_space_check_disabled use_ssl user user_id user_login user_name username users verify-delete version visibility visible w weblog_title welcome_email welcome_user_email widget_id widget_number widget-id widget-recent-comments widget-rss width withcomments withoutcomments wp_customize wp_http_referer wp_screen_options wp-preview WPLANG x1 y1 year <end node> 5P9i0s8y19Z dt= <node>Settings 1 wp_options in the database table <end node> 5P9i0s8y19Z dt= <node>Upgrades 1 http://codex.wordpress.org/Files_Automatically_Replaced_by_Core_Upgrade When using the core upgrade function, introduced with Version 2.7, some old files, which are no longer included with the latest release, will be deleted. The list of files to be deleted is in the wp-admin/includes/update-core.php file. In addition to the files to be deleted, all other core files are replaced with the newer versions. If you have made modifications to any core files, including the WordPress Default theme files, you'll need to insure they are backed up before attempting the core upgrade. After the upgrade, you'll have to retrofit the modifications to the new core files again. Simply re-using the old modified files is NOT recommended. Files Set For Deletion $_old_files = array( // 2.0 'wp-admin/import-b2.php', 'wp-admin/import-blogger.php', 'wp-admin/import-greymatter.php', 'wp-admin/import-livejournal.php', 'wp-admin/import-mt.php', 'wp-admin/import-rss.php', 'wp-admin/import-textpattern.php', 'wp-admin/quicktags.js', 'wp-images/fade-butt.png', 'wp-images/get-firefox.png', 'wp-images/header-shadow.png', 'wp-images/smilies', 'wp-images/wp-small.png', 'wp-images/wpminilogo.png', 'wp.php', // 2.0.8 'wp-includes/js/tinymce/plugins/inlinepopups/readme.txt', // 2.1 'wp-admin/edit-form-ajax-cat.php', 'wp-admin/execute-pings.php', 'wp-admin/inline-uploading.php', 'wp-admin/link-categories.php', 'wp-admin/list-manipulation.js', 'wp-admin/list-manipulation.php', 'wp-includes/comment-functions.php', 'wp-includes/feed-functions.php', 'wp-includes/functions-compat.php', 'wp-includes/functions-formatting.php', 'wp-includes/functions-post.php', 'wp-includes/js/dbx-key.js', 'wp-includes/js/tinymce/plugins/autosave/langs/cs.js', 'wp-includes/js/tinymce/plugins/autosave/langs/sv.js', 'wp-includes/links.php', 'wp-includes/pluggable-functions.php', 'wp-includes/template-functions-author.php', 'wp-includes/template-functions-category.php', 'wp-includes/template-functions-general.php', 'wp-includes/template-functions-links.php', 'wp-includes/template-functions-post.php', 'wp-includes/wp-l10n.php', // 2.2 'wp-admin/cat-js.php', 'wp-admin/import/b2.php', 'wp-includes/js/autosave-js.php', 'wp-includes/js/list-manipulation-js.php', 'wp-includes/js/wp-ajax-js.php', // 2.3 'wp-admin/admin-db.php', 'wp-admin/cat.js', 'wp-admin/categories.js', 'wp-admin/custom-fields.js', 'wp-admin/dbx-admin-key.js', 'wp-admin/edit-comments.js', 'wp-admin/install-rtl.css', 'wp-admin/install.css', 'wp-admin/upgrade-schema.php', 'wp-admin/upload-functions.php', 'wp-admin/upload-rtl.css', 'wp-admin/upload.css', 'wp-admin/upload.js', 'wp-admin/users.js', 'wp-admin/widgets-rtl.css', 'wp-admin/widgets.css', 'wp-admin/xfn.js', 'wp-includes/js/tinymce/license.html', // 2.5 'wp-admin/css/upload.css', 'wp-admin/images/box-bg-left.gif', 'wp-admin/images/box-bg-right.gif', 'wp-admin/images/box-bg.gif', 'wp-admin/images/box-butt-left.gif', 'wp-admin/images/box-butt-right.gif', 'wp-admin/images/box-butt.gif', 'wp-admin/images/box-head-left.gif', 'wp-admin/images/box-head-right.gif', 'wp-admin/images/box-head.gif', 'wp-admin/images/heading-bg.gif', 'wp-admin/images/login-bkg-bottom.gif', 'wp-admin/images/login-bkg-tile.gif', 'wp-admin/images/notice.gif', 'wp-admin/images/toggle.gif', 'wp-admin/includes/upload.php', 'wp-admin/js/dbx-admin-key.js', 'wp-admin/js/link-cat.js', 'wp-admin/profile-update.php', 'wp-admin/templates.php', 'wp-includes/images/wlw/WpComments.png', 'wp-includes/images/wlw/WpIcon.png', 'wp-includes/images/wlw/WpWatermark.png', 'wp-includes/js/dbx.js', 'wp-includes/js/fat.js', 'wp-includes/js/list-manipulation.js', 'wp-includes/js/tinymce/langs/en.js', 'wp-includes/js/tinymce/plugins/autosave/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/autosave/langs', 'wp-includes/js/tinymce/plugins/directionality/images', 'wp-includes/js/tinymce/plugins/directionality/langs', 'wp-includes/js/tinymce/plugins/inlinepopups/css', 'wp-includes/js/tinymce/plugins/inlinepopups/images', 'wp-includes/js/tinymce/plugins/inlinepopups/jscripts', 'wp-includes/js/tinymce/plugins/paste/images', 'wp-includes/js/tinymce/plugins/paste/jscripts', 'wp-includes/js/tinymce/plugins/paste/langs', 'wp-includes/js/tinymce/plugins/spellchecker/classes/HttpClient.class.php', 'wp-includes/js/tinymce/plugins/spellchecker/classes/TinyGoogleSpell.class.php', 'wp-includes/js/tinymce/plugins/spellchecker/classes/TinyPspell.class.php', 'wp-includes/js/tinymce/plugins/spellchecker/classes/TinyPspellShell.class.php', 'wp-includes/js/tinymce/plugins/spellchecker/css/spellchecker.css', 'wp-includes/js/tinymce/plugins/spellchecker/images', 'wp-includes/js/tinymce/plugins/spellchecker/langs', 'wp-includes/js/tinymce/plugins/spellchecker/tinyspell.php', 'wp-includes/js/tinymce/plugins/wordpress/images', 'wp-includes/js/tinymce/plugins/wordpress/langs', 'wp-includes/js/tinymce/plugins/wordpress/wordpress.css', 'wp-includes/js/tinymce/plugins/wphelp', 'wp-includes/js/tinymce/themes/advanced/css', 'wp-includes/js/tinymce/themes/advanced/images', 'wp-includes/js/tinymce/themes/advanced/jscripts', 'wp-includes/js/tinymce/themes/advanced/langs', // 2.5.1 'wp-includes/js/tinymce/tiny_mce_gzip.php', // 2.6 'wp-admin/bookmarklet.php', 'wp-includes/js/jquery/jquery.dimensions.min.js', 'wp-includes/js/tinymce/plugins/wordpress/popups.css', 'wp-includes/js/wp-ajax.js', // 2.7 'wp-admin/css/press-this-ie-rtl.css', 'wp-admin/css/press-this-ie.css', 'wp-admin/css/upload-rtl.css', 'wp-admin/edit-form.php', 'wp-admin/images/comment-pill.gif', 'wp-admin/images/comment-stalk-classic.gif', 'wp-admin/images/comment-stalk-fresh.gif', 'wp-admin/images/comment-stalk-rtl.gif', 'wp-admin/images/del.png', 'wp-admin/images/gear.png', 'wp-admin/images/media-button-gallery.gif', 'wp-admin/images/media-buttons.gif', 'wp-admin/images/postbox-bg.gif', 'wp-admin/images/tab.png', 'wp-admin/images/tail.gif', 'wp-admin/js/forms.js', 'wp-admin/js/upload.js', 'wp-admin/link-import.php', 'wp-includes/images/audio.png', 'wp-includes/images/css.png', 'wp-includes/images/default.png', 'wp-includes/images/doc.png', 'wp-includes/images/exe.png', 'wp-includes/images/html.png', 'wp-includes/images/js.png', 'wp-includes/images/pdf.png', 'wp-includes/images/swf.png', 'wp-includes/images/tar.png', 'wp-includes/images/text.png', 'wp-includes/images/video.png', 'wp-includes/images/zip.png', 'wp-includes/js/tinymce/tiny_mce_config.php', 'wp-includes/js/tinymce/tiny_mce_ext.js', // 2.8 'wp-admin/js/users.js', 'wp-includes/js/swfupload/plugins/swfupload.documentready.js', 'wp-includes/js/swfupload/plugins/swfupload.graceful_degradation.js', 'wp-includes/js/swfupload/swfupload_f9.swf', 'wp-includes/js/tinymce/plugins/autosave', 'wp-includes/js/tinymce/plugins/paste/css', 'wp-includes/js/tinymce/utils/mclayer.js', 'wp-includes/js/tinymce/wordpress.css', // 2.8.5 'wp-admin/import/btt.php', 'wp-admin/import/jkw.php', // 2.9 'wp-admin/js/page.dev.js', 'wp-admin/js/page.js', 'wp-admin/js/set-post-thumbnail-handler.dev.js', 'wp-admin/js/set-post-thumbnail-handler.js', 'wp-admin/js/slug.dev.js', 'wp-admin/js/slug.js', 'wp-includes/gettext.php', 'wp-includes/js/tinymce/plugins/wordpress/js', 'wp-includes/streams.php', // MU 'README.txt', 'htaccess.dist', 'index-install.php', 'wp-admin/css/mu-rtl.css', 'wp-admin/css/mu.css', 'wp-admin/images/site-admin.png', 'wp-admin/includes/mu.php', 'wp-admin/wpmu-admin.php', 'wp-admin/wpmu-blogs.php', 'wp-admin/wpmu-edit.php', 'wp-admin/wpmu-options.php', 'wp-admin/wpmu-themes.php', 'wp-admin/wpmu-upgrade-site.php', 'wp-admin/wpmu-users.php', 'wp-includes/images/wordpress-mu.png', 'wp-includes/wpmu-default-filters.php', 'wp-includes/wpmu-functions.php', 'wpmu-settings.php', // 3.0 'wp-admin/categories.php', 'wp-admin/edit-category-form.php', 'wp-admin/edit-page-form.php', 'wp-admin/edit-pages.php', 'wp-admin/images/admin-header-footer.png', 'wp-admin/images/browse-happy.gif', 'wp-admin/images/ico-add.png', 'wp-admin/images/ico-close.png', 'wp-admin/images/ico-edit.png', 'wp-admin/images/ico-viewpage.png', 'wp-admin/images/fav-top.png', 'wp-admin/images/screen-options-left.gif', 'wp-admin/images/wp-logo-vs.gif', 'wp-admin/images/wp-logo.gif', 'wp-admin/import', 'wp-admin/js/wp-gears.dev.js', 'wp-admin/js/wp-gears.js', 'wp-admin/options-misc.php', 'wp-admin/page-new.php', 'wp-admin/page.php', 'wp-admin/rtl.css', 'wp-admin/rtl.dev.css', 'wp-admin/update-links.php', 'wp-admin/wp-admin.css', 'wp-admin/wp-admin.dev.css', 'wp-includes/js/codepress', 'wp-includes/js/codepress/engines/khtml.js', 'wp-includes/js/codepress/engines/older.js', 'wp-includes/js/jquery/autocomplete.dev.js', 'wp-includes/js/jquery/autocomplete.js', 'wp-includes/js/jquery/interface.js', 'wp-includes/js/scriptaculous/prototype.js', 'wp-includes/js/tinymce/wp-tinymce.js', // 3.1 'wp-admin/edit-attachment-rows.php', 'wp-admin/edit-link-categories.php', 'wp-admin/edit-link-category-form.php', 'wp-admin/edit-post-rows.php', 'wp-admin/images/button-grad-active-vs.png', 'wp-admin/images/button-grad-vs.png', 'wp-admin/images/fav-arrow-vs-rtl.gif', 'wp-admin/images/fav-arrow-vs.gif', 'wp-admin/images/fav-top-vs.gif', 'wp-admin/images/list-vs.png', 'wp-admin/images/screen-options-right-up.gif', 'wp-admin/images/screen-options-right.gif', 'wp-admin/images/visit-site-button-grad-vs.gif', 'wp-admin/images/visit-site-button-grad.gif', 'wp-admin/link-category.php', 'wp-admin/sidebar.php', 'wp-includes/classes.php', 'wp-includes/js/tinymce/blank.htm', 'wp-includes/js/tinymce/plugins/media/css/content.css', 'wp-includes/js/tinymce/plugins/media/img', 'wp-includes/js/tinymce/plugins/safari', // 3.2 'wp-admin/images/logo-login.gif', 'wp-admin/images/star.gif', 'wp-admin/js/list-table.dev.js', 'wp-admin/js/list-table.js', 'wp-includes/default-embeds.php', 'wp-includes/js/tinymce/plugins/wordpress/img/help.gif', 'wp-includes/js/tinymce/plugins/wordpress/img/more.gif', 'wp-includes/js/tinymce/plugins/wordpress/img/toolbars.gif', 'wp-includes/js/tinymce/themes/advanced/img/fm.gif', 'wp-includes/js/tinymce/themes/advanced/img/sflogo.png', // 3.3 'wp-admin/css/colors-classic-rtl.css', 'wp-admin/css/colors-classic-rtl.dev.css', 'wp-admin/css/colors-fresh-rtl.css', 'wp-admin/css/colors-fresh-rtl.dev.css', 'wp-admin/css/dashboard-rtl.dev.css', 'wp-admin/css/dashboard.dev.css', 'wp-admin/css/global-rtl.css', 'wp-admin/css/global-rtl.dev.css', 'wp-admin/css/global.css', 'wp-admin/css/global.dev.css', 'wp-admin/css/install-rtl.dev.css', 'wp-admin/css/login-rtl.dev.css', 'wp-admin/css/login.dev.css', 'wp-admin/css/ms.css', 'wp-admin/css/ms.dev.css', 'wp-admin/css/nav-menu-rtl.css', 'wp-admin/css/nav-menu-rtl.dev.css', 'wp-admin/css/nav-menu.css', 'wp-admin/css/nav-menu.dev.css', 'wp-admin/css/plugin-install-rtl.css', 'wp-admin/css/plugin-install-rtl.dev.css', 'wp-admin/css/plugin-install.css', 'wp-admin/css/plugin-install.dev.css', 'wp-admin/css/press-this-rtl.dev.css', 'wp-admin/css/press-this.dev.css', 'wp-admin/css/theme-editor-rtl.css', 'wp-admin/css/theme-editor-rtl.dev.css', 'wp-admin/css/theme-editor.css', 'wp-admin/css/theme-editor.dev.css', 'wp-admin/css/theme-install-rtl.css', 'wp-admin/css/theme-install-rtl.dev.css', 'wp-admin/css/theme-install.css', 'wp-admin/css/theme-install.dev.css', 'wp-admin/css/widgets-rtl.dev.css', 'wp-admin/css/widgets.dev.css', 'wp-admin/includes/internal-linking.php', 'wp-includes/images/admin-bar-sprite-rtl.png', 'wp-includes/js/jquery/ui.button.js', 'wp-includes/js/jquery/ui.core.js', 'wp-includes/js/jquery/ui.dialog.js', 'wp-includes/js/jquery/ui.draggable.js', 'wp-includes/js/jquery/ui.droppable.js', 'wp-includes/js/jquery/ui.mouse.js', 'wp-includes/js/jquery/ui.position.js', 'wp-includes/js/jquery/ui.resizable.js', 'wp-includes/js/jquery/ui.selectable.js', 'wp-includes/js/jquery/ui.sortable.js', 'wp-includes/js/jquery/ui.tabs.js', 'wp-includes/js/jquery/ui.widget.js', 'wp-includes/js/l10n.dev.js', 'wp-includes/js/l10n.js', 'wp-includes/js/tinymce/plugins/wplink/css', 'wp-includes/js/tinymce/plugins/wplink/img', 'wp-includes/js/tinymce/plugins/wplink/js', 'wp-includes/js/tinymce/themes/advanced/img/wpicons.png', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/butt2.png', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/button_bg.png', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/down_arrow.gif', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/fade-butt.png', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/separator.gif', // Don't delete, yet: 'wp-rss.php', // Don't delete, yet: 'wp-rdf.php', // Don't delete, yet: 'wp-rss2.php', // Don't delete, yet: 'wp-commentsrss2.php', // Don't delete, yet: 'wp-atom.php', // Don't delete, yet: 'wp-feed.php', // 3.4 'wp-admin/images/gray-star.png', 'wp-admin/images/logo-login.png', 'wp-admin/images/star.png', 'wp-admin/index-extra.php', 'wp-admin/network/index-extra.php', 'wp-admin/user/index-extra.php', 'wp-admin/images/screenshots/admin-flyouts.png', 'wp-admin/images/screenshots/coediting.png', 'wp-admin/images/screenshots/drag-and-drop.png', 'wp-admin/images/screenshots/help-screen.png', 'wp-admin/images/screenshots/media-icon.png', 'wp-admin/images/screenshots/new-feature-pointer.png', 'wp-admin/images/screenshots/welcome-screen.png', 'wp-includes/css/editor-buttons.css', 'wp-includes/css/editor-buttons.dev.css', 'wp-includes/js/tinymce/plugins/paste/blank.htm', 'wp-includes/js/tinymce/plugins/wordpress/css', 'wp-includes/js/tinymce/plugins/wordpress/editor_plugin.dev.js', 'wp-includes/js/tinymce/plugins/wordpress/img/embedded.png', 'wp-includes/js/tinymce/plugins/wordpress/img/more_bug.gif', 'wp-includes/js/tinymce/plugins/wordpress/img/page_bug.gif', 'wp-includes/js/tinymce/plugins/wpdialogs/editor_plugin.dev.js', 'wp-includes/js/tinymce/plugins/wpeditimage/css/editimage-rtl.css', 'wp-includes/js/tinymce/plugins/wpeditimage/editor_plugin.dev.js', 'wp-includes/js/tinymce/plugins/wpfullscreen/editor_plugin.dev.js', 'wp-includes/js/tinymce/plugins/wpgallery/editor_plugin.dev.js', 'wp-includes/js/tinymce/plugins/wpgallery/img/gallery.png', 'wp-includes/js/tinymce/plugins/wplink/editor_plugin.dev.js', // Don't delete, yet: 'wp-pass.php', // Don't delete, yet: 'wp-register.php', // 3.5 'wp-admin/gears-manifest.php', 'wp-admin/includes/manifest.php', 'wp-admin/images/archive-link.png', 'wp-admin/images/blue-grad.png', 'wp-admin/images/button-grad-active.png', 'wp-admin/images/button-grad.png', 'wp-admin/images/ed-bg-vs.gif', 'wp-admin/images/ed-bg.gif', 'wp-admin/images/fade-butt.png', 'wp-admin/images/fav-arrow-rtl.gif', 'wp-admin/images/fav-arrow.gif', 'wp-admin/images/fav-vs.png', 'wp-admin/images/fav.png', 'wp-admin/images/gray-grad.png', 'wp-admin/images/loading-publish.gif', 'wp-admin/images/logo-ghost.png', 'wp-admin/images/logo.gif', 'wp-admin/images/menu-arrow-frame-rtl.png', 'wp-admin/images/menu-arrow-frame.png', 'wp-admin/images/menu-arrows.gif', 'wp-admin/images/menu-bits-rtl-vs.gif', 'wp-admin/images/menu-bits-rtl.gif', 'wp-admin/images/menu-bits-vs.gif', 'wp-admin/images/menu-bits.gif', 'wp-admin/images/menu-dark-rtl-vs.gif', 'wp-admin/images/menu-dark-rtl.gif', 'wp-admin/images/menu-dark-vs.gif', 'wp-admin/images/menu-dark.gif', 'wp-admin/images/required.gif', 'wp-admin/images/screen-options-toggle-vs.gif', 'wp-admin/images/screen-options-toggle.gif', 'wp-admin/images/toggle-arrow-rtl.gif', 'wp-admin/images/toggle-arrow.gif', 'wp-admin/images/upload-classic.png', 'wp-admin/images/upload-fresh.png', 'wp-admin/images/white-grad-active.png', 'wp-admin/images/white-grad.png', 'wp-admin/images/widgets-arrow-vs.gif', 'wp-admin/images/widgets-arrow.gif', 'wp-admin/images/wpspin_dark.gif', 'wp-includes/images/upload.png', 'wp-includes/js/prototype.js', 'wp-includes/js/scriptaculous', 'wp-admin/css/wp-admin-rtl.dev.css', 'wp-admin/css/wp-admin.dev.css', 'wp-admin/css/media-rtl.dev.css', 'wp-admin/css/media.dev.css', 'wp-admin/css/colors-classic.dev.css', 'wp-admin/css/customize-controls-rtl.dev.css', 'wp-admin/css/customize-controls.dev.css', 'wp-admin/css/ie-rtl.dev.css', 'wp-admin/css/ie.dev.css', 'wp-admin/css/install.dev.css', 'wp-admin/css/colors-fresh.dev.css', 'wp-includes/js/customize-base.dev.js', 'wp-includes/js/json2.dev.js', 'wp-includes/js/comment-reply.dev.js', 'wp-includes/js/customize-preview.dev.js', 'wp-includes/js/wplink.dev.js', 'wp-includes/js/tw-sack.dev.js', 'wp-includes/js/wp-list-revisions.dev.js', 'wp-includes/js/autosave.dev.js', 'wp-includes/js/admin-bar.dev.js', 'wp-includes/js/quicktags.dev.js', 'wp-includes/js/wp-ajax-response.dev.js', 'wp-includes/js/wp-pointer.dev.js', 'wp-includes/js/hoverIntent.dev.js', 'wp-includes/js/colorpicker.dev.js', 'wp-includes/js/wp-lists.dev.js', 'wp-includes/js/customize-loader.dev.js', 'wp-includes/js/jquery/jquery.table-hotkeys.dev.js', 'wp-includes/js/jquery/jquery.color.dev.js', 'wp-includes/js/jquery/jquery.color.js', 'wp-includes/js/jquery/jquery.hotkeys.dev.js', 'wp-includes/js/jquery/jquery.form.dev.js', 'wp-includes/js/jquery/suggest.dev.js', 'wp-admin/js/xfn.dev.js', 'wp-admin/js/set-post-thumbnail.dev.js', 'wp-admin/js/comment.dev.js', 'wp-admin/js/theme.dev.js', 'wp-admin/js/cat.dev.js', 'wp-admin/js/password-strength-meter.dev.js', 'wp-admin/js/user-profile.dev.js', 'wp-admin/js/theme-preview.dev.js', 'wp-admin/js/post.dev.js', 'wp-admin/js/media-upload.dev.js', 'wp-admin/js/word-count.dev.js', 'wp-admin/js/plugin-install.dev.js', 'wp-admin/js/edit-comments.dev.js', 'wp-admin/js/media-gallery.dev.js', 'wp-admin/js/custom-fields.dev.js', 'wp-admin/js/custom-background.dev.js', 'wp-admin/js/common.dev.js', 'wp-admin/js/inline-edit-tax.dev.js', 'wp-admin/js/gallery.dev.js', 'wp-admin/js/utils.dev.js', 'wp-admin/js/widgets.dev.js', 'wp-admin/js/wp-fullscreen.dev.js', 'wp-admin/js/nav-menu.dev.js', 'wp-admin/js/dashboard.dev.js', 'wp-admin/js/link.dev.js', 'wp-admin/js/user-suggest.dev.js', 'wp-admin/js/postbox.dev.js', 'wp-admin/js/tags.dev.js', 'wp-admin/js/image-edit.dev.js', 'wp-admin/js/media.dev.js', 'wp-admin/js/customize-controls.dev.js', 'wp-admin/js/inline-edit-post.dev.js', 'wp-admin/js/categories.dev.js', 'wp-admin/js/editor.dev.js', 'wp-includes/js/tinymce/plugins/wpeditimage/js/editimage.dev.js', 'wp-includes/js/tinymce/plugins/wpdialogs/js/popup.dev.js', 'wp-includes/js/tinymce/plugins/wpdialogs/js/wpdialog.dev.js', 'wp-includes/js/plupload/handlers.dev.js', 'wp-includes/js/plupload/wp-plupload.dev.js', 'wp-includes/js/swfupload/handlers.dev.js', 'wp-includes/js/jcrop/jquery.Jcrop.dev.js', 'wp-includes/js/jcrop/jquery.Jcrop.js', 'wp-includes/js/jcrop/jquery.Jcrop.css', 'wp-includes/js/imgareaselect/jquery.imgareaselect.dev.js', 'wp-includes/css/wp-pointer.dev.css', 'wp-includes/css/editor.dev.css', 'wp-includes/css/jquery-ui-dialog.dev.css', 'wp-includes/css/admin-bar-rtl.dev.css', 'wp-includes/css/admin-bar.dev.css', 'wp-includes/js/jquery/ui/jquery.effects.clip.min.js', 'wp-includes/js/jquery/ui/jquery.effects.scale.min.js', 'wp-includes/js/jquery/ui/jquery.effects.blind.min.js', 'wp-includes/js/jquery/ui/jquery.effects.core.min.js', 'wp-includes/js/jquery/ui/jquery.effects.shake.min.js', 'wp-includes/js/jquery/ui/jquery.effects.fade.min.js', 'wp-includes/js/jquery/ui/jquery.effects.explode.min.js', 'wp-includes/js/jquery/ui/jquery.effects.slide.min.js', 'wp-includes/js/jquery/ui/jquery.effects.drop.min.js', 'wp-includes/js/jquery/ui/jquery.effects.highlight.min.js', 'wp-includes/js/jquery/ui/jquery.effects.bounce.min.js', 'wp-includes/js/jquery/ui/jquery.effects.pulsate.min.js', 'wp-includes/js/jquery/ui/jquery.effects.transfer.min.js', 'wp-includes/js/jquery/ui/jquery.effects.fold.min.js', 'wp-admin/images/screenshots/captions-1.png', 'wp-admin/images/screenshots/captions-2.png', 'wp-admin/images/screenshots/flex-header-1.png', 'wp-admin/images/screenshots/flex-header-2.png', 'wp-admin/images/screenshots/flex-header-3.png', 'wp-admin/images/screenshots/flex-header-media-library.png', 'wp-admin/images/screenshots/theme-customizer.png', 'wp-admin/images/screenshots/twitter-embed-1.png', 'wp-admin/images/screenshots/twitter-embed-2.png', 'wp-admin/js/utils.js', 'wp-admin/options-privacy.php', 'wp-app.php', 'wp-includes/class-wp-atom-server.php', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/ui.css', // 3.5.2 'wp-includes/js/swfupload/swfupload-all.js', // 3.6 'wp-admin/js/revisions-js.php', 'wp-admin/images/screenshots', 'wp-admin/js/categories.js', 'wp-admin/js/categories.min.js', 'wp-admin/js/custom-fields.js', 'wp-admin/js/custom-fields.min.js', // 3.7 'wp-admin/js/cat.js', 'wp-admin/js/cat.min.js', 'wp-includes/js/tinymce/plugins/wpeditimage/js/editimage.min.js', // 3.8 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/page_bug.gif', 'wp-includes/js/tinymce/themes/advanced/skins/wp_theme/img/more_bug.gif', 'wp-includes/js/thickbox/tb-close-2x.png', 'wp-includes/js/thickbox/tb-close.png', 'wp-includes/images/wpmini-blue-2x.png', 'wp-includes/images/wpmini-blue.png', 'wp-admin/css/colors-fresh.css', 'wp-admin/css/colors-classic.css', 'wp-admin/css/colors-fresh.min.css', 'wp-admin/css/colors-classic.min.css', 'wp-admin/js/about.min.js', 'wp-admin/js/about.js', 'wp-admin/images/arrows-dark-vs-2x.png', 'wp-admin/images/wp-logo-vs.png', 'wp-admin/images/arrows-dark-vs.png', 'wp-admin/images/wp-logo.png', 'wp-admin/images/arrows-pr.png', 'wp-admin/images/arrows-dark.png', 'wp-admin/images/press-this.png', 'wp-admin/images/press-this-2x.png', 'wp-admin/images/arrows-vs-2x.png', 'wp-admin/images/welcome-icons.png', 'wp-admin/images/wp-logo-2x.png', 'wp-admin/images/stars-rtl-2x.png', 'wp-admin/images/arrows-dark-2x.png', 'wp-admin/images/arrows-pr-2x.png', 'wp-admin/images/menu-shadow-rtl.png', 'wp-admin/images/arrows-vs.png', 'wp-admin/images/about-search-2x.png', 'wp-admin/images/bubble_bg-rtl-2x.gif', 'wp-admin/images/wp-badge-2x.png', 'wp-admin/images/wordpress-logo-2x.png', 'wp-admin/images/bubble_bg-rtl.gif', 'wp-admin/images/wp-badge.png', 'wp-admin/images/menu-shadow.png', 'wp-admin/images/about-globe-2x.png', 'wp-admin/images/welcome-icons-2x.png', 'wp-admin/images/stars-rtl.png', 'wp-admin/images/wp-logo-vs-2x.png', 'wp-admin/images/about-updates-2x.png', // 3.9 'wp-admin/css/colors.css', 'wp-admin/css/colors.min.css', 'wp-admin/css/colors-rtl.css', 'wp-admin/css/colors-rtl.min.css', 'wp-admin/css/media-rtl.min.css', 'wp-admin/css/media.min.css', 'wp-admin/css/farbtastic-rtl.min.css', 'wp-admin/images/lock-2x.png', 'wp-admin/images/lock.png', 'wp-admin/js/theme-preview.js', 'wp-admin/js/theme-install.min.js', 'wp-admin/js/theme-install.js', 'wp-admin/js/theme-preview.min.js', 'wp-includes/js/plupload/plupload.html4.js', 'wp-includes/js/plupload/plupload.html5.js', 'wp-includes/js/plupload/changelog.txt', 'wp-includes/js/plupload/plupload.silverlight.js', 'wp-includes/js/plupload/plupload.flash.js', 'wp-includes/js/plupload/plupload.js', 'wp-includes/js/tinymce/plugins/spellchecker', 'wp-includes/js/tinymce/plugins/inlinepopups', 'wp-includes/js/tinymce/plugins/media/js', 'wp-includes/js/tinymce/plugins/media/css', 'wp-includes/js/tinymce/plugins/wordpress/img', 'wp-includes/js/tinymce/plugins/wpdialogs/js', 'wp-includes/js/tinymce/plugins/wpeditimage/img', 'wp-includes/js/tinymce/plugins/wpeditimage/js', 'wp-includes/js/tinymce/plugins/wpeditimage/css', 'wp-includes/js/tinymce/plugins/wpgallery/img', 'wp-includes/js/tinymce/plugins/wpfullscreen/css', 'wp-includes/js/tinymce/plugins/paste/js', 'wp-includes/js/tinymce/themes/advanced', 'wp-includes/js/tinymce/tiny_mce.js', 'wp-includes/js/tinymce/mark_loaded_src.js', 'wp-includes/js/tinymce/wp-tinymce-schema.js', 'wp-includes/js/tinymce/plugins/media/editor_plugin.js', 'wp-includes/js/tinymce/plugins/media/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/media/media.htm', 'wp-includes/js/tinymce/plugins/wpview/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wpview/editor_plugin.js', 'wp-includes/js/tinymce/plugins/directionality/editor_plugin.js', 'wp-includes/js/tinymce/plugins/directionality/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wordpress/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wordpress/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wpdialogs/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wpdialogs/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wpeditimage/editimage.html', 'wp-includes/js/tinymce/plugins/wpeditimage/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wpeditimage/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/fullscreen/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/fullscreen/fullscreen.htm', 'wp-includes/js/tinymce/plugins/fullscreen/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wplink/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wplink/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wpgallery/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wpgallery/editor_plugin.js', 'wp-includes/js/tinymce/plugins/tabfocus/editor_plugin.js', 'wp-includes/js/tinymce/plugins/tabfocus/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/wpfullscreen/editor_plugin.js', 'wp-includes/js/tinymce/plugins/wpfullscreen/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/paste/editor_plugin.js', 'wp-includes/js/tinymce/plugins/paste/pasteword.htm', 'wp-includes/js/tinymce/plugins/paste/editor_plugin_src.js', 'wp-includes/js/tinymce/plugins/paste/pastetext.htm', 'wp-includes/js/tinymce/langs/wp-langs.php', // 4.1 'wp-includes/js/jquery/ui/jquery.ui.accordion.min.js', 'wp-includes/js/jquery/ui/jquery.ui.autocomplete.min.js', 'wp-includes/js/jquery/ui/jquery.ui.button.min.js', 'wp-includes/js/jquery/ui/jquery.ui.core.min.js', 'wp-includes/js/jquery/ui/jquery.ui.datepicker.min.js', 'wp-includes/js/jquery/ui/jquery.ui.dialog.min.js', 'wp-includes/js/jquery/ui/jquery.ui.draggable.min.js', 'wp-includes/js/jquery/ui/jquery.ui.droppable.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-blind.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-bounce.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-clip.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-drop.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-explode.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-fade.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-fold.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-highlight.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-pulsate.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-scale.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-shake.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-slide.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect-transfer.min.js', 'wp-includes/js/jquery/ui/jquery.ui.effect.min.js', 'wp-includes/js/jquery/ui/jquery.ui.menu.min.js', 'wp-includes/js/jquery/ui/jquery.ui.mouse.min.js', 'wp-includes/js/jquery/ui/jquery.ui.position.min.js', 'wp-includes/js/jquery/ui/jquery.ui.progressbar.min.js', 'wp-includes/js/jquery/ui/jquery.ui.resizable.min.js', 'wp-includes/js/jquery/ui/jquery.ui.selectable.min.js', 'wp-includes/js/jquery/ui/jquery.ui.slider.min.js', 'wp-includes/js/jquery/ui/jquery.ui.sortable.min.js', 'wp-includes/js/jquery/ui/jquery.ui.spinner.min.js', 'wp-includes/js/jquery/ui/jquery.ui.tabs.min.js', 'wp-includes/js/jquery/ui/jquery.ui.tooltip.min.js', 'wp-includes/js/jquery/ui/jquery.ui.widget.min.js', ); <end node> 5P9i0s8y19Z dt= <node>uploads 1 wpconfig.php file define( 'UPLOADS', 'uploads/' ); <end node> 5P9i0s8y19Z dt= <node>urls 1 https://wordpress.org/plugins/bulletproof-security/installation/ http://clicknathan.com/web-design/include-wordpress-page/ How to Include a WordPress Page on Another WP Page or Part of Your Theme (without using a Plugin) Dec052012 So you have some content from one WordPress post or page and you want to include it elsewhere in your theme. Perhaps you have a “Store Hours” page that you’d like to be able to only update once and have it show in various spots of your website, not just on that particular page. The following snippet of code shows you how to tell PHP to grab a particular page via get_pages, and then sets two variables depending on that page’s content and title. The last line shows you how to output the content. $include = get_pages('include=4177'); $content = apply_filters('the_content',$include[0]->post_content); $title = apply_filters('the_title',$include[0]->post_title); echo '<h1>'.$title.'</h1>'; echo $content; Remember to change the 4177 to whatever the ID of your particular page is, and note that you don’t need to keep the last “echo” line in there, you could use that elsewhere in your template. <end node> 5P9i0s8y19Z dt= <node>How to Include a WordPress Page 2 <h1>How to Include a WordPress Page on Another WP Page or Part of Your Theme (without using a Plugin)</h1> <?php $pages = get_pages('include=144'); $count = 0; foreach($pages as $page) { $content = $page->post_content; if(!$content) continue; if($count >= 2) break; $count++; $content = apply_filters('the_content', $content); ?> <div class=\\"entry\\"><?php echo $content ?></div> <?php } ?>
<p>So you have some content from one WordPress post or page and you want to include it elsewhere in your theme. Perhaps you have a “Store Hours” page that you’d like to be able to only update once and have it show in various spots of your website, not just on that particular page.</p> <p>The following snippet of code shows you how to tell PHP to grab a particular page via <code>get_pages</code>, and then sets two variables depending on that page’s content and title. </p> <p>The last line shows you how to output the content.</p> <div class="code-snippet"> <code>$include = get_pages('include=4177');<br> $content = apply_filters('the_content',$include[0]->post_content);<br> $title = apply_filters('the_title',$include[0]->post_title);<br> echo '<h1>'.$title.'</h1>'; echo $content; </code> </div> <p><strong>Remember to change the <code>4177</code> to whatever the ID of your particular page is</strong>, and note that you don’t need to keep the last “echo” line in there, you could use that elsewhere in your template.</p> <end node> 5P9i0s8y19Z dt= <node>Stupid WordPress Tricks 2 http://perishablepress.com/stupid-wordpress-tricks/ Perishable Press WordPress, Web Design, Code & Tutorials Tutorials Plugins Archives Demos Tools New book on WordPress Theme Development: WordPress Themes In Depth x « Getting Serious with a New Design The New Clearfix Method » Stupid WordPress Tricks [ WordPress ] One of the most popular articles here at Perishable Press is my January 2005 post, Stupid htaccess Tricks. In that article, I bring together an extensive collection of awesome copy-&-paste HTAccess code snippets. Four years later, people continue to tell me how much they enjoy and use the content as a bookmarked reference for many of their HTAccess needs. The article was even published in a book on Joomla! Security. This is very inspiring to me, so I have decided to create a similar post for all of the useful WordPress code snippets, tips and tricks that I have collected while working on Digging into WordPress, the new book by co-author Chris Coyier and myself that really “digs in” to all of the awesome ways to get the most out of WordPress. While writing the DiW book, I collected hundreds of incredibly useful WordPress tips and tricks. After packing the book with as many of these techniques as possible, I decided to share the “best of the rest” here at Perishable Press. If you are one of the millions of people who use WordPress, this article will help you improve the appearance, functionality, and performance of your WordPress-powered websites. Each of these “stupid WordPress tricks” is presented as clearly and succinctly as possible, including as many notes, instructions, and pointers as needed for successful implementation. Of course, keep in mind that we are only scratching the surface here. For a much more complete resource that is packed with tons of tasty techniques, you need to get Digging into WordPress. So now, without further ado, here is my personal collection of easy-to-use, copy-&-paste WordPress tricks. Enjoy! :) Table of Contents WordPress Shortcodes WordPress Permalinks Outside of the Loop Custom Message to Returning Visitors Recently Updated Posts and Pages Custom Content to Search Engine Visitors Last Modified Time and Date for Posts Display Total Number of Trackbacks and Pingbacks Display Recently Registered Users List all of Your Site’s Posts List WordPress User Information Display List of Scheduled Posts Display Private Posts to Logged-in Users Display Posts from Exactly One Year Ago Custom CSS Styles for Recent Posts New WordPress-2.7 Comments Loop Backwards-Compatible Comment Templates Disable WordPress Post Revisions Limit WordPress Post Revisions Remove WordPress Post Revisions from the Database Reduce Comment Spam by Blocking No-Referrer Requests Prevent Google Analytics from Tracking Admin Pages Meta Descriptions without a Plugin Differentiate Between Posts Depending on Presence of Excerpt Modify the wp_options Table via the WordPress Admin Alternate Comment Styles Automatically Remove Code Mistakes in Posts Automatically Disable Comments and Trackbacks in Old Posts Access Post Data Outside the Loop Display Posts for a Specified Time Period Unique Single Post Templates for Different Categories Display Performance Statistics for WordPress Pages Custom Post Thumbnails in Two Steps Highlight Author Comments Easy Random Posts Display Dates for Groups of Posts Display a Sticky Post in the Sidebar Display Latest Comments without a Plugin Display Most Commented Posts without a Plugin Change Permalinks from Date-Based to Post-Date Only Test for Sub-Pages Multiple Widgetizable Sidebars Remove Fancy Quotes from Comments Display a List of All Untagged Posts Easy Display of Custom Headers, Footers, and Sidebars A Better Way for Users to Logout Display a Custom Message on a Specific Date Display Three Columns of Posts Disable WordPress Search Functionality Display Posts with Specific Custom Fields How to Number Your Comments, Pingbacks, & Trackbacks in 2.7+ How to Number Your Comments Using the Classic Loop Invite Readers to Comment via Feed Display the Total Number of Users for Your Blog Automatically Insert Content into Your WordPress Post Editor How to Prevent Duplicate Content Conditionally Display Full Posts or Excerpts Display Related Posts without a Plugin Drop-Dead Easy Styles for Author Comments Display Posts Upcoming Scheduled Posts Display Automatic TinyURLs for Your Posts Implement a Site-Maintenance Page for Your Blog Display the First Image from Each of Your Posts Display Most Popular Posts without a Plugin Automatically Highlight Search Terms Automatically Disable Widgets Display All Images from Your Post Content Display Category List in Two Columns Show Ads or Other Content Only in the First Three Posts A Better Way to Display Recent Comments without a Plugin Selectively Disable Automatic Post Formatting Browser Detection via WordPress’ body_class Function Get Post or Page Contents as a PHP Variable Simple Example of How to Use WordPress Cron Add More Default Avatar Choices to the WordPress Admin Add a Private Page to Your Navigation Menu How to Add Additional Links to wp_list_pages WordPress Shortcodes ? Save time by replacing your most commonly typed words and phrases with WordPress shortcodes. For example, if you are frequently typing your blog’s URL, you could place the following code your theme’s functions.php file: function shortURL() { return 'http://perishablepress.com/'; } add_shortcode('myurl', 'shortURL'); Now whenever I write a post via “HTML-mode”, all I need to include my blog’s URL is type “[myurl]”. Works great in WordPress 2.5 or better. Shortcodes with Attributes To create a shortcode for links, we need to include the href attribute information as well as the anchor text for the link itself. We can do this by placing this function in your theme’s functions.php file: function shortLink($atts, $content = null) { extract(shortcode_atts(array( "href" => 'http://' // default URL ), $atts)); return '<a href="'.$href.'">'.$content.'</a>'; } add_shortcode('link', 'shortLink'); Then, when creating a post, emulate the following format to include any links you wish: [link href="http://perishablepress.com/"]Perishable Press[/link] ..which will output the following code: <a href="http://perishablepress.com/">Perishable Press</a> When the href attribute is removed from the shortcode, the default URL will be used. You may specify the default URL in the third line of the funtion (see comment). Source: Digging into WordPress Display WordPress Permalinks Outside of the Loop ? Normally, permalink display via the_permalink() requires the loop. To display permalinks outside of the loop, we may use either of the following methods: <!-- external permalink via post ID --> <a href="<?php echo get_permalink(33); ?>" >Permalink</a> <!-- external permalink via global $post variable --> <a href="<?php echo get_permalink($post->ID); ?>" >Permalink</a> Source: Julien Chauvin (404 link removed 2013/06/27) Display Custom Message to Returning Visitors ? We can greet returning commentators with a custom message by extracting their information from the comment cookie left on their machine. Place the following code into the desired location in your theme and customize the message and markup to whatever you wish: <?php if(isset($_COOKIE['comment_author_'.COOKIEHASH])) { $lastCommenter = $_COOKIE['comment_author_'.COOKIEHASH]; echo "Welcome Back ". $lastCommenter ."!"; } else { echo "Welcome, Guest!"; } ?> Source: ifohdesigns (404 link removed 2012/09/14) Display Recently Updated Posts and Pages ? Easily display a list of recently updated posts by placing the following code into the desired location in your theme: <?php $today = current_time('mysql', 1); $number = 5; // number of posts if($recentposts = $wpdb->get_results("SELECT ID, post_title FROM $wpdb->posts WHERE post_status = 'publish' AND post_modified_gmt < '$today' ORDER BY post_modified_gmt DESC LIMIT $number")): ?> <h2><?php _e("Recently Updated"); ?></h2> <ul> <?php foreach($recentposts as $post) { if($post->post_title == '') $post->post_title = sprintf(__('Post #%s'), $post->ID); echo '<li><a href="'.get_permalink($post->ID).'">'.the_title().'</a></li>'; } ?> </ul> <?php endif; ?> Of course, customize the details as necessary and remember to set the number of posts via the “$howMany” variable. Source: Corey (404 link removed 2014/06/08) Display Custom Content to Search Engine Visitors ? Display custom content to your search-engine traffic by placing the following code into your theme’s functions.php file: <?php function scratch99_fromasearchengine() { $ref = $_SERVER['HTTP_REFERER']; $SE = array('/search?', 'images.google.', 'web.info.com', 'search.', 'del.icio.us/search', 'soso.com', '/search/', '.yahoo.');
foreach($SE as $source) { if(strpos($ref, $source) !== false) return true; } return false; } ?> After checking and editing the $SE array with the search-engine referrer information of your choice, place this next chunk of code into the desired display location in your theme file(s): <?php if(function_exists('scratch99_fromasearchengine')) { if (scratch99_fromasearchengine()) { // INSERT YOUR CODE HERE } } ?> Add whatever content or code you wish to the specified area and enjoy targeted delivery to search-engine visitors only. Source: Stephen Cronin Display Last Modified Time and Date for Posts ? Display the “last-modified” time for your posts by placing this code anywhere within the loop: Posted on <?php the_time('F jS, Y') ?> <?php $u_time = get_the_time('U'); $u_modified_time = get_the_modified_time('U'); if($u_modified_time != $u_time) { echo "and last modified on "; the_modified_time('F jS, Y'); echo ". "; } ?> Source: Kyle Eslick Display Total Number of Trackbacks and Pingbacks ? Display the trackback/pingback count for each of your posts by first placing this code into your theme’s functions.php file: function comment_count() { global $wpdb; $count = "SELECT COUNT(*) FROM $wpdb->comments WHERE comment_type = 'pingback' OR comment_type = 'trackback'"; echo $wpdb->get_var($count); } And then call the number for display anywhere in your theme by adding this code to the desired location: <?php comment_count(); ?> Alternately, in WordPress 2.7, you may display the total number of comments by inserting this code directly into your comments.php template: <?php if(!empty($comments_by_type['comment'])) : $count = count($comments_by_type['comment']); ($count !== 1) ? $txt = "Comments" : $txt = "Comment"; ?> <h3><?php echo $count . " " . $txt; ?></h3> Edit the markup as desired. Will display “” or “”, depending on the number of comments. Source: WPengineer.com Display Recently Registered Users ? Quick and easy method for displaying a list of recently registered users. Place the following code directly into your theme, wherever you would like to display the list: <ul> <?php $usernames = $wpdb->get_results("SELECT user_nicename, user_url FROM $wpdb->users ORDER BY ID DESC LIMIT 5"); foreach ($usernames as $username) { echo '<li><a href="'.$username->user_url.'">'.$username->user_nicename."</a></li>"; } ?> </ul> As-is, this code will spit out the five most recent registered users. This is easily changed to whatever number you wish by simply editing the number “5” in the first line. Source: WPRecipes.com List all of Your Site’s Posts ? If the default wp_get_archives(type=postbypost&limit=) function doesn’t provide enough flexibility to meet your needs, here is another way to list all of your site’s posts: <?php while(have_posts()) : the_post(); ?> <ul> <?php $allposts = get_posts('numberposts=-1&offset=0'); foreach($allposts as $post) : ?> <li><?php the_time('d/m/y'); ?>: <a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></li> <?php endforeach; ?> </ul> <?php endwhile; ?> In place, that code will display a list of all of your blog’s posts. As a bonus, you may use any of the applicable parameters available to the get_posts() function to do just about anything you need with your posts list. Source: WPRecipes.com List WordPress User Information ? Here is an easy way to display flexible lists of your blog’s registered users’ information. In this example, we will list the first and last name of each user registered in the database: <ul> <?php $szSort = "user_nicename"; $aUsersID = $wpdb->get_col($wpdb->prepare("SELECT $wpdb->users.ID FROM $wpdb->users ORDER BY %s ASC", $szSort)); foreach($aUsersID as $iUserID) : $user = get_userdata($iUserID); echo '<li>'.ucwords(strtolower($user->first_name.' '.$user->last_name)).'</li>'; endforeach; ?> </ul> The following variables may be used to display different types of user information and also to specify the sort order of the output list: ID - User ID number user_login - User Login name user_nicename - nice version of login name user_email - User Email Address user_url - User Website URL user_registered - User Registration date To display any of these different types of user information, call it with $user->name_of_the_column anywhere within the function’s foreach() loop. To change the display order of the output, use any of the above as the value of the $szSort variable in the first line of the function. Note that strtolower and ucwords are used to ensure proper capitalization of the user names. Source: Matt Varone Display List of Scheduled Posts ? Got scheduled posts? Cool. Here’s how to display them to your readers: <ul> <?php $my_query = new WP_Query('post_status=future&order=DESC&showposts=5'); if ($my_query->have_posts()) { while ($my_query->have_posts()) : $my_query->the_post(); $do_not_duplicate = $post->ID; ?> <li><?php the_title(); ?></li> <?php endwhile; } ?> </ul> Place that code in the desired location of your WordPress template and display a list of scheduled posts to your readers. To change the total number of displayed posts, edit the showposts=5 parameter to any number you wish. You may also use other parameters available to the WP_Query() function to further customize the output. Source: Pascal Birchler Display Private Posts to Logged-in Users ? To display private posts to your logged-in users, you will need to add a custom field called “private” for each private post and give it a value of “true”. Then, replace your default WordPress loop with the following: <?php if (have_posts()) : while (have_posts()) : the_post(); $private = get_post_custom_values("private"); if (isset($private[0]) && $private == "true") { if (is_user_logged_in()) { // Display private post to logged user } } else { // Display public post to everyone } endwhile; endif; ?> This custom loop will check each post for the presence of a custom-field value of true. For each post that has this value, the loop will then check to see if the user is logged into your site. If the user is in fact logged in, the loop will display the private post(s). Public posts will be displayed as usual and regardless of whether the user is logged in or not. Source: Digging into WordPress Display Posts from Exactly One Year Ago ? Use this code to display posts that are exactly one year old: <?php $current_day = date('j'); $last_year = date('Y')-1; ?> <?php query_posts('day='.$current_day.'&year='.$last_year); if (have_posts()): while (have_posts()) : the_post(); ?> <h1><?php the_title(); ?></h1> <?php the_excerpt(); ?> <?php endwhile; endif; ?> To display posts from different days or different years, edit the two variables in the beginning of the method. Custom CSS Styles for Recent Posts ? Use some custom CSS styles to highlight your recent posts. To do this, replace your existing loop with the following: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> $currentdate = date('Y-m-d',mktime(0,0,0,date('m'),date('d'),date('Y'))); $postdate = get_the_time('Y-m-d'); if ($postdate == $currentdate) { echo '<div class="post new">'; } else { echo '<div class="post">'; } ?> <a href="<?php the_permalink(); ?>"><?php the_title(); ?></a> </div> <?php endwhile; endif; ?> This new loop will check the date of each post and include a CSS class of “new” to any post published within the previous 24-hour time period. Once the new post class is included, you may style it with some custom CSS such as the following: .post{ /* styles for all posts */ } .post.new { /* styles for new posts */ } Source: Fred jaillet [via] WPRecipes.com New WordPress-2.7 Comments Loop ? Due to the changes made to comment-related functions in WordPress 2.7, you will need to upgrade your comments template in order accomodate for the new functionality. The major changes are the new wp_list_comments() function and the next/previous_comments_link() functions. Here is an example comments.php loop to get you started: <?php if (have_comments()) : ?> <h4><?php comments_number('No Comments', 'One Comment', '% Comments' );?></h4> <ul class="commentlist"> <?php wp_list_comments(); ?> </ul> <div class="navigation"> <div class="alignleft"><?php previous_comments_link(); ?></div> <div class="alignright"><?php next_comments_link(); ?></div> </div> <?php else : // if there are no comments so far ?> <?php if ('open' == $post->comment_status) : ?> <p>Comments are open, but there are no comments.</p> <?php else : ?> <p>Comments are closed, and there are no comments.</p> <?php endif; ?> <?php endif; ?> As you can see, we are now using the wp_list_comments() function as the method by which our individual comments are displayed. This function wraps each comment with a set of <li> elements, but this may be changed via customized parameters. We are also using the next/previous_comments_link() functions to accommodate the new built-in paged comments feature. Source: Digging into WordPress Backwards-Compatible Comment Templates ? The easiest way to accommodate for both old (pre-2.7) and new (2.7+) WordPress comment loops is to create two different versions of the comments template and then use some conditional logic to process the correct file. Place the 2.7-compatible code from the previous section into your default comments.php file, and then place your existing (pre-2.7) comments code into a file called legacy-comments.php. Once you have both of these files setup and included among your theme files, place the following function in your theme’s functions.php file: <?php add_filter('comments_template', 'legacy_comments'); function legacy_comments($file) { if(!function_exists('wp_list_comments')) : // WP 2.7-only check $file = TEMPLATEPATH.'/legacy-comments.php'; endif; return $file; } ?> This code will then check for the presence of the new wp_list_comments() function. If it exists, then the version of WordPress is at least 2.7, and the default comments.php file will be used. If the new function doesn’t exist, we have a dinosaur on our hands and so the legacy comments file will be used instead. Source: Justin Tadlock Disable WordPress Post Revisions ? One of the new features rolled out in WordPress 2.6 involved post revisions. Revisions are a way for users to keep a working collection of each different version of a post and then revert back to it in the future if necessary. Some people think this is the greatest thing since lightsabers, others (such as myself) find it to be a royal pain in the database. It convolutes the Admin area, gobbles up disk space, and usually doesn’t work as intended. Fortunately, we can disable this amazing new “feature” (which should NOT have been included in the core) by adding the following line to the wp-config.php file: /* disable post-revisioning nonsense */ define('WP_POST_REVISIONS', FALSE); Just place that line above the “Happy blogging” comment and say goodbye to needless revisioning bloat. Source: Digging into WordPress Limit WordPress Post Revisions ? If you like the idea of WordPress-2.6’s new post-revisioning feature, but don’t want thousands of extra records bloating up your database, here is an easy way to limit the total number of revisions that WordPress is allowed to keep. This code will instruct WordPress to keep only the most recent “x” number of revisions: /* limit number of post revisions */ define('WP_POST_REVISIONS', 3); Place that line above the “Happy blogging” comment in the wp-config.php file and enjoy conserved disk space and less Admin clutter. Change the number “3” to any number you wish. Works a treat. Source: Digging into WordPress Remove WordPress Post Revisions from the Database ? In line with the previous two sections, here we will remove all existing post revisions from the WordPress database. This is useful if you have disabled the post-revisioning feature or perhaps even reduced the total number of allowed revisions. The easiest way to do this is to run the following SQL command via your favorite database interface (such as my personal favorite, phpMyAdmin): DELETE a,b,c FROM wp_posts a LEFT JOIN wp_term_relationships b ON (a.ID = b.object_id) LEFT JOIN wp_postmeta c ON (a.ID = c.post_id) WHERE a.post_type = 'revision'; Note that if you have changed the default WordPress database table prefix to something other than “wp_”, you will want to edit the command to reflect the correct prefix information. This information is available in your site’s wp-config.php file. Also note that you should backup your database before casting any SQL spells on it. Upon successful execution of the above command, all data associated with post revisions will be removed the database. This includes the post revisions themselves and all the meta data associated with each revision. Credit: Andrei Neculau Reduce Comment Spam by Blocking No-Referrer Requests ? As explained in my article, denying access to no-referrer requests, you can greatly reduce the number of spam comments by eliminating all direct requests for your blog’s comments-post.php file. This will block automated spam scripts from bypassing your comments form by hitting the comment processing script directly. Here are two ways to block no-referrer comment requests, one uses HTAccess and the other uses PHP. Here is the HTAccess method: RewriteEngine On RewriteCond %{REQUEST_METHOD} POST RewriteCond %{REQUEST_URI} .wp-comments-post.php RewriteCond %{HTTP_REFERER} !domain.tld [OR] RewriteCond %{HTTP_USER_AGENT} ^$ RewriteRule (.*) http://%{REMOTE_ADDR}/$ [R=301,L] Place that code in your site’s root HTAccess file and edit the “domain.tld” to match your own domain. Once in place, this code will redirect any request for your blog’s comments-post.php file that didn’t originate from your site back to the URL from whence it came. This may also be accomplished via PHP. Place the following function in your theme’s functions.php file: function check_referrer() { if (!isset($_SERVER['HTTP_REFERER']) || $_SERVER['HTTP_REFERER'] == '') { wp_die(__('Please do not access this file directly.')); } } add_action('check_comment_flood', 'check_referrer'); Source: Perishable Press Prevent Google Analytics from Tracking Admin Pages ? This handy snippet will prevent Google Analytics from tracking your Admin pages or anything else that you wish. Replace your default Google Analytics code with the following: <?php if (!current_user_can('level_10')) { ?> /* Google Analytics Code */ <?php } ?> This code will then include your Google Analytics code only on non-Admin pages. This in turn will prevent Google Analytics from gathering statistics about your Admin pages. Note that the basic functionality of this method is great for restricting just about anything - scripts, markup, content - to logged-in administrators. Meta Descriptions without a Plugin ? We don’t need no stinkin’ plugin for custom meta descriptions. All you need is a custom field named “metadescription” with the desired meta description for each post. Once you have that going, include the following function to your theme’s header.php file (within the <head> section: <meta name="description" content=" <?php if ((is_home()) || (is_front_page())) { echo ('Your main description goes here'); } elseif(is_category()) { echo category_description(); } elseif(is_tag()) { echo 'Tag archive page for this blog - ' . single_tag_title(); } elseif(is_month()) { echo 'Archive page for this blog - ' . the_time('F, Y'); } else { echo get_post_meta($post->ID, 'metadescription', true); } ?>" /> This function enables you to customize the descriptions for various types of pages, such as the home page, category pages, tag archives, and so on. For single post-view pages, this function will display the value of the metadescription custom field. Source: Malcolm Coles (404 link removed) Differentiate Between Posts Depending on Presence of Excerpt ? Here is a quick conditional snippet that displays different content depending on the presence of an excerpt: <?php if(!empty($post->post_excerpt)) { // this post has an excerpt, so display it: the_excerpt(); } else { // this post has no excerpt, so display something else instead: the_content(); } ?> Placed inside the loop, this code will check each post for an excerpt. If one is found, the excerpt is displayed; otherwise, the code specified in the else condition is displayed. Modify the wp_options Table via the WordPress Admin ? As you probably know, the wp_options table stores a great deal of useful information, including everything from custom-field values, plugin settings, blog information, and much more. If any table in the WordPress database needs its own friendly user-interface, this would be it. Normally, you would access the wp_options table using a database interface such as phpMyAdmin. This certainly works, but there is a much easier way to work with the options table, especially if you are already logged into WordPress. Once logged in to the Admin area, navigate to the following URL: http://domain.tld/wp-admin/options.php This will open a “secret” Admin page that provides editable options fields for every record in the wp_options table. Bookmark this page, and save yourself a trip to phpMyAdmin! Source: Digging into WordPress Alternate Comment Styles ? Alternating comments for old versions of WordPress (pre-2.7) This is one of the oldest tricks in the book, but it is still a favorite. Alternating comment styles is a great way to enhance usability and add some stylistic flair to your comments display. The trick is to add an alternating set of classes - odd or even - to the containing element of each comment. While there are many ways to do this, here is one of the easiest. Open your comments.php and modify the comments loop as follows: <ul> <?php $i = 0; ?> <?php foreach ($comments as $comment) : ?> <?php $i++; ?> <li id="comment-<?php comment_ID(); ?>" <?php if($i&1) { echo 'class="odd"'; } else { echo 'class="even"'; } ?>> <?php comment_text(); ?> </li> <php endforeach; ?> </ul> With that code in place, your comments will now have alternating CSS classes with which to apply custom styles to your oddly and evenly numbered comments: .odd { background: white; color: black; } .even { background: black; color: white; } Alternating comments for old versions of WordPress (pre-2.7) In WordPress 2.7 and better, comments automagically include “odd” and “even” classes for oddly and evenly numbered comments, respectively. This makes it a snap to throw down your own custom CSS styles for each of these classes. Credit: WordPress Garage Automatically Remove Code Mistakes in Posts ? Here is a handy trick that will automatically remove basic mistakes in XHTML markup, such as empty paragraphs, inline font styles, and more. Place this function in your functions.php file: function clean_bad_content($bPrint = false) { global $post; $szPostContent = $post->post_content; $szRemoveFilter = array("~<p[^>]*>\\s?</p>~", "~<a[^>]*>\\s?</a>~", "~<font[^>]*>~", "~<\\/font>~", "~style\\=\\"[^\\"]*\\"~", "~<span[^>]*>\\s?</span>~"); $szPostContent = preg_replace($szRemoveFilter, '', $szPostContent); $szPostContent = apply_filters('the_content', $szPostContent); if ($bPrint == false) return $szPostContent; else echo $szPostContent; } Once in place, use the following function call to display your “cleaned” content in the loop: <?php if (function_exists('clean_bad_content')) clean_bad_content(true); ?> Note that the clean_bad_content() accepts a boolean argument (true or false) specifying whether or not to print the function output. Credit: Matt Varone Automatically Disable Comments and Trackbacks in Old Posts ? Here is yet another method for auto-disabling comments and trackbacks on old posts. This function automatically closes comments and trackbacks after the specified number of days. Add the following to your functions.php file: <?php function autoclose_comments() { global $wpdb, $tableposts; if (!isset($tableposts)) $tableposts = $wpdb->posts; $age = '21 DAY';
$date = $wpdb->get_var("SELECT DATE_ADD(DATE_SUB(CURDATE(), INTERVAL $age), INTERVAL 1 DAY)"); $wpdb->query("UPDATE $tableposts SET comment_status = 'closed' WHERE comment_status = 'open' AND post_status = 'publish' AND post_date < '$date'"); } function autoclose_trackback() { global $wpdb, $tableposts; if (!isset($tableposts)) $tableposts = $wpdb->posts; $age = '21 DAY';
add_action('publish_post', 'autoclose_comments', 7); add_action('edit_post', 'autoclose_comments', 7); add_action('delete_post', 'autoclose_comments', 7); add_action('comment_post', 'autoclose_comments', 7); add_action('trackback_post', 'autoclose_comments', 7); add_action('pingback_post', 'autoclose_comments', 7); add_action('edit_comment', 'autoclose_comments', 7); add_action('delete_comment', 'autoclose_comments', 7); add_action('template_save', 'autoclose_comments', 7); ?> Once in place, you may change the number of days allowed for comments and trackbacks to stay open by editing the two instances of the $age variable to whatever you wish. No other editing or code is required for this function to operate effectively. The function is executed automatically upon various posting actions. Note that this function is included in newer versions of WordPress (2.7 or better), and is therefore only required for older versions. Source: WP EngineerPlugin: Autoclose Access Post Data Outside the Loop ? The easiest way to access and display post data outside of the loop is to use the built-in WordPress core function get_post(); however, for more control over the process, check out this nifty little function from WP Recipes: function get_post_data($postId) { global $wpdb; return $wpdb->get_row("SELECT * FROM $wpdb->posts WHERE ID=$postId"); } Place this function in your functions.php and then add this code to the desired location outside of the loop: <?php $data = get_post_data(77); echo $data->post_date; // post date echo $data->post_title; // post title echo $data->post_content; // post content echo $data->comment_count; // comments number ?> For the argument of the function, specify the post ID for which you would like to display data. The function will return an array containing all of the available fields for the specified post (post_title, date, content, author_id, post_id, etc). Display Posts for a Specified Time Period ? Here is an easy way to create posts that will only be displayed for the duration of a specified time period. Replace your current loop with the following: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> $expirationtime = get_post_custom_values('expiration'); if (is_array($expirationtime)) { $expirestring = implode($expirationtime); } $secondsbetween = strtotime($expirestring)-time(); if ($secondsbetween > 0) { ?> <h1><?php the_title(); ?></h1> <?php the_excerpt(); ?> <?php } endwhile; endif; ?> And then add a custom field named “expiration” to any post that needs an expiration date. For the value of the expiration key, specify the date/time in the following format: mm/dd/yyyy 00:00:00. Each post that contains such a custom field will expire after the specified date and time and will no longer appear in the loop. Unique Single Post Templates for Different Categories ? Here is an easy way to display custom post styles depending on the post’s category. With the following code, each single-view post will be displayed according to a template that is specific to the post’s category: <?php $post = $wp_query->post; if (in_category('1')) { include(TEMPLATEPATH.'/single-01.php'); } elseif (in_category('2')) { include(TEMPLATEPATH.'/single-02.php'); } else { include(TEMPLATEPATH.'/single-default.php'); } ?> This code should be placed in your theme’s single.php file. As written, this code will display posts from the first category with the single template, “single-01.php”; also, posts from the second category will be displayed with a single template named “single-02.php”; finally, all other posts will be displayed via the default single template, “single-default.php”. Of course, you will want to customize the category IDs according to your own needs, and also you will want to create the customized single files as they are called. That’s all there is to it. Having said that, here is an alternate version of the custom-post-template script: <?php add_filter('single_template', create_function('$t', 'foreach((array) get_the_category() as $cat) { if (file_exists(TEMPLATEPATH . "/single-{$cat->term_id}.php")) return TEMPLATEPATH . "/single-{$cat->term_id}.php"; } return $t;')); ?> Placed in your theme’s functions.php file, this alternate script checks all categories for the presence of a custom single template. Any category with a custom single-post template will then have its posts displayed with that template. If a post’s category does not feature a custom template, the default single.php template will be used. Note that this code will use the template for the first listed category of each post. Even so, you should only create custom post templates for categories that will always be mutually exclusive. That is, make sure that your posts aren’t in more than one custom-templated category. Source: Austin Matzko Display Performance Statistics for WordPress Pages ? Everyone is familair with the following information: <!-- 33 queries in 0.333 seconds --> These statistics are usually seen in the footer area of individual pages and serve as a general indicator of performance. The “queries” refer to the number of times WordPress requested information from the database, while the number of seconds indicates the amount of time required for Apache to generate the page. This information is generated by including the following code in your footer template file (or wherever you would like): <!-- <?php echo get_num_queries(); ?> queries in <?php timer_stop(3); ?> seconds --> Or, if you don’t like the idea of sharing this information with the entire world, you can limit its display to logged-in administrators only: <?php if (current_user_can('level_10')) { echo '<!-- ' . get_num_queries() . ' queries in ' . timer_stop(3) . ' seconds -->'; } ?> Easy breezy beautiful! Source: Digging into WordPress Custom Post Thumbnails in Two Steps ? Alright, kids. Time for the ‘ol three-step custom-field tutorial. This time we’re going to implement post thumbnails. You know, representative images for each of your posts that may be displayed anywhere you wish, including outside of the flow of post content, and even outside of the loop. This is a great trick for advanced page layouts. Ready? Sharpen your keystrokes! Step 1: Open your write panel and create a key called “thumbnail”. Then, for the value of the “thumbnail” key, enter the URL of the thumbnail image for that particular post. Write the post and then publish it as normal. Wash, rinse, repeat to get a nice collection of posts with thumbnails. Or, go back to exisiting posts and add a thumbnail as we have just described. Step 2: Open your theme template file containing the loop and add the following code to the location where you would like the post thumbnail images to appear: <?php $thumbnail = get_post_meta($post->ID, 'image', true); if ($thumbnail) { ?> <img src="<?php echo $thumbnail; ?>" alt="" width="100" height="100" /> <?php } ?> That’s it! Don’t forget to edit the width and height attributes of the <img> element to account for the proper image size. Source: Perishable Press Highlight Author Comments ? Make your author comments look fabulous darling! Newer versions of WordPress come equipped with a specific “author” class that may be targeted with the CSS of your choice. For older versions of WordPress, however, you will need to add the custom class attribute with a little PHP magic. First, open your theme’s comments.php template and add the following code snippet in the (X)HTML element that contains the comment information: <div<?php if ($comment->comment_author_email == "email@domain.tld") echo ' class="author"'; ?> id="comment-<?php comment_ID(); ?>"> . . . </div> After changing the email address to that of your own (i.e., the one used for your WP Admin user profile), style it up with a little CSS: .author { background: red !important; color: yellow !important; } You probably don’t want your author comments to appear with yellow text on a red background, but you get the idea. Anything is possible. For blogs with multiple authors, you can style each of their comments differently as well by using something like this: <div<?php if ($comment->comment_author_email == "email-01@domain.tld") echo ' class="author-01"'; elseif ($comment->comment_author_email == "email-02@domain.tld") echo ' class="author-02"'; elseif ($comment->comment_author_email == "email-03@domain.tld") echo ' class="author-03"'; ?> id="comment-<?php comment_ID(); ?>"> . . . </div> Replace each of the email addresses with those of the various authors. Style to taste. Credit: Nyssa Brown (404 link removed) Easy Random Posts ? Newer versions of WordPress enable easy randomizing of posts by using the (relatively) new “orderby=rand” parameter in any query_posts loop: <?php query_posts('orderby=rand"); ?> But for older versions of WordPress, this randomizing functionality must be added manually. Here is a quick and painless plugin that will enable you to randomize post queries in older versions: <?php /* Plugin Name: Random Posts Query */ function query_random_posts($query) { return query_posts($query . '&random=true'); } class RandomPosts { function orderby($orderby) { if (get_query_var('random') == 'true') return "RAND()"; else return $orderby; } function register_query_var($vars) { $vars[] = 'random'; return $vars; } } add_filter( 'posts_orderby', array('RandomPosts', 'orderby') ); add_filter( 'query_vars', array('RandomPosts', 'register_query_var') ); ?> Once activated, invoke the randomness by adding the “random=true” parameter in your query_posts loop: <?php query_posts('cat=11&showposts=11&random=true'); ?> Here, we are specifying “cat=11” for the category and “showposts=11” for the number of posts to display. There are many other parameters available as well, so knock yourself out. Credit: rembem Display Dates for Groups of Posts ? In order to display the date that a post was published, you have two options: <?php the_time(); ?> - displays the date for each and every post <?php the_date(); ?> - displays the date only once for each group of posts published on a certain day So, if you want to list the post date next to each post, use the the_time(). If, on the other hand, you have multiple posts on any given day, use the_date() to list the post date only once for each days’ posts. Something like this: // the_time(); Jan 01, 2009 - Post #1 Jan 01, 2009 - Post #2 Jan 01, 2009 - Post #3 Jan 02, 2009 - Post #4 Jan 02, 2009 - Post #5 Jan 02, 2009 - Post #6 Jan 03, 2009 - Post #7 Jan 03, 2009 - Post #8 Jan 03, 2009 - Post #9 // the_date(); Jan 01, 2009 Post #1 Post #2 Post #3 Jan 02, 2009 Post #4 Post #5 Post #6 Jan 03, 2009 Post #7 Post #8 Post #9 See the difference? Good, because I’m not going to explain the concept any further. Instead, I will move on by showing you how to use either template tag in your loop. This really doesn’t need explaining either, but for the sake of completeness, here it is. First, the_time() tag: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <h1><?php the_title(); ?></h1> <p><?php the_time(); ?><p> <?php the_content(); ?> <?php endwhile; ?> <?php else : ?> <?php endif; ?> This loop will output the post title, date, and content for every post. Alternately, here is how to use the_date tag: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php the_date('','<p>','</p><hr />'); ?> <h1><?php the_title(); ?></h1> <?php the_content(); ?>
<?php endwhile; ?> <?php else : ?> <?php endif; ?> This loop will output the post title and content for every post, and also output the date for each group of posts published on any given day, as explained above. Notice we are adding the paragraph elements for the post date based on whether or not the date is actually output. If it is, then the date will be wrapped in <p> elements; if it’s not, no <p> elements will be output, thereby preventing repetitive sets of empty paragraph elements. Make sense? Good. Here are the available parameters for the nifty the_date() template tag: <?php the_date('date format', 'before the date', 'after the date'); ?> Display a Sticky Post in the Sidebar ? Here is a juicy little nugget that displays a “sticky” post in the sidebar of your theme: <?php // initialize new query of one post from category 11 $my_query = new WP_Query('cat=11&showposts=1'); // loop through the database to find related information while ($my_query->have_posts()) : $my_query->the_post(); // set expiration time of two days $goAwayDate = time() - (60 * 60 * 24 * 2); // get date of sticky post $postDate = get_the_time('U'); // if post is too old, do nothing if ($postDate < $goAwayDate) { // else show the post } else { ?> <h1><?php the_title(); ?></h1> <?php the_excerpt(); ?> <?php } endwhile; ?> This method employs a second loop to display the sticky post, so it may be placed just about anywhere in your theme’s template files. You can also change the number of days that the post will remain sticky by editing the expiration variable with a number other than "2". For example, to set a duration period of seven days, you would use this: $goAwayDate = time() - (60 * 60 * 24 * 7); Credit: The Closet Entrepreneur Display Latest Comments without a Plugin ? Good rule of thumb when working with WordPress: don’t use a plugin if you can acheive the same functionality without one. Case in point: displaying latest comments on your blog. Sure, you could always install a plugin to do it for you, but you really don’t need to. In fact, it’s actually easier to display recent comments without a plugin. SImply add the following code to the desired location within your theme’s template files: <?php global $wpdb; $sql = "SELECT DISTINCT ID, post_title, post_password, comment_ID, comment_post_ID, comment_author, comment_date_gmt, comment_approved, comment_type,comment_author_url, SUBSTRING(comment_content,1,50) // NUMBER OF CHARACTERS AS com_excerpt FROM $wpdb->comments LEFT OUTER JOIN $wpdb->posts ON ($wpdb->comments.comment_post_ID = $wpdb->posts.ID) WHERE comment_approved = '1' AND comment_type = '' AND post_password = '' ORDER BY comment_date_gmt DESC LIMIT 5"; // NUMBER OF COMMENTS $comments = $wpdb->get_results($sql); $output = $pre_HTML; $output .= "\\n<ul>"; foreach ($comments as $comment) { $output .= "\\n<li>"."<a href=\\"" . get_permalink($comment->ID) . "#comment-" . $comment->comment_ID . "\\" title=\\"on " . $comment->post_title . "\\">" .strip_tags($comment->comment_author) .":<br/><div>" . strip_tags($comment->com_excerpt) ."</div></a></li>"; } $output .= "\\n</ul>"; $output .= $post_HTML; echo $output; ?> This code will display the 5 most recent comments in the following (X)HTML output format: <ul> <li> <a href="http://domain.tld/post#comment-01" title="on Post Title">Comment Author:<br /> <div>This is the first 50 characters of the first most recent comment</div></a> </li> <li> <a href="http://domain.tld/post#comment-01" title="on Post Title">Comment Author:<br /> <div>This is the first 50 characters of the first most recent comment</div></a> </li> <li> <a href="http://domain.tld/post#comment-01" title="on Post Title">Comment Author:<br /> <div>This is the first 50 characters of the first most recent comment</div></a> </li> <li> <a href="http://domain.tld/post#comment-01" title="on Post Title">Comment Author:<br /> <div>This is the first 50 characters of the first most recent comment</div></a> </li> <li> <a href="http://domain.tld/post#comment-01" title="on Post Title">Comment Author:<br /> <div>This is the first 50 characters of the first most recent comment</div></a> </li> </ul> By editing the commented lines in the PHP script, you may specify alternate number of comments and characters. Source: StylizedWeb Display Most Commented Posts without a Plugin ? Here is another trick that will enable you avoid yet another needless plugin. This code results in the display of your most-commented posts in list format: <ul> <?php $result = $wpdb->get_results("SELECT comment_count, ID, post_title FROM $wpdb->posts ORDER BY comment_count DESC LIMIT 0 , 10"); // NUMBER OF POSTS foreach ($result as $topten) { $postid = $topten->ID; $title = $topten->post_title; $commentcount = $topten->comment_count; if ($commentcount != 0) { ?> <li><a href="<?php echo get_permalink($postid); ?>"><?php echo $title ?></a></li> <?php } } ?> </ul> This code may be modified to display any number of posts by changing the LIMIT from “10” to whatever you wish. You may also change the display order from DESC (descending order) to ASC (ascending order). Once in place, this code will display a list of the 10 most-commented posts in the following (X)HTML output format: <ul> <li><a href="http://domain.tld/post-01/">Post Title 01</a></li> <li><a href="http://domain.tld/post-02/">Post Title 02</a></li> <li><a href="http://domain.tld/post-03/">Post Title 03</a></li> . . . </ul> Source: StylizedWeb Change Permalinks from Date-Based to Post-Date Only ? Here is an HTAccess method for switching your permalinks from the lengthy date-based format (i.e., http://domain.tld/2009/03/03/post-name/) to the concise post-name format (i.e., http://domain.tld/post-name/). To do so, first login to the WordPress Admin and switch your permalink structure from this: /%year%/%monthnum%/%day%/%postname%/ ..to this: /%postname%/ This change will ensure that all future posts are located at the new post-name-only URL, but we still need to redirect all requests for existing posts via the old date-based URL format. This is easily accomplished with a single directive in your site’s root HTAccess file: RedirectMatch 301 /([0-9]+)/([0-9]+)/([0-9]+)/(.*)$ http://domain.tld/$4 And that’s all there is to it! Remember to test vigorously to convince yourself that everything is working properly. Source: Perishable Press Test for Sub-Pages ? Until WordPress includes an is_subpage() function, here is a manual method of testing for sub-pages: <?php global $post; if ( is_page() && $post->post_parent ) { // subpage content goes here } else { // non-subpage content goes here } ?> Further, here are some other ways to use this method to test for different combinations of pages and sub-pages: <?php if (is_page('about') || $post->post_parent == '1') { $banner = 'business.png'; } elseif (is_page('archives') || $post->post_parent == '2') { $banner = 'pleasure.png'; } elseif (is_page('contact') || $post->post_parent == '3') { $banner = 'personal.png'; } else { $banner = 'default.png'; } ?> Note that the numbers “1”, “2”, and “3” represent the IDs of the target parent pages. Multiple Widgetizable Sidebars ? Instead of using multiple “if” statements to include multiple widgetizable areas, WPEngineer shows us how to do it a better way: <?php // multiple widgetizable sidebars if (function_exists('register_sidebar')) { $sidebars = array('Home Sidebar', 'Post Sidebar', 'Page Sidebar'); foreach($sidebars as $name) { register_sidebar(array('name'=> $name, 'before_widget' => '<div id="%1$s" class="widget %2$s">', 'after_widget' => '</div>', 'before_title' => '<h3 class="widgetTitle">', 'after_title' => '</h3>', )); } } ?> Source: wpengineer Remove Fancy Quotes from Comments ? Prevent invalid markup and sloppy code by disabling WordPress’ automatic generation of “fancy” or “curly” quotes where they fail the most: your comments area. Only one simple line of code is required, placed into your theme’s functions.php file: remove_filter(‘comment_text’, ‘wptexturize’); Source: WPRecipes.com Display a List of All Untagged Posts ? Here is an easy way to display a list of all untagged posts. All that’s required is a custom loop and a quick check of the get_the_tags variable. Here is the code to make it work: <?php query_posts('orderby=title&order=asc&showposts=-1'); ?> <?php if (have_posts()) : ?> <ul> <?php while (have_posts()) : the_post(); ?> <?php $tag = get_the_tags(); if (!$tag) { ?> <li><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a> <?php edit_post_link('Edit', ' ',''); ?></li> <?php } ?> <?php endwhile; ?> </ul> <?php endif; ?> Place that snippet into the theme file of your choice and navigate to that page in a browser to see a permlink-linked list of all posts that have not yet been tagged. Even better, next to each post title will be a an easy-access “Edit” link that will make it easy to quickly edit each of your untagged posts and add some tags, if necessary. Nothing on this planet could be easier. Almost. Easy Display of Custom Headers, Footers, and Sidebars ? WordPress 2.7 includes new functionality that makes it super-easy to include custom headers, footers, and sidebars into your theme. Normally, you include the default files with the following tags: <?php get_header(); ?> <?php get_sidebar(); ?> <?php get_footer(); ?> These will include the files named “header.php”, “sidebar.php”, and “footer.php”, respectively. Now, to include alternate versions of these files, simply include the name of the file as a parameter in its associated tag. Here is an example that should illustrate the idea: <?php get_header('custom-header'); ?> <?php get_sidebar('custom-sidebar'); ?> <?php get_footer('custom-footer'); ?> These will include the files named “custom-header.php”, “custom-sidebar.php”, and “custom-footer.php”, respectively. We can now use this new functionality to get fine-grained with includes. For example, if we wanted to display a custom footer for the “Bananaz” category, we could use the following code: <?php if is_category('Bananaz') { get_footer('Bananaz'); } else { get_footer(); } ?> Source: WordPress Codex A Better Way for Users to Logout ? The old way of displaying a “Logout” link for your users looks like this: <a href="<?php echo get_option('siteurl'); ?>/wp-login.php?action=logout">Logout</a> Now, since WordPress 2.7, we can simplify this hodgepodge with a sleeker, cleaner, built-in template tag: <a href="<?php echo wp_logout_url(); ?>">Logout</a> Sweetness. Display a Custom Message on a Specific Date ? Using a snippet of PHP, we can display a custom message (or any code, markup, or content) on a specific date: <?php if ((date('m') == 4) && (date('d') == 9)) { ?> <p>Today is <a href="http://naked.dustindiaz.com/">CSS Naked Day</a>!</p> <?php } ?> You could even use this technique to join in on CSS Naked Day by removing your stylesheet on that day. Simply wrap your CSS <link> as follows: <?php // strip for CSS Naked Day if ((date('m') !== 4) && (date('d') !== 9)) { ?> <link rel="stylesheet" href="<?php bloginfo('stylesheet_url'); ?>" type="text/css" media="screen" /> <?php } ?> The possibilities are endless! Display Three Columns of Posts ? Displaying content in multiple columns is a much sought-after WordPress technique. There are some good tutorials around explaining various ways of doing the job, but this one is perhaps the easiest. To display your posts in three columns, begin by segmenting your post with some HTML comments: Lorem ipsum blah blah. This content appears before the three columns. <!--column--> This content will appear in the first column. <!--column--> This content will appear in the second column. <!--column--> This content will appear in the third column. The next step is to create columns based on the markup comments. Open your theme file and include the following code within the loop: <?php // multiple columns $page_columns = explode("<--column-->", $post->post_content); echo $page_columns[0]; // before columns echo '<div class="first column">'.$page_columns[1].'</div>'; // first column echo '<div class="second column">'.$page_columns[2].'</div>'; // second column echo '<div class="third column">'.$page_columns[3].'</div>'; // third column ?> That’s essentially all there is to it. To get the columns to actually look like columns, add something similar to the following in your CSS file: /* column structure */ .column { margin-right: 10px; float: left; width: 33%; } /* column styles */ column.first, column.second, column.third {} The cool thing about this method is that you have full control over the layout of each particular post. Each column may contain as much or as little content as desired, and adding or removing columns is straightforward. Even better is that you can easily remove the column functionality and display your content in a single column by simply removing the custom code from the loop. The post markup consists of HTML comments, so they will be ignored if not acted upon from within the loop. Source: Enhanced version of krimsly’s technique (via the WP Codex) Disable WordPress Search Functionality ? Disabling the WordPress search functionality is as simple as adding the following code to your functions.php file: function fb_filter_query($query, $error = true) {
// to error if ($error == true) $query->is_404 = true; } } if (!is_admin()) { add_action('parse_query', 'fb_filter_query'); add_filter('get_search_form', create_function('$a', "return null;")); } In place, this code will disable the search form for your theme while leaving search functionality intact for the Admin area. As is, the $error variable is set to TRUE, which causes the function to display the theme’s error page. Setting this variable to FALSE will prevent the error message and keep the user on the same page. Source: WPengineer Display Posts with Specific Custom Fields ? Displaying posts that are associated with a certain custom field is as easy as adding an “if” condition to your loop. Here is an example that checks for the presence of a custom field called “name-of-custom-field”. If such a custom field is associated with the post, the entire post is displayed; otherwise, only the excerpt is displayed. <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php $custom_field = get_post_custom_values("name-of-custom-field"); ?> <?php if (isset($custom_field[0])) { ?> <h1><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h1> <?php the_content(); ?> <?php } else { ?> <h2><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h2> <?php the_excerpt(); ?> <?php } ?> <?php endwhile; endif; ?> To get more specific and display only posts associated with a custom-field that is set to a certain value, we simply add an additional parameter to the “if” condition: <?php if ((isset($custom_field[0])) && ($custom_field[0] == "name-of-value")) { ?> Using that line of code, we modify our previous loop as follows: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php $custom_field = get_post_custom_values("name-of-custom-field"); ?> <?php if ((isset($custom_field[0])) && ($custom_field[0] == "name-of-value")) { ?> <h1><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h1> <?php the_content(); ?> <?php } else { ?> <h2><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h2> <?php the_excerpt(); ?> <?php } ?> <?php endwhile; endif; ?> With this code, any post with a custom-field of “name-of-custom-field” that has a specific value of “name-of-value” will be displayed in its entirety. All other posts will be displayed as an excerpt. Source: Perishable Press How to Number Your Comments, Pingbacks, and Trackbacks in 2.7+ ? Numbering comments, pingbacks, and trackbacks in WordPress versions 2.7 and greater requires two steps. First, you need to add a couple of parameters to your comments_template tag, which is used to display your comments template and normally located in your single.php file. Edit this tag so that it looks like this: <?php comments_template('/comments.php',true); ?> Once this is in place, you can display the number of your comments, pingbacks, trackbacks, and both using the following tags: echo count($wp_query->comments_by_type['comment']); // display comment count echo count($wp_query->comments_by_type['pingback']); // display pingback count echo count($wp_query->comments_by_type['trackback']); // display trackback count echo count($wp_query->comments_by_type['pings']); // display pingback and trackback count comments_number('No Responses', 'One Response', '% Responses' ); // display total response count These tags can be placed anywhere in your comments loop. For more information on how to implement this, check out our in-depth article at Digging into WordPress. How to Number Your Comments Using the Classic Loop ? Before, WordPress added the new comments API in version 2.7, the “classic” comment-loop mechanism was used. This loop still works in any version of WordPress, and is useful for extreme formatting of the comment display area. Numbering your comments in the classic loop is as easy as it is in the new-fangled loop. Here’s how: In your comments.php file, add a counter variable ( <?php $i = 0; ?> ) just above the loop’s foreach statement, like so: <?php $i = 0; ?> <?php foreach ($comments as $comment) : ?> Then, to increment the counter variable with each iteration of the loop, we add another snippet just below the foreach line, like so: <?php $i = 0; ?> <?php foreach ($comments as $comment) : ?> <?php $i++; ?> Everything is now set. To display the number of comments, simply echo the value of the counter variable anywhere within your comment loop. Here is an example: There are comments so far! Source: Digging into WordPress Invite Readers to Comment via Feed ? Nice little snippet showing how to invite your readers to leave a comment by clicking on a link within your feed. Just add the following code to your theme’s functions.php file: // comment invite feed link function rss_comment_footer($content) { if (is_feed()) { if (comments_open()) { $content .= 'Comments are open! <a href="'.get_permalink().'">Add yours!</a>'; } } return $content; } In place, this function will output a link that says, “Comments are open! Add yours!” This message will be displayed at the end of each post for which comments are open. If comments are closed, no invite message is displayed. Source: Hendry Lee Display the Total Number of Users for Your Blog ? Here is a tasty little snippet from WPRecipes that will enable you to display the total number of users for your WordPress-powered blog. All you need to do is place the following code in your theme file(s) where you would like to display your total number of users: $users = $wpdb->get_var("SELECT COUNT(ID) FROM $wpdb->users"); echo $users." registered users."; Source: WPRecipes.com Automatically Insert Content into Your WordPress Post Editor ? Here is a nice way to automatically insert some custom content into your post editor. This makes it easy to add repetitive content to your posts while retaining the ability to make changes before publishing. To try it out, add the following code to your functions.php file: <?php // auto-insert content to post editor function my_editor_content($content) { $content = "<h5>Thank you for your generous attention!</h5>."; return $content; } add_filter('default_content', 'my_editor_content'); ?> This code will display a message thanking people for their generous attention, but you can easily edit the message to display whatever content (text/markup) that you wish. After configuring your message, open your WordPress text editor to see the automatically inserted content. Source: Justin Tadlock How to Prevent Duplicate Content ? Unless you’re using excerpts for non-single page views, your post content is being displayed in your single pages, date-based archives, category archive, tags archives, author archives, and so on. From an SEO perspective, this “duplicate” content may be detrimental to your search-engine rankings. To prevent duplicate content, we can conditionally display one of two <meta> tags depending on the type of page being displayed. Pages that we want to have indexed in the search engines will display a “meta-index” tag, while duplicate pages will display a “meta-noindex” tag. To do this, simply add the following code to the <head> section of your theme’s header.php file: <?php if ((is_home() && ($paged < 2 )) || is_single() || is_page() || is_category()) { echo '<meta name="robots" content="index,archive,follow" />'; } else { echo '<meta name="robots" content="noindex,noarchive,follow" />'; } Once in place, this code effectively stops search engines from indexing all types of pages except for single-post, page-page, category-archive, and the first two index pages. These are considered by many to be the most effective pages to have indexed, but feel free to add or remove anything you see fit to customize the technique. Source: Perishable Press Conditionally Display Full Posts or Excerpts ? By default, you can either display full-posts or excerpts when displaying your posts. This may be fine for common blogging purposes, but specialized blogs may find it beneficial to exercise control over which type of post format is displayed. Here’s how to conditionally display either full-post or excerpt based on the presence of a custom field named “full-post-display”. To implement this technique, setup the following loop in your theme file(s): <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php $customdisplay = get_post_custom_values("full-post-display"); ?> <?php if (isset($customdisplay[0])) { ?>
<h1><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h1> <?php the_content(); ?> <?php } else { ?> <h1><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></h1> <?php the_excerpt(); ?> <?php } ?> <?php endwhile; endif; ?> Then, for any post that you would like to display with full-post formatting, simply add a custom-field of “full-post-display” and give it a value of “true”. Display Related Posts without a Plugin ? We don’t need no stinking plugins to display related posts! Here’s how to do the job using tags as the associative criteria. Place the following code in your loop and take a nap or something: <?php // related posts based on first tag of current post $tags = wp_get_post_tags($post->ID); if ($tags) { echo '<h3>Related Posts</h3>'; $first_tag = $tags[0]->term_id; $args = array( 'tag__in' => array($first_tag), 'post__not_in' => array($post->ID), 'showposts' => 7, // how many posts? 'caller_get_posts' => 1 ); $my_query = new WP_Query($args); if ($my_query->have_posts()) { ?> <ul> <?php while ($my_query->have_posts()) : $my_query->the_post(); ?> <li><a href="<?php the_permalink(); ?>"><?php the_title(); ?></a></li> <?php endwhile; ?> </ul> <?php } ?> <?php } ?> Customize as needed. To change the number of posts, edit the line that says, “how many posts?” Source: Enhanced version of the code provided by MichaelH (via WP Codex) Drop-Dead Easy Styles for Author Comments ? This is almost too easy. To make your Author comments stand out from the crowd in WordPress 2.7 or better, use this code to apply some custom CSS stylez: li.bypostauthor { background: red; color: white; } li.byuser { background: white; color: black; } Display Upcoming Scheduled Posts ? Here’s an easy way to display a list of posts that are scheduled to be published at some point in the future. Create a page called “Upcoming Posts” (or whatever), and use this code for the loop: <?php query_posts('showposts=7&post_status=future'); ?> <?php if (have_posts()) : ?> <h3>Upcoming Scheduled Posts</h3> <ul> <?php while (have_posts()) : the_post(); ?> <li><?php the_title(); ?> — <?php the_time('l, F j, Y'); ?></li> <?php endwhile; ?> </ul> <?php else: ?> <p>Nothing new in queue!</p> <?php endif; ?> In place, this code will output a list of all posts that exist within the database that have a post_status of “future”. I.e., anything that you have setup in draft mode that is set to auto-publish at a certain point in the future. Display Automatic TinyURLs for Your Posts ? Make it super-easy for your visitors to share the URL of your posts with their favorite social-media service. Providing an alternate “short” version of your URLs is possible using the free TinyURL service and a couple snippets of code. To display short URLs at the end of your posts, place this code into your theme’s functions.php file: function getTinyUrl($url) { $tinyurl = file_get_contents("http://tinyurl.com/api-create.php?url=".$url); return $tinyurl; } Then, call the function and display the URL by placing this code into your single.php file in the desired location within the loop: <?php $turl = getTinyUrl(get_permalink($post->ID)); echo 'TinyURL for this post: <a href="'.$turl.'">'.$turl.'</a>'; ?> That’s it! Your posts now feature super-short URLs for all of your tweet-hungry visitors. Tuper Tweet Tude! Source: Perishable Press Implement a Site-Maintenance Page for Your Blog ? Ever do maintenance on your site? Certainly, we all do. Here’s an easy way to display a “site-maintenance” page that will display whatever content you desire. The key here is setting up your HTAccess file to handle the redirect properly. First, you need to create your maintenance page. This can be as simple or as advanced as you would like. At minimum, you could include something like this into a file named “maintenance.html”: <h1>Site Maintenance</h1> <p>Please check back in 15 minutes</p> Then, add this bit of voodoo to your site’s root htaccess file: # SITE MAINTENANCE PAGE RewriteEngine on RewriteCond %{REQUEST_URI} !/maintenance.html$ RewriteCond %{REMOTE_ADDR} !^111\\.222\\.333\\.444 RewriteRule $/maintenance.html [R=302,L] Once that’s in place, replace the example IP address with that of your own. Upload to your site and check it out. What you will see is that you have full access to your site, but all other visitors will see the maintenance page. Once maintenance is complete, simply comment out the code in your htaccess file to allow visitors back into the site. Source: Catswhocode Display the First Image from Each of Your Posts ? If your posts include an image that you would like to display as a thumbnail elsewhere on your blog, here is an easy way to do it with no custom fields required. Place the following code into your theme’s functions.php file: function catch_that_image() { global $post, $posts; $first_img = ''; ob_start(); ob_end_clean(); $output = preg_match_all('/<img.+src=[\\'"]([^\\'"]+)[\\'"].*>/i', $post->post_content, $matches); $first_img = $matches [1] [0]; if(empty($first_img)){ $first_img = "/images/default.jpg"; // default image } return $first_img; } Then, to call the function and display the images as thumbnails, place the following code into the desired location within your loop: <?php echo catch_that_image(); ?> That’s all there is to it. If you would like to display a default image for posts that may not have one, specify its path in the code (on the line that says “default image). Source: WPRecipes Display Most Popular Posts without a Plugin ? Simple but effective method of displaying your blog’s most popular posts based on comment count. This code snippet may be placed anywhere within your theme’s files (i.e., no loop required). Check it out: <h3>Popular Posts</h3> <ul> <?php $result = $wpdb->get_results(" SELECT comment_count, ID, post_title FROM $wpdb->posts ORDER BY comment_count DESC LIMIT 0 , 7 "); foreach ($result as $post) { setup_postdata($post); $postid = $post->ID; $title = $post->post_title; $commentcount = $post->comment_count; if ($commentcount != 0) { ?> <li><a href="<?php echo get_permalink($postid); ?>"> <?php echo $title; ?></a> [<?php echo $commentcount ?>]</li> <?php } ?> <?php } ?> </ul> Once in place, this code will display the seven most popular posts along with their associated comment count in unordered list format. Customize according to your needs. Source: ProBlogDesign (404 link removed 2013/09/15) Automatically Highlight Search Terms ? Make things easy for people who are searching your site by applying some custom styling to the search terms that are displayed in the search results. A common way to display search terms is with a yellow background so that users can easily identify locations of the text that may apply to their query. It’s all about about usability, and improving the way search results are displayed on your site. Here’s how to do it: First, replace the the_title() tag in your search.php file with the following: <?php // highlight search terms in title $title = get_the_title(); $keys = explode(" ", $s); $title = preg_replace('/('.implode('|',$keys).')/iu','<span class="search-terms">\\0</span>',$title); echo $title; ?> This will setup styling for search terms located in the title of each result. Then, for the content, replace the the_excerpt() tag in your search.php file with the following: <?php // highlight search terms in content $excerpt = get_the_excerpt(); $keys = explode(" ", $s); $excerpt = preg_replace('/('.implode('|',$keys).')/iu','<span class="search-terms">\\0</span>',$excerpt); echo $excerpt; ?> Finally, open your theme’s CSS file and add some custom styles for the search terms. A great way to highlight each term is to display it in bold text with yellow highlighting. Something like this: span.search-terms { background: yellow; font-weight: bold; } That’s all there is to it! Go run a few searches to see it in action. Source: Enhanced version of code provided by Yoast.com Automatically Disable Widgets ? Quick tip to disable all widget functionality from your theme. Add the following to your functions.php file and call it done: <?php // disable all widgets function disable_all_widgets($sidebars_widgets) { $sidebars_widgets = array(false); return $sidebars_widgets; } add_filter('sidebars_widgets', 'disable_all_widgets'); ?> Source: Justin Tadlock Display All Images from Your Post Content ? Want to display all of the images from each of your posts somewhere on your blog? Easy. Check out this code snippet from Matt Varone: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php $szPostContent = $post->post_content; $szSearchPattern = '~<img [^\\>]*\\ />~'; // Run preg_match_all to grab all the images and save the results in $aPics preg_match_all($szSearchPattern, $szPostContent, $aPics); // Check to see if we have at least 1 image $iNumberOfPics = count($aPics[0]); if ($iNumberOfPics > 0) { // now here you would do whatever you need to do with the images // for this example the images are just displayed for ( $i=0; $i < $iNumberOfPics ; $i++ ) { echo $aPics[0][$i]; }; }; endwhile; endif; ?> Just customize the output in the second part of the code (see code comments) and paste the function wherever you would like to display the images. Sweetness. Source: Matt Varone Display Category List in Two Columns ? Tired of that boring, single-column category display? Spice things up with a spiffy two-column category list that will get your visitors’ hearts pumping. Let’s deface a WordPress tag, shall we? See this bad boy: <?php wp_list_categories(); ?> We’re going to blow it up, divide its contents into two pieces, and spit it all back out as two unordered lists. Impossible, you say? Nah, just a little PHP to make it all go. Wherever you would like to display your categories in two columns, throw down the following code snippet: <?php // display categories in columns $cats = explode("<br />",wp_list_categories('title_li=&echo=0&depth=1&style=none')); $cat_n = count($cats) - 1; for ($i=0;$i<$cat_n;$i++) : if ($i<$cat_n/2) : $cat_left = $cat_left.'<li>'.$cats[$i].'</li>'; elseif ($i>=$cat_n/2): $cat_right = $cat_right.'<li>'.$cats[$i].'</li>'; endif; endfor; ?> <ul class="left"> <?php echo $cat_left;?> </ul> <ul class="right"> <?php echo $cat_right;?> </ul> Completely awesome. Now let’s add some style to make the columns work: .right { float: left; width: 140px; } .left { float: left; width: 140px; } You are all set. You should probably fine-tune this business until it’s all good. You know. Source: Blog Oh Blog (404 link removed 2013/06/24) Show Ads or Other Content Only in the First Three Posts ? Advertising may require you to limit the number of advertisements on your page to three. For some, this is three too many. For others, it’s far too few. Still others feel that it’s just the right amount. Regardless of your feelings, here is a trick that will enable you to limit the number of posts that displays some specific content - ads, images, scripts, whatever you want. Check out the three indented lines in the following loop: <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <?php if ($wp_query->current_post < 3) { ?> <!-- any content here will be displayed only in first three posts --> <?php } ?> <?php endwhile; else: ?> <?php endif; ?> See what’s happening here. We’ve got a loop, see. In this loop, we specify a condition that says, “if this is one of the first three posts, display this content.” And that’s the magic. Of course, you can use whatever content you would like, and there is nothing special about the number “3” either. Source: Blog Oh Blog (404 link removed 2013/06/24) A Better Way to Display Recent Comments without a Plugin ? Here is a better way to display your recent comments without a plugin. Instead of slapping a bunch of gnarly code into our index.php or sidebar.php file, we are going to slap it right where it belongs: in your theme’s functions.php file. Here is the code, all exploded for your viewing and analytical pleasure (well, for mine anyway). For a more minified version of this snippet, be sure to check out the source link. <?php // display recent comments without a plugin function recent_comments($src_count=10, $src_length=60, $pre_HTML='<ul>', $post_HTML='</ul>') { global $wpdb; $sql = " SELECT DISTINCT ID, post_title, post_password, comment_ID, comment_post_ID, comment_author, comment_date_gmt, comment_approved, comment_type, SUBSTRING( comment_content, 1, $src_length ) AS com_excerpt FROM $wpdb->comments LEFT OUTER JOIN $wpdb->posts ON ( $wpdb->comments.comment_post_ID = $wpdb->posts.ID ) WHERE comment_approved = '1' AND comment_type = '' AND post_password = '' ORDER BY comment_date_gmt DESC LIMIT $src_count "; $comments = $wpdb->get_results($sql); $output = $pre_HTML; foreach ($comments as $comment) { $output .= '<li><a href="'.get_permalink($comment->ID).'#comment-'.$comment->comment_ID.'" title="on '.$comment->post_title.'">'.strip_tags($comment->com_excerpt).'...</a></li>'; } $output .= $post_HTML; echo $output; } ?> Ah, it’s a thing of beauty. Once you have that code in place, rock it out anywhere in your theme with this charming little tag: <?php recent_comments(); ?> see also: Display Latest Comments without a PluginSource: Blog Oh Blog (404 link removed 2013/06/24) Selectively Disable Automatic Post Formatting ? This trick is by far my favorite “stupid WordPress trick.” You know how WordPress likes to mangle HTML comments, empty elements, blockquotes, curly quotes, and other miscellaneous markup elements? Here is a tight little method that will enable you to selectively disable WordPress’ automatic post formatting. Do this: Place the following code into your theme’s functions.php file: // disable auto-formatting function my_formatter($content) { $new_content = ''; $pattern_full = '{(\\[raw\\].*?\\[/raw\\])}is'; $pattern_contents = '{\\[raw\\](.*?)\\[/raw\\]}is'; $pieces = preg_split($pattern_full, $content, -1, PREG_SPLIT_DELIM_CAPTURE); foreach ($pieces as $piece) { if (preg_match($pattern_contents, $piece, $matches)) { $new_content .= $matches[1]; } else { $new_content .= wptexturize(wpautop($piece)); } } return $new_content; } remove_filter('the_content', 'wpautop'); remove_filter('the_content', 'wptexturize'); add_filter('the_content', 'my_formatter', 99); Then do this: Use the [raw] shortcode wherever you would like to disable auto-formatting in your post content. For example, if you wanted to prevent the following sentence from being formatted, you would write this: [raw]This text will not be automatically formatted.[/raw] Absolutely brilliant. Source: WPRecipes Browser Detection via WordPress’ body_class Function ? WordPress makes it possible to detect a handful of different browsers using a variety of built-in global variables. WordPress also provides a body_class tag that outputs a variety of class attributes depending on various page properties. Why not combine these two techniques so that the user’s detected browser is added to the list of output classes for the body tag? Here’s the code that will do it via functions.php: // browser detection via body_class function browser_body_class($classes) { global $is_lynx, $is_gecko, $is_IE, $is_opera, $is_NS4, $is_safari, $is_chrome, $is_iphone; if($is_lynx) $classes[] = 'lynx'; elseif($is_gecko) $classes[] = 'gecko'; elseif($is_opera) $classes[] = 'opera'; elseif($is_NS4) $classes[] = 'ns4'; elseif($is_safari) $classes[] = 'safari'; elseif($is_chrome) $classes[] = 'chrome'; elseif($is_IE) $classes[] = 'ie'; else $classes[] = 'unknown'; if($is_iphone) $classes[] = 'iphone'; return $classes; } add_filter('body_class','browser_body_class'); This code will output the detected browser along with the other body_class tags. Here is an example: <body class="home blog logged-in safari"> Hooked. Sources: Nathan Rice Get Post or Page Contents as a PHP Variable ? Here is a quick snippet for placing all post or page content into a variable. We’re talking the entire page contents here, not just the content of the post. Place this code into your theme’s functions.php file: // post contents as variable function callback($buffer) { return $buffer; } function buffer_start() { ob_start("callback"); } function buffer_end() { ob_end_flush(); } add_action('wp_head', 'buffer_start'); add_action('wp_footer', 'buffer_end'); Once in place, this function will capture the entire page contents into a variable called “$buffer”. You may then do whatever you wish to this variable. Filter it, match it, slap it around a little and show it who’s boss. That sort of thing. Source: Dagon DesignSee also: Digging into WordPress Simple Example of How to Use WordPress Cron ? I have been meaning to get into WordPress’ wp-cron functionality, and this looks like a good way to get started with it. This code snippet uses wp-cron to schedule an automatic email that will be sent every hour. // send automatic scheduled email if (!wp_next_scheduled('my_task_hook')) { wp_schedule_event(time(), 'hourly', 'my_task_hook'); } add_action('my_task_hook', 'my_task_function'); function my_task_function() { wp_mail('you@yoursite.com', 'Automatic email', 'Hello, this is an automatically scheduled email from WordPress.'); } Of course, this is meant only as an example. The key here is to schedule and event and then hook into it with some specific function. Source: slaven.net (404 link removed 2013/02/04) Add More Default Avatar Choices to the WordPress Admin ? Here is a quick and easy way to add more default avatars to the list of available gravatars in the Settings area of the WordPress Admin. Here is the functions.php code to make it happen: // add more default avatars to options if (!function_exists('fb_addgravatar')) { function fb_addgravatar($avatar_defaults) { $myavatar1 = get_bloginfo('template_directory').'/images/avatar-01.png'; $avatar_defaults[$myavatar1] = 'dude';
<meta name="viewport" content="width=device-width, initial-scale=1.0" /> <meta charset="UTF-8"> <!-- Favicon --> <link rel="icon" type="image/x-icon" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/favicon.ico" /><link rel="shortcut icon" type="image/x-icon" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/favicon.ico" /><link type="image/x-icon" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/favicon.ico" /> <!-- Windows 8 Tiles and Feed --> <meta name="application-name" content="Smashing Magazine"/> <meta name="msapplication-TileColor" content="#e53b2c"/> <meta name="msapplication-square70x70logo" content="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/smashing-windows-icon-70-70.png"/> <meta name="msapplication-square150x150logo" content="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/smashing-windows-icon-150-150.png"/> <meta name="msapplication-wide310x150logo" content="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/smashing-windows-icon-310-150.png"/> <meta name="msapplication-square310x310logo" content="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/smashing-windows-icon-310-310.png"/> <meta name="msapplication-notification" content="frequency=30;polling-uri=http://notifications.buildmypinnedsite.com/?feed=http://www.smashingmagazine.com/feed/&id=1;polling-uri2=http://notifications.buildmypinnedsite.com/?feed=http://www.smashingmagazine.com/feed/&id=2;polling-uri3=http://notifications.buildmypinnedsite.com/?feed=http://www.smashingmagazine.com/feed/&id=3;polling-uri4=http://notifications.buildmypinnedsite.com/?feed=http://www.smashingmagazine.com/feed/&id=4;polling-uri5=http://notifications.buildmypinnedsite.com/?feed=http://www.smashingmagazine.com/feed/&id=5; cycle=1"/> <!-- iOS Icons --> <link rel="apple-touch-icon-precomposed" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/apple-touch-icon-precomposed.png" /> <link rel="apple-touch-icon-precomposed" sizes="57x57" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/apple-touch-icon-57x57-precomposed.png" /> <link rel="apple-touch-icon-precomposed" sizes="72x72" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/apple-touch-icon-72x72-precomposed.png" /> <link rel="apple-touch-icon-precomposed" sizes="114x114" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/apple-touch-icon-114x114-precomposed.png" /> <link rel="apple-touch-icon-precomposed" sizes="144x144" href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/apple-touch-icon-144x144-precomposed.png" /> <!-- This site is optimized with the Yoast WordPress SEO plugin v1.5.2.7 - https://yoast.com/wordpress/plugins/seo/ --> <meta name="description" content="Plugins are a major part of why WordPress powers millions of blogs and websites around the world. The ability to extend WordPress to meet just about any need is a powerful motivator for choosing WordPress over other alternatives."/> <link rel="canonical" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/" /> <link rel="publisher" href="https://plus.google.com/+SmashingMagazine?"/> <meta property="og:locale" content="en_US" /> <meta property="og:type" content="article" /> <meta property="og:title" content="Ten Things Every WordPress Plugin Developer Should Know - Smashing Magazine" /> <meta property="og:description" content="Plugins are a major part of why WordPress powers millions of blogs and websites around the world. The ability to extend WordPress to meet just about any need is a powerful motivator for choosing WordPress over other alternatives." /> <meta property="og:url" content="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/" /> <meta property="og:site_name" content="Smashing Magazine" /> <meta property="article:publisher" content="https://www.facebook.com/smashmag" /> <meta property="article:tag" content="Essentials" /> <meta property="article:tag" content="PHP" /> <meta property="article:tag" content="Plugins" /> <meta property="article:tag" content="Techniques (WP)" /> <meta property="article:section" content="WordPress" /> <meta property="article:published_time" content="2011-03-08T05:35:31+01:00" /> <meta property="article:modified_time" content="2014-04-25T13:28:41+02:00" /> <meta property="og:updated_time" content="2014-04-25T13:28:41+02:00" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/images/post-pictures/wordpress-blue-illu.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/03/wordpress_plugin.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-black1.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-globals1.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-profiler1.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-sql1.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-errors1.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/general-settings-same-url.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/general-settings-different-url.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/admin-menu-options-page.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/admin-menu-custom.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/plugin-action-links-none.jpg" /> <meta property="og:image" content="http://www.smashingmagazine.com/wp-content/uploads/2011/02/plugin-action-links-settings.jpg" /> <meta name="twitter:card" content="summary_large_image"/> <meta name="twitter:site" content="@smashingmag"/> <meta name="twitter:domain" content="Smashing Magazine"/> <meta name="twitter:creator" content="@arcware"/> <meta name="twitter:image:src" content="http://www.smashingmagazine.com/wp-content/uploads/images/post-pictures/wordpress-blue-illu.jpg"/> <!-- / Yoast WordPress SEO plugin. --> <link rel="alternate" type="application/rss+xml" title="Smashing Magazine » Feed" href="http://www.smashingmagazine.com/feed/" /> <link rel="alternate" type="application/rss+xml" title="Smashing Magazine » Comments Feed" href="http://www.smashingmagazine.com/comments/feed/" /> <link rel="alternate" type="application/rss+xml" title="Smashing Magazine » Ten Things Every WordPress Plugin Developer Should Know Comments Feed" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/feed/" /> <link rel='shortlink' href='http://www.smashingmagazine.com/?p=111255' /> <script type="text/javascript">!function(){function e(e,t,n){e.addEventListener?e.addEventListener(t,n,!1):e.attachEvent&&e.attachEvent("on"+t,n)}function t(e){return window.localStorage&&localStorage.font_css_cache&&localStorage.font_css_cache_file===e}function n(){if(window.localStorage&&window.XMLHttpRequest)if(t(o))a(localStorage.font_css_cache);else{var n=new XMLHttpRequest;n.open("GET",o,!0),e(n,"load",function(){4===n.readyState&&(a(n.responseText),localStorage.font_css_cache=n.responseText,localStorage.font_css_cache_file=o)}),n.send()}else{var c=document.createElement("link");c.href=o,c.rel="stylesheet",c.type="text/css",document.getElementsByTagName("head")[0].appendChild(c),document.cookie="font_css_cache"}}function a(e){var t=document.createElement("style");t.innerHTML=e,document.getElementsByTagName("head")[0].appendChild(t)}var o="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/stylesheets/webfonts.min.css?ver=1.1.0";window.localStorage&&localStorage.font_css_cache||document.cookie.indexOf("font_css_cache")>-1?n():e(window,"load",n)}();</script> <!--[if IE 8]><script type="text/javascript" src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script><link href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/stylesheets/ie8-nu.css" media="all" rel="stylesheet" type="text/css" /><![endif]--> <noscript><link href="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/stylesheets/main.min.css?ver=2014.14.0" rel="stylesheet" media="all" type="text/css" /></noscript> </head> <body class="single single-post postid-111255 single-format-standard www-section"> <nav id="top" class="tn clearfix"> <div class="mini"> <h1><span class="sr">Smashing Magazine</span><a href="http://www.smashingmagazine.com/"><img src="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/logo.png" alt="Smashing Magazine" title="Jump to the front page" /></a></h1> </div> <div class="mnb"> <a href="#mn" class="ntb">Menu</a> <a href="#ms" class="stb">Search</a> </div> <ul id="menu-network-menu" class="nw clearfix"><li class="current"><a href="http://www.smashingmagazine.com"><img src="http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/images/logo.png" alt="Smashing Magazine" title="Jump to the front page" /></a></li><li id="menu-item-77918" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-77918 menu-item-books"><a href="http://www.smashingmagazine.com/books/">Books</a></li> <li id="menu-item-78659" class="cody menu-item menu-item-type-post_type menu-item-object-page menu-item-78659 menu-item-ebooks"><a href="http://www.smashingmagazine.com/ebooks/">eBooks</a></li> <li id="menu-item-85386" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-85386 menu-item-workshops"><a href="http://www.smashingmagazine.com/smashing-workshops/">Workshops</a></li> <li id="menu-item-2" class="menu-item menu-item-type-custom menu-item-object-custom menu-item-2 menu-item-job-board"><a href="http://jobs.smashingmagazine.com/">Job Board</a></li> </ul> <ul class="ch"> <li class="rss"><a href="http://www.smashingmagazine.com/feed/" title="Subscribe to our RSS-feed (120K)">RSS</a></li> <li class="fb"><a href="http://www.facebook.com/smashmag" title="Join our Facebook page! (221k)">Facebook</a></li> <li class="tw"><a href="http://twitter.com/smashingmag" title="Follow us on Twitter! (811k)">Twitter</a></li> <li class="nl"><a href="http://www.smashingmagazine.com/the-smashing-newsletter/" title="Subscribe to our Email Newsletter (180k)">Newsletter</a></li> </ul></nav> <div class="cc"><div class="fluid clearfix"><div class="grid clearfix"> <div class="mise sf clearfix" > <form id="search" method="get" action="http://www.smashingmagazine.com/search-results/" target="_top"> <input name="q" type="text" placeholder="e.g. JavaScript" /> <button class="search_submit" type="submit">Search</button> <input type="hidden" name="cx" value="partner-pub-6779860845561969:5884617103"> <input type="hidden" name="cof" value="FORID:10"> <input type="hidden" name="ie" value="UTF-8"> </form> </div><div class="col sn"> <nav class="sct"><ul id="menu-category-menu" class="clearfix"><li id="menu-item-116" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-has-children menu-item-116 menu-item-coding"><a href="http://www.smashingmagazine.com/category/coding/">Coding</a> <ul class="sub-menu"> <li id="menu-item-2014" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2014 menu-item-css"><a href="http://www.smashingmagazine.com/tag/css/">CSS</a></li> <li id="menu-item-134810" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-134810 menu-item-html"><a href="http://www.smashingmagazine.com/tag/html/">HTML</a></li> <li id="menu-item-2015" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2015 menu-item-javascript"><a href="http://www.smashingmagazine.com/tag/javascript/">JavaScript</a></li> <li id="menu-item-2016" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2016 menu-item-techniques"><a href="http://www.smashingmagazine.com/tag/techniques/">Techniques</a></li> </ul> </li> <li id="menu-item-117" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-has-children menu-item-117 menu-item-design"><a href="http://www.smashingmagazine.com/category/design/">Design</a> <ul class="sub-menu"> <li id="menu-item-2017" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2017 menu-item-web-design"><a href="http://www.smashingmagazine.com/tag/web-design/">Web Design</a></li> <li id="menu-item-2032" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2032 menu-item-typography"><a href="http://www.smashingmagazine.com/tag/typography/">Typography</a></li> <li id="menu-item-2063" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2063 menu-item-inspiration"><a href="http://www.smashingmagazine.com/tag/inspiration/">Inspiration</a></li> <li id="menu-item-2120" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2120 menu-item-business"><a href="http://www.smashingmagazine.com/tag/business/">Business</a></li> </ul> </li> <li id="menu-item-119" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-has-children menu-item-119 menu-item-mobile"><a href="http://www.smashingmagazine.com/category/mobile/">Mobile</a> <ul class="sub-menu"> <li id="menu-item-142132" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-142132 menu-item-iphone-ipad"><a href="http://www.smashingmagazine.com/tag/ios/">iPhone & iPad</a></li> <li id="menu-item-143596" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143596 menu-item-android"><a href="http://www.smashingmagazine.com/tag/android/">Android</a></li> <li id="menu-item-143608" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143608 menu-item-design-patterns"><a href="http://www.smashingmagazine.com/tag/design-patterns/">Design Patterns</a></li> </ul> </li> <li id="menu-item-118" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-has-children menu-item-118 menu-item-graphics"><a href="http://www.smashingmagazine.com/category/graphics/">Graphics</a> <ul class="sub-menu"> <li id="menu-item-2264" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2264 menu-item-photoshop"><a href="http://www.smashingmagazine.com/tag/photoshop/">Photoshop</a></li> <li id="menu-item-160" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-160 menu-item-fireworks"><a href="http://www.smashingmagazine.com/category/fireworks/">Fireworks</a></li> <li id="menu-item-2283" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2283 menu-item-wallpapers"><a href="http://www.smashingmagazine.com/tag/wallpapers/">Wallpapers</a></li> <li id="menu-item-2305" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-2305 menu-item-freebies"><a href="http://www.smashingmagazine.com/tag/freebies/">Freebies</a></li> </ul> </li> <li id="menu-item-120" class="menu-item-uxdesign menu-item menu-item-type-taxonomy menu-item-object-category menu-item-has-children menu-item-120 menu-item-ux-design"><a href="http://www.smashingmagazine.com/category/uxdesign/">UX Design</a> <ul class="sub-menu"> <li id="menu-item-143609" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143609 menu-item-usability"><a href="http://www.smashingmagazine.com/tag/usability/">Usability</a></li> <li id="menu-item-143610" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143610 menu-item-user-experience"><a href="http://www.smashingmagazine.com/tag/user-experience/">User Experience</a></li> <li id="menu-item-143611" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143611 menu-item-ui-design"><a href="http://www.smashingmagazine.com/tag/ui/">UI Design</a></li> <li id="menu-item-143612" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143612 menu-item-e-commerce"><a href="http://www.smashingmagazine.com/tag/e-commerce/">E-Commerce</a></li> </ul> </li> <li id="menu-item-121" class="menu-item menu-item-type-taxonomy menu-item-object-category current-post-ancestor current-menu-parent current-post-parent menu-item-has-children menu-item-121 menu-item-wordpress"><a href="http://www.smashingmagazine.com/category/wordpress/"><span class="long"><span>Word</span><span>Press</span></span><span class="short">WP</span></a> <ul class="sub-menu"> <li id="menu-item-143677" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143677 menu-item-essentials"><a href="http://www.smashingmagazine.com/tag/essentials/">Essentials</a></li> <li id="menu-item-143678" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143678 menu-item-techniques"><a href="http://www.smashingmagazine.com/tag/techniques-wp/">Techniques</a></li> <li id="menu-item-143679" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143679 menu-item-plugins"><a href="http://www.smashingmagazine.com/tag/plugins/">Plugins</a></li> <li id="menu-item-143680" class="menu-item menu-item-type-taxonomy menu-item-object-post_tag menu-item-143680 menu-item-themes"><a href="http://www.smashingmagazine.com/tag/themes/">Themes</a></li> </ul> </li> </ul></nav></div> <div class="col main single"> <article class="post-111255 post type-post status-publish format-standard has-post-thumbnail hentry category-wordpress tag-essentials tag-php tag-plugins tag-techniques-wp post"> <h2><a href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/" rel="bookmark" title="Read 'Ten Things Every WordPress Plugin Developer Should Know'">Ten Things Every WordPress Plugin Developer Should Know</a></h2> <ul class="pmd clearfix"> <li class="a">By <a rel="author" class="poa" href="http://www.smashingmagazine.com/author/dave-donaldson/?rel=author" title="Posts by Dave Donaldson">Dave Donaldson</a></li> <li class="date">March 8th, 2011</li> <li class="tags"><a href="http://www.smashingmagazine.com/tag/essentials/">Essentials</a><a href="http://www.smashingmagazine.com/tag/php/">PHP</a><a href="http://www.smashingmagazine.com/tag/plugins/">Plugins</a></li> <li class="comments"><a href="#comments" title="Comment on Ten Things Every WordPress Plugin Developer Should Know">94 Comments</a> </li> </ul> <div class="ad ed"> <span class="declare">Advertisement</span> <div id="cad"></div> </div> <p>Plugins are a major part of why WordPress powers millions of blogs and websites around the world. The ability to extend WordPress to meet just about any need is a powerful motivator for choosing WordPress over other alternatives. Having written several plugins myself, I’ve come to learn many (but certainly not all) of the ins-and-outs of <strong>WordPress plugin development</strong>, and this article is a culmination of the things I think every WordPress plugin developer should know. Oh, and keep in mind everything you see here is compatible with WordPress 3.0+.</p> <h3>Don’t Develop Without Debugging</h3> <p>The first thing you should do when developing a WordPress plugin is to enable debugging, and I suggest leaving it on the entire time you’re writing plugin code. When things go wrong, WordPress raises warnings and error messages, but if you can’t see them then they might as well have not been raised at all. <p><a href="http://www.smashingmagazine.com/wp-content/uploads/2011/03/wordpress_plugin.jpg"><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/03/wordpress_plugin.jpg" alt="Screenshot" title="WordPress_Plugins" width="500" /></a><sup class="po" id="note-1"><a href="#1">1</a></sup></p> <p>Enabling debugging also turns on WordPress notices, which is important because that’s how you’ll know if you’re using any deprecated functions. Deprecated functions may be removed from future versions of WordPress, and just about every WordPress release contains functions slated to die at a later date. If you see that you are using a deprecated function, it’s best to find its replacement and use that instead.</p> <h4>How to Enable Debugging</h4> <p>By default, WordPress debugging is turned off, so to enable it, open <strong>wp-config.php</strong> (tip: make a backup copy of this file that you can revert to later if needed) in the root of your WordPress installation and look for this line:</p> <pre><code class="language-php">define('WP_DEBUG', false);</code></pre> <p>Replace that line with the following:</p> <pre><code class="language-php">// Turns WordPress debugging on define('WP_DEBUG', true); // Tells WordPress to log everything to the /wp-content/debug.log file define('WP_DEBUG_LOG', true); // Doesn't force the PHP 'display_errors' variable to be on define('WP_DEBUG_DISPLAY', false); // Hides errors from being displayed on-screen @ini_set('display_errors', 0);</code></pre> <p>With those lines added to your wp-config.php file, debugging is fully enabled. Here’s an example of a notice that got logged to /wp-content/debug.log for using a deprecated function:</p> <p><em>[15-Feb-2011 20:09:14] PHP Notice: get_usermeta is <strong>deprecated</strong> since version 3.0! Use get_user_meta() instead. in C:CodePluginswordpresswp-includesfunctions.php on line 3237</em></p> <p>With debugging enabled, <strong>keep a close eye on /wp-content/debug.log</strong> as you develop your plugin. Doing so will save you, your users, and other plugin developers a lot of headaches.</p> <h4>How to Log Your Own Debug Statements</h4> <p>So what about logging your own debug statements? Well, the simplest way is to use <code>echo</code> and see the message on the page. It’s the quick-and-dirty-hack way to debug, but everyone has done it one time or another. A better way would be to create a function that does this for you, and then you can see all of your own debug statements in the debug.log file with everything else.</p> <p>Here’s a function you can use; notice that it only logs the message if WP_DEBUG is enabled:</p> <pre><code class="language-php">function log_me($message) { if (WP_DEBUG === true) { if (is_array($message) || is_object($message)) { error_log(print_r($message, true)); } else { error_log($message); } } }</code></pre> <p>And then you can call the <code>log_me</code> function like this:</p> <pre><code class="language-php">log_me(array('This is a message' => 'for debugging purposes')); log_me('This is a message for debugging purposes');</code></pre> <h4>Use the BlackBox Debug Bar Plugin</h4> <p>I only recently discovered this plugin, but it’s already been a huge help as I work on my own plugins. The <a href="http://ditio.net/2011/01/29/wordpress-debug-bar-plugin-blackbox/">BlackBox</a><sup class="po" id="note-2"><a href="#2">2</a></sup> plugin adds a thin black bar to the top of any WordPress post or page, and provides quick access to errors, global variables, profile data, and SQL queries.</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-black1.jpg" alt="" title="debug-bar-black" width="525" height="27" class="alignnone size-full wp-image-90255" /></p> <p>Clicking on the Globals tab in the bar shows all of the global variables and their values that were part of the request, essentially everything in the $_GET, $_POST, $_COOKIE, $_SESSION, and $_SERVER variables:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-globals1.jpg" alt="" title="debug-bar-globals" width="525" height="353" class="alignnone size-full wp-image-90251" /></p> <p>The next tab is the Profiler, which displays the time that passed since the profiler was started and the total memory WordPress was using when the checkpoint was reached:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-profiler1.jpg" alt="" title="debug-bar-profiler" width="525" height="98" class="alignnone size-full wp-image-90252" /></p> <p>You can add your own checkpoints to the Profiler by putting this line of code anywhere in your plugin where you want to capture a measurement:</p> <pre><code class="language-php">apply_filters('debug', 'This is a checkpoint');</code></pre> <p>Perhaps the most valuable tab in the BlackBox plugin is the SQL tab, which shows you all of the database queries that executed as part of the request. Very useful for determining long-running database calls:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-sql1.jpg" alt="" title="debug-bar-sql" width="525" height="176" class="alignnone size-full wp-image-90253" /></p> <p>And finally we have the Errors tab, which lists all of the notices, warnings, and errors that occurred during the request:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/debug-bar-errors1.jpg" alt="" title="debug-bar-errors" width="525" height="111" class="alignnone size-full wp-image-90250" /></p> <p>By providing quick access to essential debug information, the BlackBox plugin is a big-timer when it comes to debugging your WordPress plugin.</p> <h3>Prefix Your Functions</h3> <p>One of the first things that bit me when I started developing WordPress plugins was finding out that other plugin developers sometimes use the same names for functions that I use. For example, function names like <code>copy_file()</code>, <code>save_data()</code>, and <code>database_table_exists()</code> have a decent chance of being used by other plugins in addition to yours.</p> <p>The reason for this is because when WordPress activates a plugin, PHP loads the functions from the plugin into the WordPress execution space, where all functions from all plugins live together. There is no separation or isolation of functions for each plugin, which means that <strong>each function must be uniquely named</strong>.</p> <p>Fortunately, there is an easy way around this, and it’s to name all of your plugin functions with a prefix. For example, the common functions I mentioned previously might now look like this:</p> <pre><code class="language-php">function myplugin_copy_file() { } function myplugin_save_data() { } function myplugin_database_table_exists() { }</code></pre> <p>Another common naming convention is to use a prefix that is an abbreviation of your plugin’s name, such as “My Awesome WordPress Plugin”, in which case the function names would be:</p> <pre><code class="language-php">function mawp_copy_file() { } function mawp_save_data() { } function mawp_database_table_exists() { }</code></pre> <p>There is one caveat to this, however. If you use PHP classes that contain your functions (which in many cases is a good idea), you don’t really have to worry about clashing with functions defined elsewhere. For example, let’s say you have a class in your plugin named “CommonFunctions” with a <code>copy_file()</code> function, and another plugin has the same <code>copy_file()</code> function defined, but not in a class. Invoking the two functions would look similar to this:</p> <pre><code class="language-php">// Calls the copy_file() function from your class $common = new CommonFunctions(); $common->copy_file(); // Calls the copy_file() function from the other plugin copy_file();</code></pre> <p><strong>By using classes, the need to explicitly prefix your functions goes away.</strong> Just keep in mind that WordPress will raise an error if you use a function name that’s already taken, so keep an eye on the debug.log file to know if you’re in the clear or not.</p> <h3>Global Paths Are Handy</h3> <p>Writing the PHP code to make your plugin work is one thing, but if you want to make it look and feel good at the same time, you’ll need to include some images, CSS, and perhaps a little JavaScript as well (maybe in the form of a jQuery plugin). And in typical fashion, you’ll most likely organize these files into their own folders, such as “images”, “css”, and “js”.</p> <p>That’s all well and good, but how should you code your plugin so that it can always find those files, no matter what domain the plugin is running under? The best way that I’ve found is to <strong>create your own global paths</strong> that can be used anywhere in your plugin code.</p> <p>For example, I always create four global variables for my plugins, one each for the following:</p> <ul> <li>The path to the theme directory</li> <li>The name of the plugin</li> <li>The path to the plugin directory</li> <li>The url of the plugin</li> </ul> <p>For which the code looks like this:</p> <pre><code class="language-php">if (!defined('MYPLUGIN_THEME_DIR')) define('MYPLUGIN_THEME_DIR', ABSPATH . 'wp-content/themes/' . get_template()); if (!defined('MYPLUGIN_PLUGIN_NAME')) define('MYPLUGIN_PLUGIN_NAME', trim(dirname(plugin_basename(__FILE__)), '/')); if (!defined('MYPLUGIN_PLUGIN_DIR')) define('MYPLUGIN_PLUGIN_DIR', WP_PLUGIN_DIR . '/' . MYPLUGIN_PLUGIN_NAME); if (!defined('MYPLUGIN_PLUGIN_URL')) define('MYPLUGIN_PLUGIN_URL', WP_PLUGIN_URL . '/' . MYPLUGIN_PLUGIN_NAME);</code></pre> <p>Having these global paths defined lets me write the code below in my plugin anywhere I need to, and I know it will resolve correctly for any website that uses the plugin:</p> <pre><code class="language-php">$image = MYPLUGIN_PLUGIN_URL . '/images/my-image.jpg'; $style = MYPLUGIN_PLUGIN_URL . '/css/my-style.css'; $script = MYPLUGIN_PLUGIN_URL . '/js/my-script.js';</code></pre> <h3>Store the Plugin Version for Upgrades</h3> <p>When it comes to WordPress plugins, one of the things you’ll have to deal with sooner or later is upgrades. For instance, let’s say the first version of your plugin required one database table, but the next version requires another table. How do you know if you should run the code that creates the second database table?</p> <p>I suggest storing the plugin version in the WordPress database so that you can read it later to decide certain upgrade actions your plugin should take. To do this, you’ll need to create a couple more global variables and invoke the <code>add_option()</code> function:</p> <pre><code class="language-php">if (!defined('MYPLUGIN_VERSION_KEY')) define('MYPLUGIN_VERSION_KEY', 'myplugin_version'); if (!defined('MYPLUGIN_VERSION_NUM')) define('MYPLUGIN_VERSION_NUM', '1.0.0'); add_option(MYPLUGIN_VERSION_KEY, MYPLUGIN_VERSION_NUM);</code></pre> <p>I certainly could have simply called <code>add_option('myplugin_version', '1.0.0');</code> without the need for the global variables, but like the global path variables, I’ve found these just as handy for using in other parts of a plugin, such as a Dashboard or About page.</p> <p>Also note that <code>update_option()</code> could have been used instead of <code>add_option()</code>. The difference is that <code>add_option()</code> does nothing if the option already exists, whereas <code>update_option()</code> checks to see if the option already exists, and if it doesn’t, it will add the option to the database using <code>add_option()</code>; otherwise, it updates the option with the value provided.</p> <p>Then, when it comes time to check whether or not to perform upgrade actions, your plugin will end up with code that looks similar to this:</p> <pre><code class="language-php">$new_version = '2.0.0'; if (get_option(MYPLUGIN_VERSION_KEY) != $new_version) { // Execute your upgrade logic here // Then update the version value update_option(MYPLUGIN_VERSION_KEY, $new_version); }</code></pre> <h3>Use dbDelta() to Create/Update Database Tables</h3> <p>If your plugin requires its own database tables, you will inevitably need to modify those tables in future versions of your plugin. This can get a bit tricky to manage if you’re not careful, but WordPress helps alleviate this problem by providing the <code>dbDelta()</code> function.</p> <p>A useful feature of the <code>dbDelta()</code> function is that it can be used for both creating and updating tables, but according to the WordPress codex page <a href="http://codex.wordpress.org/Creating_Tables_with_Plugins">“Creating Tables with Plugins”</a><sup class="po" id="note-3"><a href="#3">3</a></sup>, it’s a little picky:</p> <ul> <li>You have to put each field on its own line in your SQL statement.</li> <li>You have to have two spaces between the words PRIMARY KEY and the definition of your primary key.</li> <li>You must use the keyword KEY rather than its synonym INDEX and you must include at least one KEY.</li> </ul> <p>Knowing these rules, we can use the function below to create a table that contains an ID, a name, and an email:</p> <pre><code class="language-php">function myplugin_create_database_table() { global $wpdb; $table = $wpdb->prefix . 'myplugin_table_name'; $sql = "CREATE TABLE " . $table . " ( id INT NOT NULL AUTO_INCREMENT, name VARCHAR(100) NOT NULL DEFAULT '', email VARCHAR(100) NOT NULL DEFAULT '', UNIQUE KEY id (id) );"; require_once(ABSPATH . 'wp-admin/includes/upgrade.php'); dbDelta($sql); }</code></pre> <p><em><strong>Important:</strong> The <code>dbDelta()</code> function is found in <strong>wp-admin/includes/upgrade.php</strong>, but it has to be included manually because it’s not loaded by default.</em></p> <p>So now we have a table, but in the next version we need to expand the size of the name column from 100 to 250. Fortunately <code>dbDelta()</code> makes this straightforward, and using our upgrade logic previously, the next version of the plugin will have code similar to this:</p> <pre><code class="language-php">$new_version = '2.0.0'; if (get_option(MYPLUGIN_VERSION_KEY) != $new_version) { myplugin_update_database_table(); update_option(MYPLUGIN_VERSION_KEY, $new_version); } function myplugin_update_database_table() { global $wpdb; $table = $wpdb->prefix . 'myplugin_table_name'; $sql = "CREATE TABLE " . $table . " ( id INT NOT NULL AUTO_INCREMENT, name VARCHAR(250) NOT NULL DEFAULT '', // Bigger name column email VARCHAR(100) NOT NULL DEFAULT '', UNIQUE KEY id (id) );"; require_once(ABSPATH . 'wp-admin/includes/upgrade.php'); dbDelta($sql); }</code></pre> <p>While there are other ways to create and update database tables for your WordPress plugin, it’s hard to ignore the flexibility of the <code>dbDelta()</code> function.</p> <h3>Know the Difference Between include, include_once, require, and require_once</h3> <p>There will come a time during the development of your plugin where you will want to put code into other files so that maintaining your plugin is a bit easier. For instance, a common practice is to create a functions.php file that contains all of the shared functions that all of the files in your plugin can use.</p> <p>Let’s say your main plugin file is named myplugin.php and you want to include the functions.php file. You can use any of these lines of code to do it:</p> <pre><code class="language-php">include 'functions.php'; include_once 'functions.php'; require 'functions.php'; require_once 'functions.php';</code></pre> <p>But which should you use? It mostly depends on your expected outcome of the file not being there.</p> <ul> <li><strong>include:</strong> Includes and evaluates the specified file, throwing a warning if the file can’t be found.</li> <li><strong>include_once:</strong> Same as include, but if the file has already been included it will not be included again.</li> <li><strong>require:</strong> Includes and evaluates the specified file (same as include), but instead of a warning, throws a fatal error if the file can’t be found.</li> <li><strong>require_once:</strong> Same as require, but if the file has already been included it will not be included again.</li> </ul> <p>My experience has been to always use <code>include_once</code> because a) how I structure and use my files usually requires them to be included once and only once, and b) if a required file can’t be found I don’t expect parts of the plugin to work, but it doesn’t need to break anything else either.</p> <p>Your expectations may vary from mine, but it’s important to know the subtle differences between the four ways of including files.</p> <h3>Use bloginfo(‘wpurl’) Instead of bloginfo(‘url’)</h3> <p>By and large, WordPress is installed in the root folder of a website; it’s standard operating procedure. However, every now and then you’ll come across websites that install WordPress into a separate subdirectory under the root. Seems innocent enough, but the location of WordPress is critically important.</p> <p>To demonstrate, in the “General Settings” section of the WordPress admin panel, you’ll find the “WordPress address (URL)” and “Site address (URL)” settings, and for sites where WordPress is installed into the root directory, they will have the exact same values:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/general-settings-same-url.jpg" alt="" title="general-settings-same-url" width="525" height="84" class="alignnone size-full wp-image-90926" /></p> <p>But for sites where WordPress is installed into a subdirectory under the root (in this case a “wordpress” subdirectory), their values will be different:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/general-settings-different-url.jpg" alt="" title="general-settings-different-url" width="525" height="84" class="alignnone size-full wp-image-90925" /></p> <p>At this stage it’s important to know the following:</p> <ul> <li><strong>bloginfo(‘wpurl’)</strong> equals the “WordPress address (URL)” setting</li> <li><strong>bloginfo(‘url’)</strong> equals the “Site address (URL)” setting</li> </ul> <p>Where this matters is when you need to build URLs to certain resources or pages. For example, if you want to provide a link to the WordPress login screen, you could do this:</p> <pre><code class="language-php">// URL will be http://mydomain.com/wp-login.php <a href="<?php bloginfo('url') ?>/wp-login.php">Login</a></code></pre> <p>But that won’t resolve to the correct URL in the scenario such as the one above where WordPress is installed to the “wordpress” subdirectory. To do this correctly, you must use <code>bloginfo('wpurl')</code> instead:</p> <pre><code class="language-php">// URL will be http://mydomain.com/wordpress/wp-login.php <a href="<?php bloginfo('wpurl') ?>/wp-login.php">Login</a></code></pre> <p>Using <code>bloginfo('wpurl')</code> instead of <code>bloginfo('url')</code> is the safest way to go when building links and URLs inside your plugin because it works in both scenarios: when WordPress is installed in the root of a website and also when it’s installed in a subdirectory. Using <code>bloginfo('url')</code> only gets you the first one.</p> <h3>How and When to Use Actions and Filters</h3> <p>WordPress allows developers to add their own code during the execution of a request by providing various hooks. These hooks come in the form of actions and filters:</p> <ul> <li><strong>Actions</strong>: WordPress invokes actions at certain points during the execution request and when certain events occur.</li> <li><strong>Filters</strong>: WordPress uses filters to modify text before adding it to the database and before displaying it on-screen.</li> </ul> <p>The number of actions and filters is quite large, so we can’t get into them all here, but let’s at least take a look at how they are used.</p> <p>Here’s an example of how to use the <code>admin_print_styles</code> action, which allows you to add your own stylesheets to the WordPress admin pages:</p> <pre><code class="language-php">add_action('admin_print_styles', 'myplugin_admin_print_styles'); function myplugin_admin_print_styles() { $handle = 'myplugin-css'; $src = MYPLUGIN_PLUGIN_URL . '/styles.css'; wp_register_style($handle, $src); wp_enqueue_style($handle); }</code></pre> <p>And here’s how you would use the <code>the_content</code> filter to add a “Follow me on Twitter!” link to the bottom of every post:</p> <pre><code class="language-php">add_filter('the_content', 'myplugin_the_content'); function myplugin_the_content($content) { $output = $content; $output .= '<p>'; $output .= '<a href="http://twitter.com/username">Follow me on Twitter!</a>'; $output .= '</p>'; return $output; }</code></pre> <p>It’s impossible to write a WordPress plugin without actions and filters, and knowing what’s available to use and when to use them can make a big difference. See the WordPress codex page <a href="http://codex.wordpress.org/Plugin_API/Action_Reference">“Plugin API/Action Reference”</a><sup class="po" id="note-4"><a href="#4">4</a></sup> for the complete list of actions and the page <a href="http://codex.wordpress.org/Plugin_API/Filter_Reference">“Plugin API/Filter Reference”</a><sup class="po" id="note-5"><a href="#5">5</a></sup> for the complete list of filters.</p> <p><em><strong>Tip:</strong> Pay close attention to the order in which the actions are listed on its codex page. While not an exact specification, my experimentation and trial-and-error has shown it to be pretty close to the order in which actions are invoked during the WordPress request pipeline.</em></p> <h3>Add Your Own Settings Page or Admin Menu</h3> <p>Many WordPress plugins require users to enter settings or options for the plugin to operate properly, and the way plugin authors accomplish this is by either adding their own settings page to an existing menu or by adding their own new top-level admin menu to WordPress.</p> <h4>How to Add a Settings Page</h4> <p>A common practice for adding your own admin settings page is to use the <code>add_menu()</code> hook to call the <code>add_options_page()</code> function:</p> <pre><code class="language-php">add_action('admin_menu', 'myplugin_admin_menu'); function myplugin_admin_menu() { $page_title = 'My Plugin Settings'; $menu_title = 'My Plugin'; $capability = 'manage_options'; $menu_slug = 'myplugin-settings'; $function = 'myplugin_settings'; add_options_page($page_title, $menu_title, $capability, $menu_slug, $function); } function myplugin_settings() { if (!current_user_can('manage_options')) { wp_die('You do not have sufficient permissions to access this page.'); } // Here is where you could start displaying the HTML needed for the settings // page, or you could include a file that handles the HTML output for you. }</code></pre> <p>By invoking the <code>add_options_page()</code> function, we see that the “My Plugin” option has been added to the built-in <strong>Settings</strong> menu in the WordPress admin panel:</p> <p class="showcase"><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/admin-menu-options-page.jpg" alt="" title="admin-menu-options-page" width="147" height="207" class="alignnone size-full wp-image-91029" /></p> <p>The <code>add_options_page()</code> function is really just a wrapper function on top of the <code>add_submenu_page()</code> function, and there are other wrapper functions that do similar work for the other sections of the WordPress admin panel:</p> <ul> <li>add_dashboard_page()</li> <li>add_posts_page()</li> <li>add_media_page()</li> <li>add_links_page()</li> <li>add_pages_page()</li> <li>add_comments_page()</li> <li>add_theme_page()</li> <li>add_plugins_page()</li> <li>add_users_page()</li> <li>add_management_page()</li> </ul> <h4>How to Add a Custom Admin Menu</h4> <p>Those wrapper functions work great, but what if you wanted to create your own admin menu section for your plugin? For example, what if you wanted to create a “My Plugin” admin section with more than just the Settings page, such as a Help page? This is how you would do that:</p> <pre><code class="language-php">add_action('admin_menu', 'myplugin_menu_pages'); function myplugin_menu_pages() { // Add the top-level admin menu $page_title = 'My Plugin Settings'; $menu_title = 'My Plugin'; $capability = 'manage_options'; $menu_slug = 'myplugin-settings'; $function = 'myplugin_settings'; add_menu_page($page_title, $menu_title, $capability, $menu_slug, $function); // Add submenu page with same slug as parent to ensure no duplicates $sub_menu_title = 'Settings'; add_submenu_page($menu_slug, $page_title, $sub_menu_title, $capability, $menu_slug, $function); // Now add the submenu page for Help $submenu_page_title = 'My Plugin Help'; $submenu_title = 'Help'; $submenu_slug = 'myplugin-help'; $submenu_function = 'myplugin_help'; add_submenu_page($menu_slug, $submenu_page_title, $submenu_title, $capability, $submenu_slug, $submenu_function); } function myplugin_settings() { if (!current_user_can('manage_options')) { wp_die('You do not have sufficient permissions to access this page.'); } // Render the HTML for the Settings page or include a file that does } function myplugin_help() { if (!current_user_can('manage_options')) { wp_die('You do not have sufficient permissions to access this page.'); } // Render the HTML for the Help page or include a file that does }</code></pre> <p>Notice that this code doesn’t use any of the wrapper functions. Instead, it calls <code>add_menu_page()</code> (for the parent menu page) and <code>add_submenu_page()</code> (for the child pages) to create a separate “My Plugin” admin menu that contains the Settings and Help pages:</p> <p class="showcase"><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/admin-menu-custom.jpg" alt="" title="admin-menu-custom" width="147" height="233" class="alignnone size-full wp-image-91091" /></p> <p>One advantage of adding your own custom menu is that <strong>it’s easier for users to find the settings for your plugin</strong> because they aren’t buried within one of the built-in WordPress admin menus. Keeping that in mind, if your plugin is simple enough to only require a single admin page, then using one of the wrapper functions might make the most sense. But if you need more than that, creating a custom admin menu is the way to go.</p> <h3>Provide a Shortcut to Your Settings Page with Plugin Action Links</h3> <p>In much the same way that adding your own custom admin menu helps give the sense of a well-rounded plugin, plugin action links work in the same fashion. So what are plugin action links? It’s best to start with a picture:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/plugin-action-links-none.jpg" alt="" title="plugin-action-links-none" width="525" height="118" class="alignnone size-full wp-image-91097" /></p> <p>See the “Deactivate” and “Edit” links underneath the name of the plugin? Those are plugin action links, and WordPress provides a filter named <code>plugin_action_links</code> for you to add more. Basically, <strong>plugin action links are a great way to add a quick shortcut to your most commonly used admin menu page</strong>.</p> <p>Keeping with our Settings admin page, here’s how we would add a plugin action link for it:</p> <pre><code class="language-php">add_filter('plugin_action_links', 'myplugin_plugin_action_links', 10, 2); function myplugin_plugin_action_links($links, $file) { static $this_plugin; if (!$this_plugin) { $this_plugin = plugin_basename(__FILE__); } if ($file == $this_plugin) { // The "page" query string value must be equal to the slug // of the Settings admin page we defined earlier, which in // this case equals "myplugin-settings". $settings_link = '<a href="' . get_bloginfo('wpurl') . '/wp-admin/admin.php?page=myplugin-settings">Settings</a>'; array_unshift($links, $settings_link); } return $links; }</code></pre> <p>With this code in place, now when you view your plugins list you’ll see this:</p> <p><img src="http://www.smashingmagazine.com/wp-content/uploads/2011/02/plugin-action-links-settings.jpg" alt="" title="plugin-action-links-settings" width="550" height="118" class="alignnone size-full wp-image-91112" /></p> <p>Here we provided a plugin action link to the Settings admin page, which is the same thing as clicking on Settings from our custom admin menu. The benefit of the plugin action link is that <strong>users see it immediately after they activate the plugin</strong>, thus adding to the overall experience.</p> <h3>Additional Resources</h3> <p>I’ve covered a lot in this article, but there’s plenty more out there to keep you busy awhile. The most comprehensive documentation for WordPress plugin development can be found on the <a href="http://codex.wordpress.org/">WordPress Codex</a><sup class="po" id="note-6"><a href="#6">6</a></sup>, a huge collection of pages documenting everything that is WordPress. Below are some of the more pertinent links from the codex you’ll need:</p> <ul> <li><a href="http://codex.wordpress.org/Writing_a_Plugin">Writing a Plugin</a><sup class="po" id="note-7"><a href="#7">7</a></sup> – If you’re brand new to WordPress plugin development, start here.</li> <li><a href="http://codex.wordpress.org/Plugin_API/Action_Reference">Plugin API – Action Reference</a><sup class="po" id="note-8"><a href="#8">8</a></sup></li> <li><a href="http://codex.wordpress.org/Plugin_API/Filter_Reference">Plugin API – Filter Reference</a><sup class="po" id="note-9"><a href="#9">9</a></sup></li> <li><a href="http://codex.wordpress.org/Pluggable_Functions">Pluggable Functions</a><sup class="po" id="note-10"><a href="#10">10</a></sup></li> <li><a href="http://codex.wordpress.org/Data_Validation">Data Validation</a><sup class="po" id="note-11"><a href="#11">11</a></sup></li> </ul> <p>I also suggest reading Joost de Valk’s article “<a href="http://www.smashingmagazine.com/2010/07/30/lessons-learned-from-maintaining-a-wordpress-plug-in/">Lessons Learned From Maintaining a WordPress Plug-In</a><sup class="po" id="note-12"><a href="#12">12</a></sup>“, which provides more good tips on WordPress plugin development.</p> <p><em>(vf) (ik)</em></p> <h4 class="po">Footnotes</h4><ol class="po"><li id="#1"><a href="#note-1">1 http://www.smashingmagazine.com/wp-content/uploads/2011/03/wordpress_plugin.jpg</a></li><li id="#2"><a href="#note-2">2 http://ditio.net/2011/01/29/wordpress-debug-bar-plugin-blackbox/</a></li><li id="#3"><a href="#note-3">3 http://codex.wordpress.org/Creating_Tables_with_Plugins</a></li><li id="#4"><a href="#note-4">4 http://codex.wordpress.org/Plugin_API/Action_Reference</a></li><li id="#5"><a href="#note-5">5 http://codex.wordpress.org/Plugin_API/Filter_Reference</a></li><li id="#6"><a href="#note-6">6 http://codex.wordpress.org/</a></li><li id="#7"><a href="#note-7">7 http://codex.wordpress.org/Writing_a_Plugin</a></li><li id="#8"><a href="#note-8">8 http://codex.wordpress.org/Plugin_API/Action_Reference</a></li><li id="#9"><a href="#note-9">9 http://codex.wordpress.org/Plugin_API/Filter_Reference</a></li><li id="#10"><a href="#note-10">10 http://codex.wordpress.org/Pluggable_Functions</a></li><li id="#11"><a href="#note-11">11 http://codex.wordpress.org/Data_Validation</a></li><li id="#12"><a href="#note-12">12 http://www.smashingmagazine.com/2010/07/30/lessons-learned-from-maintaining-a-wordpress-plug-in/</a></li></ol> <div id="textadtarget"></div> <div class="lt"> <a href="http://www.smashingmagazine.com/tag/essentials/">Essentials</a><a href="http://www.smashingmagazine.com/tag/php/">PHP</a><a href="http://www.smashingmagazine.com/tag/plugins/">Plugins</a> </div> <p><a href="#top" class="top single" title="Jump to the top of the page">↑ Back to top</a><a class="sot single" href="https://twitter.com/intent/tweet?original_referer=http%3A%2F%2Fwww.smashingmagazine.com%2F2011%2F03%2F08%2Ften-things-every-wordpress-plugin-developer-should-know%2F&source=tweetbutton&text=Ten%20Things%20Every%20WordPress%20Plugin%20Developer%20Should%20Know&url=http%3A%2F%2Fwww.smashingmagazine.com%2F2011%2F03%2F08%2Ften-things-every-wordpress-plugin-developer-should-know%2F&via=smashingmag" title="Share on Twitter!">Share on Twitter</a></p> </article> <div class="bio clearfix"> <div class="grv"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/5d1c4c4bffa1f1133b17dc54f7bf40d1?s=78&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D78&r=G" class="avatar avatar-78 photo" height="78" width="78" /> </div> <div class="about"> <a rel="author" class="poa" href="http://www.smashingmagazine.com/author/dave-donaldson/?rel=author" title="Posts by Dave Donaldson">Dave Donaldson</a> <p>Dave lives in Columbus, OH and is one of the founders of <a href="http://maxfoundry.com/">Max Foundry</a>, a company that makes WordPress plugins for <a href="http://maxfoundry.com/plugins/maxlanding/">landing pages</a>, <a href="http://maxfoundry.com/plugins/maxsqueeze/">squeeze pages</a>, <a href="http://maxfoundry.com/plugins/maxsales/">sales pages</a>, and <a href="http://maxfoundry.com/plugins/maxab/">A/B testing</a>. You can <a href="http://twitter.com/arcware">follow Dave on Twitter</a> and <a href="http://arcware.net">on his blog</a>, where he writes about living the bootstrapped startup life.</p> </div> </div> <div class="ras clearfix"> <h2>Related Articles</h2> <div class="ra clearfix"> <a class="pp" href="http://www.smashingmagazine.com/2014/09/25/the-ultimate-guide-to-choosing-a-wordpress-host/"><img width="84" height="84" src="http://www.smashingmagazine.com/wp-content/uploads/2014/09/illu-wp-14.jpg" class="attachment-related-thumb wp-post-image" alt="illu-wp-14" /></a> <h3><a href="http://www.smashingmagazine.com/2014/09/25/the-ultimate-guide-to-choosing-a-wordpress-host/">The Ultimate Guide To Choosing A WordPress Host</a></h3> </div> <div class="ra clearfix"> <a class="pp" href="http://www.smashingmagazine.com/2014/08/27/customizing-wordpress-archives-categories-terms-taxonomies/"><img width="84" height="84" src="http://www.smashingmagazine.com/wp-content/uploads/2014/08/wordpress-blue-illu.jpg" class="attachment-related-thumb wp-post-image" alt="wordpress-blue-illu" /></a> <h3><a href="http://www.smashingmagazine.com/2014/08/27/customizing-wordpress-archives-categories-terms-taxonomies/">Customizing WordPress Archives For Categories, Tags And Other Taxonomies</a></h3> </div> <div class="ra clearfix"> <a class="pp" href="http://www.smashingmagazine.com/2014/08/27/a-tour-of-wordpress-4-0/"><img width="84" height="84" src="http://www.smashingmagazine.com/wp-content/uploads/2014/08/wp-logo-4-0-illu.png" class="attachment-related-thumb wp-post-image" alt="wp-logo-4-0-illu" /></a> <h3><a href="http://www.smashingmagazine.com/2014/08/27/a-tour-of-wordpress-4-0/">A Quick Tour Of WordPress 4.0</a></h3> </div> </div> <div class="adv"> <span class="declare">Advertising</span> <div id="commentspnsrtarget"></div> </div> <ul id="comments" class="sub-tabs clearfix"> <li><a href="#show-comments" class="active">94 Comments</a></li> </ul> <div id="discussion" class="subtab-pages"> <div id="show-comments"> <ol id="comments-overview" class="cl"> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">1</span> <div class="c" id="comment-169926"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/b473ef78b653e5aa33656f54f7f090bc?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Eddie Gear</h3> <span class="dati"> <a title="Commentlink #1" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169926"> March 8, 2011 5:48 am </a> </span> </div> </div> <div class="ctx"> <p>Great insights Dave. I loved the way you have pointed out the things that any developer that needs to keep track of. Thanks for sharing.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169926" class="inpsyde_extended_comments_rate positive">3</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169926" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">2</span> <div class="c" id="comment-169927"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/be19e396141c6328782a2852844d58f1?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Frederick Luna</h3> <span class="dati"> <a title="Commentlink #2" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169927"> March 8, 2011 6:07 am </a> </span> </div> </div> <div class="ctx"> <p>Intersting stuff about adding a custom menu and a settings page :D great post Dave.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169927" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169927" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">3</span> <div class="c" id="comment-169928"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/53c424111bd9e2571763aed8c55c3745?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Matt Rittman</h3> <span class="dati"> <a title="Commentlink #3" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169928"> March 8, 2011 6:26 am </a> </span> </div> </div> <div class="ctx"> <p>Great article Dave! This will really help out my future endeavors with WordPress plugin development. Thanks for sharing!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169928" class="inpsyde_extended_comments_rate positive">3</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169928" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">4</span> <div class="c" id="comment-169929"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/0b95637f2168ded35b2d9812f3fbaf9f?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>David</h3> <span class="dati"> <a title="Commentlink #4" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169929"> March 8, 2011 6:27 am </a> </span> </div> </div> <div class="ctx"> <p>This is brilliant, thanks for the write up. Bookmarked! I see that you recommend the Blackbox debug plugin. Having just started creating my own plugins, why this and not the DebugBar plugin (<a href="http://wordpress.org/extend/plugins/debug-bar/" rel="nofollow">http://wordpress.org/extend/plugins/debug-bar/</a>)? What’s the primary difference?</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169929" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169929" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">5</span> <div class="c" id="comment-169959"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #5" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169959"> March 8, 2011 3:31 pm </a> </span> </div> </div> <div class="ctx"> <p>@David – I didn’t include the DebugBar plugin because it requires WordPress 3.1, which was only in Release Candidate mode at the time of writing. Both plugins provide similar debug info, so I suggest trying both and going with the one you like best.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169959" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169959" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">6</span> <div class="c" id="comment-169930"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/fd58a5b6b89266f6095d15566f290ecd?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Chris</h3> <span class="dati"> <a title="Commentlink #6" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169930"> March 8, 2011 6:35 am </a> </span> </div> </div> <div class="ctx"> <p>Great advices! I wish it would have been released much earlier – could have saved me a lot of time and trouble :)</p> <p>Regarding bloginfo(wpurl): The codex says to use site_url() instead, for it also supports https, eg. if is_ssl() is true.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169930" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169930" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">7</span> <div class="c" id="comment-169935"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #7" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169935"> March 8, 2011 7:09 am </a> </span> </div> </div> <div class="ctx"> <p>@Chris – I can’t find the codex article that says to use site_url() instead of bloginfo(‘wpurl’), but yes, I suppose you could do that. There seems to be some confusion about whether or not site_url() includes the install directory of WordPress (if installed in a subdirectory), but looking at the core WordPress code it looks like it does.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169935" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169935" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-3 clearfix"> <span class="cn">8</span> <div class="c" id="comment-169995"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/46e57cfd694f0c9c91737a14e4913af8?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Christofer</h3> <span class="dati"> <a title="Commentlink #8" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169995"> March 15, 2011 12:03 am </a> </span> </div> </div> <div class="ctx"> <p>@Dave — Maybe, this is the page Chris referred to:<br /> <a href="http://codex.wordpress.org/Function_Reference/get_bloginfo" rel="nofollow">http://codex.wordpress.org/Function_Reference/get_bloginfo</a></p> <p>“‘wpurl’ / ‘siteurl’ – Returns the ‘WordPress address (URI)’ [..] Consider using site_url() instead.”</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169995" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169995" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">9</span> <div class="c" id="comment-169931"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/c41cbd0f894f1c1d570ab99a568e41d2?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Pete</h3> <span class="dati"> <a title="Commentlink #9" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169931"> March 8, 2011 6:38 am </a> </span> </div> </div> <div class="ctx"> <p>Nice article, thanks for sharing. I especially like the notes on debugging & function prefixes. Hopefully this will change the coding habits of some Developers when writing a WP plugin.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169931" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169931" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">10</span> <div class="c" id="comment-169932"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/1486cf246811f6cdaa9894d7f9ede233?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Donna Vitan</h3> <span class="dati"> <a title="Commentlink #10" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169932"> March 8, 2011 6:48 am </a> </span> </div> </div> <div class="ctx"> <p>Another awesome and well described tutorial Dave! I especially love how concise the part about creating admin settings panel and menu.</p> <p>Cheers,</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169932" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169932" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">11</span> <div class="c" id="comment-169933"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/9c97d846b29e7a50e82af8ab40225023?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Thomas Bachmann</h3> <span class="dati"> <a title="Commentlink #11" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169933"> March 8, 2011 6:55 am </a> </span> </div> </div> <div class="ctx"> <p>thanks!<br /> … if you are a trained professional developer and familiar with PHP only half of it should be new (wordpress specifics)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169933" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169933" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">12</span> <div class="c" id="comment-169934"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/e06e23e82d25e39ae6e04e77a3aad1a2?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Hung Bui</h3> <span class="dati"> <a title="Commentlink #12" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169934"> March 8, 2011 7:04 am </a> </span> </div> </div> <div class="ctx"> <p>Great stuff! Very useful thought.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169934" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169934" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">13</span> <div class="c" id="comment-169936"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/ae17fd59d1f4261b04860e1a8997892c?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>kwasseem</h3> <span class="dati"> <a title="Commentlink #13" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169936"> March 8, 2011 7:30 am </a> </span> </div> </div> <div class="ctx"> <p>Precise and short; good, clear checkpoints!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169936" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169936" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">14</span> <div class="c" id="comment-169937"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/8f80a2914655c2dddf59bddd8af8e62d?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Samundra Shrestha</h3> <span class="dati"> <a title="Commentlink #14" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169937"> March 8, 2011 7:33 am </a> </span> </div> </div> <div class="ctx"> <p>Really loved the way you have mentioned the tricks for wordpress developer. I liked the way you described the usuage of require, require_once, include and include_once. All most of us use them but never seem to care since we all use include_once most of the time :).</p> <p>I have already been using some of the tricks you have mentioned.</p> <p>Great Article.</p> <p>best regards,<br /> Samundra Shrestha<br /> Realtime Solutions, Nepal</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169937" class="inpsyde_extended_comments_rate negative">-3</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169937" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">15</span> <div class="c" id="comment-169938"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7ba0e1a12efe734f77b4fba4d97dd8ef?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Pieter Carette</h3> <span class="dati"> <a title="Commentlink #15" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169938"> March 8, 2011 7:35 am </a> </span> </div> </div> <div class="ctx"> <p>Great post. It makes me want to write a plugin! :)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169938" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169938" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">16</span> <div class="c" id="comment-169939"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/21fc7f3431b9b07560c2bdbd6b0389e2?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Joseph Carrington</h3> <span class="dati"> <a title="Commentlink #16" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169939"> March 8, 2011 7:37 am </a> </span> </div> </div> <div class="ctx"> <p>Good stuff. I’d point out that using a class as a fill-in for a namespace is not exactly the intention of OOP however.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169939" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169939" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">17</span> <div class="c" id="comment-169940"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #17" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169940"> March 8, 2011 7:53 am </a> </span> </div> </div> <div class="ctx"> <p>@Joseph Carrington – You’re right, using classes as a namespace fill-in is not the intention of OOP, but it is a common practice for avoiding function name collisions in PHP and WordPress.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169940" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169940" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">18</span> <div class="c" id="comment-169941"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/41d0698209bfdc9cb69b31e8fccd1459?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Josh Hartman</h3> <span class="dati"> <a title="Commentlink #18" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169941"> March 8, 2011 7:54 am </a> </span> </div> </div> <div class="ctx"> <p>Great info! I wasn’t aware of the bloginfo(‘wpurl’) vs. bloginfo(‘url’) difference.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169941" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169941" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">19</span> <div class="c" id="comment-169942"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/aee526984fe85082c6a902d028806522?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>David</h3> <span class="dati"> <a title="Commentlink #19" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169942"> March 8, 2011 7:54 am </a> </span> </div> </div> <div class="ctx"> <p>Really enjoyed this. It was encouraging that I found I was already doing most of these things. Some good tips, though, and I’ve updated my plugin with some of these suggestions.</p> <p>I tried blackbar, but got tons of deprecated errors, which kind of made me laugh…</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169942" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169942" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-2 clearfix"> <span class="cn">20</span> <div class="c" id="comment-169943"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #20" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169943"> March 8, 2011 7:57 am </a> </span> </div> </div> <div class="ctx"> <p>@David – Hehe, yea, the irony of that was not lost on me :-)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169943" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169943" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">21</span> <div class="c" id="comment-169944"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/907728625b3b0f36cfc56582a736d10a?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Vivek Parmar</h3> <span class="dati"> <a title="Commentlink #21" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169944"> March 8, 2011 8:12 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks for so much, getitng started with plugin development and wordpress theme development, and this article help me a lot in knowing many things that i do not know</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169944" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169944" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">22</span> <div class="c" id="comment-169945"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/03e89dba5cb218b78f43ac4ca2a6aec7?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>scasmflop</h3> <span class="dati"> <a title="Commentlink #22" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169945"> March 8, 2011 8:53 am </a> </span> </div> </div> <div class="ctx"> <p>Great article, very informative without straying too far down rabbit trails. Thanks.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169945" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169945" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">23</span> <div class="c" id="comment-169946"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/429e15ea1f962e579cd1d59b0f0e6d37?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Raherian</h3> <span class="dati"> <a title="Commentlink #23" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169946"> March 8, 2011 9:25 am </a> </span> </div> </div> <div class="ctx"> <p>Hi,<br /> Using blackbox-debug-bar with wp_debug on true display a bunch of notices, not very good for developping :/</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169946" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169946" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-2 clearfix"> <span class="cn">24</span> <div class="c" id="comment-169947"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #24" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169947"> March 8, 2011 9:28 am </a> </span> </div> </div> <div class="ctx"> <p>@Raherian – But that’s kind of the point of enabling debugging in the first place, to see all of the notices you wouldn’t have otherwise known were there.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169947" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169947" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-3 clearfix"> <span class="cn">25</span> <div class="c" id="comment-169955"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/429e15ea1f962e579cd1d59b0f0e6d37?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Raherian</h3> <span class="dati"> <a title="Commentlink #25" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169955"> March 8, 2011 12:14 pm </a> </span> </div> </div> <div class="ctx"> <p>Yes but this plugin is usefull for developping, and i develop with wp_debug true, so having a bunch of notices while developping isn’t good.<br /> It were a good idea to make a plugin available on repository only if he doesn’t have any notices, like themes ^^</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169955" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169955" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">26</span> <div class="c" id="comment-169948"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/ec905543ea918ee9546033a8ec2bfca9?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>aurel</h3> <span class="dati"> <a title="Commentlink #26" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169948"> March 8, 2011 9:32 am </a> </span> </div> </div> <div class="ctx"> <p>So far I developed only two themes, both of them using different methods (or no method apart from “hope it will work”)</p> <p>it seems that these 10 plugins will make the process much easier to manage and hopefully to be able to understand by things work – that way things could stick in the head when developing the next theme</p> <p>thanks</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169948" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169948" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">27</span> <div class="c" id="comment-169949"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/fc6a528fe2b60482971b1642577ae43d?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Alan Stevens</h3> <span class="dati"> <a title="Commentlink #27" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169949"> March 8, 2011 9:32 am </a> </span> </div> </div> <div class="ctx"> <p>Nice article, Dave. I don’t know if there is a codex article on using site_url() but this article has some good tips on guarding for ssl: <a href="http://blogs.sitepoint.com/2011/02/22/crimes-against-wordpress/" rel="nofollow">http://blogs.sitepoint.com/2011/02/22/crimes-against-wordpress/</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169949" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169949" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">28</span> <div class="c" id="comment-169950"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/1f7d16fe6425d85f05aa229464b49843?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Thai Bui</h3> <span class="dati"> <a title="Commentlink #28" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169950"> March 8, 2011 9:35 am </a> </span> </div> </div> <div class="ctx"> <p>Great article. One of my biggest hurdles is debugging my plugins properly and these tips are outstanding. I usually use firephp to see what’s going on with the variables being passed back and fourth. Such an invaluable tool.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169950" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169950" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">29</span> <div class="c" id="comment-169951"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/0f0319b397cd2a0443f73a94ab6934cf?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Conrad Muan</h3> <span class="dati"> <a title="Commentlink #29" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169951"> March 8, 2011 10:16 am </a> </span> </div> </div> <div class="ctx"> <p>Great post. I’ll have to try blackbar in my future projects.</p> <p>I was also _just_ looking for a tutorial on adding menu items when I found this gem.</p> <p>Thanks again,<br /> Conrad</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169951" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169951" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">30</span> <div class="c" id="comment-169952"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/aac7e0386facd070f6d4b817c257a958?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Zé</h3> <span class="dati"> <a title="Commentlink #30" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169952"> March 8, 2011 10:55 am </a> </span> </div> </div> <div class="ctx"> <p>Great article, but I am a little sad that i18n wasn’t contemplated from the beginning for all those strings, i.e.</p> <p><code>$page_title = __('My Plugin Settings', 'myplugin_textdomain');</code><br /> instead of<br /> <code>$page_title = 'My Plugin Settings';</code></p> <p>It’s great for all other languages to have plugins that are translatable from the get go.<br /> <a href="http://codex.wordpress.org/I18n_for_WordPress_Developers" rel="nofollow">http://codex.wordpress.org/I18n_for_WordPress_Developers</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169952" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169952" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">31</span> <div class="c" id="comment-169957"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #31" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169957"> March 8, 2011 2:55 pm </a> </span> </div> </div> <div class="ctx"> <p>@Ze – I mentioned on another comment that I thought about including internationalization but decided against it for this article. The topic is probably big enough for another article on its own, so maybe I’ll write that one next.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169957" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169957" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">32</span> <div class="c" id="comment-169953"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/95c934fa2c3362794bf62ff8c59ada08?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Drew</h3> <span class="dati"> <a title="Commentlink #32" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169953"> March 8, 2011 11:48 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks for the lead on Blackbox!. I installed it mid-read on your post and played with it for 30 minutes on three of my sites. Then I remember I was reading your post so I came back to finish. Great roundup!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169953" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169953" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">33</span> <div class="c" id="comment-169954"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/1a659e051ae2d889b0e4421408b6ff34?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Tomáš Kapler</h3> <span class="dati"> <a title="Commentlink #33" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169954"> March 8, 2011 12:12 pm </a> </span> </div> </div> <div class="ctx"> <p>one very common problem from US writers missing – forgotting internationalization so __(), _x(), _e() functions etc.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169954" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169954" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-2 clearfix"> <span class="cn">34</span> <div class="c" id="comment-169956"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #34" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169956"> March 8, 2011 12:29 pm </a> </span> </div> </div> <div class="ctx"> <p>@Tomas – I thought about including a section on internationalization, but decided against it for this article. Maybe I’ll write another article just for that.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169956" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169956" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">35</span> <div class="c" id="comment-169958"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/815d913154a591f2c2b4718ef6003d98?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Brett Lewis</h3> <span class="dati"> <a title="Commentlink #35" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169958"> March 8, 2011 3:23 pm </a> </span> </div> </div> <div class="ctx"> <p>This is great :)</p> <p>Thank you so much.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169958" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169958" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">36</span> <div class="c" id="comment-169960"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/d0517bf908028685b3b25b815ef75068?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Phuoc Huynh</h3> <span class="dati"> <a title="Commentlink #36" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169960"> March 8, 2011 6:24 pm </a> </span> </div> </div> <div class="ctx"> <p>Thanks for this great. This is awesome !</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169960" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169960" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">37</span> <div class="c" id="comment-169961"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/909cdcfc310e3cdab83586232d6e81f8?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Patent Litigation</h3> <span class="dati"> <a title="Commentlink #37" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169961"> March 8, 2011 10:03 pm </a> </span> </div> </div> <div class="ctx"> <p>Here is a similar story</p> <p>Until recently, migrating all your blogs to a single multisite blog was a massive task because of the need to resolve conflicting IDs across different tables. Fortunately, newer WordPress versions have built-in functions to make life a bit easier for all of us.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169961" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169961" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">38</span> <div class="c" id="comment-169962"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/30b5f53666c7c520e8142a372f8a54f6?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Steve mg</h3> <span class="dati"> <a title="Commentlink #38" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169962"> March 8, 2011 11:02 pm </a> </span> </div> </div> <div class="ctx"> <p>As a customer of WordPress plugins, my biggest gripe is the lack of screenshots displaying what the plugin does. Is it really that hard to grab screens? Great you’ve made this fantastic plugin, and also great that you’ve put it up for free, just telling me what it does, isn’t going to completely sell me on it.<br /> Screenshots, do it.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169962" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169962" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">39</span> <div class="c" id="comment-169963"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/6666ae2b2012ee49fe01c5e18ebfe2d0?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Mick</h3> <span class="dati"> <a title="Commentlink #39" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169963"> March 8, 2011 11:42 pm </a> </span> </div> </div> <div class="ctx"> <p>I wish every single plugin developer followed these simple rules!<br /> It would make life a little bit easier</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169963" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169963" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">40</span> <div class="c" id="comment-169964"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/115ee6ccc6f3375410990a387bf5c0bb?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Justin</h3> <span class="dati"> <a title="Commentlink #40" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169964"> March 9, 2011 12:43 am </a> </span> </div> </div> <div class="ctx"> <p>This is a great article. Thanks for consolidating all of this information instead of making me search everywhere for it!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169964" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169964" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">41</span> <div class="c" id="comment-169965"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/61ad912b724a2554976edd74ee6e0266?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Jerry</h3> <span class="dati"> <a title="Commentlink #41" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169965"> March 9, 2011 12:45 am </a> </span> </div> </div> <div class="ctx"> <p>Dave, Awesome post. Pretty helpful for green-hands like me for wordpress.<br /> Usually we use netbeans and X-debug for debugging. This time we could try blackbox for help :)</p> <p>One question: How do you do unit test for new built WP plugin? Use PHPUnit or something else? I am quite new to the test procedure of PHP, any help will be much appreciated.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169965" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169965" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">42</span> <div class="c" id="comment-169966"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/8327520245e97889fca3b0270d69acc8?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>jeFFF</h3> <span class="dati"> <a title="Commentlink #42" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169966"> March 9, 2011 12:59 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks a lot for this great article Dave !</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169966" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169966" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">43</span> <div class="c" id="comment-169967"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/8291ab5d74a9f6d7b8a98ed62ad1709e?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Ruslan</h3> <span class="dati"> <a title="Commentlink #43" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169967"> March 9, 2011 1:29 am </a> </span> </div> </div> <div class="ctx"> <p>One thing that you have understand about include vs include_once, require vs require_once is performance penalty.</p> <p>If you develop your code, and you are 100% for sure, that after you included your file in following code it wont be included again, never use *_once functions. They are more resource eating that simple include or require.</p> <p>Read this article to understand difference in C level:<br /> <a href="http://www.techyouruniverse.com/software/php-performance-tip-require-versus-require_once" rel="nofollow">http://www.techyouruniverse.com/software/php-performance-tip-require-versus-require_once</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169967" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169967" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">44</span> <div class="c" id="comment-169968"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/26c5bc5b88075a54b55ae54e98be2c09?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Fernando Agüero</h3> <span class="dati"> <a title="Commentlink #44" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169968"> March 9, 2011 1:42 am </a> </span> </div> </div> <div class="ctx"> <p>One of the best post written in Smashing Magazine. Now I have no doubts.</p> <p>Thank you!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169968" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169968" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">45</span> <div class="c" id="comment-169969"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/00abc2999b2a32f9072fc8b9ae2ccfe9?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Baltech</h3> <span class="dati"> <a title="Commentlink #45" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169969"> March 9, 2011 2:13 am </a> </span> </div> </div> <div class="ctx"> <p>Great you’ve made this fantastic plugin, and also great that you’ve put it up for free.It seems that these 10 plugins will make the process much easier to manage and hopefully to be able to understand by things. Thanks for give us this information.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169969" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169969" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">46</span> <div class="c" id="comment-169970"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/00abc2999b2a32f9072fc8b9ae2ccfe9?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Baltech</h3> <span class="dati"> <a title="Commentlink #46" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169970"> March 9, 2011 2:14 am </a> </span> </div> </div> <div class="ctx"> <p>Great you’ve made this fantastic plugin, and also great that you’ve put it up for free.It seems that these 10 plugins will make the process much easier to manage and hopefully to be able to understand by things. Thanks for this useful knowledge..</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169970" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169970" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">47</span> <div class="c" id="comment-169971"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/48c28e5f2f6f1b32dd7beb2d9bb63d17?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Thorsten</h3> <span class="dati"> <a title="Commentlink #47" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169971"> March 9, 2011 2:36 am </a> </span> </div> </div> <div class="ctx"> <p>A very important topic that is missing here is Data Validation.<br /> <a href="http://codex.wordpress.org/Data_Validation" rel="nofollow">http://codex.wordpress.org/Data_Validation</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169971" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169971" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">48</span> <div class="c" id="comment-169972"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/b8cefc2f7b65fd5e4204711ee5fc3d42?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Max</h3> <span class="dati"> <a title="Commentlink #48" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169972"> March 9, 2011 3:05 am </a> </span> </div> </div> <div class="ctx"> <p>One bad thing was described above.<br /> When webmaster changes <em>wp-content</em> directory name, following code will break the site:<br /> <code>define('MYPLUGIN_THEME_DIR', ABSPATH . 'wp-content/themes/' . get_template());</code><br /> You should use following code instead wrong one:<br /> <code>define('MYPLUGIN_THEME_DIR', WP_CONTENT_DIR . 'themes/' . get_template());</code></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169972" class="inpsyde_extended_comments_rate positive">2</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169972" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">49</span> <div class="c" id="comment-169976"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #49" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169976"> March 9, 2011 6:10 am </a> </span> </div> </div> <div class="ctx"> <p>@Max – Good point, thanks for catching that. Using WP_CONTENT_DIR instead of a hardcoded ‘wp-content’ string would be better.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169976" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169976" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt depth-2 clearfix"> <span class="cn">50</span> <div class="c" id="comment-169998"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/41a7bd5fd7e182e3705c51338285f2a8?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>YellowShark</h3> <span class="dati"> <a title="Commentlink #50" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169998"> March 15, 2011 9:53 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks for pointing this out, I 100% concur – every WP install I do, I move the wp-content to site root, so i wind up with a nice structure like:<br /> /themes<br /> /plugins<br /> /wordpress<br /> /index.php</p> <p>Developers should definitely utilize WP_PLUGIN_DIR and WP_CONTENT_DIR. Google either of those terms for more info on how to leverage them.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169998" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169998" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">51</span> <div class="c" id="comment-169973"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/f439b5e33c6a8bf37337611cb6a9b283?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>STPo</h3> <span class="dati"> <a title="Commentlink #51" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169973"> March 9, 2011 4:17 am </a> </span> </div> </div> <div class="ctx"> <p>And please: do NOT fill the front-end HTML with plugin-specific CSS/jQuery/meta crap without a way to properly erase them if it is not required. I code my own front-end markup and i’m tired to see jQuery/Prototype/Mootools included everytime I use a plugin…</p> <p>PLEASE!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169973" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169973" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">52</span> <div class="c" id="comment-169974"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/8a01f1cc43100cc77bf7fa249f3486db?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>catalin cimpanu</h3> <span class="dati"> <a title="Commentlink #52" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169974"> March 9, 2011 4:49 am </a> </span> </div> </div> <div class="ctx"> <p>Hell of a job on this article.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169974" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169974" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">53</span> <div class="c" id="comment-169975"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/771eb1edb297f17b15e0efde616a840b?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>wparena</h3> <span class="dati"> <a title="Commentlink #53" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169975"> March 9, 2011 5:36 am </a> </span> </div> </div> <div class="ctx"> <p>Although my current WordPress blogs have some of the SeO plugins installed I have found a good tips on your list that I must to follow</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169975" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169975" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">54</span> <div class="c" id="comment-169977"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/a89d26529cebfe446596439bfe4cc74a?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>djavupixel</h3> <span class="dati"> <a title="Commentlink #54" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169977"> March 9, 2011 10:56 am </a> </span> </div> </div> <div class="ctx"> <p>Good WordPress summary to develop a WordPress plugin.<br /> Great work and good explanations!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169977" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169977" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">55</span> <div class="c" id="comment-169978"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/628dfd9e3e905064c09ae089f60b2595?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Douglas Bonneville</h3> <span class="dati"> <a title="Commentlink #55" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169978"> March 9, 2011 11:47 am </a> </span> </div> </div> <div class="ctx"> <p>Dave: Great article – I’m going to give making a plugin a shot pretty soon and I’ll start here. I’ve edited a few, but this outline really lowers the threshold to new development. This is one of the best WordPress articles I’ve seen in a while, and certainly on my list of top articles at Smashing!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169978" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169978" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">56</span> <div class="c" id="comment-169979"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/5dfcd8fbb95d1a7cf5ef40eab3ba0611?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>darell</h3> <span class="dati"> <a title="Commentlink #56" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169979"> March 9, 2011 4:36 pm </a> </span> </div> </div> <div class="ctx"> <p>Thanks for your post, it’s very helpful for my daily work and thoughts.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169979" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169979" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">57</span> <div class="c" id="comment-169980"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/a91236f90b1063e60ad30e7c5f9e30bd?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Jurdefur</h3> <span class="dati"> <a title="Commentlink #57" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169980"> March 10, 2011 1:38 am </a> </span> </div> </div> <div class="ctx"> <p>Seriously why is everybody still using wordpress its the biggest crap of code i ever seen, its like IE6 under the browsers…</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169980" class="inpsyde_extended_comments_rate negative">-1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169980" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">58</span> <div class="c" id="comment-169981"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/922a5911c9e2bba510333139d9f08122?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Christian K. Nordtømme</h3> <span class="dati"> <a title="Commentlink #58" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169981"> March 10, 2011 2:29 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks for this. I’m just now learning how to develop my own plugins, and have bookmarked this post.</p> <p>I also wish more plugin developers made the plugin’s documentation and help easier accessible, though.</p> <p>I don’t think digging up readme files from the plugin folder, rummaging through every page on the author’s website or trying to decipher the code in search of basic answers should be neccessary. Instead, a “Quick Start” action link (either to 100% self-explanatory settings or to a readme file) should be standard.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169981" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169981" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">59</span> <div class="c" id="comment-169982"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/2901240fe75416f14f03fbdd82c00f87?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>jakub</h3> <span class="dati"> <a title="Commentlink #59" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169982"> March 10, 2011 2:42 am </a> </span> </div> </div> <div class="ctx"> <p>This is superuseful article! In-depth yet still accessible for occassional developers. Much better than “25 nice inspirational designs in pink” or “100 beautiful photos of furry pets” type stuff…</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169982" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169982" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">60</span> <div class="c" id="comment-169983"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/41e4c684ba730c88e05fc9bdf563cbc2?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Marty</h3> <span class="dati"> <a title="Commentlink #60" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169983"> March 10, 2011 3:08 pm </a> </span> </div> </div> <div class="ctx"> <p>excellent post… stumbled.. :)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169983" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169983" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">61</span> <div class="c" id="comment-169984"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/403337506ddc11158cad4b76d304fbe7?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>seedy</h3> <span class="dati"> <a title="Commentlink #61" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169984"> March 10, 2011 11:38 pm </a> </span> </div> </div> <div class="ctx"> <p>these articles are getting lamer and lamer</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169984" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169984" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">62</span> <div class="c" id="comment-169985"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/de87d78c47a8f6e6802c23544ef4bd90?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>web3mantra</h3> <span class="dati"> <a title="Commentlink #62" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169985"> March 11, 2011 3:18 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks for sharing this post.I like this post.It contains good examples of wordpress plugin developer should know.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169985" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169985" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">63</span> <div class="c" id="comment-169986"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/dd2e765b964f9f3887c4518b294e42ac?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>ig-ffm</h3> <span class="dati"> <a title="Commentlink #63" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169986"> March 12, 2011 11:16 am </a> </span> </div> </div> <div class="ctx"> <p>I really appreciate your posting. Thanks.</p> <p>There is one issue I’ld like to add: localization.<br /> I have to translate all kinds of plugins and that can be a really annoying waste of time, if a plugin is not meant to be localized.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169986" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169986" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">64</span> <div class="c" id="comment-169987"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/70325f2bf83316d1ba0c44bbc9bc2b1e?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Rahul</h3> <span class="dati"> <a title="Commentlink #64" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169987"> March 13, 2011 10:23 am </a> </span> </div> </div> <div class="ctx"> <p>Great post. Really helps a lot. But need to ask something. I saw this effect on a recently launched blog with wp posts coming in like a js gallery slider.</p> <p><a href="http://sputznik.com/" rel="nofollow">http://sputznik.com/</a></p> <p>How have they achieved this transition and post thing? Is there a plugin that I could use? Thanks for the help.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169987" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169987" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">65</span> <div class="c" id="comment-169991"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #65" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169991"> March 14, 2011 4:07 am </a> </span> </div> </div> <div class="ctx"> <p>@Rahul – It looks like that transition is done with jQuery and the easing plugin for jQuery. Just give it a quick Google and you’ll find what you need.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169991" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169991" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-3 clearfix"> <span class="cn">66</span> <div class="c" id="comment-170002"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/70325f2bf83316d1ba0c44bbc9bc2b1e?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Rahul</h3> <span class="dati"> <a title="Commentlink #66" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170002"> March 24, 2011 11:23 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks a ton. Is there any plugin for this?</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170002" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170002" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">67</span> <div class="c" id="comment-169988"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/281d234ca83251614a66121a05cb8fad?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Manny Fleurmond</h3> <span class="dati"> <a title="Commentlink #67" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169988"> March 13, 2011 9:26 pm </a> </span> </div> </div> <div class="ctx"> <p>I also recommend using the plugins_url() function to find your plugins base directory:<br /> <a href="http://codex.wordpress.org/Function_Reference/plugins_url" rel="nofollow">http://codex.wordpress.org/Function_Reference/plugins_url</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169988" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169988" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">68</span> <div class="c" id="comment-169989"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/f3fc67a71bef1394539fd4be794cb73e?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dax Davis</h3> <span class="dati"> <a title="Commentlink #68" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169989"> March 13, 2011 9:52 pm </a> </span> </div> </div> <div class="ctx"> <p>This is a great post. Thanks for bringing it all together in one place.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169989" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169989" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">69</span> <div class="c" id="comment-169990"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/f8393ef67ed5144e15890d60eaa2289e?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Valentinas</h3> <span class="dati"> <a title="Commentlink #69" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169990"> March 14, 2011 1:28 am </a> </span> </div> </div> <div class="ctx"> <p>Great article! Particularly the part about using wp_debug is a must-read for every plugin developer.<br /> By the way, just wanted to point out that there is a function wp_login_url() for login url. People should use this, because some plugins may modify it with filter that is inside it and bloginfo(‘wpurl’) . “/wp-login.php” is not necessary the right login URL.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169990" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169990" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment odd alt depth-2 clearfix"> <span class="cn">70</span> <div class="c" id="comment-169992"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7f46ae04d74b786bcaabec5a431c7937?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dave Donaldson</h3> <span class="dati"> <a title="Commentlink #70" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169992"> March 14, 2011 4:08 am </a> </span> </div> </div> <div class="ctx"> <p>@Valentinas – Good catch about the wp_login_url() function, thanks for pointing that out.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169992" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169992" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">71</span> <div class="c" id="comment-169993"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/61a894194ade535460a0e34ed4b56c31?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Gavin Potts</h3> <span class="dati"> <a title="Commentlink #71" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169993"> March 14, 2011 7:34 am </a> </span> </div> </div> <div class="ctx"> <p>Awesome post. 9 of 10 i’ve found extremely interesting and enlightening…</p> <p>I’d just like to query the tip: “Use bloginfo(‘wpurl’) Instead of bloginfo(‘url’)”. I believe this is bad advice.</p> <p>When developing a WordPress website, developers may be forced to work in a live environment with a holding page in place. If you use ‘wpurl’ in your themes/plugins, this will fail, as you will need to rename index.php and point ‘siteurl’ to the index page to have the website up for development.</p> <p>If all of your internal links are output with the ‘wpurl’ parameter, these will link to your holding page and you will have to type permalinks into your browser manually instead of clicking on links within the website.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169993" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169993" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">72</span> <div class="c" id="comment-169994"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/c92d3f3fe8e5b19bd7dc3d08142b400e?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Jim Krill</h3> <span class="dati"> <a title="Commentlink #72" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169994"> March 14, 2011 6:54 pm </a> </span> </div> </div> <div class="ctx"> <p>This is a great article for anyone wanting to develop a WordPress plugin. Hopefully it will lead to some brilliant plug-ins which will enrich the WordPress community even more.</p> <p>Thanks Dave!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169994" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169994" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">73</span> <div class="c" id="comment-169996"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/e94a2e120ad98cc9d2708b156c6a1c69?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Philip Norton</h3> <span class="dati"> <a title="Commentlink #73" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169996"> March 15, 2011 1:58 am </a> </span> </div> </div> <div class="ctx"> <p>This is a great list, but one thing that every WordPress developer should know about (more important than knowing about require_once() etc) is nonces. Nonces are a very important part of WordPress that help to combat security problems and should definitely be on this list.<br /> <a href="http://codex.wordpress.org/WordPress_Nonces" rel="nofollow">http://codex.wordpress.org/WordPress_Nonces</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169996" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169996" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">74</span> <div class="c" id="comment-169997"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7ac2e44aeff39f6df1187cb0e4f7fb92?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Jason LaRose</h3> <span class="dati"> <a title="Commentlink #74" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169997"> March 15, 2011 9:15 am </a> </span> </div> </div> <div class="ctx"> <p>One thing every WordPress plugin developer should do is NOT include default styles for their generated HTML. Doing so means reverse engineering for other WordPress developers. If you do add default styles, add in the option to deactivate the CSS.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169997" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169997" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">75</span> <div class="c" id="comment-169999"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/25c608d2c1b076011369920bfcd889a3?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Dan Coulter</h3> <span class="dati"> <a title="Commentlink #75" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-169999"> March 15, 2011 12:12 pm </a> </span> </div> </div> <div class="ctx"> <p>Nothing about wp_enqueue_script()?</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_169999" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="169999" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">76</span> <div class="c" id="comment-170000"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/5c65fecb4e4179a59ebecb18034dcb64?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Permana Jayanta</h3> <span class="dati"> <a title="Commentlink #76" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170000"> March 15, 2011 6:40 pm </a> </span> </div> </div> <div class="ctx"> <p>Really helpful post as I’m writing WordPress plugin now. Maybe should added list of functions that can help plugin development, instead of writing a functions again.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170000" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170000" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">77</span> <div class="c" id="comment-170001"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/0445bfc3e671c35b39d6036658c57a0e?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Kyathi</h3> <span class="dati"> <a title="Commentlink #77" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170001"> March 16, 2011 10:24 pm </a> </span> </div> </div> <div class="ctx"> <p>Thank you.. superb.. !!! its really helpful…</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170001" class="inpsyde_extended_comments_rate positive">1</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170001" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">78</span> <div class="c" id="comment-170003"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/b80742b6d859d848f839c270c2543f3c?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Sterling Hamilton</h3> <span class="dati"> <a title="Commentlink #78" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170003"> April 9, 2011 11:15 am </a> </span> </div> </div> <div class="ctx"> <p>Hey there!</p> <p>A few things…</p> <p>In regards to dbDelta:<br /> “require_once(ABSPATH . ‘wp-admin/includes/upgrade.php’);”</p> <p>That means you are now including a core WP file into your plugin…not really recommended. Further more, by doing that – it will start throwing aggressive cache busting headers. This will get in the way of caching plugins and proxies.</p> <p>Also – rather than prefixing every function, it’s better to just do an Object in PHP and give that a unique name. That way prefixing is not needed – just a unique object name.</p> <p>And the BlackBox plugin has been known to drastically slow down servers, so it should not be used in any sort of production environment.</p> <p>Also – you want to load your plugins meta data rather than creating your own. So version number/plugin path/etc are able to be loaded like this: <a href="https://gist.github.com/911684" rel="nofollow">https://gist.github.com/911684</a></p> <p>Another really good tip…do NOT rely on environment variables like HTTP_HOST, REQUEST_URI and such.</p> <p>These tend to be unreliable – its best to use the wordpress variables for determining locations and what not.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170003" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170003" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">79</span> <div class="c" id="comment-170004"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7a831efd240c56f74f4c4f2618d9a51a?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>cogmios`</h3> <span class="dati"> <a title="Commentlink #79" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170004"> May 6, 2011 10:30 am </a> </span> </div> </div> <div class="ctx"> <p>Because of the topic the “Objective Best Practices for Plugin Development?” on <a href="http://wordpress.stackexchange.com/questions/715/objective-best-practices-for-plugin-development" rel="nofollow">http://wordpress.stackexchange.com/questions/715/objective-best-practices-for-plugin-development</a> is also a good addition.</p> <p>Maybe to add to the debugging part: I also found using Zend Server community edition together with PHP PDT increase my debugging abilities (I dumped xampp for it).</p> <p> For making names unique well… I use php 5.3 with namespaces -end of problem- the language solves it for me. So I just state “this plugin is only for php 5.3 onwards” (although some discussion exist on “only 5.3″ <a href="http://groups.google.com/group/wp-hackers/browse_thread/thread/19dc7c7197f66754/9a60ad0b37ccaf1b?show_docid=9a60ad0b37ccaf1b&pli=1" rel="nofollow">http://groups.google.com/group/wp-hackers/browse_thread/thread/19dc7c7197f66754/9a60ad0b37ccaf1b?show_docid=9a60ad0b37ccaf1b&pli=1</a>)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170004" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170004" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">80</span> <div class="c" id="comment-170005"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/8c06582f15e2a41ca172044202c426eb?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>anyon</h3> <span class="dati"> <a title="Commentlink #80" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170005"> May 7, 2011 2:25 pm </a> </span> </div> </div> <div class="ctx"> <p>rule #1 wordpress is coded badly you will not learn anything about design patterns or best practices from looking at the wordpress source code, use your initiative ;)</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170005" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170005" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">81</span> <div class="c" id="comment-170006"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/216c409be1cbf323cbd714f4010e6797?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Brett Widmann</h3> <span class="dati"> <a title="Commentlink #81" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170006"> May 10, 2011 7:22 pm </a> </span> </div> </div> <div class="ctx"> <p>Thanks for these really awesome tips! They will be really helpful.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170006" class="inpsyde_extended_comments_rate negative">-2</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170006" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">82</span> <div class="c" id="comment-170007"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/827b430098defd203fa74ed9ce92e0d9?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>mikaweb</h3> <span class="dati"> <a title="Commentlink #82" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170007"> September 11, 2011 2:28 am </a> </span> </div> </div> <div class="ctx"> <p>Nice tips. I’m currently writing my first plugin and it helped me a lot especially for the upgrade system.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170007" class="inpsyde_extended_comments_rate positive">2</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170007" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-even depth-1 clearfix"> <span class="cn">83</span> <div class="c" id="comment-170008"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/78d5156936de65aac7e00ea273db82e7?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>liskel</h3> <span class="dati"> <a title="Commentlink #83" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170008"> August 25, 2012 4:22 am </a> </span> </div> </div> <div class="ctx"> <p>Really nice things to keep in mind and great for beginners exploring the deep depths of wordpress plugin development!<br /> Thanks!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170008" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170008" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-odd thread-alt depth-1 clearfix"> <span class="cn">84</span> <div class="c" id="comment-170009"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/0fa974dbdfd8afc7390131f9fd4c097c?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Ryan S</h3> <span class="dati"> <a title="Commentlink #84" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170009"> September 14, 2012 12:09 am </a> </span> </div> </div> <div class="ctx"> <p>Hi thanks for the tip, I just notice in Settings link, I think there is the better way to declare setting link.</p> <p>something like this<br /> $settings_link = ‘<a href="'.admin_url('admin.php?page=plugin-settings').'" rel="nofollow">Settings</a>‘;</p> <p>Ryan S</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170009" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170009" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> <ul class="children"> <li class="comment even depth-2 clearfix"> <span class="cn">85</span> <div class="c" id="comment-170010"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/0fa974dbdfd8afc7390131f9fd4c097c?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Ryan S</h3> <span class="dati"> <a title="Commentlink #85" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170010"> September 14, 2012 12:10 am </a> </span> </div> </div> <div class="ctx"> <p>Oops sorry for this second comment, it does not look good on my previous comment.</p> <p><code>$settings_link = '<a href="'.admin_url('admin.php?page=cx-events').'" rel="nofollow">Settings</a>';</code></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170010" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170010" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ul><!-- .children --> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">86</span> <div class="c" id="comment-170011"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/98d0a24074949185147845293651e72c?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Arch!tect</h3> <span class="dati"> <a title="Commentlink #86" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170011"> January 7, 2013 11:27 pm </a> </span> </div> </div> <div class="ctx"> <p>thanks dude!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170011" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170011" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">87</span> <div class="c" id="comment-170012"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/1cde71fd2000a3649df05c3be7fd7ba9?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>David Hazelden</h3> <span class="dati"> <a title="Commentlink #87" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170012"> February 17, 2013 8:04 am </a> </span> </div> </div> <div class="ctx"> <p>Good stuff!</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170012" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170012" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">88</span> <div class="c" id="comment-170013"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/2af83baa1864c442b08865d2f9ed8223?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Byron Dunn</h3> <span class="dati"> <a title="Commentlink #88" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170013"> February 28, 2013 7:50 am </a> </span> </div> </div> <div class="ctx"> <p>Great article. Being new to WP development, this is really helpful. Even for those of us struggling to tweak plugins we use.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170013" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170013" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">89</span> <div class="c" id="comment-170014"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/1441f3f17c4f72a0153415048e442bf0?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Manuel Marquez</h3> <span class="dati"> <a title="Commentlink #89" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170014"> March 21, 2013 1:43 am </a> </span> </div> </div> <div class="ctx"> <p>Thanks Dave,</p> <p>These are fantastic tips to start quality plugin development. Please keep up the good work!<br /> Much appreciated.</p> <p>Cheers,<br /> Manuel</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170014" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170014" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">90</span> <div class="c" id="comment-170019"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/ad64f6ef4b9c5b4f8b3c90be203be4d2?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Alex Buri</h3> <span class="dati"> <a title="Commentlink #90" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170019"> June 28, 2013 3:04 am </a> </span> </div> </div> <div class="ctx"> <p>Clear and well-written – you’ve allowed me to understand php even in the middle of the night….<br /> thanks</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170019" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170019" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">91</span> <div class="c" id="comment-170018"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://1.gravatar.com/avatar/7807fb5b55bfd79bc0c36c307b3a4bd8?s=38&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Juergen</h3> <span class="dati"> <a title="Commentlink #91" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170018"> October 14, 2013 11:31 pm </a> </span> </div> </div> <div class="ctx"> <p>Hello,<br /> a really really good tutorial.<br /> Thanks</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170018" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170018" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">92</span> <div class="c" id="comment-170017"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/c1b4eb8751a973da835b8fb6588586aa?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Will</h3> <span class="dati"> <a title="Commentlink #92" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170017"> January 3, 2014 12:10 pm </a> </span> </div> </div> <div class="ctx"> <p>Thanks for the article. The menu stuff in particular was very helpful. </p> <p>I’d add 11): Understand how/when WordPress loads things. This flow chart of what happens during a WP request cycle is pretty illuminating: <a href="http://www.rarst.net/script/wordpress-core-load/" rel="nofollow">http://www.rarst.net/script/wordpress-core-load/</a> </p> <p>Couple of other handy flow charts linked from that page as well in particular this chart that explains WP Query Functions <a href="http://www.rarst.net/script/wordpress-query-functions/" rel="nofollow">http://www.rarst.net/script/wordpress-query-functions/</a></p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170017" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170017" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment even thread-odd thread-alt depth-1 clearfix"> <span class="cn">93</span> <div class="c" id="comment-170015"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/e85eff52524a64e38ddc4316fb079c22?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>jack</h3> <span class="dati"> <a title="Commentlink #93" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170015"> January 20, 2014 12:02 am </a> </span> </div> </div> <div class="ctx"> <p>i have developed a plugin for paggination along with a shortcode but the output is showing in dashboad and when adding shortcode in any pages then it displays output in pages.<br /> Kindly suggest how to hide the output from dashbord.</p> <p>Thank You in advance</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170015" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170015" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> <li class="comment odd alt thread-even depth-1 clearfix"> <span class="cn">94</span> <div class="c" id="comment-170016"> <div class="cau clearfix"> <img alt="" src="http://www.smashingmagazine.com/wp-content/plugins/inpsyde-gravatar-load-delay/inc/frontend/../../assets/img/avatar-placeholder.png" data-gravatar-url="http://0.gravatar.com/avatar/6c94850a0051b2ab23ab7a18c7d4d181?s=38&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D38&r=G" class="avatar avatar-38 photo" height="38" width="38" /> <div class="aum"> <h3>Wordpress plugins</h3> <span class="dati"> <a title="Commentlink #94" href="http://www.smashingmagazine.com/2011/03/08/ten-things-every-wordpress-plugin-developer-should-know/#comment-170016"> February 20, 2014 10:04 pm </a> </span> </div> </div> <div class="ctx"> <p>Good post. I learn something totally new and challenging on blogs I stumbleupon on a daily basis. It will always be helpful to read through content from other authors and use something from their sites.</p> </div> <div class="com"> <div class="reply"></div> <div class="inpsyde_extended_comments_rate_wrapper clearfix" aria-live="polite"> <div id="inpsyde_extended_comments_rate_170016" class="inpsyde_extended_comments_rate">0</div> <div class="inpsyde_extended_comments_rate_stars" data-comment_id="170016" data-action="inpsyde_extended_comments_rate"></div> </div> </div> </div> </li><!-- #comment-## --> </ol> </div> </div> </div></div><p><a href="#top" class="top" title="Jump to the top of the page">↑ Back to top</a></p> </div><div class="fo-na"> <div class="mn" id="mn"> <ul id="menu-smashing-mobile-network" class="mnu"><li class="mnh">Smashing Pages:</li><li id="menu-item-188956" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-188956 menu-item-books"><a href="http://www.smashingmagazine.com/books/">Books</a></li> <li id="menu-item-188957" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-188957 menu-item-ebooks"><a href="http://www.smashingmagazine.com/ebooks/">eBooks</a></li> <li id="menu-item-188955" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-188955 menu-item-workshops"><a href="http://www.smashingmagazine.com/smashing-workshops/">Workshops</a></li> <li id="menu-item-188959" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-188959 menu-item-email-newsletter"><a href="http://www.smashingmagazine.com/the-smashing-newsletter/">Email Newsletter</a></li> <li id="menu-item-188961" class="menu-item menu-item-type-custom menu-item-object-custom menu-item-188961 menu-item-job-board"><a href="http://jobs.smashingmagazine.com">Job Board</a></li> <li id="menu-item-188958" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-188958 menu-item-about-us-impressum"><a href="http://www.smashingmagazine.com/about/">About us / Impressum</a></li> </ul> <ul id="menu-mobile-categories" class="mnu"><li class="mnh">Categories:</li><li id="menu-item-181575" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-181575 menu-item-coding"><a href="http://www.smashingmagazine.com/category/coding/">Coding</a></li> <li id="menu-item-181576" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-181576 menu-item-design"><a href="http://www.smashingmagazine.com/category/design/">Design</a></li> <li id="menu-item-181580" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-181580 menu-item-mobile"><a href="http://www.smashingmagazine.com/category/mobile/">Mobile</a></li> <li id="menu-item-181579" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-181579 menu-item-graphics"><a href="http://www.smashingmagazine.com/category/graphics/">Graphics</a></li> <li id="menu-item-181577" class="menu-item menu-item-type-taxonomy menu-item-object-category menu-item-181577 menu-item-ux-design"><a href="http://www.smashingmagazine.com/category/uxdesign/">UX Design</a></li> <li id="menu-item-181578" class="menu-item menu-item-type-taxonomy menu-item-object-category current-post-ancestor current-menu-parent current-post-parent menu-item-181578 menu-item-wordpress"><a href="http://www.smashingmagazine.com/category/wordpress/"><span class="long"><span>Word</span><span>Press</span></span><span class="short">WP</span></a></li> </ul> <a href="#top" class="top" title="Jump to the top of the page">↑ Back to top</a> </div><div class="ms" id="ms"> <form id="searching" class="sfm" method="get" action="http://www.smashingmagazine.com/search-results/" target="_top"> <div class="clearfix"> <input name="q" id="mobile-search-input" type="text" placeholder="e.g. CSS" /> <button class="search_submit" type="submit">Search</button> <input type="hidden" name="cx" value="partner-pub-6779860845561969:5884617103"> <input type="hidden" name="cof" value="FORID:10"> <input type="hidden" name="ie" value="UTF-8"> </div> </form> <a href="#top" class="top" title="Jump to the top of the page">↑ Back to top</a> </div> <!-- Search form --></div> </div><div id="wpsidebar" class="sb"> <div class="col side"> <div class="sf"> <form method="get" action="http://www.smashingmagazine.com/search-results/" target="_top"> <label for="magazine-search">Search on Smashing Magazine</label> <input id="magazine-search" name="q" type="text" placeholder="e.g. Responsive design" /> <button type="submit">Search</button> <input type="hidden" name="cx" value="partner-pub-6779860845561969:5884617103"> <input type="hidden" name="cof" value="FORID:10"> <input type="hidden" name="ie" value="UTF-8"> </form> </div> <div class="bw faw"> <span class="declare">Advertisement</span> <span class="awithus"><a class="sprite ed-us" href="mailto:advertising@smashingmagazine.com" title="Advertise with us!">Advertise with us!</a></span> <div id="spnsrlist-a"></div> </div> <div class="sf wg"> <h3> <a href="http://www.smashingmagazine.com/the-smashing-newsletter/"> <img src="http://www.smashingmagazine.com/files/smashing-widget/v006/img/smnl.png" alt="Smashing Newsletter" /> Smashing Newsletter </a> </h3> <p>Subscribe to our email newsletter for useful tips and valuable resources, sent out every second Tuesday.</p> <form action="http://smashingmagazine.us1.list-manage1.com/subscribe/post?u=16b832d9ad4b28edf261f34df&id=a1666656e0" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate"> <input name="EMAIL" type="text" placeholder="email address" /> <button class="search_submit" type="submit">Subscribe</button> </form> </div> <div class="bw"> <div id="spnsrlist-b"></div> </div> <div class="so wg"> <div class="fir"> <a href="http://www.smashingmagazine.com/books/#digital-adaptation" style="border: none;"> <img src="http://www.smashingmagazine.com/wp-content/uploads/2013/04/sidebar-digital-adaptation-paul-boag-v5-opt.png" alt="Digital Adaptation by Paul Boag"> </a> <p>Nothing is more frustrating than <strong>stubborn management</strong>. That's why we have published <a href="http://www.smashingmagazine.com/books/#digital-adaptation">Digital Adaptation</a>, a new book by Paul Boag on how to help management overcome legacy practices - for good.</p> </div> <div class="sec"> <a href="http://www.smashingmagazine.com/smashing-book-4-new-perspectives/?pk_campaign=sb4-sidebar"><img src="http://www.smashingmagazine.com/wp-content/uploads/2013/04/Smashing-Book-4-sidebar-transparent-opt.png" alt="Smashing Book #4"></a> <p>It's done. The <a href="http://www.smashingmagazine.com/smashing-book-4-new-perspectives/?pk_campaign=sb4-sidebar">Smashing Book #4</a>, our brand new book with smart <strong>front-end techniques</strong> and design approaches. Written by respected designers and developers, neatly packed in a gorgeous hardcover.</p> </div> <div class="thi"> <a href="http://www.smashingmagazine.com/ebooks/?pk_campaign=sb4-sidebar"> <img src="http://www.smashingmagazine.com/wp-content/uploads/2014/08/sidebar-smashing-library.png" alt="Smashing Library"> </a> <p>Hungry for more content? Over 60 <strong>eBooks</strong> are waiting to be discovered in our lovely <a href="http://www.smashingmagazine.com/ebooks/?pk_campaign=sb4-sidebar">Smashing Library</a>. And guess what? You can watch Smashing Conference talks there, too.</p> </div> </div> <div class="bw"> <div id="spnsrlist-c"></div> </div> <div class="wg"> <div id="jobs"> <h3> <a href="http://jobs.smashingmagazine.com/?pk_campaign=sm&piwik_kwd=widget"> <span>Smashing Job Board</span> <img src="http://www.smashingmagazine.com/files/smashing-widget/v006/img/sm-jobs.png" alt="Smashing Jobs"> </a> </h3> <ul class="tl"> <li style="display:none;"></li> <ul class="tl"><li class="clearfix"><a href="http://feedproxy.google.com/~r/smjobs/~3/l1iopv9T-xg/2415960">Senior Web/Graphic Designer - RateHub - (Toronto, ON) - FullTime</a><p>Position for hire: Senior Web / Graphic designer Location: Downtown Toronto, ON Start Date: As soon as possible About us We’re a talen...</p></li><li class="clearfix"><a href="http://feedproxy.google.com/~r/smjobs/~3/ODntye-bheY/2415959">Senior Front-End Engineer (Yes, You can Work from Home) - Twin Technologies - (Altamont, New York) - FullTime</a><p>About the Opportunity We are seeking a few good men and women to help build a “best of breed” eCommerce platform that supports the creation, maintenance...</p></li></ul> </ul> <a class="cr" href="http://jobs.smashingmagazine.com?pk_campaign=sm&piwik_kwd=widget">View more job openings…</a> </div> </div> <div id="sidebar_special-1"></div> <div id="sidebar_special-2"></div> <div class="sidebar_sky" id="sidebar_sky-1"></div> <div class="sidebar_sky" id="sidebar_sky-2"></div> </div> </div><div id="footer">
<div class="fp clearfix"> <a class="pi" href="http://www.smashingmagazine.com/smashing-book-4-new-perspectives/?pk_campaign=sb4-footer"><img src="http://www.smashingmagazine.com/wp-content/uploads/2013/10/smashing-book-4-footer-opt.png" alt="Smashing Book #4"></a> <p class="pd"> <a href="http://www.smashingmagazine.com/smashing-book-4-new-perspectives/?pk_campaign=sb4-footer"><strong>Smashing Book #4</strong></a><br />Get our brand new Smashing Book #4, available as print and eBook. <a href="http://www.smashingmagazine.com/smashing-book-4-new-perspectives/?pk_campaign=sb4-footer">Learn more...</a> </p> </div> <div class="fp clearfix"> <a class="pi" href="https://shop.smashingmagazine.com/smashing-library-complete.html?pk_campaign=smashingmagazine-footer"><img src="http://www.smashingmagazine.com/wp-content/uploads/2013/10/smashing-library-footer-new-opt.png" alt="The Smashing Library"></a> <p class="pd"> <a href="https://shop.smashingmagazine.com/smashing-library-complete.html?pk_campaign=smashingmagazine-footer"><strong>The Smashing Library</strong></a><br />Grab all published and upcoming Smashing eBooks, in one swoop. <a href="https://shop.smashingmagazine.com/smashing-library-complete.html?pk_campaign=smashingmagazine-footer">Learn more...</a> </p> </div> <div class="fp clearfix"> <a class="pi" href="http://www.smashingmagazine.com/smashing-workshops/"><img src="http://www.smashingmagazine.com/wp-content/uploads/2013/08/footer-brad-frost-opt.jpg" alt="Smashing Workshops"></a> <p class="pd"> <a href="http://www.smashingmagazine.com/smashing-workshops/"><strong>Smashing Workshops</strong></a><br />Join our hands-on full-day workshops, run by experts of the industry. Good stuff. <a href="http://www.smashingmagazine.com/smashing-workshops/">Learn more...</a> </p> </div><p class="stmt"><em>With a commitment to quality content for the design community.</em><br />Founded by Vitaly Friedman and Sven Lennartz. 2006-2014.<br />Made in Germany. ? <a href="http://www.smashingmagazine.com/write-for-us/">Write for us</a> - <a href="http://www.smashingmagazine.com/contact/">Contact us</a> - <a href="http://www.smashingmagazine.com/about/">Impressum</a>.</p> </div> <script type="text/javascript">var clicky_site_ids=clicky_site_ids||[];clicky_site_ids.push(2727),function(){var e=document.createElement("script");e.type="text/javascript",e.async=!0,e.src="//static.getclicky.com/js",(document.getElementsByTagName("head")[0]||document.getElementsByTagName("body")[0]).appendChild(e)}();</script><noscript><p><img alt="Clicky" width="1" height="1" src="//in.getclicky.com/2727ns.gif" /></p></noscript>
<script type='text/javascript' src='http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/javascripts/ads.min.js?ver=2014.1.3'></script> <script type="text/javascript">var elements=["http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/javascripts/onload.min.js?ver=2014.12.0","http://www.smashingmagazine.com/wp-content/themes/smashing-magazine/javascripts/prism.js"],downloadJSAtOnload=function(n){if("[object Array]"!==Object.prototype.toString.call(n))return 0;var t,e;for(t=0;t<n.length;t++)e=document.createElement("script"),e.src=n[t],document.body.appendChild(e);return !0};window.addEventListener ? window.addEventListener("load",function(){downloadJSAtOnload(elements)},!1):window.attachEvent ? window.attachEvent("onload",function(){downloadJSAtOnload(elements)}):window.onload=function(){downloadJSAtOnload(elements)};window.onload=function(){var avatars=document.querySelectorAll('.avatar');for(var i=0,length=avatars.length;i<length;i++){var gravatar_url=avatars[i].getAttribute('data-gravatar-url');avatars[i].src=gravatar_url;}};</script> <script type='text/javascript'>/* <![CDATA[ */ SmashingAds.load(); /* ]]> */</script><script type='text/javascript'>/* <![CDATA[ */ SmashingAds.postLoad(); /* ]]> */</script><script type='text/javascript'>/* <![CDATA[ */ SmashingAds.postPostLoad(); /* ]]> */</script> <script type="text/javascript">(function(){"use strict";if("querySelector" in document){var forEach=function(array,callback,scope){for(var i=0;i<array.length;i++){callback.call(scope,i,array[i]);}};var articles=document.getElementsByTagName("article");forEach(articles,function(i,el){var tagElements=el.querySelectorAll("li.tags a");var tags=[];forEach(tagElements,function(i,el){var content=el.innerText||el.textContent;tags.push(content.toLowerCase());});var image=el.querySelector(".at");if(image)image.setAttribute("data-adt-keywords",tags);});adtile("[data-adt-keywords]",{apiKey:"4624ca9f-0982-442f-b691-bb5f04643a74",channel:"technology",keywords:["Smashing Conference","Smashingconf","Whistler","Front-end","CSS","Javascript"],taglineFontFamily:"'Proxima Nova Bold','Helvetica Neue',Helvetica,Arial,sans-serif",taglineBorderRadius:"1.25em",colors:{iconBackground:"#e53b2c",closeButtonBackground:"#e53b2c"}});}})();</script> </body></html> <end node> 5P9i0s8y19Z dt= <node>WARNINGS 1 [FORMS] DO not use name="name" into inputs. RETURNS PAGE NOT FOUND <end node> 5P9i0s8y19Z
<node>CUSTOM CODING <node>Disable auto updates <node>Disable site <node>EXTERNAL PHP <node>Hacks <node>footer changes <node>Header Change <node>New user <node>is logged in <node>Merging admins <node>Protect Login Screen <node>redirect <node>Codects <node>database access <node>domain change <node>Embed wordpress page <node>MEMBERlogin <node>Redirect <node>database <node>get_row <node>MergeDatabases <node>minimum permissions <node>New subject <node>notes <node>plugin <node>backupWordpress <node>Contact form <node>shortcodes <node>WIDGET <node>example <node>new area <node>saved info <node>simple one
<Treepad version 3.0> dt= <node>CUSTOM CODING 0 accepted
If you are getting to the point where the code in your theme's functions.php is starting to overwhelm you I would definitely say you are ready to consider splitting it up into multiple files. I tend to do that almost by second nature at this point. Use Include Files in your Theme's functions.php File I create a subdirectory called "includes" under my theme directory and segment my code into include files organized by what makes sense to me at the time (which means I'm constantly refactoring and moving code around as a site evolves.) I also rarely put any real code in functions.php; everything goes in the include files; just my preference. Just to give you an example here's my test install that I use to test my answers to questions here on WordPress Answers. Every time I answer a question I keep the code around in case I need it again. This isn't exactly what you'll do for a live site but it shows the mechanics of splitting up the code: require_once('includes/null-meta-compare.php'); require_once('includes/older-examples.php'); require_once('includes/wp-admin-menu-classes.php'); <end node> 5P9i0s8y19Z dt= <node>Disable auto updates 1 Example Coding Magic: Turn Off Automatic Updates Auto updates have been a part of WordPress since version 3.7. Not everyone likes this feature; many would like to turn it off. All you need to do is add this line of code to your wp-config.php file. 1./* Disable WordPress automatic updates */ .2.define( 'WP_AUTO_UPDATE_CORE', false ); <end node> 5P9i0s8y19Z dt= <node>Disable site 1 In the header.php file of genisis <?php if(!is_user_logged_in()){ echo "This site is under construction"; exit; } <end node> 5P9i0s8y19Z dt= <node>EXTERNAL PHP 1 home | photos | login
Outreach Child Theme: wpHeaderInclude.php <link rel="stylesheet" href="<?php echo includes_url(); ?>/js/lightbox/lightbox.css" type="text/css" media="screen" > <script type="text/javascript" src="<?php echo includes_url(); ?>/js/lightbox/lightbox.js"></script> Just add your lightbox folder to the include/js folder ===================================================== I actually found how to do it, it's pretty straight forward: 1/ Register a function to be executed when the wp_head action fires: add_action('wp_head', 'my_function'); 2/ Make the function echo whatever you want in the header: function my_function() { <link rel="stylesheet" href="<?php echo includes_url(); ?>/js/lightbox/lightbox.css" type="text/css" media="screen" > echo '<meta name="robots" content="noindex, nofollow">'; } Using this trick for the Facebook Like plugin, thanks to the smart Add Your Own Headers plugin that showed me pointers. <end node> 5P9i0s8y19Z dt= <node>New user 2 REQUIRES 3 INSERTS INSERT INTO `databasename`.`wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES ('4', 'demo', MD5('demo'), 'Syed Balkhi', 'test@yourdomain.com', 'http://www.wpbeginner.com/', '2011-06-07 00:00:00', '', '0', 'Syed Balkhi'); 2 3 4 INSERT INTO `databasename`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, '4', 'wp_capabilities', 'a:1:{s:13:"administrator";s:1:"1";}'); 5 6 7 INSERT INTO `databasename`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, '4', 'wp_user_level', '10'); wp_w3q1o7u0_usermeta WPBeginner» Blog» Tutorials» How to Add an Admin User to… How to Add an Admin User to the WordPress Database via MySQL Last updated on November 25th, 2014 by Editorial Staff Share This Article 101 Follow WPBeginner on YouTube How to Add an Admin User to the WordPress Database via MySQL Few days ago, we ran into an issue where a user’s site got hacked and their admin account was deleted from the database. This locked them out of their site without any other entry. We went in to the phpMyAdmin and created a new admin user to grant them access. In this article, we will show you a step by step guide on how to create an admin user in WordPress Database via MySQL. Note: You should always make a backup of your database before performing any MySQL edits. This tutorial requires basic understanding of how phpMyAdmin works. Video Tutorial If you don’t like the video or need more instructions, then continue reading. First, you need to login to phpMyAdmin and locate your WordPress database. (Below is a screenshot of a HostGator cPanel) cPanel phpMyAdmin Once you are in, we will be making changes to the wp_users and wp_usermeta tables. Lets go ahead and click on wp_users table. phpMyAdmin wp_users table We need to insert our new admin user’s information, so click on the Insert tab like it shows in the image above. In the insert form, add the following: ID – pick a number (in our example, we will use the number 4). user_login – insert the username you want to use to access the WordPress Dashboard. user_pass – add a password for this username. Make sure to select MD5 in the functions menu (Refer to the screenshot below). user_nicename – put a nickname or something else that you would like to refer yourself as. user_email – add the email you want to associate with this account. user_url – this would be the url to your website. user_registered – select the date/time for when this user is registered. user_status – set this to 0. display_name – put the name you like to display for this user on the site (it can be your user_nicename value as well). Click on the Go Button phpMyAdmin Insert values in wp_users table Next we are going to have to add the values to wp_usermeta table. Click on the wp_usermeta table and then click on the Insert tab just like the previous step. Then add the following information to the insert form: unmeta_id – leave this blank (it will be auto-generated) user_id – this will be the id of the user you created in the previous step. Remember we picked 4. meta_key – this should be wp_capabilities meta_value – insert this: a:1:{s:13:"administrator";s:1:"1";} Insert another row with the following information: unmeta_id – leave this blank (it will be auto-generated) user_id – this will be the id of the user you created in the previous step. Remember we picked 4. meta_key – this should be wp_user_level meta_value – 10 Then click on the Go button, and you have created yourself a new username. Now you should be able to login to your wp-admin with the username and password you specified for this user. Once logged in, click on Users and edit the username you just created. Go down and click on the Save button (you don’t have to change anything). This will allow WordPress to go through and add some more information and clean-up the user we just added. SQL query For developers who want to speed this process up, you can simply drop this SQL query in your database. 1 INSERT INTO `databasename`.`wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES ('4', 'demo', MD5('demo'), 'Syed Balkhi', 'test@yourdomain.com', 'http://www.wpbeginner.com/', '2011-06-07 00:00:00', '', '0', 'Syed Balkhi'); 2 3 4 INSERT INTO `databasename`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, '4', 'wp_capabilities', 'a:1:{s:13:"administrator";s:1:"1";}'); 5 6 7 INSERT INTO `databasename`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, '4', 'wp_user_level', '10'); Remember to change the databasename to the database you are working with. Also don’t forget to change the appropriate values. About the Editorial Staff Editorial Staff at WPBeginner is a team of WordPress lovers led by Syed Balkhi. Page maintained by Syed Balkhi. More on WPBeginner Right Now How to Easily Create a Responsive WordPress Slider with Soliloquy How to Easily Create a Responsive WordPress Slider with Soliloquy How We Increased Our Organic Search Traffic By Using HitTail How We Increased Our Organic Search Traffic By Using HitTail WordPress Custom Fields 101: Tips, Tricks, and Hacks WordPress Custom Fields 101: Tips, Tricks, and Hacks How to Get Google’s Verified Authorship for your WordPress Blog How to Get Google’s Verified Authorship for your WordPress Blog WPBeginner's WordPress Training Videos Free WPBeginner's Video Icon Our HD-Quality tutorial videos for WordPress Beginners will teach you how to use WordPress to create and manage your own website in about an hour. Get started now » Join over 130,000 WordPress Users who get fresh content from WPBeginner! <end node> 5P9i0s8y19Z dt= <node>is logged in 1 <?php if(!is_user_logged_in()){ echo "This site is under construction"; exit; } <end node> 5P9i0s8y19Z dt= <node>Merging admins 1 Add this to the mystuff.php of the non wordpress admin FROM THE WINDSORSEVERANCESTORAGE.COM session_start(); include("config.php"); require_once("../wp-load.php"); if(!is_user_logged_in() && $bypass!=true){ echo "This site is under construction"; exit; } else $wordpress=true; if($wordpress==false){ $db = mysql_pconnect($server, $user,$password); if (!$db){ echo 'Error: Could not connect to database. Please try again later.'; exit; } mysql_select_db($database); if($pageLevel=='')$pageLevel=3; if($LEVEL<$pageLevel && $bypass!=true){ echo "<body onload=setTimeout(\\"location.href='LoginScreen.php'\\",2000)>"; echo "You need to login with more security.<p>Click <a href='LoginScreen.php'>here</a> to continue.";$_SESSION['LEVEL']='';exit; } }else $_SESSION['LEVEL']=10; <end node> 5P9i0s8y19Z dt= <node>Protect Login Screen 1 This is done near the top in both files in the index.php of the root/wp-admin folder add: if($_GET["SWD"]!="") setcookie("SWD_ADMIN","swd", time()+(60*60*24*30),"/"); in the root folder wp-login.php add: if($_COOKIE["SWD_ADMIN"]!="swd"){ echo "You have been terminated"; exit; } <end node> 5P9i0s8y19Z dt= <node>redirect 1 add_action( 'template_redirect', 'restrictPage_blah', 100 ); function restrictPage_blah() { if( ! is_user_logged_in() && is_page('restrictedPage') ) { wp_redirect( 'http://www.google.com' ); exit; } } <end node> 5P9i0s8y19Z dt= <node>Codects 1 <?php require_once("../wp-load.php"); require_once("swdFunctions.php"); function current_session(){ $sessionid =$_COOKIE["MYCOOKIE"];//$_SESSION["MYSESSION"]; if($sessionid==""){ $sessionid=strtotime(date("Y-m-d H:i:s")); setcookie("MYCOOKIE",$sessionid,time()+60*60*24*300); } return $sessionid; } get_header(); include(get_site_url()."/swd/mdropdown.php"); ?> <div id="content-full" class="grid col-940"> </div><!-- end of #content-full --> <?php get_footer(); ?> <end node> 5P9i0s8y19Z dt= <node>database access 2 <?php $path = $_SERVER['DOCUMENT_ROOT']; include_once $path . '/wp-config.php'; include_once $path . '/wp-load.php'; // THIS MAY BE THE ONLY LINE YOU MAY NEED include_once $path . '/wp-includes/wp-db.php'; include_once $path . '/wp-includes/pluggable.php'; // $wpdb is available, do stuff <end node> 5P9i0s8y19Z dt= <node>domain change 2 UPDATE wp_posts SET guid = replace(guid, 'http://www.old-domain.com','http://www.new-domain.com'); UPDATE whs_posts SET guid = replace(guid, 'http://www.softwarewebsecure.com/WINDSORHAIR','http://new.windsorhairshoppe.com'); <end node> 5P9i0s8y19Z dt= <node>Embed wordpress page 2 From the swinterTmpl.php from Storage include(includes_url()."storageLeaseForm.php?WPLOGIN=".STORAGE_MEMBER."&site1=".urlencode(site_url())); $include1 = get_pages('include=62'); $content = apply_filters('the_content',$include1[0]->post_content); echo $content; //echo includes_url()."storageLeaseForm.php?site1=".urlencode(site_url()); break; ID: page/post ID (int) ?post_author: author ID (string) ?post_date: time-date string (YYYY-MM-DD HH:MM:SS), e.g., "2012-10-15 01:02:59" ?post_date_gmt: time-date string ?post_content: HTML (string) ?post_title ?post_excerpt: HTML (string) ?post_status: (publish|inherit|pending|private|future|draft|trash) ?comment_status: closed/open ?ping_status: (closed|open) ?post_password ?post_name: slug for page/post ?to_ping ?pinged ?post_modified: time-date string ?post_modified_gmt: time-date string ?post_content_filtered ?post_parent: parent ID (int) ?guid: URL ?menu_order: (int) ?post_type: (page|post|attachment) ?post_mime_type ?comment_count: number of comments (string) ?filter All values are strings unless otherwise shown as (int). <end node> 5P9i0s8y19Z dt= <node>MEMBERlogin 2 using the index.php <?php session_start(); define('DARNELL_MEMBER', $_SESSION["DARNELL"]); //echo "shoot";exit; /** * Front to the WordPress application. This file doesn't do anything, but loads * wp-blog-header.php which does and tells WordPress to load the theme. * * @package WordPress */ /** * Tells WordPress to load the WordPress theme and output it. * * @var bool */ define('WP_USE_THEMES', true); /** Loads the WordPress Environment and Template */ require( dirname( __FILE__ ) . '/wp-blog-header.php' ); <end node> 5P9i0s8y19Z dt= <node>Redirect 2 [mix wordpress with non-wordpress site] $actual_link = "https://$_SERVER[HTTP_HOST]$_SERVER[REQUEST_URI]"; $parse = parse_url($actual_link); //echo "dog--".$server1; if($parse['host']=="new.angeldesignsbydenise.com"){ define('WP_USE_THEMES', true); // Loads the WordPress Environment and Template require( dirname( __FILE__ ) . '/wp-blog-header.php' ); exit; } <end node> 5P9i0s8y19Z dt= <node>database 1 [MULTIPLE RECORDS] $rows=$wpdb->get_results($query);$num=$wpdb->num_rows; foreach ( $rows as $row ) { if($cnt>$defaultField){ $dis.="\\n</td></tr></table><td width=175><table><tr><td><b>Member</b><td><b>Year<b></td>\\n";$cnt=0; } $donationid=$row->donationid; $last_name=$row->last_name; $last_name=ShortenString($last_name); $first_name=$row->first_name; $first_name=ShortenString($first_name); $authcode=$row->authcode; $datefill=$row->datefill; $timelapse=(int)((strtotime(date("Y-m-d"))-strtotime($datefill))/$yearlapse); if($timelapse==0)$timelapse="NEW"; //REPORT FORMAT here if($authcode=="YES"){ $dis.="<tr><td align=right>Anonymous</td><td width=20 style='text-align:center;'>$timelapse</td></tr>\\n"; }else{ $dis.="<tr><td align=right>$first_name $last_name</td><td width=20 style='text-align:center;'>$timelapse</td></tr>\\n"; // <td class=view>$first_name</td> <td class=view>$address</td> <td class=view>$city</td> <td class=view>$state</td> <td class=view>$zip</td> <td class=view>$phone</td> <td class=view>$email</td> <td class=viewnumber align=right>$pay_interval</td> <td class=view>$pay_option</td> <td class=viewnumber align=right>$amount</td> <td class=view>$datefill</td> <td class=view>$responsecode</td> <td class=viewnumber align=right>$subscriptionid</td> <td class=view>$reasoncode</td> <td class=view>$reasontext</td> <td class=view>$authcode</td> <td class=view>$avscode</td> <td class=view>$cardType</td> <td class=view>$cardnum</td> <td class=view>$csc</td> <td class=view>$month</td> <td class=viewnumber align=right>$year</td>"; } $cnt++; } SELECT Generic Results Generic, mulitple row results can be pulled from the database with get_results. The function returns the entire query result as an array, or NULL on no result. Each element of this array corresponds to one row of the query result and, like get_row, can be an object, an associative array, or a numbered array. <?php $wpdb->get_results('query', output_type); ?> query (string) The query you wish to run. Setting this parameter to null will return the data from the cached results of the previous query. output_type One of four pre-defined constants. Defaults to OBJECT. See SELECT a Row and its examples for more information. OBJECT - result will be output as a numerically indexed array of row objects. OBJECT_K - result will be output as an associative array of row objects, using first column's values as keys (duplicates will be discarded). ARRAY_A - result will be output as an numerically indexed array of associative arrays, using column names as keys. ARRAY_N - result will be output as a numerically indexed array of numerically indexed arrays. Since this function uses the '$wpdb->query()' function all the class variables are properly set. The results count for a 'SELECT' query will be stored in $wpdb->num_rows. [UPDATE OR DELETE] Run Any Query on the Database The query function allows you to execute any SQL query on the WordPress database. It is best to use a more specific function (see below), however, for SELECT queries. <?php $wpdb->query('query'); ?> query (string) The SQL query you wish to execute. The function returns an integer corresponding to the number of rows affected/selected. If there is a MySQL error, the function will return FALSE. (Note: since both 0 and FALSE can be returned, make sure you use the correct comparison operator: equality == vs. identicality ===). <end node> 5P9i0s8y19Z dt= <node>get_row 2 SELECT a Row To retrieve an entire row from a query, use get_row. The function can return the row as an object, an associative array, or as a numerically indexed array. If more than one row is returned by the query, only the specified row is returned by the function, but all rows are cached for later use. Returns OBJECT holding NULL if no result is found, consider this when using the returned value in arguments, see example below <?php $wpdb->get_row('query', output_type, row_offset); ?> query (string) The query you wish to run. output_type One of three pre-defined constants. Defaults to OBJECT. ¦OBJECT - result will be output as an object. ¦ARRAY_A - result will be output as an associative array. ¦ARRAY_N - result will be output as a numerically indexed array. row_offset (integer) The desired row (0 being the first). Defaults to 0. Examples Get all the information about Link 10. $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10"); The properties of the $mylink object are the column names of the result from the SQL query (in this example all the columns from the $wpdb->links table, but you could also query for specific columns only). echo $mylink->link_id; // prints "10" In contrast, using $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10", ARRAY_A); would result in an associative array: echo $mylink['link_id']; // prints "10" and $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10", ARRAY_N); would result in a numerically indexed array: echo $mylink[1]; // prints "10" If there is no record with ID 10 in the links table, null will be returned. The following would then be false: if ($mylink != null) { // do something with the link return true; } else { // no link found return false; } <end node> 5P9i0s8y19Z dt= <node>MergeDatabases 2 http://wordpress.stackexchange.com/questions/94018/merging-two-wp-posts-tables-while-avoiding-duplicates Import the new table as wp_posts_2, then join them and delete all duplicates based on post_content; then merge the two tables. The following SQL query (untested!) should give the posts from the new table to be deleted: SELECT wp2.* FROM wp_posts_2 as wp2 LEFT JOIN wp_posts as wp ON wp2.post_content = wp.post_content WHERE wp2.post_content = wp.post_content So, you can delete the entries with this query (also untested): DELETE wp_posts_2.* LEFT JOIN wp_posts as wp ON wp_posts_2.post_content = wp.post_content WHERE wp_posts_2.post_content = wp.post_content Then merge the two tables. <end node> 5P9i0s8y19Z dt= <node>minimum permissions 2 Below is an example of the minimum privileges a database user needs to have. Other database permissions are regarded as “extra” privileges that in most cases are not needed. A typical WordPress user should be granted the following database privileges only: The official documentation says to give the user all privs. Others suggest that you can restrict it to SELECT •INSERT •UPDATE •DELETE •CREATE •ALTER •INDEX •DROP optional Plugins etc can though call any statement they want so you would have to thoroughly test Data: SELECT INSERT UPDATE Example of How to Grant Access Privileges If you are upgrading WordPress, the above database permissions might not suffice between versions, WordPress might need to make further changes to the database. In this case, if you are only upgrading to the latest version of WordPress, add the below privileges to the WordPress database user: Structure: CREATE ALTER NOTE: Some plugins might require additional database privileges such as CREATE, DROP or DELETE and in those cases these privileges should be granted. <end node> 5P9i0s8y19Z dt= <node>New subject 2 <end node> 5P9i0s8y19Z dt= <node>notes 2 Interfacing With the Database WordPress provides a class of functions for all database manipulations. The class is called wpdb and is loosely based on the ezSQL class written and maintained by Justin Vincent. Using the $wpdb Object Methods in the wpdb() class should not be called directly. WordPress provides a global variable, $wpdb, which is an instantiation of the class already set up to talk to the WordPress database. Always use the global $wpdb variable. (Remember to globalize $wpdb before using it in any custom functions.) The $wpdb object can be used to read data from any table in the WordPress database (such as custom plugin tables), not just the standard tables that WordPress creates. For example to SELECT some information from a custom table called "mytable", you can do the following. $myrows = $wpdb->get_results( "SELECT id, name FROM mytable" ); The $wpdb object can talk to any number of tables, but only one database: the WordPress database. In the rare case you need to connect to another database, you will have to instantiate your own object from the wpdb class with the appropriate connection details. For extremely complicated setups with many databases, consider using hyperdb instead. Run Any Query on the Database The query function allows you to execute any SQL query on the WordPress database. It is best to use a more specific function (see below), however, for SELECT queries. <?php $wpdb->query('query'); ?> query (string) The SQL query you wish to execute. The function returns an integer corresponding to the number of rows affected/selected. If there is a MySQL error, the function will return FALSE. (Note: since both 0 and FALSE can be returned, make sure you use the correct comparison operator: equality == vs. identicality ===). Note: As with all functions in this class that execute SQL queries, you must SQL escape all inputs (e.g., wpdb->escape($user_entered_data_string)). See the section entitled Protect Queries Against SQL Injection Attacks below. Examples Delete the 'gargle' meta key and value from Post 13. (We'll add the 'prepare' method to make sure we're not dealing with an illegal operation or any illegal characters): $wpdb->query( $wpdb->prepare( " DELETE FROM $wpdb->postmeta WHERE post_id = %d AND meta_key = %s ", 13, 'gargle' ) ); Performed in WordPress by delete_post_meta(). Set the parent of Page 15 to Page 7. $wpdb->query( " UPDATE $wpdb->posts SET post_parent = 7 WHERE ID = 15 AND post_status = 'static' " ); SELECT a Variable The get_var function returns a single variable from the database. Though only one variable is returned, the entire result of the query is cached for later use. Returns NULL if no result is found. <?php $wpdb->get_var('query',column_offset,row_offset); ?> query (string) The query you wish to run. Setting this parameter to null will return the specified variable from the cached results of the previous query. column_offset (integer) The desired column (0 being the first). Defaults to 0. row_offset (integer) The desired row (0 being the first). Defaults to 0. Examples Retrieve and display the number of users. <?php $user_count = $wpdb->get_var( "SELECT COUNT(*) FROM $wpdb->users" ); echo "<p>User count is {$user_count}</p>"; ?> Retrieve and display the sum of a Custom Field value. <?php // set the meta_key to the appropriate custom field meta key $meta_key = 'miles'; $allmiles = $wpdb->get_var( $wpdb->prepare( " SELECT sum(meta_value) FROM $wpdb->postmeta WHERE meta_key = %s ", $meta_key ) ); echo "<p>Total miles is {$allmiles}</p>"; ?> SELECT a Row To retrieve an entire row from a query, use get_row. The function can return the row as an object, an associative array, or as a numerically indexed array. If more than one row is returned by the query, only the specified row is returned by the function, but all rows are cached for later use. Returns OBJECT holding NULL if no result is found, consider this when using the returned value in arguments, see example below. <?php $wpdb->get_row('query', output_type, row_offset); ?> query (string) The query you wish to run. output_type One of three pre-defined constants. Defaults to OBJECT. ¦OBJECT - result will be output as an object. ¦ARRAY_A - result will be output as an associative array. ¦ARRAY_N - result will be output as a numerically indexed array. row_offset (integer) The desired row (0 being the first). Defaults to 0. Examples Get all the information about Link 10. $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10"); The properties of the $mylink object are the column names of the result from the SQL query (in this example all the columns from the $wpdb->links table, but you could also query for specific columns only). echo $mylink->link_id; // prints "10" In contrast, using $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10", ARRAY_A); would result in an associative array: echo $mylink['link_id']; // prints "10" and $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10", ARRAY_N); would result in a numerically indexed array: echo $mylink[1]; // prints "10" If there is no record with ID 10 in the links table, null will be returned. The following would then be false: if ($mylink != null) { // do something with the link return true; } else { // no link found return false; } SELECT a Column To SELECT a column, use get_col. This function outputs a one dimensional array. If more than one column is returned by the query, only the specified column will be returned by the function, but the entire result is cached for later use. Returns an empty array if no result is found. <?php $wpdb->get_col('query',column_offset); ?> query (string) the query you wish to execute. Setting this parameter to null will return the specified column from the cached results of the previous query. column_offset (integer) The desired column (0 being the first). Defaults to 0. Examples For this example, assume the blog is devoted to information about automobiles. Each post describes a particular car (e.g. 1969 Ford Mustang), and three Custom Fields, manufacturer, model, and year, are assigned to each post. This example will display the post titles, filtered by a particular manufacturer (Ford), and sorted by model and year. The get_col form of the wpdb Class is used to return an array of all the post ids meeting the criteria and sorted in the correct order. Then a foreach construct is used to iterate through that array of post ids, displaying the title of each post. Note that the SQL for this example was created by Andomar. <?php $meta_key1 = 'model'; $meta_key2 = 'year'; $meta_key3 = 'manufacturer'; $meta_key3_value = 'Ford'; $postids=$wpdb->get_col( $wpdb->prepare( " SELECT key3.post_id FROM $wpdb->postmeta key3 INNER JOIN $wpdb->postmeta key1 ON key1.post_id = key3.post_id AND key1.meta_key = %s INNER JOIN $wpdb->postmeta key2 ON key2.post_id = key3.post_id AND key2.meta_key = %s WHERE key3.meta_key = %s AND key3.meta_value = %s ORDER BY key1.meta_value, key2.meta_value ", $meta_key1, $meta_key2, $meta_key3, $meta_key3_value ) ); if ( $postids ) { echo "List of {$meta_key3_value}(s), sorted by {$meta_key1}, {$meta_key2}"; foreach ( $postids as $id ) { $post = get_post( intval( $id ) ); setup_postdata( $post ); ?> <p> <a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link to <?php the_title_attribute(); ?>"> <?php the_title(); ?> </a> </p> <?php } } ?> This example lists all posts that contain a particular custom field, but sorted by the value of a second custom field. <?php // List all posts with custom field Color, sorted by the value of custom field Display_Order // does not exclude any 'post_type' // assumes each post has just one custom field for Color, and one for Display_Order $meta_key1 = 'Color'; $meta_key2 = 'Display_Order'; $postids = $wpdb->get_col( $wpdb->prepare( " SELECT key1.post_id FROM $wpdb->postmeta key1 INNER JOIN $wpdb->postmeta key2 ON key2.post_id = key1.post_id AND key2.meta_key = %s WHERE key1.meta_key = %s ORDER BY key2.meta_value+(0) ASC ", $meta_key2, $meta_key1 ) ); if ( $postids ) { echo "List of {$meta_key1} posts, sorted by {$meta_key2}"; foreach ( $postids as $id ) { $post = get_post( intval( $id ) ); setup_postdata( $post ); ?> <p> <a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link to <?php the_title_attribute(); ?>"> <?php the_title(); ?> </a> </p> <?php } } ?> SELECT Generic Results Generic, mulitple row results can be pulled from the database with get_results. The function returns the entire query result as an array, or NULL on no result. Each element of this array corresponds to one row of the query result and, like get_row, can be an object, an associative array, or a numbered array. <?php $wpdb->get_results('query', output_type); ?> query (string) The query you wish to run. Setting this parameter to null will return the data from the cached results of the previous query. output_type One of four pre-defined constants. Defaults to OBJECT. See SELECT a Row and its examples for more information. ¦OBJECT - result will be output as a numerically indexed array of row objects. ¦OBJECT_K - result will be output as an associative array of row objects, using first column's values as keys (duplicates will be discarded). ¦ARRAY_A - result will be output as an numerically indexed array of associative arrays, using column names as keys. ¦ARRAY_N - result will be output as a numerically indexed array of numerically indexed arrays. Since this function uses the '$wpdb->query()' function all the class variables are properly set. The results count for a 'SELECT' query will be stored in $wpdb->num_rows. Examples Get the IDs and Titles of all the Drafts by User 5 and echo the Titles. $fivesdrafts = $wpdb->get_results( " SELECT ID, post_title FROM $wpdb->posts WHERE post_status = 'draft' AND post_author = 5 " ); foreach ( $fivesdrafts as $fivesdraft ) { echo $fivesdraft->post_title; } Get all information on the Drafts by User 5. <?php $fivesdrafts = $wpdb->get_results( " SELECT * FROM $wpdb->posts WHERE post_status = 'draft' AND post_author = 5 " ); if ( $fivesdrafts ) { foreach ( $fivesdrafts as $post ) { setup_postdata( $post ); ?> <h2> <a href="<?php the_permalink(); ?>" rel="bookmark" title="Permalink: <?php the_title(); ?>"> <?php the_title(); ?> </a> </h2> <?php } else { ?> <h2>Not Found</h2> <?php } } ?> INSERT rows Insert a row into a table. <?php $wpdb->insert( $table, $data, $format ); ?> table (string) The name of the table to insert data into. data (array) Data to insert (in column => value pairs). Both $data columns and $data values should be "raw" (neither should be SQL escaped). format (array|string) (optional) An array of formats to be mapped to each of the value in $data. If string, that format will be used for all of the values in $data. If omitted, all values in $data will be treated as strings unless otherwise specified in wpdb::$field_types. Possible format values: %s as string; %d as decimal number; and %f as float. After insert, the ID generated for the AUTO_INCREMENT column can be accessed with: $wpdb->insert_idThis function returns false if the row could not be inserted. Examples Insert two columns in a row, the first value being a string and the second a number: $wpdb->insert( 'table', array( 'column1' => 'value1', 'column2' => 123 ), array( '%s', '%d' ) ); UPDATE rows Update a row in the table. Returns false if errors, or the number of rows affected if successful. <?php $wpdb->update( $table, $data, $where, $format = null, $where_format = null ); ?> table (string) The name of the table to update. data (array) Data to update (in column => value pairs). Both $data columns and $data values should be "raw" (neither should be SQL escaped). where (array) A named array of WHERE clauses (in column => value pairs). Multiple clauses will be joined with ANDs. Both $where columns and $where values should be "raw". format (array|string) (optional) An array of formats to be mapped to each of the values in $data. If string, that format will be used for all of the values in $data. where_format (array|string) (optional) An array of formats to be mapped to each of the values in $where. If string, that format will be used for all of the items in $where. Possible format values: %s as string; %d as decimal number and %f as float. If omitted, all values in $where will be treated as strings. This function returns the number of rows updated, or false if there is an error. Examples Update a row, where the ID is 1, the value in the first column is a string and the value in the second column is a number: $wpdb->update( 'table', array( 'column1' => 'value1', // string 'column2' => 'value2' // integer (number) ), array( 'ID' => 1 ), array( '%s', // value1 '%d' // value2 ), array( '%d' ) ); Attention: %d can't deal with comma values - if you're not using full numbers, use string/%s. Protect Queries Against SQL Injection Attacks For a more complete overview of SQL escaping in WordPress, see database Data Validation. That Data Validation article is a must-read for all WordPress code contributors and plugin authors. Briefly, though, all data in SQL queries must be SQL-escaped before the SQL query is executed to prevent against SQL injection attacks. This can be conveniently done with the prepare method, which supports both a sprintf()-like and vsprintf()-like syntax. Please note: As of 3.5, wpdb::prepare() enforces a minimum of 2 arguments. [more info] <?php $sql = $wpdb->prepare( 'query' , value_parameter[, value_parameter ... ] ); ?> query (string) The SQL query you wish to execute, with %s and %d placeholders. Any other % characters may cause parsing errors unless they are escaped. All % characters inside SQL string literals, including LIKE wildcards, must be double-% escaped as %%. value_parameter (int|string|array) The value to substitute into the placeholder. Many values may be passed by simply passing more arguments in a sprintf()-like fashion. Alternatively the second argument can be an array containing the values as in PHP's vsprintf() function. Care must be taken not to allow direct user input to this parameter, which would enable array manipulation of any query with multiple placeholders. Values must not already be SQL-escaped. Examples Add Meta key => value pair "Harriet's Adages" => "WordPress' database interface is like Sunday Morning: Easy." to Post 10. $metakey = "Harriet's Adages"; $metavalue = "WordPress' database interface is like Sunday Morning: Easy."; $wpdb->query( $wpdb->prepare( " INSERT INTO $wpdb->postmeta ( post_id, meta_key, meta_value ) VALUES ( %d, %s, %s ) ", 10, $metakey, $metavalue ) ); Performed in WordPress by add_meta(). <end node> 5P9i0s8y19Z dt= <node>plugin 1 [admin plugin] <?php ./* Plugin Name: swd_admin Description: A test plugin to demonstrate wordpress functionality Author: SWD Version: 0.1 */ add_action('admin_menu', 'test_plugin_setup_menu'); function test_plugin_setup_menu(){ add_menu_page( 'Test Plugin Page', 'Test Plugin', 'manage_options', 'test-plugin', 'swd_menu' ); } function swd_menu(){ echo "<h1>Hello World!</h1>"; } ?> You may think that it may be super hard, but it really is not.
All you have to do is create a new folder in the plugins directory. Example: /wp-content/plugins/yoursitename-plugin/ Open a blank file and save it as “yoursitename-plugin.php” Put the following code in the file: <?php /* Plugin Name: Site Plugin for example.com Description: Site specific code changes for example.com */ /* Start Adding Functions Below this Line */
// this is widget code /* Stop Adding Functions Below this Line */ ?> Now upload this file into the folder you created in the plugins directory. Then simply activate the plugin. <end node> 5P9i0s8y19Z dt= <node>backupWordpress 2 [Resolved] 3.4.3 update getting incorrect root directory Adding define( 'HMBKP_ROOT', dirname( __FILE__ )); to wp-config.php seems to fix the issue for me, thanks. <end node> 5P9i0s8y19Z dt= <node>Contact form 2 http://www.sitepoint.com/build-your-own-wordpress-contact-form-plugin-in-5-minutes/ short codes <HEADER> <H1>Build Your Own WordPress Contact Form Plugin in 5 Minutes</H1> <DIV> <FIGURE> <A href="http://www.sitepoint.com/author/acollins/"> <IMG src="http://1.gravatar.com/avatar/75eb5abf4f342e434c23fb0216631d3e?s=96&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D96&r=G"> </A> </FIGURE> <DIV> <DIV> <A href="http://www.sitepoint.com/author/acollins/">Agbonghama Collins</A> </DIV> </DIV> </DIV> <DIV> <P>Published <time>July 23, 2014</time> </P> </DIV> <DIV> <!-- make sure to update trackTweetsAndSubscriptions in scripts.js if the Tweet button DOM path changes in the future --> <A href="https://twitter.com/share?text=Build+Your+Own+WordPress+Contact+Form+Plugin+in+5+Minutes&via=sitepointdotcom"> <I> </I> Tweet </A> <!-- make sure to update trackTweetsAndSubscriptions in scripts.js if the Subscribe button DOM path changes in the future --> <A href="https://confirmsubscription.com/h/y/1FD5B523FA48AA2B"> <!--<i> </i>--> Subscribe </A> </DIV> </HEADER> <SECTION> <P>Most websites are typically designed to comply with standard web practices by including a dedicated page where a contact form is located. This provides visitors with an easy way to reach out to the site owner.</P> <P>In simple terms, a contact form has a set of questions and fields which are filled in by a visitor. The information is usually automatically sent via email to the site administrator or another nominated email account. It is worth noting that this email address isn’t displayed to visitors, so using a contact form typically reduces email spam from bots that harvest naked email addresses on the Internet. Contact forms play a very important role on a website, where they are used for collecting feedback, enquiries and other data from users.</P> <P>If your website is powered by WordPress, there are numerous plugins that seamlessly integrate a <STRONG>contact form</STRONG> on your website.</P> <P>In this article, I will provide a list of some free WordPress contact form plugins. I will also discuss why you should consider rolling your own contact form. Then, I will provide you with a short tutorial showing you how to build your own WordPress contact form plugin.</P> <H2>WordPress Contact Form Plugins</H2> <P>Before we get started, we’re going to go over a few of the popular free contact form plugins available in the <A href="https://wordpress.org/plugins/">WordPress Plugin Directory</A>. These are great to use, but even better to learn from when you’re getting started building your own plugins.</P> <P>Below are some of the most highly rated free contact form plugins for WordPress:</P> <OL> <LI> <P> <A href="http://wordpress.org/plugins/contact-form-7/">Contact Form 7</A> – This is the second <A href="http://wordpress.org/plugins/browse/popular/">most popular plugin</A> with over 18 million downloads, it could almost be considered as the de facto contact form plugin for a WordPress website. Contact Form 7 can manage multiple contact forms and you can customize the form and the email contents with simple markup. The form features include Ajax-powered submission, CAPTCHA, Akismet spam filtering and lots more.</P> </LI> <LI> <P> <A href="https://wordpress.org/plugins/contact-form-to-email/">Contact Form to Email</A> – This plugin not only creates contact forms and sends the data to a specified email address it also saves the contact form data into a database, providing printable reports and the option to export the selected data to CSV/Excel file.</P> </LI> <LI> <P> <A href="http://wordpress.org/plugins/formget-contact-form/">FormGet Contact Form</A> – An easy online drag and drop contact form builder tool. All you need to do is click on the fields that you want in your form, and within few seconds your contact form is ready.</P> </LI> <LI> <P> <A href="http://wordpress.org/plugins/contact-form-plugin/">Bestwebsoft Contact Form</A> – Allows you to implement a feedback form to a web page or a post effortlessly. It is extremely easy, and you won’t require any additional settings, even though there are some available to play with.</P> </LI> </OL> <H2>Why Roll Your Own Contact Form Plugin?</H2> <H3>Becoming a Better Developer</H3> <P>Developing your own WordPress plugin helps you better understand how WordPress works ‘under the hood’ which can help you to become a more experienced web developer. While there are tens of thousands of plugins in the WordPress Plugin Directory to use, being able to modify and extend other plugins is a very useful skill.</P> <H3>Building a Better Form</H3> <P>Many WordPress contact form plugins are bloated. They include many features that you may never use. Heavy usage of JavaScript and CSS files are also common in some of the standard contact form plugins. This increases the number of HTTP requests which adversely affects WordPress performance.</P> <P>According to <A href="http://developer.yahoo.com/performance/rules.html#num_http">Yahoo’s performance rules</A>:</P> <BLOCKQUOTE> <P>80% of the end-user response time is spent on the front-end. Most of this time is tied up in downloading all the components in the page: images, stylesheets, scripts, Flash, etc. Reducing the number of components in turn reduces the number of HTTP requests required to render the page. This is the key to faster pages.</P> </BLOCKQUOTE> <P>If you are like me, and you desire a simple contact form plugin that just works, read on. I’ll guide you through the simple process of develop your own plugin so you can kiss goodbye bloated plugins. In this example no extra CSS and JavaScript files are required, the <A href="http://www.sitepoint.com/client-side-form-validation-html5/">validation done using HTML5</A>.</P> <H2>Contact Form Plugin Development</H2> <P>In five minutes, you will learn how to develop a simple WordPress contact form, that’s a promise!</P> <P>Ready? Set? Go!</P> <P>All WordPress pluigns are PHP files, located in the <CODE>/wp-content/plugins/ directory</CODE>. In our example, the file will be called <CODE>sp-form-example.php</CODE>. I assume you’re comfortable with connecting to your server using FTP/SFTP/SCP or SSH.</P> <P>If you want to follow along, simply create a file called <CODE>sp-form-example.php</CODE> (the final complete example will be available at the end of the article):</P> <DIV> <DIV> <TABLE> <TBODY> <TR> <TD> <DIV>1</DIV> <DIV>2</DIV> <DIV>3</DIV> <DIV>4</DIV> <DIV>5</DIV> <DIV>6</DIV> <DIV>7</DIV> <DIV>8</DIV> <DIV>9</DIV> <DIV>10</DIV> <DIV>11</DIV> <DIV>12</DIV> <DIV>13</DIV> </TD> <TD> <DIV> <DIV> <CODE class="php plain"><?php</CODE> </DIV> <DIV> <CODE class="php comments">/*</CODE> </DIV> <DIV> <CODE class="php comments">Plugin Name: Example Contact Form Plugin</CODE> </DIV> <DIV> <CODE class="php comments">Plugin URI: <A href="http://example.com/">http://example.com</A> </CODE> </DIV> <DIV> <CODE class="php comments">Description: Simple non-bloated WordPress Contact Form</CODE> </DIV> <DIV> <CODE class="php comments">Version: 1.0</CODE> </DIV> <DIV> <CODE class="php comments">Author: Agbonghama Collins</CODE> </DIV> <DIV> <CODE class="php comments">Author URI: <A href="http://w3guy.com/">http://w3guy.com</A> </CODE> </DIV> <DIV> <CODE class="php comments">*/</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">//</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">// the plugin code will go here..</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">//</CODE> </DIV> <DIV> <CODE class="php plain">?></CODE> </DIV> </DIV> </TD> </TR> </TBODY> </TABLE> </DIV> </DIV> <P>Next, we add the function <CODE>html_form_code()</CODE> that contains the contact form HTML:</P> <DIV> <DIV> <TABLE> <TBODY> <TR> <TD> <DIV>1</DIV> <DIV>2</DIV> <DIV>3</DIV> <DIV>4</DIV> <DIV>5</DIV> <DIV>6</DIV> <DIV>7</DIV> <DIV>8</DIV> <DIV>9</DIV> <DIV>10</DIV> <DIV>11</DIV> <DIV>12</DIV> <DIV>13</DIV> <DIV>14</DIV> <DIV>15</DIV> <DIV>16</DIV> <DIV>17</DIV> <DIV>18</DIV> <DIV>19</DIV> <DIV>20</DIV> <DIV>21</DIV> </TD> <TD> <DIV> <DIV> <CODE class="php keyword">function</CODE> <CODE class="php plain">html_form_code() {</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<form action="'</CODE> <CODE class="php plain">. esc_url( </CODE> <CODE class="php variable">$_SERVER</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">'REQUEST_URI'</CODE> <CODE class="php plain">] ) . </CODE> <CODE class="php string">'" method="post">'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'Your Name (required) <br />'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<input type="text" name="cf-name" pattern="[a-zA-Z0-9 ]+" value="'</CODE> <CODE class="php plain">. ( isset( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">["cf-name</CODE> <CODE class="php string">"] ) ? esc_attr( $_POST["</CODE> <CODE class="php plain">cf-name</CODE> <CODE class="php string">"] ) : '' ) . '"</CODE> <CODE class="php plain">size=</CODE> <CODE class="php string">"40"</CODE> <CODE class="php plain">/>';</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'Your Email (required) <br />'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<input type="email" name="cf-email" value="'</CODE> <CODE class="php plain">. ( isset( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">["cf-email</CODE> <CODE class="php string">"] ) ? esc_attr( $_POST["</CODE> <CODE class="php plain">cf-email</CODE> <CODE class="php string">"] ) : '' ) . '"</CODE> <CODE class="php plain">size=</CODE> <CODE class="php string">"40"</CODE> <CODE class="php plain">/>';</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'Subject (required) <br />'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<input type="text" name="cf-subject" pattern="[a-zA-Z ]+" value="'</CODE> <CODE class="php plain">. ( isset( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">["cf-subject</CODE> <CODE class="php string">"] ) ? esc_attr( $_POST["</CODE> <CODE class="php plain">cf-subject</CODE> <CODE class="php string">"] ) : '' ) . '"</CODE> <CODE class="php plain">size=</CODE> <CODE class="php string">"40"</CODE> <CODE class="php plain">/>';</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'Your Message (required) <br />'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<textarea rows="10" cols="35" name="cf-message">'</CODE> <CODE class="php plain">. ( isset( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-message"</CODE> <CODE class="php plain">] ) ? esc_attr( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-message"</CODE> <CODE class="php plain">] ) : </CODE> <CODE class="php string">''</CODE> <CODE class="php plain">) . </CODE> <CODE class="php string">'</textarea>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p><input type="submit" name="cf-submitted" value="Send"/></p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</form>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php plain">}</CODE> </DIV> </DIV> </TD> </TR> </TBODY> </TABLE> </DIV> </DIV> <P>Basic validation was added to the form via the <CODE>pattern</CODE> input attribute.</P> <P>The RegEX in the contact form does the following field validation:</P> <UL> <LI> <P> <STRONG>[a-zA-Z0-9 ]</STRONG>: only letters, spaces and numbers allowed in the name field; special symbols are deemed invalid.</P> </LI> <LI> <P> <STRONG>[a-zA-Z ]</STRONG>: only letters and spaces are allowed in the subject field.</P> </LI> <LI> <P>The <CODE>email</CODE> form control validates the email field hence there is no need for a pattern attribute.</P> </LI> </UL> <P>For more information on how this works, read my article on <A href="http://www.sitepoint.com/client-side-form-validation-html5/">Client-Side Form Validation with HTML5</A> to understand how the pattern attribute assists with form validation.</P> <H3>Hurry Up!</H3> <P>Okay, how many minutes do we have left? Four minutes! We still have time to get this over with.</P> <P>The function <CODE>deliver_mail()</CODE> sanitizes the form data and sends the mail to the WordPress administrator’s email address.</P> <DIV> <DIV> <TABLE> <TBODY> <TR> <TD> <DIV>1</DIV> <DIV>2</DIV> <DIV>3</DIV> <DIV>4</DIV> <DIV>5</DIV> <DIV>6</DIV> <DIV>7</DIV> <DIV>8</DIV> <DIV>9</DIV> <DIV>10</DIV> <DIV>11</DIV> <DIV>12</DIV> <DIV>13</DIV> <DIV>14</DIV> <DIV>15</DIV> <DIV>16</DIV> <DIV>17</DIV> <DIV>18</DIV> <DIV>19</DIV> <DIV>20</DIV> <DIV>21</DIV> <DIV>22</DIV> <DIV>23</DIV> <DIV>24</DIV> <DIV>25</DIV> <DIV>26</DIV> </TD> <TD> <DIV> <DIV> <CODE class="php keyword">function</CODE> <CODE class="php plain">deliver_mail() {</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">// if the submit button is clicked, send the email</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php keyword">if</CODE> <CODE class="php plain">( isset( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">'cf-submitted'</CODE> <CODE class="php plain">] ) ) {</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">// sanitize form values</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$name</CODE> <CODE class="php plain">= sanitize_text_field( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-name"</CODE> <CODE class="php plain">] );</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$email</CODE> <CODE class="php plain">= sanitize_email( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-email"</CODE> <CODE class="php plain">] );</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$subject</CODE> <CODE class="php plain">= sanitize_text_field( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-subject"</CODE> <CODE class="php plain">] );</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$message</CODE> <CODE class="php plain">= esc_textarea( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-message"</CODE> <CODE class="php plain">] );</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">// get the blog administrator's email address</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$to</CODE> <CODE class="php plain">= get_option( </CODE> <CODE class="php string">'admin_email'</CODE> <CODE class="php plain">);</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$headers</CODE> <CODE class="php plain">= </CODE> <CODE class="php string">"From: $name <$email>"</CODE> <CODE class="php plain">. </CODE> <CODE class="php string">"\\r\\n"</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">// If email has been process for sending, display a success message</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php keyword">if</CODE> <CODE class="php plain">( wp_mail( </CODE> <CODE class="php variable">$to</CODE> <CODE class="php plain">, </CODE> <CODE class="php variable">$subject</CODE> <CODE class="php plain">, </CODE> <CODE class="php variable">$message</CODE> <CODE class="php plain">, </CODE> <CODE class="php variable">$headers</CODE> <CODE class="php plain">) ) {</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<div>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p>Thanks for contacting me, expect a response soon.</p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</div>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">} </CODE> <CODE class="php keyword">else</CODE> <CODE class="php plain">{</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'An unexpected error occurred'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">}</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">}</CODE> </DIV> <DIV> <CODE class="php plain">}</CODE> </DIV> </DIV> </TD> </TR> </TBODY> </TABLE> </DIV> </DIV> <P>The sanitation of the form data is done by the following WordPress internal functions:</P> <UL> <LI> <P> <CODE>sanitize_text_field()</CODE>: Sanitize the data from user input.</P> </LI> <LI> <P> <CODE>sanitize_email()</CODE>: Strips out all characters that are not allowable in an email.</P> </LI> <LI> <P> <CODE>esc_textarea()</CODE>: Escape the <EM>message</EM> text area values.</P> </LI> </UL> <P>The code <CODE>get_option( 'admin_email' )</CODE> programmatically retrieves the WordPress administrator’s email address from the database where the email will be delivered to.</P> <P>Don’t want the contact form to send the mail to admin? Simply set the variable <CODE>$to</CODE> to the desired email address.</P> <P>If the email has successfully been processed without any errors by the function <CODE>wp_mail()</CODE> , the text <EM>Thanks for contacting me, expect a response soon</EM> will be shown, otherwise <EM>An unexpected error occurred</EM> is displayed.</P> <H3>1 Minute and 30 Seconds Left</H3> <P>The function <CODE>cf_shortcode()</CODE> is the callback function that is called when the contact form shortcode <CODE>[sitepoint_contact_form]</CODE> is active.</P> <DIV> <DIV> <TABLE> <TBODY> <TR> <TD> <DIV>1</DIV> <DIV>2</DIV> <DIV>3</DIV> <DIV>4</DIV> <DIV>5</DIV> <DIV>6</DIV> <DIV>7</DIV> </TD> <TD> <DIV> <DIV> <CODE class="php keyword">function</CODE> <CODE class="php plain">cf_shortcode() {</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">ob_start();</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">deliver_mail();</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">html_form_code();</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php keyword">return</CODE> <CODE class="php plain">ob_get_clean();</CODE> </DIV> <DIV> <CODE class="php plain">}</CODE> </DIV> </DIV> </TD> </TR> </TBODY> </TABLE> </DIV> </DIV> <P>The above functions calls the <CODE>html_form_code()</CODE> and <CODE>deliver_mail()</CODE> functions to display the contact form HTML form and validate the form data respectively.</P> <P>Finally, the shortcode <CODE>[sitepoint_contact_form]</CODE> is registered to WordPress. So simply add:</P> <DIV> <DIV> <TABLE> <TBODY> <TR> <TD> <DIV>1</DIV> </TD> <TD> <DIV> <DIV> <CODE class="php plain">add_shortcode( </CODE> <CODE class="php string">'sitepoint_contact_form'</CODE> <CODE class="php plain">, </CODE> <CODE class="php string">'cf_shortcode'</CODE> <CODE class="php plain">);</CODE> </DIV> </DIV> </TD> </TR> </TBODY> </TABLE> </DIV> </DIV> <H3>3, 2, 1… Time’s Up!</H3> <P>Congratulations, we have successfully developed our own WordPress contact form plugin and I have fulfilled my earlier promise.</P> <P>Now, to use this plugin on your website, simply activate it in under the ‘Plugins’ section of your WordPress dashboard, then create a post or page and then simply add the shortcode where you want the form to appear <CODE>[sitepoint_contact_form]</CODE>.</P> <P>If you then preview the page and you should see the contact form displayed as shown below.</P> </SECTION> <end node> 5P9i0s8y19Z dt= <node>shortcodes 2 <?php /* * Plugin Name: WordPress ShortCode * Description: Create your WordPress shortcode. * Version: 1.0 * Author: InkThemes * Author URI: https://inkthemes.com */ // Example 1 : WP Shortcode to display form on any page or post. function form_creation(){ $imagedirectory="../stylists/"; $dir = opendir($imagedirectory); while ($file = readdir($dir)){ //for ($i=1; $i<=500; $i++){ // $file = readdir($dir); $fullpath=$current_dir.$file; $fullpath2=$current_dir."/stylists/large/".$file; /* $filedate=date('Y-m-j', filemtime($fullpath)); if(trim($file)!='.' && trim($file)!='..'){ $fsize=filesize($fullpath)/1000; $fsize=(int)$fsize;$fsize=$fsize/1000; $message[]=$filedate."|".$file."@".$fsize; } */ echo "<div style='float:left;padding:20px;'><a href='$fullpath2'><img src='$fullpath'><br>$file</a></div>"; } closedir($dir); } add_shortcode('test', 'form_creation'); ?> [test] in whatever page you want <end node> 5P9i0s8y19Z dt= <node>WIDGET 1 <?php /** * Plugin Name: A simple Widget * Description: A widget that displays authors name. * Version: 0.1 * Author: Bilal Shaheen * Author URI: http://gearaffiti.com/about */ add_action( 'widgets_init', 'my_widget' ); function my_widget() { register_widget( 'SWDWidget' ); } class SWDWidget extends WP_Widget { function SWDWidget() { $widget_ops = array( 'classname' => 'example', 'description' => __('A widget that displays SWD garbage ', 'example') );
function widget( $args, $instance ) { extract( $args ); //Our variables from the widget settings. $title = apply_filters('widget_title', $instance['title'] ); $name = $instance['name']; $show_info = isset( $instance['show_info'] ) ? $instance['show_info'] : false; echo $before_widget; // Display the widget title if ( $title ) echo $before_title . $title . $after_title; //Display the name on website if ( $name ) printf( '<p>' . __('Hey their Sailor! My name is %1$s.', 'example1') . '</p>', $name );
if ( $show_info ) printf( $name );
echo $after_widget; } //Update the widget
function update( $new_instance, $old_instance ) { $instance = $old_instance; //Strip tags from title and name to remove HTML $instance['title'] = strip_tags( $new_instance['title'] ); $instance['name'] = strip_tags( $new_instance['name'] ); $instance['show_info'] = $new_instance['show_info']; return $instance; }
//Checkbox. <p> <input class="checkbox" type="checkbox" <?php checked( $instance['show_info'], true ); ?> id="<?php echo $this->get_field_id( 'show_info' ); ?>" name="<?php echo $this->get_field_name( 'show_info' ); ?>" /> <label for="<?php echo $this->get_field_id( 'show_info' ); ?>"><?php _e('Display info publicly?', 'example'); ?></label> </p> <?php } } ?> <end node> 5P9i0s8y19Z dt= <node>example 2 [code] Before we get started, it would be best if you create a site-specific plugin where you will be pasting widget code. You can also paste it in your theme’s functions.php file but a site-specific plugin is better. In this tutorial, we will create a simple widget that just greets visitors. Take a look at this code and then paste it in your site-specific plugin to see it in action. 01 // Creating the widget 02 class wpb_widget extends WP_Widget { 03 04 function __construct() { 05 parent::__construct( 06 // Base ID of your widget 07 'wpb_widget', 08 09 // Widget name will appear in UI 10 __('WPBeginner Widget', 'wpb_widget_domain'), 11 12 // Widget description 13 array( 'description' => __( 'Sample widget based on WPBeginner Tutorial', 'wpb_widget_domain' ), ) 14 ); 15 } 16 17 // Creating widget front-end 18 // This is where the action happens 19 public function widget( $args, $instance ) { 20 $title = apply_filters( 'widget_title', $instance['title'] ); 21 // before and after widget arguments are defined by themes 22 echo $args['before_widget']; 23 if ( ! empty( $title ) ) 24 echo $args['before_title'] . $title . $args['after_title']; 25 26 // This is where you run the code and display the output 27 echo __( 'Hello, World!', 'wpb_widget_domain' ); 28 echo $args['after_widget']; 29 } 30 31 // Widget Backend 32 public function form( $instance ) { 33 if ( isset( $instance[ 'title' ] ) ) { 34 $title = $instance[ 'title' ]; 35 } 36 else { 37 $title = __( 'New title', 'wpb_widget_domain' ); 38 } 39 // Widget admin form 40 ?> 41 <p> 42 <label for="<?php echo $this->get_field_id( 'title' ); ?>"><?php _e( 'Title:' ); ?></label> 43 <input class="widefat" id="<?php echo $this->get_field_id( 'title' ); ?>" name="<?php echo $this->get_field_name( 'title' ); ?>" type="text" value="<?php echo esc_attr( $title ); ?>" /> 44 </p> 45 <?php 46 } 47 48 // Updating widget replacing old instances with new 49 public function update( $new_instance, $old_instance ) { 50 $instance = array(); 51 $instance['title'] = ( ! empty( $new_instance['title'] ) ) ? strip_tags( $new_instance['title'] ) : ''; 52 return $instance; 53 } 54 } // Class wpb_widget ends here 55 56 // Register and load the widget 57 function wpb_load_widget() { 58 register_widget( 'wpb_widget' ); 59 } 60 add_action( 'widgets_init', 'wpb_load_widget' ); Now go to Appearance » Widgets, drag and drop WPBeginner Widget in your sidebar to see this custom widget in action. Simple wasn’t it? First we created a custom widget. Then we defined what that widget does and how to display the widget back-end. Then we defined how to handle changes made to widget. Lastly, we registered and loaded the widget. Now there are a few things that you might want to ask. For example, what wpb_text_domain does? WordPress uses gettext to handle translation and localization. This wpb_text_domain and __e tells gettext to make a string available for translation. See how you can find translation ready WordPress themes. We hope this tutorial helped you learn how to create a custom WordPress widget. Let us know what widgets you are creating, by leaving a comment below. ===================================== // used on the windsor hair shoppe <?php /* Plugin Name: Social Media Icons Plugin URI: http://softwarewebdesign.com Description: Adds Icons. Version: 1.0 Author: Software Web Design Author URI: http://softwarewebdesign.com License: GPL2 */ class WP_Widget_SocialMedia extends WP_Widget {
// The widget construct. Mumbo-jumbo that loads our code. function WP_Widget_SocialMedia() { $widget_ops = array( 'classname' => 'widget_SocialMedia', 'description' => __( "Social Media Icons" ) ); $this->WP_Widget('SocialMedia', __('SocialMedia'), $widget_ops); } // End function WP_Widget_SocialMedia
// This code displays the widget on the screen. function widget($args, $instance) { extract($args); echo $before_widget; if(!empty($instance['title'])) { echo $before_title . $instance['title'] . $after_title; } echo "<p><a href='http://www.facebook.com/pages/Windsor-Hair-Shoppe/469480233075402'><img src='".site_url()."/images/facebook.jpg'></a></p>"; echo $after_widget; } // End function widget.
// Updates the settings. function update($new_instance, $old_instance) { return $new_instance; } // End function update // The admin form. function form($instance) { echo '<div id="bareBones-admin-panel">'; echo '<label for="' . $this->get_field_id("title") .'">Social Media Title:</label>'; echo '<input type="text" class="widefat" '; echo 'name="' . $this->get_field_name("title") . '" '; echo 'id="' . $this->get_field_id("title") . '" '; echo 'value="' . $instance["title"] . '" />'; echo '<p>This widget will display Social Media Icons below.</p>'; echo '</div>'; } // end function form
$options = get_option('simple_widget'); if ( !isset($options[$number]) ) return; $title = $options[$number]['title']; // single value $text = $options[$number]['text']; // single value $check = $options[$number]['check']; // multi value $radio = $options[$number]['radio']; // single value $select = $options[$number]['select']; // single value $textarea = $options[$number]['textarea']; // single value echo $before_widget; // start widget display code */ ?>
<?php echo "LINE 1"; // end widget display code
}
function jad_simple_widget_control($widget_args) { global $wp_registered_widgets; static $updated = false; /* if ( is_numeric($widget_args) ) $widget_args = array( 'number' => $widget_args ); $widget_args = wp_parse_args( $widget_args, array( 'number' => -1 ) ); extract( $widget_args, EXTR_SKIP ); $options = get_option('simple_widget'); if ( !is_array($options) ) $options = array(); if ( !$updated && !empty($_POST['sidebar']) ) { $sidebar = (string) $_POST['sidebar']; $sidebars_widgets = wp_get_sidebars_widgets(); if ( isset($sidebars_widgets[$sidebar]) ) $this_sidebar =& $sidebars_widgets[$sidebar]; else $this_sidebar = array(); foreach ( (array) $this_sidebar as $_widget_id ) { if ( 'jad_simple_widget' == $wp_registered_widgets[$_widget_id]['callback'] && isset($wp_registered_widgets[$_widget_id]['params'][0]['number']) ) { $widget_number = $wp_registered_widgets[$_widget_id]['params'][0]['number']; if ( !in_array( "simple-widget-$widget_number", $_POST['widget-id'] ) ) // the widget has been removed. unset($options[$widget_number]); } } foreach ( (array) $_POST['simple-widget'] as $widget_number => $simple_widget ) { if ( !isset($simple_widget['title']) && isset($options[$widget_number]) ) // user clicked cancel continue; $title = strip_tags(stripslashes($simple_widget['title'])); $text = strip_tags(stripslashes($simple_widget['text_value'])); $check = $simple_widget['check_array']; $radio = $simple_widget['radio_value']; $select = $simple_widget['select_value']; $textarea = $simple_widget['textarea_value']; // Pact the values into an array $options[$widget_number] = compact( 'title', 'text', 'check', 'radio', 'select', 'textarea' ); } update_option('simple_widget', $options); $updated = true; } if ( -1 == $number ) { // if it's the first time and there are no existing values $title = ''; $text = ''; $check = ''; $radio = ''; $select = ''; $textarea = ''; $number = '%i%'; } else { // otherwise get the existing values $title = attribute_escape($options[$number]['title']); $text = attribute_escape($options[$number]['text']); // attribute_escape used for security $check = $options[$number]['check']; $radio = $options[$number]['radio']; $select = $options[$number]['select']; $textarea = format_to_edit($options[$number]['textarea']); } print_r($options[$number]); */ ECHO "lINE2"; }
$options = get_option('simple_widget'); if ( !isset($options[$number]) ) return; $title = $options[$number]['title']; // single value $text = $options[$number]['text']; // single value $check = $options[$number]['check']; // multi value $radio = $options[$number]['radio']; // single value $select = $options[$number]['select']; // single value $textarea = $options[$number]['textarea']; // single value
if ( !$id ) { wp_register_sidebar_widget( 'simple-widget-1', $name, 'jad_simple_widget', $widget_ops, array( 'number' => -1 ) ); wp_register_widget_control( 'simple-widget-1', $name, 'jad_simple_widget_control', $control_ops, array( 'number' => -1 ) ); } } add_action('init', jad_simple_widget_register, 1); ?> <end node> 5P9i0s8y19Z dt= <node>new area 2 http://howtomatter.com/how-to-create-a-new-widget-area/ I’ve found it helpful in certain situations to have widgetized areas (that is, places I can drag/drop widgets into from the Appearance>Widget menu) other than the standard Sidebar 1 and Sidebar 2. Certain themes have this built in, but it’s not terribly difficult to create them yourself, so I thought I’d write up a quick tutorial. What is a new widget area? As always, head on over to my test site to see an example of what I’m talking about. Scroll down to the footer and you’ll see a light red area with 2 boxes in it that say something along the lines of ‘this is your new sidebar’. In case that site/example is gone by the time you’re reading this, here’s a picture of it. New Sidebar for Widgets click to enlarge So what I’ve done is created 2 new sidebar areas and placed them, in this case, after the content box. Widgets can be dragged into these sidebars in the same way as you’d add widgets to the default sidebars – by going to the Appearance>Widgets menu and dragging them into the appropriate place. More about that in a minute. How to create a new widget area Per my typical approach, I’m just going to give you the code, and the instructions on where/how to place it, and if you have questions beyond this or want to know more about how/why it works, you can leave a comment or reach out to me individually…cool? Okay, so the first thing we need to do is register the new sidebars. This is done by going to the Thesis>Custom File Editor menu, and from the drop down menu at the top of that page, choose ‘custom_functions.php’ and click the ‘edit selected file’ button to its right. Once there, scroll down to the very bottom and paste the following code: /**************************************************************** * REGISTER NEW SIDEBARS ****************************************************************/ $args = array( 'name' => 'New Sidebar %d', 'before_widget' => '<li id="%1$s" class="widget %2$s">', 'after_widget' => '</li>', 'before_title' => '<h3>', 'after_title' => '</h3>' ); register_sidebars( 2, $args ); /**************************************************************** * CREATES NEW SIDEBARS ****************************************************************/ function new_sidebars(){ ?> <div id="new-sidebars"> <div id="new-sidebar-1"> <ul class="sidebar_list"> <?php if (!dynamic_sidebar('New Sidebar 1') ) { ?> <li class="widget"> <div class="widget_box"> <h3><?php _e('New Sidebar 1', 'thesis'); ?></h3> <p>This is your new sidebar. Add widgets here from your WP Dashboard just like normal.</p> </div> </li> <?php } ?> </ul> </div> <div id="new-sidebar-2"> <ul class="sidebar_list"> <?php if (!dynamic_sidebar('New Sidebar 2') ) { ?> <li class="widget"> <div class="widget_box"> <h3><?php _e('New Sidebar 2', 'thesis'); ?></h3> <p>This is your new sidebar. Add widgets here from your WP Dashboard just like normal.</p> </div> </li> <?php } ?> </ul> </div> </div> <?php } add_action('thesis_hook_after_content_box', 'new_sidebars'); So what that has done is created 2 new sidebars and placed them at the bottom of your content box…well, after it, actually. If you were to look at your site now, you’d see them placed one on top of the other…not what we want in this case, but we’ll remedy that with a little CSS styling. Styling your newly created sidebars Now that these widgetized sidebars are created, we need to style them to look how we want them to look. So, go to the Thesis>Custom File Editor menu, and make sure it says ‘custom.css’ in the drop down menu. Scroll down to the bottom (or to the appropriate place if you’ve got this file organized) and paste the following code: /*********************************** NEW WIDGET STYLING ***********************************/ #new-sidebars { float:left; width:100%; background-color:#ffaaaa; border-bottom:.1em solid #000000; } #new-sidebar-1 { float:left; margin-left:7em; width:40%; } #new-sidebar-2 { float:left; margin-left:2em; width:40%; } If everything was done properly, you should now have two sidebars after your content box that look very similar to/the same as what’s pictured above. Add widgets to your new sidebarsAnd if you go to your Appearance>Widgets menu, you should now see 2 new boxes in the right column where you can drag widgets. Just click the drop down arrow to expand them (pictured here) and you can begin dragging widgets into them…text, pictures, recent post widgets, whatever you like. What if I want my widgetized sidebars to appear somewhere else? Okay, so what if you don’t want these new widget areas to appear below your content box? No problem, you just need to ‘hook’ them to the area you do want them in. Look at the 1st bit of code above (that went into your custom_functions.php file). The last line says “add action…”, and you see ‘thesis_hook_after_content_box’. That ‘after_content_box is the hook we used and it tells Thesis to place it in that specific area. Well, Thesis has lots of hooks available (a hook essentially just refers to a different place on your site you can ‘hang’ code). Check out this visual reference and click on one of the thumbnail images you see there. As you’ll see, the hooks are all over the place and they each refer to a different spot on the page. Choose where you want your widgetized sidebars to go and replace ‘after_content_box’ in the above code with the hook you want. Of course, that will require you to style your sidebars differently because the size of the space/hook you’re placing them in/on will determine how you style them. If you decide to do that, leave me a comment and I’ll show you how to do it. Things to keep in mind We registered/created just 2 widgetized sidebars. If you want more, that’s totally doable and it’s a matter of a few tweaks to the above code. Comment me if you would like to learn how to do so. Depending on what widget(s) you drop into these newly created sidebars, your styling (CSS) may need to be altered (an image, for example, may be taller than, say, a list of links, etc), so if you run into an issue where it just doesn’t look right, comment me. Alright, so that wraps things up. If anything is unclear or doesn’t work or if you need some additional support, please holler. And of course, if you’re at your wit’s end and want to hire me to build you a WordPress site or provide some WordPress Coaching, please do. Cheers… ========================================================= http://www.studiograsshopper.ch/code-snippets/how-to-add-a-widgetised-area-in-a-wordpress-theme/ How to add a Widgetised area in a WordPress theme July 11, 2009 26 Comments Darling, I'm not in the mood to go dancing. Let's stay home and code widgets instead! Darling, I'm not in the mood to go dancing. Let's stay home and code widgets instead! Here’s a tutorial to show you how to add a widget to a theme template file. Most themes these days come with built-in widget support, most commonly in the sidebar, but also sometimes in other parts of the theme such as the header, homepage or single post pages. In this tutorial I show you how to add a widget area to single post pages, and how to use the new widget area to display an advert on every single post page. Widget basics There are only four things we need to know in order to set up our new widget area: Which theme template file we need to edit The code for a Widget area, which we will place in the relevant theme template file How to “register” a Widget area, usually in the theme’s functions.php, in order to tell WordPress that the widget area exists and therefore allow you to add widgets to this widget area in the Dashboard. Add some styling to the widget area so that it fits in with the look of our site. Which template file? If you familiar with WordPress you will know that different pages on your site are produced by different theme template files. Which template file is used to display different views of your site is taken care of by WordPress, behind the scenes, and follows the Template Hierarchy coded into the WordPress Core files. In our example, we want to add the widget area to the single post page. Depending on your theme this will be either single.php or index.php. In our example, let’s assume it is index.php. Adding Widget code to the theme file Open up your index.php (take a backup first, just in case you need to put everything back to how it was) and decide where you want the new widget area to appear. Typically, your index.php file will be structured something like this (I’ve left out most of the code to keep things simple): 1 <?php get_header(); ?> 2 3 <div id="content"> 4 5 <div id="contentleft"> 6 7 <div class="postarea"> 8 9 <?php if (have_posts()) : while (have_posts()) : the_post(); ?> 10 11 // Loop stuff goes here eg Title, Date, Content etc 12 13 14 <!-- 15 <?php trackback_rdf(); ?> 16 --> 17 18 <?php endwhile; else: ?> 19 20 <p><?php _e('Sorry, no posts matched your criteria.'); ?></p><?php endif; ?> 21 22 </div><!-- End of postarea --> 23 24 <div class="postcomments"> 25 26 <?php comments_template('',true); ?> 27 28 </div> 29 30 </div> 31 32 <?php include(TEMPLATEPATH."/sidebar.php");?> 33 34 </div> 35 36 <?php get_footer(); ?> Your index.php file may not have the same DIV id name’s, but the structure should be similar: a DIV containing the Loop, in this case the postarea div (lines 7-22), and a DIV containing the call to the comments template, in this case the postcomments DIV (lines 24-28). We want to place our widget area between these two DIVs. That way, the widget content will display below the post content and above the comments section of the page. First, let’s add a new DIV and give it a new class called “widget-post”. You can name this class whatever you like, but choose something that has some meaning so that it’s easier to remember its purpose. Here’s our added code in lines 24-28: 1 </div><!-- End of postarea --> 2 3 <div class="widget-post"> 4 5 // Our widget stuff will go here... 6 7 </div> 8 9 <div class="postcomments"> 10 11 <?php comments_template('',true); ?> 12 13 </div> Now let’s add the code to display our new widget area. Here it is: 1 </div><!-- End of postarea --> 2 3 <div class="widget-post"> 4 5 <?php if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar('Post Widget') ) : ?> 6 <?php endif; ?> 7 8 </div> 9 10 <div class="postcomments"> 11 12 <?php comments_template('',true); ?> 13 14 </div> The new code we’ve added will pull in the widget content. In plain English, the code says – if widgets aren’t enabled in this theme or a widget area called “Post Widget” hasn’t been registered, do nothing. Therefore, if widgets are enabled and the widget area called “Post Widget” exists, the widget content will be displayed here. That’s it – no more work needed on the template file, and it’s time to add the “register” code in functions.php. Registering the widget in functions.php We now need to tell WordPress that it should enable a widget area called “Post Widget”. Open up your functions.php and look for a block of code something like this: 1 if ( function_exists('register_sidebars') ) { 2 register_sidebar(array('name'=>'Sidebar 1',)); 3 register_sidebar(array('name'=>'Sidebar 2',)); 4 register_sidebar(array('name'=>'Sidebar 3',)); 5 } This is the section of code that tells WordPress to enable widget areas. All we need to do is add a new line to this block of code to register our new widget area. Like this: 1 if ( function_exists('register_sidebars') ) { 2 register_sidebar(array('name'=>'Sidebar 1',)); 3 register_sidebar(array('name'=>'Sidebar 2',)); 4 register_sidebar(array('name'=>'Sidebar 3',)); 5 register_sidebar(array('name'=>'Post Widget',)); 6 } The important points to note are: We’ve added the extra line below the existing lines, but before the closing curly bracket. This ensures that our changes do not mess up the widgets you’ve already set up in your sidebar, for example. We’ve used exactly the same name “Post Widget” that we used in the new code added in index.php above. Another important point to remember is that the names of widget areas must be unique! Adding widgets to the new widget area Go to Dashboard>Appearance>Widgets and you should now see that your Post Widget appears in the righthand side of this screen. You can now drag a Text Widget to the Post Widget, and then add the code necessary to display your adverts within the Text Widget. For example, you can add Google Adsense code here, or affiliate code for a banner ad etc. View your site and check that on single post pages you now see your adverts between the post content and the comments. If it doesn’t appear, re-check the above steps in case you’ve missed something. If using a newly set up Google Adsense, remember that it can take a short while for the Adsense to populate. Styling the new widget area You will probably need to adjust your CSS to get the new widget area to fit in with the look of your site. The most important thing to do first is to add something like this to your style.css to define a style for the new widget-post DIV class which is the container for the widget area: 1 .widget-post { 2 background: #FFFFFF; 3 margin: 0px; 4 padding: 10px; 5 width: 600px; 6 } This is just a starting point – adjust the width, background, padding and margin to suit you. If you are using Google Adsense, your Google code will already include various styles based on the selections you made when setting up the Google Adsense. If you are posting your own HTML in the Text Widget you will probably have to add some styling to style.css to make the neceesary adjustments. If you are unfamiliar with CSS, check out the many great tutorials that are out there. And finally… As you can see, it isn’t too difficult to add a widget area to a theme file. This same method can be used elsewhere in your site to create other widget areas – just remember to name each one uniquely, and have fun ================================================= How to add widget area http://www.templatemonster.com/help/how-to-add-widget-area.html Author: Chris Diaz Posted on: April 7, 2011 Relation: Layout Complexity: Advanced Tags: widget, WordPress Rating: 3.3/5 (2 votes cast)
How to add widget area in WordPress This tutorial will show you how to create new widget area in WordPress. Any widget in WordPress template could be displayed in any place on the page. This could be done using WordPress widget areas.
To add widget area access to your WordPress installation folder. 1. Open ‘wp-content/themes/theme###’ folder. 2. View the functions.php file 3. Use search tool (CTRL+F) and search for ‘widget’. You can fund the following lines: Here you can see that widgets are defined in the sidebar-init.php file ? 1 2
//Widget and Sidebar require_once $includes_path . 'sidebar-init.php'; This line defines the $includes_path variable value. ? 1
$includes_path = TEMPLATEPATH . '/includes/'; These lines shows you that the widgets are defined in the wp-content/themes/theme###/includes/sidebar-init.php file 4. Open sidebar-init.php file. All widget areas are defined here. The following code is used to define wach area: ? 1 2 3 4 5 6 7 8 9
register_sidebar(array( 'name' => 'Sidebar 2', 'id' => 'sidebar-2', 'description' => __( 'Located at the right side of pages.'), 'before_widget' => '<div id="%1$s" class="widget %2$s">', 'after_widget' => '</div>', 'before_title' => '<h3 class="widget-title">', 'after_title' => '</h3>', )); To register new widget area copy the code above and paste it before the closing ‘}’ bracket Change the ‘name’, ‘id’ and ‘description’ values.
5. Now you can insert the widget area to any part of the template. Go back to the ‘wp-content/themes/theme###‘ folder. You can insert the area to any layout file: header.php footer.php single.php category.php index.php sidebar.php etc 6. Paste the following code to the required place to insert the widget area. ? 1
<?php if ( ! dynamic_sidebar( 'New Widget Area' ) ) :?><?php endif;?> Replace ‘New Widget Area’ with your widget area name. 7. If everything has been done correctly the new widget area would be available from the WordPress admin panel Appearance>Widgets (right column) .
Feel free to check the detailed video tutorial below: <end node> 5P9i0s8y19Z dt= <node>saved info 2 ?><div id="topbar" class="sidebar widget-area"> <?php genesis_structural_wrap( 'topbar' ); do_action( 'genesis_before_sidebar_widget_area' ); do_action( 'genesis_sidebar' ); do_action( 'genesis_after_sidebar_widget_area' ); genesis_structural_wrap( 'topbar', 'close' ); ?> </div> <!-- begin #featured-top --> <div id="featured-top"> <?php if (!dynamic_sidebar('Homepage Top')) : ?> <div class="widget">
<div class="wrap"> <p><?php _e("This is a widgeted area which is called Homepage.", 'genesis'); ?></p> </div><!-- end .wrap --> </div><!-- end .widget --> <?php endif; ?> </div><!-- end #featured-top --> <end node> 5P9i0s8y19Z dt= <node>simple one 2 <?php /* Plugin Name: My Widget Plugin URI: http://mydomain.com Description: My first widget Author: Me Version: 1.0 Author URI: http://mydomain.com */ // Block direct requests if ( !defined('ABSPATH') ) die('-1');
add_action( 'widgets_init', function(){ register_widget( 'My_Widget' ); }); /** * Adds My_Widget widget. */ class My_Widget extends WP_Widget { /** * Register widget with WordPress. */ function __construct() { parent::__construct( 'My_Widget', // Base ID __('My Widget', 'text_domain'), // Name array( 'description' => __( 'My first widget!', 'text_domain' ), ) // Args ); } /** * Front-end display of widget. * * @see WP_Widget::widget() * * @param array $args Widget arguments. * @param array $instance Saved values from database. */ public function widget( $args, $instance ) {
<node>CUSTOM CODING <node>Disable auto updates <node>Disable site <node>EXTERNAL PHP <node>Hacks <node>footer changes <node>Header Change <node>New user <node>is logged in <node>Merging admins <node>Protect Login Screen <node>redirect <node>Codects <node>database access <node>domain change <node>Embed wordpress page <node>MEMBERlogin <node>Redirect <node>database <node>get_row <node>MergeDatabases <node>minimum permissions <node>New subject <node>notes <node>plugin <node>backupWordpress <node>Contact form <node>shortcodes <node>WIDGET <node>example <node>new area <node>saved info <node>simple one
<Treepad version 3.0> dt= <node>CUSTOM CODING 0 accepted
If you are getting to the point where the code in your theme's functions.php is starting to overwhelm you I would definitely say you are ready to consider splitting it up into multiple files. I tend to do that almost by second nature at this point. Use Include Files in your Theme's functions.php File I create a subdirectory called "includes" under my theme directory and segment my code into include files organized by what makes sense to me at the time (which means I'm constantly refactoring and moving code around as a site evolves.) I also rarely put any real code in functions.php; everything goes in the include files; just my preference. Just to give you an example here's my test install that I use to test my answers to questions here on WordPress Answers. Every time I answer a question I keep the code around in case I need it again. This isn't exactly what you'll do for a live site but it shows the mechanics of splitting up the code: require_once('includes/null-meta-compare.php'); require_once('includes/older-examples.php'); require_once('includes/wp-admin-menu-classes.php'); <end node> 5P9i0s8y19Z dt= <node>Disable auto updates 1 Example Coding Magic: Turn Off Automatic Updates Auto updates have been a part of WordPress since version 3.7. Not everyone likes this feature; many would like to turn it off. All you need to do is add this line of code to your wp-config.php file. 1./* Disable WordPress automatic updates */ .2.define( 'WP_AUTO_UPDATE_CORE', false ); <end node> 5P9i0s8y19Z dt= <node>Disable site 1 In the header.php file of genisis <?php if(!is_user_logged_in()){ echo "This site is under construction"; exit; } <end node> 5P9i0s8y19Z dt= <node>EXTERNAL PHP 1 home | photos | login
Outreach Child Theme: wpHeaderInclude.php <link rel="stylesheet" href="<?php echo includes_url(); ?>/js/lightbox/lightbox.css" type="text/css" media="screen" > <script type="text/javascript" src="<?php echo includes_url(); ?>/js/lightbox/lightbox.js"></script> Just add your lightbox folder to the include/js folder ===================================================== I actually found how to do it, it's pretty straight forward: 1/ Register a function to be executed when the wp_head action fires: add_action('wp_head', 'my_function'); 2/ Make the function echo whatever you want in the header: function my_function() { <link rel="stylesheet" href="<?php echo includes_url(); ?>/js/lightbox/lightbox.css" type="text/css" media="screen" > echo '<meta name="robots" content="noindex, nofollow">'; } Using this trick for the Facebook Like plugin, thanks to the smart Add Your Own Headers plugin that showed me pointers. <end node> 5P9i0s8y19Z dt= <node>New user 2 REQUIRES 3 INSERTS INSERT INTO `databasename`.`wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES ('4', 'demo', MD5('demo'), 'Syed Balkhi', 'test@yourdomain.com', 'http://www.wpbeginner.com/', '2011-06-07 00:00:00', '', '0', 'Syed Balkhi'); 2 3 4 INSERT INTO `databasename`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, '4', 'wp_capabilities', 'a:1:{s:13:"administrator";s:1:"1";}'); 5 6 7 INSERT INTO `databasename`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, '4', 'wp_user_level', '10'); wp_w3q1o7u0_usermeta WPBeginner» Blog» Tutorials» How to Add an Admin User to… How to Add an Admin User to the WordPress Database via MySQL Last updated on November 25th, 2014 by Editorial Staff Share This Article 101 Follow WPBeginner on YouTube How to Add an Admin User to the WordPress Database via MySQL Few days ago, we ran into an issue where a user’s site got hacked and their admin account was deleted from the database. This locked them out of their site without any other entry. We went in to the phpMyAdmin and created a new admin user to grant them access. In this article, we will show you a step by step guide on how to create an admin user in WordPress Database via MySQL. Note: You should always make a backup of your database before performing any MySQL edits. This tutorial requires basic understanding of how phpMyAdmin works. Video Tutorial If you don’t like the video or need more instructions, then continue reading. First, you need to login to phpMyAdmin and locate your WordPress database. (Below is a screenshot of a HostGator cPanel) cPanel phpMyAdmin Once you are in, we will be making changes to the wp_users and wp_usermeta tables. Lets go ahead and click on wp_users table. phpMyAdmin wp_users table We need to insert our new admin user’s information, so click on the Insert tab like it shows in the image above. In the insert form, add the following: ID – pick a number (in our example, we will use the number 4). user_login – insert the username you want to use to access the WordPress Dashboard. user_pass – add a password for this username. Make sure to select MD5 in the functions menu (Refer to the screenshot below). user_nicename – put a nickname or something else that you would like to refer yourself as. user_email – add the email you want to associate with this account. user_url – this would be the url to your website. user_registered – select the date/time for when this user is registered. user_status – set this to 0. display_name – put the name you like to display for this user on the site (it can be your user_nicename value as well). Click on the Go Button phpMyAdmin Insert values in wp_users table Next we are going to have to add the values to wp_usermeta table. Click on the wp_usermeta table and then click on the Insert tab just like the previous step. Then add the following information to the insert form: unmeta_id – leave this blank (it will be auto-generated) user_id – this will be the id of the user you created in the previous step. Remember we picked 4. meta_key – this should be wp_capabilities meta_value – insert this: a:1:{s:13:"administrator";s:1:"1";} Insert another row with the following information: unmeta_id – leave this blank (it will be auto-generated) user_id – this will be the id of the user you created in the previous step. Remember we picked 4. meta_key – this should be wp_user_level meta_value – 10 Then click on the Go button, and you have created yourself a new username. Now you should be able to login to your wp-admin with the username and password you specified for this user. Once logged in, click on Users and edit the username you just created. Go down and click on the Save button (you don’t have to change anything). This will allow WordPress to go through and add some more information and clean-up the user we just added. SQL query For developers who want to speed this process up, you can simply drop this SQL query in your database. 1 INSERT INTO `databasename`.`wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES ('4', 'demo', MD5('demo'), 'Syed Balkhi', 'test@yourdomain.com', 'http://www.wpbeginner.com/', '2011-06-07 00:00:00', '', '0', 'Syed Balkhi'); 2 3 4 INSERT INTO `databasename`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, '4', 'wp_capabilities', 'a:1:{s:13:"administrator";s:1:"1";}'); 5 6 7 INSERT INTO `databasename`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, '4', 'wp_user_level', '10'); Remember to change the databasename to the database you are working with. Also don’t forget to change the appropriate values. About the Editorial Staff Editorial Staff at WPBeginner is a team of WordPress lovers led by Syed Balkhi. Page maintained by Syed Balkhi. More on WPBeginner Right Now How to Easily Create a Responsive WordPress Slider with Soliloquy How to Easily Create a Responsive WordPress Slider with Soliloquy How We Increased Our Organic Search Traffic By Using HitTail How We Increased Our Organic Search Traffic By Using HitTail WordPress Custom Fields 101: Tips, Tricks, and Hacks WordPress Custom Fields 101: Tips, Tricks, and Hacks How to Get Google’s Verified Authorship for your WordPress Blog How to Get Google’s Verified Authorship for your WordPress Blog WPBeginner's WordPress Training Videos Free WPBeginner's Video Icon Our HD-Quality tutorial videos for WordPress Beginners will teach you how to use WordPress to create and manage your own website in about an hour. Get started now » Join over 130,000 WordPress Users who get fresh content from WPBeginner! <end node> 5P9i0s8y19Z dt= <node>is logged in 1 <?php if(!is_user_logged_in()){ echo "This site is under construction"; exit; } <end node> 5P9i0s8y19Z dt= <node>Merging admins 1 Add this to the mystuff.php of the non wordpress admin FROM THE WINDSORSEVERANCESTORAGE.COM session_start(); include("config.php"); require_once("../wp-load.php"); if(!is_user_logged_in() && $bypass!=true){ echo "This site is under construction"; exit; } else $wordpress=true; if($wordpress==false){ $db = mysql_pconnect($server, $user,$password); if (!$db){ echo 'Error: Could not connect to database. Please try again later.'; exit; } mysql_select_db($database); if($pageLevel=='')$pageLevel=3; if($LEVEL<$pageLevel && $bypass!=true){ echo "<body onload=setTimeout(\\"location.href='LoginScreen.php'\\",2000)>"; echo "You need to login with more security.<p>Click <a href='LoginScreen.php'>here</a> to continue.";$_SESSION['LEVEL']='';exit; } }else $_SESSION['LEVEL']=10; <end node> 5P9i0s8y19Z dt= <node>Protect Login Screen 1 This is done near the top in both files in the index.php of the root/wp-admin folder add: if($_GET["SWD"]!="") setcookie("SWD_ADMIN","swd", time()+(60*60*24*30),"/"); in the root folder wp-login.php add: if($_COOKIE["SWD_ADMIN"]!="swd"){ echo "You have been terminated"; exit; } <end node> 5P9i0s8y19Z dt= <node>redirect 1 add_action( 'template_redirect', 'restrictPage_blah', 100 ); function restrictPage_blah() { if( ! is_user_logged_in() && is_page('restrictedPage') ) { wp_redirect( 'http://www.google.com' ); exit; } } <end node> 5P9i0s8y19Z dt= <node>Codects 1 <?php require_once("../wp-load.php"); require_once("swdFunctions.php"); function current_session(){ $sessionid =$_COOKIE["MYCOOKIE"];//$_SESSION["MYSESSION"]; if($sessionid==""){ $sessionid=strtotime(date("Y-m-d H:i:s")); setcookie("MYCOOKIE",$sessionid,time()+60*60*24*300); } return $sessionid; } get_header(); include(get_site_url()."/swd/mdropdown.php"); ?> <div id="content-full" class="grid col-940"> </div><!-- end of #content-full --> <?php get_footer(); ?> <end node> 5P9i0s8y19Z dt= <node>database access 2 <?php $path = $_SERVER['DOCUMENT_ROOT']; include_once $path . '/wp-config.php'; include_once $path . '/wp-load.php'; // THIS MAY BE THE ONLY LINE YOU MAY NEED include_once $path . '/wp-includes/wp-db.php'; include_once $path . '/wp-includes/pluggable.php'; // $wpdb is available, do stuff <end node> 5P9i0s8y19Z dt= <node>domain change 2 UPDATE wp_posts SET guid = replace(guid, 'http://www.old-domain.com','http://www.new-domain.com'); UPDATE whs_posts SET guid = replace(guid, 'http://www.softwarewebsecure.com/WINDSORHAIR','http://new.windsorhairshoppe.com'); <end node> 5P9i0s8y19Z dt= <node>Embed wordpress page 2 From the swinterTmpl.php from Storage include(includes_url()."storageLeaseForm.php?WPLOGIN=".STORAGE_MEMBER."&site1=".urlencode(site_url())); $include1 = get_pages('include=62'); $content = apply_filters('the_content',$include1[0]->post_content); echo $content; //echo includes_url()."storageLeaseForm.php?site1=".urlencode(site_url()); break; ID: page/post ID (int) ?post_author: author ID (string) ?post_date: time-date string (YYYY-MM-DD HH:MM:SS), e.g., "2012-10-15 01:02:59" ?post_date_gmt: time-date string ?post_content: HTML (string) ?post_title ?post_excerpt: HTML (string) ?post_status: (publish|inherit|pending|private|future|draft|trash) ?comment_status: closed/open ?ping_status: (closed|open) ?post_password ?post_name: slug for page/post ?to_ping ?pinged ?post_modified: time-date string ?post_modified_gmt: time-date string ?post_content_filtered ?post_parent: parent ID (int) ?guid: URL ?menu_order: (int) ?post_type: (page|post|attachment) ?post_mime_type ?comment_count: number of comments (string) ?filter All values are strings unless otherwise shown as (int). <end node> 5P9i0s8y19Z dt= <node>MEMBERlogin 2 using the index.php <?php session_start(); define('DARNELL_MEMBER', $_SESSION["DARNELL"]); //echo "shoot";exit; /** * Front to the WordPress application. This file doesn't do anything, but loads * wp-blog-header.php which does and tells WordPress to load the theme. * * @package WordPress */ /** * Tells WordPress to load the WordPress theme and output it. * * @var bool */ define('WP_USE_THEMES', true); /** Loads the WordPress Environment and Template */ require( dirname( __FILE__ ) . '/wp-blog-header.php' ); <end node> 5P9i0s8y19Z dt= <node>Redirect 2 [mix wordpress with non-wordpress site] $actual_link = "https://$_SERVER[HTTP_HOST]$_SERVER[REQUEST_URI]"; $parse = parse_url($actual_link); //echo "dog--".$server1; if($parse['host']=="new.angeldesignsbydenise.com"){ define('WP_USE_THEMES', true); // Loads the WordPress Environment and Template require( dirname( __FILE__ ) . '/wp-blog-header.php' ); exit; } <end node> 5P9i0s8y19Z dt= <node>database 1 [MULTIPLE RECORDS] $rows=$wpdb->get_results($query);$num=$wpdb->num_rows; foreach ( $rows as $row ) { if($cnt>$defaultField){ $dis.="\\n</td></tr></table><td width=175><table><tr><td><b>Member</b><td><b>Year<b></td>\\n";$cnt=0; } $donationid=$row->donationid; $last_name=$row->last_name; $last_name=ShortenString($last_name); $first_name=$row->first_name; $first_name=ShortenString($first_name); $authcode=$row->authcode; $datefill=$row->datefill; $timelapse=(int)((strtotime(date("Y-m-d"))-strtotime($datefill))/$yearlapse); if($timelapse==0)$timelapse="NEW"; //REPORT FORMAT here if($authcode=="YES"){ $dis.="<tr><td align=right>Anonymous</td><td width=20 style='text-align:center;'>$timelapse</td></tr>\\n"; }else{ $dis.="<tr><td align=right>$first_name $last_name</td><td width=20 style='text-align:center;'>$timelapse</td></tr>\\n"; // <td class=view>$first_name</td> <td class=view>$address</td> <td class=view>$city</td> <td class=view>$state</td> <td class=view>$zip</td> <td class=view>$phone</td> <td class=view>$email</td> <td class=viewnumber align=right>$pay_interval</td> <td class=view>$pay_option</td> <td class=viewnumber align=right>$amount</td> <td class=view>$datefill</td> <td class=view>$responsecode</td> <td class=viewnumber align=right>$subscriptionid</td> <td class=view>$reasoncode</td> <td class=view>$reasontext</td> <td class=view>$authcode</td> <td class=view>$avscode</td> <td class=view>$cardType</td> <td class=view>$cardnum</td> <td class=view>$csc</td> <td class=view>$month</td> <td class=viewnumber align=right>$year</td>"; } $cnt++; } SELECT Generic Results Generic, mulitple row results can be pulled from the database with get_results. The function returns the entire query result as an array, or NULL on no result. Each element of this array corresponds to one row of the query result and, like get_row, can be an object, an associative array, or a numbered array. <?php $wpdb->get_results('query', output_type); ?> query (string) The query you wish to run. Setting this parameter to null will return the data from the cached results of the previous query. output_type One of four pre-defined constants. Defaults to OBJECT. See SELECT a Row and its examples for more information. OBJECT - result will be output as a numerically indexed array of row objects. OBJECT_K - result will be output as an associative array of row objects, using first column's values as keys (duplicates will be discarded). ARRAY_A - result will be output as an numerically indexed array of associative arrays, using column names as keys. ARRAY_N - result will be output as a numerically indexed array of numerically indexed arrays. Since this function uses the '$wpdb->query()' function all the class variables are properly set. The results count for a 'SELECT' query will be stored in $wpdb->num_rows. [UPDATE OR DELETE] Run Any Query on the Database The query function allows you to execute any SQL query on the WordPress database. It is best to use a more specific function (see below), however, for SELECT queries. <?php $wpdb->query('query'); ?> query (string) The SQL query you wish to execute. The function returns an integer corresponding to the number of rows affected/selected. If there is a MySQL error, the function will return FALSE. (Note: since both 0 and FALSE can be returned, make sure you use the correct comparison operator: equality == vs. identicality ===). <end node> 5P9i0s8y19Z dt= <node>get_row 2 SELECT a Row To retrieve an entire row from a query, use get_row. The function can return the row as an object, an associative array, or as a numerically indexed array. If more than one row is returned by the query, only the specified row is returned by the function, but all rows are cached for later use. Returns OBJECT holding NULL if no result is found, consider this when using the returned value in arguments, see example below <?php $wpdb->get_row('query', output_type, row_offset); ?> query (string) The query you wish to run. output_type One of three pre-defined constants. Defaults to OBJECT. ¦OBJECT - result will be output as an object. ¦ARRAY_A - result will be output as an associative array. ¦ARRAY_N - result will be output as a numerically indexed array. row_offset (integer) The desired row (0 being the first). Defaults to 0. Examples Get all the information about Link 10. $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10"); The properties of the $mylink object are the column names of the result from the SQL query (in this example all the columns from the $wpdb->links table, but you could also query for specific columns only). echo $mylink->link_id; // prints "10" In contrast, using $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10", ARRAY_A); would result in an associative array: echo $mylink['link_id']; // prints "10" and $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10", ARRAY_N); would result in a numerically indexed array: echo $mylink[1]; // prints "10" If there is no record with ID 10 in the links table, null will be returned. The following would then be false: if ($mylink != null) { // do something with the link return true; } else { // no link found return false; } <end node> 5P9i0s8y19Z dt= <node>MergeDatabases 2 http://wordpress.stackexchange.com/questions/94018/merging-two-wp-posts-tables-while-avoiding-duplicates Import the new table as wp_posts_2, then join them and delete all duplicates based on post_content; then merge the two tables. The following SQL query (untested!) should give the posts from the new table to be deleted: SELECT wp2.* FROM wp_posts_2 as wp2 LEFT JOIN wp_posts as wp ON wp2.post_content = wp.post_content WHERE wp2.post_content = wp.post_content So, you can delete the entries with this query (also untested): DELETE wp_posts_2.* LEFT JOIN wp_posts as wp ON wp_posts_2.post_content = wp.post_content WHERE wp_posts_2.post_content = wp.post_content Then merge the two tables. <end node> 5P9i0s8y19Z dt= <node>minimum permissions 2 Below is an example of the minimum privileges a database user needs to have. Other database permissions are regarded as “extra” privileges that in most cases are not needed. A typical WordPress user should be granted the following database privileges only: The official documentation says to give the user all privs. Others suggest that you can restrict it to SELECT •INSERT •UPDATE •DELETE •CREATE •ALTER •INDEX •DROP optional Plugins etc can though call any statement they want so you would have to thoroughly test Data: SELECT INSERT UPDATE Example of How to Grant Access Privileges If you are upgrading WordPress, the above database permissions might not suffice between versions, WordPress might need to make further changes to the database. In this case, if you are only upgrading to the latest version of WordPress, add the below privileges to the WordPress database user: Structure: CREATE ALTER NOTE: Some plugins might require additional database privileges such as CREATE, DROP or DELETE and in those cases these privileges should be granted. <end node> 5P9i0s8y19Z dt= <node>New subject 2 <end node> 5P9i0s8y19Z dt= <node>notes 2 Interfacing With the Database WordPress provides a class of functions for all database manipulations. The class is called wpdb and is loosely based on the ezSQL class written and maintained by Justin Vincent. Using the $wpdb Object Methods in the wpdb() class should not be called directly. WordPress provides a global variable, $wpdb, which is an instantiation of the class already set up to talk to the WordPress database. Always use the global $wpdb variable. (Remember to globalize $wpdb before using it in any custom functions.) The $wpdb object can be used to read data from any table in the WordPress database (such as custom plugin tables), not just the standard tables that WordPress creates. For example to SELECT some information from a custom table called "mytable", you can do the following. $myrows = $wpdb->get_results( "SELECT id, name FROM mytable" ); The $wpdb object can talk to any number of tables, but only one database: the WordPress database. In the rare case you need to connect to another database, you will have to instantiate your own object from the wpdb class with the appropriate connection details. For extremely complicated setups with many databases, consider using hyperdb instead. Run Any Query on the Database The query function allows you to execute any SQL query on the WordPress database. It is best to use a more specific function (see below), however, for SELECT queries. <?php $wpdb->query('query'); ?> query (string) The SQL query you wish to execute. The function returns an integer corresponding to the number of rows affected/selected. If there is a MySQL error, the function will return FALSE. (Note: since both 0 and FALSE can be returned, make sure you use the correct comparison operator: equality == vs. identicality ===). Note: As with all functions in this class that execute SQL queries, you must SQL escape all inputs (e.g., wpdb->escape($user_entered_data_string)). See the section entitled Protect Queries Against SQL Injection Attacks below. Examples Delete the 'gargle' meta key and value from Post 13. (We'll add the 'prepare' method to make sure we're not dealing with an illegal operation or any illegal characters): $wpdb->query( $wpdb->prepare( " DELETE FROM $wpdb->postmeta WHERE post_id = %d AND meta_key = %s ", 13, 'gargle' ) ); Performed in WordPress by delete_post_meta(). Set the parent of Page 15 to Page 7. $wpdb->query( " UPDATE $wpdb->posts SET post_parent = 7 WHERE ID = 15 AND post_status = 'static' " ); SELECT a Variable The get_var function returns a single variable from the database. Though only one variable is returned, the entire result of the query is cached for later use. Returns NULL if no result is found. <?php $wpdb->get_var('query',column_offset,row_offset); ?> query (string) The query you wish to run. Setting this parameter to null will return the specified variable from the cached results of the previous query. column_offset (integer) The desired column (0 being the first). Defaults to 0. row_offset (integer) The desired row (0 being the first). Defaults to 0. Examples Retrieve and display the number of users. <?php $user_count = $wpdb->get_var( "SELECT COUNT(*) FROM $wpdb->users" ); echo "<p>User count is {$user_count}</p>"; ?> Retrieve and display the sum of a Custom Field value. <?php // set the meta_key to the appropriate custom field meta key $meta_key = 'miles'; $allmiles = $wpdb->get_var( $wpdb->prepare( " SELECT sum(meta_value) FROM $wpdb->postmeta WHERE meta_key = %s ", $meta_key ) ); echo "<p>Total miles is {$allmiles}</p>"; ?> SELECT a Row To retrieve an entire row from a query, use get_row. The function can return the row as an object, an associative array, or as a numerically indexed array. If more than one row is returned by the query, only the specified row is returned by the function, but all rows are cached for later use. Returns OBJECT holding NULL if no result is found, consider this when using the returned value in arguments, see example below. <?php $wpdb->get_row('query', output_type, row_offset); ?> query (string) The query you wish to run. output_type One of three pre-defined constants. Defaults to OBJECT. ¦OBJECT - result will be output as an object. ¦ARRAY_A - result will be output as an associative array. ¦ARRAY_N - result will be output as a numerically indexed array. row_offset (integer) The desired row (0 being the first). Defaults to 0. Examples Get all the information about Link 10. $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10"); The properties of the $mylink object are the column names of the result from the SQL query (in this example all the columns from the $wpdb->links table, but you could also query for specific columns only). echo $mylink->link_id; // prints "10" In contrast, using $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10", ARRAY_A); would result in an associative array: echo $mylink['link_id']; // prints "10" and $mylink = $wpdb->get_row("SELECT * FROM $wpdb->links WHERE link_id = 10", ARRAY_N); would result in a numerically indexed array: echo $mylink[1]; // prints "10" If there is no record with ID 10 in the links table, null will be returned. The following would then be false: if ($mylink != null) { // do something with the link return true; } else { // no link found return false; } SELECT a Column To SELECT a column, use get_col. This function outputs a one dimensional array. If more than one column is returned by the query, only the specified column will be returned by the function, but the entire result is cached for later use. Returns an empty array if no result is found. <?php $wpdb->get_col('query',column_offset); ?> query (string) the query you wish to execute. Setting this parameter to null will return the specified column from the cached results of the previous query. column_offset (integer) The desired column (0 being the first). Defaults to 0. Examples For this example, assume the blog is devoted to information about automobiles. Each post describes a particular car (e.g. 1969 Ford Mustang), and three Custom Fields, manufacturer, model, and year, are assigned to each post. This example will display the post titles, filtered by a particular manufacturer (Ford), and sorted by model and year. The get_col form of the wpdb Class is used to return an array of all the post ids meeting the criteria and sorted in the correct order. Then a foreach construct is used to iterate through that array of post ids, displaying the title of each post. Note that the SQL for this example was created by Andomar. <?php $meta_key1 = 'model'; $meta_key2 = 'year'; $meta_key3 = 'manufacturer'; $meta_key3_value = 'Ford'; $postids=$wpdb->get_col( $wpdb->prepare( " SELECT key3.post_id FROM $wpdb->postmeta key3 INNER JOIN $wpdb->postmeta key1 ON key1.post_id = key3.post_id AND key1.meta_key = %s INNER JOIN $wpdb->postmeta key2 ON key2.post_id = key3.post_id AND key2.meta_key = %s WHERE key3.meta_key = %s AND key3.meta_value = %s ORDER BY key1.meta_value, key2.meta_value ", $meta_key1, $meta_key2, $meta_key3, $meta_key3_value ) ); if ( $postids ) { echo "List of {$meta_key3_value}(s), sorted by {$meta_key1}, {$meta_key2}"; foreach ( $postids as $id ) { $post = get_post( intval( $id ) ); setup_postdata( $post ); ?> <p> <a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link to <?php the_title_attribute(); ?>"> <?php the_title(); ?> </a> </p> <?php } } ?> This example lists all posts that contain a particular custom field, but sorted by the value of a second custom field. <?php // List all posts with custom field Color, sorted by the value of custom field Display_Order // does not exclude any 'post_type' // assumes each post has just one custom field for Color, and one for Display_Order $meta_key1 = 'Color'; $meta_key2 = 'Display_Order'; $postids = $wpdb->get_col( $wpdb->prepare( " SELECT key1.post_id FROM $wpdb->postmeta key1 INNER JOIN $wpdb->postmeta key2 ON key2.post_id = key1.post_id AND key2.meta_key = %s WHERE key1.meta_key = %s ORDER BY key2.meta_value+(0) ASC ", $meta_key2, $meta_key1 ) ); if ( $postids ) { echo "List of {$meta_key1} posts, sorted by {$meta_key2}"; foreach ( $postids as $id ) { $post = get_post( intval( $id ) ); setup_postdata( $post ); ?> <p> <a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link to <?php the_title_attribute(); ?>"> <?php the_title(); ?> </a> </p> <?php } } ?> SELECT Generic Results Generic, mulitple row results can be pulled from the database with get_results. The function returns the entire query result as an array, or NULL on no result. Each element of this array corresponds to one row of the query result and, like get_row, can be an object, an associative array, or a numbered array. <?php $wpdb->get_results('query', output_type); ?> query (string) The query you wish to run. Setting this parameter to null will return the data from the cached results of the previous query. output_type One of four pre-defined constants. Defaults to OBJECT. See SELECT a Row and its examples for more information. ¦OBJECT - result will be output as a numerically indexed array of row objects. ¦OBJECT_K - result will be output as an associative array of row objects, using first column's values as keys (duplicates will be discarded). ¦ARRAY_A - result will be output as an numerically indexed array of associative arrays, using column names as keys. ¦ARRAY_N - result will be output as a numerically indexed array of numerically indexed arrays. Since this function uses the '$wpdb->query()' function all the class variables are properly set. The results count for a 'SELECT' query will be stored in $wpdb->num_rows. Examples Get the IDs and Titles of all the Drafts by User 5 and echo the Titles. $fivesdrafts = $wpdb->get_results( " SELECT ID, post_title FROM $wpdb->posts WHERE post_status = 'draft' AND post_author = 5 " ); foreach ( $fivesdrafts as $fivesdraft ) { echo $fivesdraft->post_title; } Get all information on the Drafts by User 5. <?php $fivesdrafts = $wpdb->get_results( " SELECT * FROM $wpdb->posts WHERE post_status = 'draft' AND post_author = 5 " ); if ( $fivesdrafts ) { foreach ( $fivesdrafts as $post ) { setup_postdata( $post ); ?> <h2> <a href="<?php the_permalink(); ?>" rel="bookmark" title="Permalink: <?php the_title(); ?>"> <?php the_title(); ?> </a> </h2> <?php } else { ?> <h2>Not Found</h2> <?php } } ?> INSERT rows Insert a row into a table. <?php $wpdb->insert( $table, $data, $format ); ?> table (string) The name of the table to insert data into. data (array) Data to insert (in column => value pairs). Both $data columns and $data values should be "raw" (neither should be SQL escaped). format (array|string) (optional) An array of formats to be mapped to each of the value in $data. If string, that format will be used for all of the values in $data. If omitted, all values in $data will be treated as strings unless otherwise specified in wpdb::$field_types. Possible format values: %s as string; %d as decimal number; and %f as float. After insert, the ID generated for the AUTO_INCREMENT column can be accessed with: $wpdb->insert_idThis function returns false if the row could not be inserted. Examples Insert two columns in a row, the first value being a string and the second a number: $wpdb->insert( 'table', array( 'column1' => 'value1', 'column2' => 123 ), array( '%s', '%d' ) ); UPDATE rows Update a row in the table. Returns false if errors, or the number of rows affected if successful. <?php $wpdb->update( $table, $data, $where, $format = null, $where_format = null ); ?> table (string) The name of the table to update. data (array) Data to update (in column => value pairs). Both $data columns and $data values should be "raw" (neither should be SQL escaped). where (array) A named array of WHERE clauses (in column => value pairs). Multiple clauses will be joined with ANDs. Both $where columns and $where values should be "raw". format (array|string) (optional) An array of formats to be mapped to each of the values in $data. If string, that format will be used for all of the values in $data. where_format (array|string) (optional) An array of formats to be mapped to each of the values in $where. If string, that format will be used for all of the items in $where. Possible format values: %s as string; %d as decimal number and %f as float. If omitted, all values in $where will be treated as strings. This function returns the number of rows updated, or false if there is an error. Examples Update a row, where the ID is 1, the value in the first column is a string and the value in the second column is a number: $wpdb->update( 'table', array( 'column1' => 'value1', // string 'column2' => 'value2' // integer (number) ), array( 'ID' => 1 ), array( '%s', // value1 '%d' // value2 ), array( '%d' ) ); Attention: %d can't deal with comma values - if you're not using full numbers, use string/%s. Protect Queries Against SQL Injection Attacks For a more complete overview of SQL escaping in WordPress, see database Data Validation. That Data Validation article is a must-read for all WordPress code contributors and plugin authors. Briefly, though, all data in SQL queries must be SQL-escaped before the SQL query is executed to prevent against SQL injection attacks. This can be conveniently done with the prepare method, which supports both a sprintf()-like and vsprintf()-like syntax. Please note: As of 3.5, wpdb::prepare() enforces a minimum of 2 arguments. [more info] <?php $sql = $wpdb->prepare( 'query' , value_parameter[, value_parameter ... ] ); ?> query (string) The SQL query you wish to execute, with %s and %d placeholders. Any other % characters may cause parsing errors unless they are escaped. All % characters inside SQL string literals, including LIKE wildcards, must be double-% escaped as %%. value_parameter (int|string|array) The value to substitute into the placeholder. Many values may be passed by simply passing more arguments in a sprintf()-like fashion. Alternatively the second argument can be an array containing the values as in PHP's vsprintf() function. Care must be taken not to allow direct user input to this parameter, which would enable array manipulation of any query with multiple placeholders. Values must not already be SQL-escaped. Examples Add Meta key => value pair "Harriet's Adages" => "WordPress' database interface is like Sunday Morning: Easy." to Post 10. $metakey = "Harriet's Adages"; $metavalue = "WordPress' database interface is like Sunday Morning: Easy."; $wpdb->query( $wpdb->prepare( " INSERT INTO $wpdb->postmeta ( post_id, meta_key, meta_value ) VALUES ( %d, %s, %s ) ", 10, $metakey, $metavalue ) ); Performed in WordPress by add_meta(). <end node> 5P9i0s8y19Z dt= <node>plugin 1 [admin plugin] <?php ./* Plugin Name: swd_admin Description: A test plugin to demonstrate wordpress functionality Author: SWD Version: 0.1 */ add_action('admin_menu', 'test_plugin_setup_menu'); function test_plugin_setup_menu(){ add_menu_page( 'Test Plugin Page', 'Test Plugin', 'manage_options', 'test-plugin', 'swd_menu' ); } function swd_menu(){ echo "<h1>Hello World!</h1>"; } ?> You may think that it may be super hard, but it really is not.
All you have to do is create a new folder in the plugins directory. Example: /wp-content/plugins/yoursitename-plugin/ Open a blank file and save it as “yoursitename-plugin.php” Put the following code in the file: <?php /* Plugin Name: Site Plugin for example.com Description: Site specific code changes for example.com */ /* Start Adding Functions Below this Line */
// this is widget code /* Stop Adding Functions Below this Line */ ?> Now upload this file into the folder you created in the plugins directory. Then simply activate the plugin. <end node> 5P9i0s8y19Z dt= <node>backupWordpress 2 [Resolved] 3.4.3 update getting incorrect root directory Adding define( 'HMBKP_ROOT', dirname( __FILE__ )); to wp-config.php seems to fix the issue for me, thanks. <end node> 5P9i0s8y19Z dt= <node>Contact form 2 http://www.sitepoint.com/build-your-own-wordpress-contact-form-plugin-in-5-minutes/ short codes <HEADER> <H1>Build Your Own WordPress Contact Form Plugin in 5 Minutes</H1> <DIV> <FIGURE> <A href="http://www.sitepoint.com/author/acollins/"> <IMG src="http://1.gravatar.com/avatar/75eb5abf4f342e434c23fb0216631d3e?s=96&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D96&r=G"> </A> </FIGURE> <DIV> <DIV> <A href="http://www.sitepoint.com/author/acollins/">Agbonghama Collins</A> </DIV> </DIV> </DIV> <DIV> <P>Published <time>July 23, 2014</time> </P> </DIV> <DIV> <!-- make sure to update trackTweetsAndSubscriptions in scripts.js if the Tweet button DOM path changes in the future --> <A href="https://twitter.com/share?text=Build+Your+Own+WordPress+Contact+Form+Plugin+in+5+Minutes&via=sitepointdotcom"> <I> </I> Tweet </A> <!-- make sure to update trackTweetsAndSubscriptions in scripts.js if the Subscribe button DOM path changes in the future --> <A href="https://confirmsubscription.com/h/y/1FD5B523FA48AA2B"> <!--<i> </i>--> Subscribe </A> </DIV> </HEADER> <SECTION> <P>Most websites are typically designed to comply with standard web practices by including a dedicated page where a contact form is located. This provides visitors with an easy way to reach out to the site owner.</P> <P>In simple terms, a contact form has a set of questions and fields which are filled in by a visitor. The information is usually automatically sent via email to the site administrator or another nominated email account. It is worth noting that this email address isn’t displayed to visitors, so using a contact form typically reduces email spam from bots that harvest naked email addresses on the Internet. Contact forms play a very important role on a website, where they are used for collecting feedback, enquiries and other data from users.</P> <P>If your website is powered by WordPress, there are numerous plugins that seamlessly integrate a <STRONG>contact form</STRONG> on your website.</P> <P>In this article, I will provide a list of some free WordPress contact form plugins. I will also discuss why you should consider rolling your own contact form. Then, I will provide you with a short tutorial showing you how to build your own WordPress contact form plugin.</P> <H2>WordPress Contact Form Plugins</H2> <P>Before we get started, we’re going to go over a few of the popular free contact form plugins available in the <A href="https://wordpress.org/plugins/">WordPress Plugin Directory</A>. These are great to use, but even better to learn from when you’re getting started building your own plugins.</P> <P>Below are some of the most highly rated free contact form plugins for WordPress:</P> <OL> <LI> <P> <A href="http://wordpress.org/plugins/contact-form-7/">Contact Form 7</A> – This is the second <A href="http://wordpress.org/plugins/browse/popular/">most popular plugin</A> with over 18 million downloads, it could almost be considered as the de facto contact form plugin for a WordPress website. Contact Form 7 can manage multiple contact forms and you can customize the form and the email contents with simple markup. The form features include Ajax-powered submission, CAPTCHA, Akismet spam filtering and lots more.</P> </LI> <LI> <P> <A href="https://wordpress.org/plugins/contact-form-to-email/">Contact Form to Email</A> – This plugin not only creates contact forms and sends the data to a specified email address it also saves the contact form data into a database, providing printable reports and the option to export the selected data to CSV/Excel file.</P> </LI> <LI> <P> <A href="http://wordpress.org/plugins/formget-contact-form/">FormGet Contact Form</A> – An easy online drag and drop contact form builder tool. All you need to do is click on the fields that you want in your form, and within few seconds your contact form is ready.</P> </LI> <LI> <P> <A href="http://wordpress.org/plugins/contact-form-plugin/">Bestwebsoft Contact Form</A> – Allows you to implement a feedback form to a web page or a post effortlessly. It is extremely easy, and you won’t require any additional settings, even though there are some available to play with.</P> </LI> </OL> <H2>Why Roll Your Own Contact Form Plugin?</H2> <H3>Becoming a Better Developer</H3> <P>Developing your own WordPress plugin helps you better understand how WordPress works ‘under the hood’ which can help you to become a more experienced web developer. While there are tens of thousands of plugins in the WordPress Plugin Directory to use, being able to modify and extend other plugins is a very useful skill.</P> <H3>Building a Better Form</H3> <P>Many WordPress contact form plugins are bloated. They include many features that you may never use. Heavy usage of JavaScript and CSS files are also common in some of the standard contact form plugins. This increases the number of HTTP requests which adversely affects WordPress performance.</P> <P>According to <A href="http://developer.yahoo.com/performance/rules.html#num_http">Yahoo’s performance rules</A>:</P> <BLOCKQUOTE> <P>80% of the end-user response time is spent on the front-end. Most of this time is tied up in downloading all the components in the page: images, stylesheets, scripts, Flash, etc. Reducing the number of components in turn reduces the number of HTTP requests required to render the page. This is the key to faster pages.</P> </BLOCKQUOTE> <P>If you are like me, and you desire a simple contact form plugin that just works, read on. I’ll guide you through the simple process of develop your own plugin so you can kiss goodbye bloated plugins. In this example no extra CSS and JavaScript files are required, the <A href="http://www.sitepoint.com/client-side-form-validation-html5/">validation done using HTML5</A>.</P> <H2>Contact Form Plugin Development</H2> <P>In five minutes, you will learn how to develop a simple WordPress contact form, that’s a promise!</P> <P>Ready? Set? Go!</P> <P>All WordPress pluigns are PHP files, located in the <CODE>/wp-content/plugins/ directory</CODE>. In our example, the file will be called <CODE>sp-form-example.php</CODE>. I assume you’re comfortable with connecting to your server using FTP/SFTP/SCP or SSH.</P> <P>If you want to follow along, simply create a file called <CODE>sp-form-example.php</CODE> (the final complete example will be available at the end of the article):</P> <DIV> <DIV> <TABLE> <TBODY> <TR> <TD> <DIV>1</DIV> <DIV>2</DIV> <DIV>3</DIV> <DIV>4</DIV> <DIV>5</DIV> <DIV>6</DIV> <DIV>7</DIV> <DIV>8</DIV> <DIV>9</DIV> <DIV>10</DIV> <DIV>11</DIV> <DIV>12</DIV> <DIV>13</DIV> </TD> <TD> <DIV> <DIV> <CODE class="php plain"><?php</CODE> </DIV> <DIV> <CODE class="php comments">/*</CODE> </DIV> <DIV> <CODE class="php comments">Plugin Name: Example Contact Form Plugin</CODE> </DIV> <DIV> <CODE class="php comments">Plugin URI: <A href="http://example.com/">http://example.com</A> </CODE> </DIV> <DIV> <CODE class="php comments">Description: Simple non-bloated WordPress Contact Form</CODE> </DIV> <DIV> <CODE class="php comments">Version: 1.0</CODE> </DIV> <DIV> <CODE class="php comments">Author: Agbonghama Collins</CODE> </DIV> <DIV> <CODE class="php comments">Author URI: <A href="http://w3guy.com/">http://w3guy.com</A> </CODE> </DIV> <DIV> <CODE class="php comments">*/</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">//</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">// the plugin code will go here..</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">//</CODE> </DIV> <DIV> <CODE class="php plain">?></CODE> </DIV> </DIV> </TD> </TR> </TBODY> </TABLE> </DIV> </DIV> <P>Next, we add the function <CODE>html_form_code()</CODE> that contains the contact form HTML:</P> <DIV> <DIV> <TABLE> <TBODY> <TR> <TD> <DIV>1</DIV> <DIV>2</DIV> <DIV>3</DIV> <DIV>4</DIV> <DIV>5</DIV> <DIV>6</DIV> <DIV>7</DIV> <DIV>8</DIV> <DIV>9</DIV> <DIV>10</DIV> <DIV>11</DIV> <DIV>12</DIV> <DIV>13</DIV> <DIV>14</DIV> <DIV>15</DIV> <DIV>16</DIV> <DIV>17</DIV> <DIV>18</DIV> <DIV>19</DIV> <DIV>20</DIV> <DIV>21</DIV> </TD> <TD> <DIV> <DIV> <CODE class="php keyword">function</CODE> <CODE class="php plain">html_form_code() {</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<form action="'</CODE> <CODE class="php plain">. esc_url( </CODE> <CODE class="php variable">$_SERVER</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">'REQUEST_URI'</CODE> <CODE class="php plain">] ) . </CODE> <CODE class="php string">'" method="post">'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'Your Name (required) <br />'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<input type="text" name="cf-name" pattern="[a-zA-Z0-9 ]+" value="'</CODE> <CODE class="php plain">. ( isset( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">["cf-name</CODE> <CODE class="php string">"] ) ? esc_attr( $_POST["</CODE> <CODE class="php plain">cf-name</CODE> <CODE class="php string">"] ) : '' ) . '"</CODE> <CODE class="php plain">size=</CODE> <CODE class="php string">"40"</CODE> <CODE class="php plain">/>';</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'Your Email (required) <br />'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<input type="email" name="cf-email" value="'</CODE> <CODE class="php plain">. ( isset( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">["cf-email</CODE> <CODE class="php string">"] ) ? esc_attr( $_POST["</CODE> <CODE class="php plain">cf-email</CODE> <CODE class="php string">"] ) : '' ) . '"</CODE> <CODE class="php plain">size=</CODE> <CODE class="php string">"40"</CODE> <CODE class="php plain">/>';</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'Subject (required) <br />'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<input type="text" name="cf-subject" pattern="[a-zA-Z ]+" value="'</CODE> <CODE class="php plain">. ( isset( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">["cf-subject</CODE> <CODE class="php string">"] ) ? esc_attr( $_POST["</CODE> <CODE class="php plain">cf-subject</CODE> <CODE class="php string">"] ) : '' ) . '"</CODE> <CODE class="php plain">size=</CODE> <CODE class="php string">"40"</CODE> <CODE class="php plain">/>';</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'Your Message (required) <br />'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<textarea rows="10" cols="35" name="cf-message">'</CODE> <CODE class="php plain">. ( isset( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-message"</CODE> <CODE class="php plain">] ) ? esc_attr( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-message"</CODE> <CODE class="php plain">] ) : </CODE> <CODE class="php string">''</CODE> <CODE class="php plain">) . </CODE> <CODE class="php string">'</textarea>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p><input type="submit" name="cf-submitted" value="Send"/></p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</form>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php plain">}</CODE> </DIV> </DIV> </TD> </TR> </TBODY> </TABLE> </DIV> </DIV> <P>Basic validation was added to the form via the <CODE>pattern</CODE> input attribute.</P> <P>The RegEX in the contact form does the following field validation:</P> <UL> <LI> <P> <STRONG>[a-zA-Z0-9 ]</STRONG>: only letters, spaces and numbers allowed in the name field; special symbols are deemed invalid.</P> </LI> <LI> <P> <STRONG>[a-zA-Z ]</STRONG>: only letters and spaces are allowed in the subject field.</P> </LI> <LI> <P>The <CODE>email</CODE> form control validates the email field hence there is no need for a pattern attribute.</P> </LI> </UL> <P>For more information on how this works, read my article on <A href="http://www.sitepoint.com/client-side-form-validation-html5/">Client-Side Form Validation with HTML5</A> to understand how the pattern attribute assists with form validation.</P> <H3>Hurry Up!</H3> <P>Okay, how many minutes do we have left? Four minutes! We still have time to get this over with.</P> <P>The function <CODE>deliver_mail()</CODE> sanitizes the form data and sends the mail to the WordPress administrator’s email address.</P> <DIV> <DIV> <TABLE> <TBODY> <TR> <TD> <DIV>1</DIV> <DIV>2</DIV> <DIV>3</DIV> <DIV>4</DIV> <DIV>5</DIV> <DIV>6</DIV> <DIV>7</DIV> <DIV>8</DIV> <DIV>9</DIV> <DIV>10</DIV> <DIV>11</DIV> <DIV>12</DIV> <DIV>13</DIV> <DIV>14</DIV> <DIV>15</DIV> <DIV>16</DIV> <DIV>17</DIV> <DIV>18</DIV> <DIV>19</DIV> <DIV>20</DIV> <DIV>21</DIV> <DIV>22</DIV> <DIV>23</DIV> <DIV>24</DIV> <DIV>25</DIV> <DIV>26</DIV> </TD> <TD> <DIV> <DIV> <CODE class="php keyword">function</CODE> <CODE class="php plain">deliver_mail() {</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">// if the submit button is clicked, send the email</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php keyword">if</CODE> <CODE class="php plain">( isset( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">'cf-submitted'</CODE> <CODE class="php plain">] ) ) {</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">// sanitize form values</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$name</CODE> <CODE class="php plain">= sanitize_text_field( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-name"</CODE> <CODE class="php plain">] );</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$email</CODE> <CODE class="php plain">= sanitize_email( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-email"</CODE> <CODE class="php plain">] );</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$subject</CODE> <CODE class="php plain">= sanitize_text_field( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-subject"</CODE> <CODE class="php plain">] );</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$message</CODE> <CODE class="php plain">= esc_textarea( </CODE> <CODE class="php variable">$_POST</CODE> <CODE class="php plain">[</CODE> <CODE class="php string">"cf-message"</CODE> <CODE class="php plain">] );</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">// get the blog administrator's email address</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$to</CODE> <CODE class="php plain">= get_option( </CODE> <CODE class="php string">'admin_email'</CODE> <CODE class="php plain">);</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php variable">$headers</CODE> <CODE class="php plain">= </CODE> <CODE class="php string">"From: $name <$email>"</CODE> <CODE class="php plain">. </CODE> <CODE class="php string">"\\r\\n"</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php comments">// If email has been process for sending, display a success message</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php keyword">if</CODE> <CODE class="php plain">( wp_mail( </CODE> <CODE class="php variable">$to</CODE> <CODE class="php plain">, </CODE> <CODE class="php variable">$subject</CODE> <CODE class="php plain">, </CODE> <CODE class="php variable">$message</CODE> <CODE class="php plain">, </CODE> <CODE class="php variable">$headers</CODE> <CODE class="php plain">) ) {</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<div>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'<p>Thanks for contacting me, expect a response soon.</p>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'</div>'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">} </CODE> <CODE class="php keyword">else</CODE> <CODE class="php plain">{</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php functions">echo</CODE> <CODE class="php string">'An unexpected error occurred'</CODE> <CODE class="php plain">;</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">}</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">}</CODE> </DIV> <DIV> <CODE class="php plain">}</CODE> </DIV> </DIV> </TD> </TR> </TBODY> </TABLE> </DIV> </DIV> <P>The sanitation of the form data is done by the following WordPress internal functions:</P> <UL> <LI> <P> <CODE>sanitize_text_field()</CODE>: Sanitize the data from user input.</P> </LI> <LI> <P> <CODE>sanitize_email()</CODE>: Strips out all characters that are not allowable in an email.</P> </LI> <LI> <P> <CODE>esc_textarea()</CODE>: Escape the <EM>message</EM> text area values.</P> </LI> </UL> <P>The code <CODE>get_option( 'admin_email' )</CODE> programmatically retrieves the WordPress administrator’s email address from the database where the email will be delivered to.</P> <P>Don’t want the contact form to send the mail to admin? Simply set the variable <CODE>$to</CODE> to the desired email address.</P> <P>If the email has successfully been processed without any errors by the function <CODE>wp_mail()</CODE> , the text <EM>Thanks for contacting me, expect a response soon</EM> will be shown, otherwise <EM>An unexpected error occurred</EM> is displayed.</P> <H3>1 Minute and 30 Seconds Left</H3> <P>The function <CODE>cf_shortcode()</CODE> is the callback function that is called when the contact form shortcode <CODE>[sitepoint_contact_form]</CODE> is active.</P> <DIV> <DIV> <TABLE> <TBODY> <TR> <TD> <DIV>1</DIV> <DIV>2</DIV> <DIV>3</DIV> <DIV>4</DIV> <DIV>5</DIV> <DIV>6</DIV> <DIV>7</DIV> </TD> <TD> <DIV> <DIV> <CODE class="php keyword">function</CODE> <CODE class="php plain">cf_shortcode() {</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">ob_start();</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">deliver_mail();</CODE> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php plain">html_form_code();</CODE> </DIV> <DIV> </DIV> <DIV> <CODE class="php spaces"> </CODE> <CODE class="php keyword">return</CODE> <CODE class="php plain">ob_get_clean();</CODE> </DIV> <DIV> <CODE class="php plain">}</CODE> </DIV> </DIV> </TD> </TR> </TBODY> </TABLE> </DIV> </DIV> <P>The above functions calls the <CODE>html_form_code()</CODE> and <CODE>deliver_mail()</CODE> functions to display the contact form HTML form and validate the form data respectively.</P> <P>Finally, the shortcode <CODE>[sitepoint_contact_form]</CODE> is registered to WordPress. So simply add:</P> <DIV> <DIV> <TABLE> <TBODY> <TR> <TD> <DIV>1</DIV> </TD> <TD> <DIV> <DIV> <CODE class="php plain">add_shortcode( </CODE> <CODE class="php string">'sitepoint_contact_form'</CODE> <CODE class="php plain">, </CODE> <CODE class="php string">'cf_shortcode'</CODE> <CODE class="php plain">);</CODE> </DIV> </DIV> </TD> </TR> </TBODY> </TABLE> </DIV> </DIV> <H3>3, 2, 1… Time’s Up!</H3> <P>Congratulations, we have successfully developed our own WordPress contact form plugin and I have fulfilled my earlier promise.</P> <P>Now, to use this plugin on your website, simply activate it in under the ‘Plugins’ section of your WordPress dashboard, then create a post or page and then simply add the shortcode where you want the form to appear <CODE>[sitepoint_contact_form]</CODE>.</P> <P>If you then preview the page and you should see the contact form displayed as shown below.</P> </SECTION> <end node> 5P9i0s8y19Z dt= <node>shortcodes 2 <?php /* * Plugin Name: WordPress ShortCode * Description: Create your WordPress shortcode. * Version: 1.0 * Author: InkThemes * Author URI: https://inkthemes.com */ // Example 1 : WP Shortcode to display form on any page or post. function form_creation(){ $imagedirectory="../stylists/"; $dir = opendir($imagedirectory); while ($file = readdir($dir)){ //for ($i=1; $i<=500; $i++){ // $file = readdir($dir); $fullpath=$current_dir.$file; $fullpath2=$current_dir."/stylists/large/".$file; /* $filedate=date('Y-m-j', filemtime($fullpath)); if(trim($file)!='.' && trim($file)!='..'){ $fsize=filesize($fullpath)/1000; $fsize=(int)$fsize;$fsize=$fsize/1000; $message[]=$filedate."|".$file."@".$fsize; } */ echo "<div style='float:left;padding:20px;'><a href='$fullpath2'><img src='$fullpath'><br>$file</a></div>"; } closedir($dir); } add_shortcode('test', 'form_creation'); ?> [test] in whatever page you want <end node> 5P9i0s8y19Z dt= <node>WIDGET 1 <?php /** * Plugin Name: A simple Widget * Description: A widget that displays authors name. * Version: 0.1 * Author: Bilal Shaheen * Author URI: http://gearaffiti.com/about */ add_action( 'widgets_init', 'my_widget' ); function my_widget() { register_widget( 'SWDWidget' ); } class SWDWidget extends WP_Widget { function SWDWidget() { $widget_ops = array( 'classname' => 'example', 'description' => __('A widget that displays SWD garbage ', 'example') );
function widget( $args, $instance ) { extract( $args ); //Our variables from the widget settings. $title = apply_filters('widget_title', $instance['title'] ); $name = $instance['name']; $show_info = isset( $instance['show_info'] ) ? $instance['show_info'] : false; echo $before_widget; // Display the widget title if ( $title ) echo $before_title . $title . $after_title; //Display the name on website if ( $name ) printf( '<p>' . __('Hey their Sailor! My name is %1$s.', 'example1') . '</p>', $name );
if ( $show_info ) printf( $name );
echo $after_widget; } //Update the widget
function update( $new_instance, $old_instance ) { $instance = $old_instance; //Strip tags from title and name to remove HTML $instance['title'] = strip_tags( $new_instance['title'] ); $instance['name'] = strip_tags( $new_instance['name'] ); $instance['show_info'] = $new_instance['show_info']; return $instance; }
//Checkbox. <p> <input class="checkbox" type="checkbox" <?php checked( $instance['show_info'], true ); ?> id="<?php echo $this->get_field_id( 'show_info' ); ?>" name="<?php echo $this->get_field_name( 'show_info' ); ?>" /> <label for="<?php echo $this->get_field_id( 'show_info' ); ?>"><?php _e('Display info publicly?', 'example'); ?></label> </p> <?php } } ?> <end node> 5P9i0s8y19Z dt= <node>example 2 [code] Before we get started, it would be best if you create a site-specific plugin where you will be pasting widget code. You can also paste it in your theme’s functions.php file but a site-specific plugin is better. In this tutorial, we will create a simple widget that just greets visitors. Take a look at this code and then paste it in your site-specific plugin to see it in action. 01 // Creating the widget 02 class wpb_widget extends WP_Widget { 03 04 function __construct() { 05 parent::__construct( 06 // Base ID of your widget 07 'wpb_widget', 08 09 // Widget name will appear in UI 10 __('WPBeginner Widget', 'wpb_widget_domain'), 11 12 // Widget description 13 array( 'description' => __( 'Sample widget based on WPBeginner Tutorial', 'wpb_widget_domain' ), ) 14 ); 15 } 16 17 // Creating widget front-end 18 // This is where the action happens 19 public function widget( $args, $instance ) { 20 $title = apply_filters( 'widget_title', $instance['title'] ); 21 // before and after widget arguments are defined by themes 22 echo $args['before_widget']; 23 if ( ! empty( $title ) ) 24 echo $args['before_title'] . $title . $args['after_title']; 25 26 // This is where you run the code and display the output 27 echo __( 'Hello, World!', 'wpb_widget_domain' ); 28 echo $args['after_widget']; 29 } 30 31 // Widget Backend 32 public function form( $instance ) { 33 if ( isset( $instance[ 'title' ] ) ) { 34 $title = $instance[ 'title' ]; 35 } 36 else { 37 $title = __( 'New title', 'wpb_widget_domain' ); 38 } 39 // Widget admin form 40 ?> 41 <p> 42 <label for="<?php echo $this->get_field_id( 'title' ); ?>"><?php _e( 'Title:' ); ?></label> 43 <input class="widefat" id="<?php echo $this->get_field_id( 'title' ); ?>" name="<?php echo $this->get_field_name( 'title' ); ?>" type="text" value="<?php echo esc_attr( $title ); ?>" /> 44 </p> 45 <?php 46 } 47 48 // Updating widget replacing old instances with new 49 public function update( $new_instance, $old_instance ) { 50 $instance = array(); 51 $instance['title'] = ( ! empty( $new_instance['title'] ) ) ? strip_tags( $new_instance['title'] ) : ''; 52 return $instance; 53 } 54 } // Class wpb_widget ends here 55 56 // Register and load the widget 57 function wpb_load_widget() { 58 register_widget( 'wpb_widget' ); 59 } 60 add_action( 'widgets_init', 'wpb_load_widget' ); Now go to Appearance » Widgets, drag and drop WPBeginner Widget in your sidebar to see this custom widget in action. Simple wasn’t it? First we created a custom widget. Then we defined what that widget does and how to display the widget back-end. Then we defined how to handle changes made to widget. Lastly, we registered and loaded the widget. Now there are a few things that you might want to ask. For example, what wpb_text_domain does? WordPress uses gettext to handle translation and localization. This wpb_text_domain and __e tells gettext to make a string available for translation. See how you can find translation ready WordPress themes. We hope this tutorial helped you learn how to create a custom WordPress widget. Let us know what widgets you are creating, by leaving a comment below. ===================================== // used on the windsor hair shoppe <?php /* Plugin Name: Social Media Icons Plugin URI: http://softwarewebdesign.com Description: Adds Icons. Version: 1.0 Author: Software Web Design Author URI: http://softwarewebdesign.com License: GPL2 */ class WP_Widget_SocialMedia extends WP_Widget {
// The widget construct. Mumbo-jumbo that loads our code. function WP_Widget_SocialMedia() { $widget_ops = array( 'classname' => 'widget_SocialMedia', 'description' => __( "Social Media Icons" ) ); $this->WP_Widget('SocialMedia', __('SocialMedia'), $widget_ops); } // End function WP_Widget_SocialMedia
// This code displays the widget on the screen. function widget($args, $instance) { extract($args); echo $before_widget; if(!empty($instance['title'])) { echo $before_title . $instance['title'] . $after_title; } echo "<p><a href='http://www.facebook.com/pages/Windsor-Hair-Shoppe/469480233075402'><img src='".site_url()."/images/facebook.jpg'></a></p>"; echo $after_widget; } // End function widget.
// Updates the settings. function update($new_instance, $old_instance) { return $new_instance; } // End function update // The admin form. function form($instance) { echo '<div id="bareBones-admin-panel">'; echo '<label for="' . $this->get_field_id("title") .'">Social Media Title:</label>'; echo '<input type="text" class="widefat" '; echo 'name="' . $this->get_field_name("title") . '" '; echo 'id="' . $this->get_field_id("title") . '" '; echo 'value="' . $instance["title"] . '" />'; echo '<p>This widget will display Social Media Icons below.</p>'; echo '</div>'; } // end function form
$options = get_option('simple_widget'); if ( !isset($options[$number]) ) return; $title = $options[$number]['title']; // single value $text = $options[$number]['text']; // single value $check = $options[$number]['check']; // multi value $radio = $options[$number]['radio']; // single value $select = $options[$number]['select']; // single value $textarea = $options[$number]['textarea']; // single value echo $before_widget; // start widget display code */ ?>
<?php echo "LINE 1"; // end widget display code
}
function jad_simple_widget_control($widget_args) { global $wp_registered_widgets; static $updated = false; /* if ( is_numeric($widget_args) ) $widget_args = array( 'number' => $widget_args ); $widget_args = wp_parse_args( $widget_args, array( 'number' => -1 ) ); extract( $widget_args, EXTR_SKIP ); $options = get_option('simple_widget'); if ( !is_array($options) ) $options = array(); if ( !$updated && !empty($_POST['sidebar']) ) { $sidebar = (string) $_POST['sidebar']; $sidebars_widgets = wp_get_sidebars_widgets(); if ( isset($sidebars_widgets[$sidebar]) ) $this_sidebar =& $sidebars_widgets[$sidebar]; else $this_sidebar = array(); foreach ( (array) $this_sidebar as $_widget_id ) { if ( 'jad_simple_widget' == $wp_registered_widgets[$_widget_id]['callback'] && isset($wp_registered_widgets[$_widget_id]['params'][0]['number']) ) { $widget_number = $wp_registered_widgets[$_widget_id]['params'][0]['number']; if ( !in_array( "simple-widget-$widget_number", $_POST['widget-id'] ) ) // the widget has been removed. unset($options[$widget_number]); } } foreach ( (array) $_POST['simple-widget'] as $widget_number => $simple_widget ) { if ( !isset($simple_widget['title']) && isset($options[$widget_number]) ) // user clicked cancel continue; $title = strip_tags(stripslashes($simple_widget['title'])); $text = strip_tags(stripslashes($simple_widget['text_value'])); $check = $simple_widget['check_array']; $radio = $simple_widget['radio_value']; $select = $simple_widget['select_value']; $textarea = $simple_widget['textarea_value']; // Pact the values into an array $options[$widget_number] = compact( 'title', 'text', 'check', 'radio', 'select', 'textarea' ); } update_option('simple_widget', $options); $updated = true; } if ( -1 == $number ) { // if it's the first time and there are no existing values $title = ''; $text = ''; $check = ''; $radio = ''; $select = ''; $textarea = ''; $number = '%i%'; } else { // otherwise get the existing values $title = attribute_escape($options[$number]['title']); $text = attribute_escape($options[$number]['text']); // attribute_escape used for security $check = $options[$number]['check']; $radio = $options[$number]['radio']; $select = $options[$number]['select']; $textarea = format_to_edit($options[$number]['textarea']); } print_r($options[$number]); */ ECHO "lINE2"; }
$options = get_option('simple_widget'); if ( !isset($options[$number]) ) return; $title = $options[$number]['title']; // single value $text = $options[$number]['text']; // single value $check = $options[$number]['check']; // multi value $radio = $options[$number]['radio']; // single value $select = $options[$number]['select']; // single value $textarea = $options[$number]['textarea']; // single value
if ( !$id ) { wp_register_sidebar_widget( 'simple-widget-1', $name, 'jad_simple_widget', $widget_ops, array( 'number' => -1 ) ); wp_register_widget_control( 'simple-widget-1', $name, 'jad_simple_widget_control', $control_ops, array( 'number' => -1 ) ); } } add_action('init', jad_simple_widget_register, 1); ?> <end node> 5P9i0s8y19Z dt= <node>new area 2 http://howtomatter.com/how-to-create-a-new-widget-area/ I’ve found it helpful in certain situations to have widgetized areas (that is, places I can drag/drop widgets into from the Appearance>Widget menu) other than the standard Sidebar 1 and Sidebar 2. Certain themes have this built in, but it’s not terribly difficult to create them yourself, so I thought I’d write up a quick tutorial. What is a new widget area? As always, head on over to my test site to see an example of what I’m talking about. Scroll down to the footer and you’ll see a light red area with 2 boxes in it that say something along the lines of ‘this is your new sidebar’. In case that site/example is gone by the time you’re reading this, here’s a picture of it. New Sidebar for Widgets click to enlarge So what I’ve done is created 2 new sidebar areas and placed them, in this case, after the content box. Widgets can be dragged into these sidebars in the same way as you’d add widgets to the default sidebars – by going to the Appearance>Widgets menu and dragging them into the appropriate place. More about that in a minute. How to create a new widget area Per my typical approach, I’m just going to give you the code, and the instructions on where/how to place it, and if you have questions beyond this or want to know more about how/why it works, you can leave a comment or reach out to me individually…cool? Okay, so the first thing we need to do is register the new sidebars. This is done by going to the Thesis>Custom File Editor menu, and from the drop down menu at the top of that page, choose ‘custom_functions.php’ and click the ‘edit selected file’ button to its right. Once there, scroll down to the very bottom and paste the following code: /**************************************************************** * REGISTER NEW SIDEBARS ****************************************************************/ $args = array( 'name' => 'New Sidebar %d', 'before_widget' => '<li id="%1$s" class="widget %2$s">', 'after_widget' => '</li>', 'before_title' => '<h3>', 'after_title' => '</h3>' ); register_sidebars( 2, $args ); /**************************************************************** * CREATES NEW SIDEBARS ****************************************************************/ function new_sidebars(){ ?> <div id="new-sidebars"> <div id="new-sidebar-1"> <ul class="sidebar_list"> <?php if (!dynamic_sidebar('New Sidebar 1') ) { ?> <li class="widget"> <div class="widget_box"> <h3><?php _e('New Sidebar 1', 'thesis'); ?></h3> <p>This is your new sidebar. Add widgets here from your WP Dashboard just like normal.</p> </div> </li> <?php } ?> </ul> </div> <div id="new-sidebar-2"> <ul class="sidebar_list"> <?php if (!dynamic_sidebar('New Sidebar 2') ) { ?> <li class="widget"> <div class="widget_box"> <h3><?php _e('New Sidebar 2', 'thesis'); ?></h3> <p>This is your new sidebar. Add widgets here from your WP Dashboard just like normal.</p> </div> </li> <?php } ?> </ul> </div> </div> <?php } add_action('thesis_hook_after_content_box', 'new_sidebars'); So what that has done is created 2 new sidebars and placed them at the bottom of your content box…well, after it, actually. If you were to look at your site now, you’d see them placed one on top of the other…not what we want in this case, but we’ll remedy that with a little CSS styling. Styling your newly created sidebars Now that these widgetized sidebars are created, we need to style them to look how we want them to look. So, go to the Thesis>Custom File Editor menu, and make sure it says ‘custom.css’ in the drop down menu. Scroll down to the bottom (or to the appropriate place if you’ve got this file organized) and paste the following code: /*********************************** NEW WIDGET STYLING ***********************************/ #new-sidebars { float:left; width:100%; background-color:#ffaaaa; border-bottom:.1em solid #000000; } #new-sidebar-1 { float:left; margin-left:7em; width:40%; } #new-sidebar-2 { float:left; margin-left:2em; width:40%; } If everything was done properly, you should now have two sidebars after your content box that look very similar to/the same as what’s pictured above. Add widgets to your new sidebarsAnd if you go to your Appearance>Widgets menu, you should now see 2 new boxes in the right column where you can drag widgets. Just click the drop down arrow to expand them (pictured here) and you can begin dragging widgets into them…text, pictures, recent post widgets, whatever you like. What if I want my widgetized sidebars to appear somewhere else? Okay, so what if you don’t want these new widget areas to appear below your content box? No problem, you just need to ‘hook’ them to the area you do want them in. Look at the 1st bit of code above (that went into your custom_functions.php file). The last line says “add action…”, and you see ‘thesis_hook_after_content_box’. That ‘after_content_box is the hook we used and it tells Thesis to place it in that specific area. Well, Thesis has lots of hooks available (a hook essentially just refers to a different place on your site you can ‘hang’ code). Check out this visual reference and click on one of the thumbnail images you see there. As you’ll see, the hooks are all over the place and they each refer to a different spot on the page. Choose where you want your widgetized sidebars to go and replace ‘after_content_box’ in the above code with the hook you want. Of course, that will require you to style your sidebars differently because the size of the space/hook you’re placing them in/on will determine how you style them. If you decide to do that, leave me a comment and I’ll show you how to do it. Things to keep in mind We registered/created just 2 widgetized sidebars. If you want more, that’s totally doable and it’s a matter of a few tweaks to the above code. Comment me if you would like to learn how to do so. Depending on what widget(s) you drop into these newly created sidebars, your styling (CSS) may need to be altered (an image, for example, may be taller than, say, a list of links, etc), so if you run into an issue where it just doesn’t look right, comment me. Alright, so that wraps things up. If anything is unclear or doesn’t work or if you need some additional support, please holler. And of course, if you’re at your wit’s end and want to hire me to build you a WordPress site or provide some WordPress Coaching, please do. Cheers… ========================================================= http://www.studiograsshopper.ch/code-snippets/how-to-add-a-widgetised-area-in-a-wordpress-theme/ How to add a Widgetised area in a WordPress theme July 11, 2009 26 Comments Darling, I'm not in the mood to go dancing. Let's stay home and code widgets instead! Darling, I'm not in the mood to go dancing. Let's stay home and code widgets instead! Here’s a tutorial to show you how to add a widget to a theme template file. Most themes these days come with built-in widget support, most commonly in the sidebar, but also sometimes in other parts of the theme such as the header, homepage or single post pages. In this tutorial I show you how to add a widget area to single post pages, and how to use the new widget area to display an advert on every single post page. Widget basics There are only four things we need to know in order to set up our new widget area: Which theme template file we need to edit The code for a Widget area, which we will place in the relevant theme template file How to “register” a Widget area, usually in the theme’s functions.php, in order to tell WordPress that the widget area exists and therefore allow you to add widgets to this widget area in the Dashboard. Add some styling to the widget area so that it fits in with the look of our site. Which template file? If you familiar with WordPress you will know that different pages on your site are produced by different theme template files. Which template file is used to display different views of your site is taken care of by WordPress, behind the scenes, and follows the Template Hierarchy coded into the WordPress Core files. In our example, we want to add the widget area to the single post page. Depending on your theme this will be either single.php or index.php. In our example, let’s assume it is index.php. Adding Widget code to the theme file Open up your index.php (take a backup first, just in case you need to put everything back to how it was) and decide where you want the new widget area to appear. Typically, your index.php file will be structured something like this (I’ve left out most of the code to keep things simple): 1 <?php get_header(); ?> 2 3 <div id="content"> 4 5 <div id="contentleft"> 6 7 <div class="postarea"> 8 9 <?php if (have_posts()) : while (have_posts()) : the_post(); ?> 10 11 // Loop stuff goes here eg Title, Date, Content etc 12 13 14 <!-- 15 <?php trackback_rdf(); ?> 16 --> 17 18 <?php endwhile; else: ?> 19 20 <p><?php _e('Sorry, no posts matched your criteria.'); ?></p><?php endif; ?> 21 22 </div><!-- End of postarea --> 23 24 <div class="postcomments"> 25 26 <?php comments_template('',true); ?> 27 28 </div> 29 30 </div> 31 32 <?php include(TEMPLATEPATH."/sidebar.php");?> 33 34 </div> 35 36 <?php get_footer(); ?> Your index.php file may not have the same DIV id name’s, but the structure should be similar: a DIV containing the Loop, in this case the postarea div (lines 7-22), and a DIV containing the call to the comments template, in this case the postcomments DIV (lines 24-28). We want to place our widget area between these two DIVs. That way, the widget content will display below the post content and above the comments section of the page. First, let’s add a new DIV and give it a new class called “widget-post”. You can name this class whatever you like, but choose something that has some meaning so that it’s easier to remember its purpose. Here’s our added code in lines 24-28: 1 </div><!-- End of postarea --> 2 3 <div class="widget-post"> 4 5 // Our widget stuff will go here... 6 7 </div> 8 9 <div class="postcomments"> 10 11 <?php comments_template('',true); ?> 12 13 </div> Now let’s add the code to display our new widget area. Here it is: 1 </div><!-- End of postarea --> 2 3 <div class="widget-post"> 4 5 <?php if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar('Post Widget') ) : ?> 6 <?php endif; ?> 7 8 </div> 9 10 <div class="postcomments"> 11 12 <?php comments_template('',true); ?> 13 14 </div> The new code we’ve added will pull in the widget content. In plain English, the code says – if widgets aren’t enabled in this theme or a widget area called “Post Widget” hasn’t been registered, do nothing. Therefore, if widgets are enabled and the widget area called “Post Widget” exists, the widget content will be displayed here. That’s it – no more work needed on the template file, and it’s time to add the “register” code in functions.php. Registering the widget in functions.php We now need to tell WordPress that it should enable a widget area called “Post Widget”. Open up your functions.php and look for a block of code something like this: 1 if ( function_exists('register_sidebars') ) { 2 register_sidebar(array('name'=>'Sidebar 1',)); 3 register_sidebar(array('name'=>'Sidebar 2',)); 4 register_sidebar(array('name'=>'Sidebar 3',)); 5 } This is the section of code that tells WordPress to enable widget areas. All we need to do is add a new line to this block of code to register our new widget area. Like this: 1 if ( function_exists('register_sidebars') ) { 2 register_sidebar(array('name'=>'Sidebar 1',)); 3 register_sidebar(array('name'=>'Sidebar 2',)); 4 register_sidebar(array('name'=>'Sidebar 3',)); 5 register_sidebar(array('name'=>'Post Widget',)); 6 } The important points to note are: We’ve added the extra line below the existing lines, but before the closing curly bracket. This ensures that our changes do not mess up the widgets you’ve already set up in your sidebar, for example. We’ve used exactly the same name “Post Widget” that we used in the new code added in index.php above. Another important point to remember is that the names of widget areas must be unique! Adding widgets to the new widget area Go to Dashboard>Appearance>Widgets and you should now see that your Post Widget appears in the righthand side of this screen. You can now drag a Text Widget to the Post Widget, and then add the code necessary to display your adverts within the Text Widget. For example, you can add Google Adsense code here, or affiliate code for a banner ad etc. View your site and check that on single post pages you now see your adverts between the post content and the comments. If it doesn’t appear, re-check the above steps in case you’ve missed something. If using a newly set up Google Adsense, remember that it can take a short while for the Adsense to populate. Styling the new widget area You will probably need to adjust your CSS to get the new widget area to fit in with the look of your site. The most important thing to do first is to add something like this to your style.css to define a style for the new widget-post DIV class which is the container for the widget area: 1 .widget-post { 2 background: #FFFFFF; 3 margin: 0px; 4 padding: 10px; 5 width: 600px; 6 } This is just a starting point – adjust the width, background, padding and margin to suit you. If you are using Google Adsense, your Google code will already include various styles based on the selections you made when setting up the Google Adsense. If you are posting your own HTML in the Text Widget you will probably have to add some styling to style.css to make the neceesary adjustments. If you are unfamiliar with CSS, check out the many great tutorials that are out there. And finally… As you can see, it isn’t too difficult to add a widget area to a theme file. This same method can be used elsewhere in your site to create other widget areas – just remember to name each one uniquely, and have fun ================================================= How to add widget area http://www.templatemonster.com/help/how-to-add-widget-area.html Author: Chris Diaz Posted on: April 7, 2011 Relation: Layout Complexity: Advanced Tags: widget, WordPress Rating: 3.3/5 (2 votes cast)
How to add widget area in WordPress This tutorial will show you how to create new widget area in WordPress. Any widget in WordPress template could be displayed in any place on the page. This could be done using WordPress widget areas.
To add widget area access to your WordPress installation folder. 1. Open ‘wp-content/themes/theme###’ folder. 2. View the functions.php file 3. Use search tool (CTRL+F) and search for ‘widget’. You can fund the following lines: Here you can see that widgets are defined in the sidebar-init.php file ? 1 2
//Widget and Sidebar require_once $includes_path . 'sidebar-init.php'; This line defines the $includes_path variable value. ? 1
$includes_path = TEMPLATEPATH . '/includes/'; These lines shows you that the widgets are defined in the wp-content/themes/theme###/includes/sidebar-init.php file 4. Open sidebar-init.php file. All widget areas are defined here. The following code is used to define wach area: ? 1 2 3 4 5 6 7 8 9
register_sidebar(array( 'name' => 'Sidebar 2', 'id' => 'sidebar-2', 'description' => __( 'Located at the right side of pages.'), 'before_widget' => '<div id="%1$s" class="widget %2$s">', 'after_widget' => '</div>', 'before_title' => '<h3 class="widget-title">', 'after_title' => '</h3>', )); To register new widget area copy the code above and paste it before the closing ‘}’ bracket Change the ‘name’, ‘id’ and ‘description’ values.
5. Now you can insert the widget area to any part of the template. Go back to the ‘wp-content/themes/theme###‘ folder. You can insert the area to any layout file: header.php footer.php single.php category.php index.php sidebar.php etc 6. Paste the following code to the required place to insert the widget area. ? 1
<?php if ( ! dynamic_sidebar( 'New Widget Area' ) ) :?><?php endif;?> Replace ‘New Widget Area’ with your widget area name. 7. If everything has been done correctly the new widget area would be available from the WordPress admin panel Appearance>Widgets (right column) .
Feel free to check the detailed video tutorial below: <end node> 5P9i0s8y19Z dt= <node>saved info 2 ?><div id="topbar" class="sidebar widget-area"> <?php genesis_structural_wrap( 'topbar' ); do_action( 'genesis_before_sidebar_widget_area' ); do_action( 'genesis_sidebar' ); do_action( 'genesis_after_sidebar_widget_area' ); genesis_structural_wrap( 'topbar', 'close' ); ?> </div> <!-- begin #featured-top --> <div id="featured-top"> <?php if (!dynamic_sidebar('Homepage Top')) : ?> <div class="widget">
<div class="wrap"> <p><?php _e("This is a widgeted area which is called Homepage.", 'genesis'); ?></p> </div><!-- end .wrap --> </div><!-- end .widget --> <?php endif; ?> </div><!-- end #featured-top --> <end node> 5P9i0s8y19Z dt= <node>simple one 2 <?php /* Plugin Name: My Widget Plugin URI: http://mydomain.com Description: My first widget Author: Me Version: 1.0 Author URI: http://mydomain.com */ // Block direct requests if ( !defined('ABSPATH') ) die('-1');
add_action( 'widgets_init', function(){ register_widget( 'My_Widget' ); }); /** * Adds My_Widget widget. */ class My_Widget extends WP_Widget { /** * Register widget with WordPress. */ function __construct() { parent::__construct( 'My_Widget', // Base ID __('My Widget', 'text_domain'), // Name array( 'description' => __( 'My first widget!', 'text_domain' ), ) // Args ); } /** * Front-end display of widget. * * @see WP_Widget::widget() * * @param array $args Widget arguments. * @param array $instance Saved values from database. */ public function widget( $args, $instance ) {
Learn How To Create Shortcodes in WordPress Plugin With Examples
\r\nFor the beginners, creating shortcode is sometimes not easy. But, WordPress makes it pretty simple to create your own shortcode by using WordPress shortcode function.\r\n
\r\n\r\nThere are two popular shortcode plugins.\r\n
\r\nTherefore, in this tutorial I am going to explain you how easily you can create your own shortcode using 3 simple examples. You will learn how to create WordPress shortcode plugin.\r\n\r\nExample 1 – I am going to create a WordPress plugin to display form on any page or post of the website.\r\n\r\nExample 2 – I am going to create a WordPress plugin to display text on any page or post of the website.\r\n\r\nExample 3 – I am going to create a WordPress plugin that helps to share pages or posts on Twitter.\r\n\r\n\r\n\r\n
Create Shortcodes in WordPress Plugin
\r\nWordPress offers a predefined shortcode function to create shortcode in WordPress plugin. For using shortcode function, you have to define a handler function that parse the shortcode and return some output.\r\n\r\nThen, you need to register a shortcode using add_shortcode() function.\r\n\r\nadd_shortcode( $shortcode_name, $handler_function);\r\n
\r\n
$shortcode_name – (required, string)It is a string that to be searched in the post.
\r\n
$handler_function – (required, callable) It is a hook to run when shortcode is found.
\r\n
\r\n\r\n\r\n \r\n\r\n\r\n\r\n\r\n\r\nNote: I have created a shortcode folder under the plugin folder of my WordPress where I have created a file named shortcode.php.\r\n
WordPress ShortCode Example 1 – Display Form On Pages/Posts
\r\nYou can create shortcode to display form on any page or post of the website. The below code includes-\r\n
\r\n
Plugin details
\r\n
form_creation() to create a form which includes form fields.
\r\n
add_shortcode() function which contain shortcode name test and calling of form_creation() function as parameters.
\r\n
\r\n
\r\n
\r\n<?php\r\n/*\r\n* Plugin Name: WordPress ShortCode\r\n* Description: Create your WordPress shortcode.\r\n* Version: 1.0\r\n* Author: InkThemes\r\n* Author URI: https://inkthemes.com\r\n*/\r\n\r\n// Example 1 : WP Shortcode to display form on any page or post.\r\nfunctionform_creation(){\r\n?>\r\n<form>\r\nFirst name:<inputtype=\"text\"name=\"firstname\"><br>\r\nLast name:<inputtype=\"text\"name=\"lastname\"><br>\r\nMessage:<textareaname=\"message\"> Enter text here...</textarea>\r\n</form>]\r\n<?php\r\n}\r\nadd_shortcode(\'test\',\'form_creation\');\r\n?>
\r\n
\r\n
Output
\r\nYou need to place WordPress shortcode within square brackets in order to represent it on any page or post of the website. As you can see in the below image, code word test enclosed within square brackets.\r\n
\r\nThis is how the form page appears on the front end.\r\n\r\n\r\n
WordPress Shortcode Example 2 – Display Text On Pages/Posts
\r\nYou can create shortcode to display text on any page or post of the website. The below code includes-\r\n
\r\n
Plugin details
\r\n
wp_first_shortcode() contain the text that you want to display in front end.
\r\n
add_shortcode() function contain shortcode name first and calling of wp_first_shortcode() function as parameters.
\r\n
\r\n
\r\n
\r\n\r\n<?php\r\n/*\r\n* Plugin Name: WordPress ShortCode\r\n* Description: Create your WordPress shortcode.\r\n* Version: 1.0\r\n* Author: InkThemes\r\n* Author URI: https://inkthemes.com\r\n*/\r\n\r\n// Example 2 : WP Shortcode to display text on page or post.\r\nfunctionwp_first_shortcode(){\r\necho\"Hello, This is your another shortcode!\";\r\n}\r\nadd_shortcode(\'first\',\'wp_first_shortcode\');\r\n\r\n?>\r\n\r\n
\r\n
\r\n
Output
\r\nYou can insert a shortcode with code word first enclosed with square brackets.\r\n\r\n\r\n\r\nThis is how the text display in the post on front end.\r\n\r\n\r\n
WordPress Shortcode Example 3 – Share Pages/Posts On Twitter
\r\nYou can create shortcode to share your pages or posts on Twitter. The below code includes-\r\n
\r\n
Plugin details
\r\n
ink_wp_shortcode() get the particular post or page that you want to share on Twitter.
\r\n
add_shortcode() function contain shortcode name twitter and calling of ink_wp_shortcode() function as parameters.
\r\n
\r\n
\r\n
\r\n\r\n<?php\r\n/*\r\n* Plugin Name: WordPress ShortCode\r\n* Description: Create your WordPress shortcode.\r\n* Version: 1.0\r\n* Author: InkThemes\r\n* Author URI: https://inkthemes.com\r\n*/\r\n\r\n// Example 3 : WP Shortcode to share post or page on Twitter.\r\nfunctionink_wp_shortcode($atts,$content=null)\r\n{\r\n$post_url=get_permalink($post->ID);\r\n$post_title=get_the_title($post->ID);\r\n$tweet= \'<astyle=\"color:blue; font-size: 20px;\"href=\"http://twitter.com/home/?status=Read\' . $post_title . \'at\' . $post_url . \'\">\r\n<b>Share on Twitter </b></a>\';\r\nreturn$tweet;\r\n}\r\nadd_shortcode(\'twitter\',\'ink_wp_shortcode\');\r\n?>\r\n\r\n
\r\n
\r\n
Output
\r\nYou can see in the below image, shortcode twitter is placed at the end of the post.\r\n\r\n\r\n\r\nYou can directly share the pages or posts on Twitter by click on the text Share on Twitter.\r\n\r\n\r\n
Conclusion
\r\nI hope this tutorial is helpful to you and make you understand the concept that you need to use while creating a WordPress shortcode for your own purpose. You can create as many as shortcode you want and use it wherever you want.\r\n\r\nMoreover, you can also watch the video tutorial for this post, just check it out.\r\n\r\nPlease do share your thoughts about the post and how much you find it useful to you.\r\n
\r\n\r\nLast Updated on: June 6, 2017\r\n\r\nUnder:Blog, WordPress\r\n\r\n
Learn How To Create Shortcodes in WordPress Plugin With Examples
\r\nFor the beginners, creating shortcode is sometimes not easy. But, WordPress makes it pretty simple to create your own shortcode by using WordPress shortcode function.\r\n
\r\n\r\nThere are two popular shortcode plugins.\r\n
\r\nTherefore, in this tutorial I am going to explain you how easily you can create your own shortcode using 3 simple examples. You will learn how to create WordPress shortcode plugin.\r\n\r\nExample 1 – I am going to create a WordPress plugin to display form on any page or post of the website.\r\n\r\nExample 2 – I am going to create a WordPress plugin to display text on any page or post of the website.\r\n\r\nExample 3 – I am going to create a WordPress plugin that helps to share pages or posts on Twitter.\r\n\r\n\r\n\r\n
Create Shortcodes in WordPress Plugin
\r\nWordPress offers a predefined shortcode function to create shortcode in WordPress plugin. For using shortcode function, you have to define a handler function that parse the shortcode and return some output.\r\n\r\nThen, you need to register a shortcode using add_shortcode() function.\r\n\r\nadd_shortcode( $shortcode_name, $handler_function);\r\n
\r\n
$shortcode_name – (required, string)It is a string that to be searched in the post.
\r\n
$handler_function – (required, callable) It is a hook to run when shortcode is found.
\r\n
\r\n\r\n\r\n \r\n\r\n\r\n\r\n\r\n\r\nNote: I have created a shortcode folder under the plugin folder of my WordPress where I have created a file named shortcode.php.\r\n
WordPress ShortCode Example 1 – Display Form On Pages/Posts
\r\nYou can create shortcode to display form on any page or post of the website. The below code includes-\r\n
\r\n
Plugin details
\r\n
form_creation() to create a form which includes form fields.
\r\n
add_shortcode() function which contain shortcode name test and calling of form_creation() function as parameters.
\r\n
\r\n
\r\n
\r\n<?php\r\n/*\r\n* Plugin Name: WordPress ShortCode\r\n* Description: Create your WordPress shortcode.\r\n* Version: 1.0\r\n* Author: InkThemes\r\n* Author URI: https://inkthemes.com\r\n*/\r\n\r\n// Example 1 : WP Shortcode to display form on any page or post.\r\nfunctionform_creation(){\r\n?>\r\n<form>\r\nFirst name:<inputtype=\"text\"name=\"firstname\"><br>\r\nLast name:<inputtype=\"text\"name=\"lastname\"><br>\r\nMessage:<textareaname=\"message\"> Enter text here...</textarea>\r\n</form>]\r\n<?php\r\n}\r\nadd_shortcode(\'test\',\'form_creation\');\r\n?>
\r\n
\r\n
Output
\r\nYou need to place WordPress shortcode within square brackets in order to represent it on any page or post of the website. As you can see in the below image, code word test enclosed within square brackets.\r\n
\r\nThis is how the form page appears on the front end.\r\n\r\n\r\n
WordPress Shortcode Example 2 – Display Text On Pages/Posts
\r\nYou can create shortcode to display text on any page or post of the website. The below code includes-\r\n
\r\n
Plugin details
\r\n
wp_first_shortcode() contain the text that you want to display in front end.
\r\n
add_shortcode() function contain shortcode name first and calling of wp_first_shortcode() function as parameters.
\r\n
\r\n
\r\n
\r\n\r\n<?php\r\n/*\r\n* Plugin Name: WordPress ShortCode\r\n* Description: Create your WordPress shortcode.\r\n* Version: 1.0\r\n* Author: InkThemes\r\n* Author URI: https://inkthemes.com\r\n*/\r\n\r\n// Example 2 : WP Shortcode to display text on page or post.\r\nfunctionwp_first_shortcode(){\r\necho\"Hello, This is your another shortcode!\";\r\n}\r\nadd_shortcode(\'first\',\'wp_first_shortcode\');\r\n\r\n?>\r\n\r\n
\r\n
\r\n
Output
\r\nYou can insert a shortcode with code word first enclosed with square brackets.\r\n\r\n\r\n\r\nThis is how the text display in the post on front end.\r\n\r\n\r\n
WordPress Shortcode Example 3 – Share Pages/Posts On Twitter
\r\nYou can create shortcode to share your pages or posts on Twitter. The below code includes-\r\n
\r\n
Plugin details
\r\n
ink_wp_shortcode() get the particular post or page that you want to share on Twitter.
\r\n
add_shortcode() function contain shortcode name twitter and calling of ink_wp_shortcode() function as parameters.
\r\n
\r\n
\r\n
\r\n\r\n<?php\r\n/*\r\n* Plugin Name: WordPress ShortCode\r\n* Description: Create your WordPress shortcode.\r\n* Version: 1.0\r\n* Author: InkThemes\r\n* Author URI: https://inkthemes.com\r\n*/\r\n\r\n// Example 3 : WP Shortcode to share post or page on Twitter.\r\nfunctionink_wp_shortcode($atts,$content=null)\r\n{\r\n$post_url=get_permalink($post->ID);\r\n$post_title=get_the_title($post->ID);\r\n$tweet= \'<astyle=\"color:blue; font-size: 20px;\"href=\"http://twitter.com/home/?status=Read\' . $post_title . \'at\' . $post_url . \'\">\r\n<b>Share on Twitter </b></a>\';\r\nreturn$tweet;\r\n}\r\nadd_shortcode(\'twitter\',\'ink_wp_shortcode\');\r\n?>\r\n\r\n
\r\n
\r\n
Output
\r\nYou can see in the below image, shortcode twitter is placed at the end of the post.\r\n\r\n\r\n\r\nYou can directly share the pages or posts on Twitter by click on the text Share on Twitter.\r\n\r\n\r\n
Conclusion
\r\nI hope this tutorial is helpful to you and make you understand the concept that you need to use while creating a WordPress shortcode for your own purpose. You can create as many as shortcode you want and use it wherever you want.\r\n\r\nMoreover, you can also watch the video tutorial for this post, just check it out.\r\n\r\nPlease do share your thoughts about the post and how much you find it useful to you.\r\n
\r\n\r\nLast Updated on: June 6, 2017\r\n\r\nUnder:Blog, WordPress\r\n\r\n
For the beginners, creating shortcode is sometimes not easy. But, WordPress makes it pretty simple to create your own shortcode by using WordPress shortcode function.
Therefore, in this tutorial I am going to explain you how easily you can create your own shortcode using 3 simple examples. You will learn how to create WordPress shortcode plugin.
\r\n
Example 1 – I am going to create a WordPress plugin to display form on any page or post of the website.
\r\n
Example 2 – I am going to create a WordPress plugin to display text on any page or post of the website.
\r\n
Example 3 – I am going to create a WordPress plugin that helps to share pages or posts on Twitter.
\r\n\r\n
Create Shortcodes in WordPress Plugin
\r\n
WordPress offers a predefined shortcode function to create shortcode in WordPress plugin. For using shortcode function, you have to define a handler function that parse the shortcode and return some output.
\r\n
Then, you need to register a shortcode using add_shortcode() function.
$shortcode_name – (required, string)It is a string that to be searched in the post.
\r\n
$handler_function – (required, callable) It is a hook to run when shortcode is found.
\r\n
\r\n
\r\n
\r\n
Note: I have created a shortcode folder under the plugin folder of my WordPress where I have created a file named shortcode.php.
\r\n
WordPress ShortCode Example 1 – Display Form On Pages/Posts
\r\n
You can create shortcode to display form on any page or post of the website. The below code includes-
\r\n
\r\n
Plugin details
\r\n
form_creation() to create a form which includes form fields.
\r\n
add_shortcode() function which contain shortcode name test and calling of form_creation() function as parameters.
\r\n
\r\n
\r\n
\r\n<?php\r\n/*\r\n* Plugin Name: WordPress ShortCode\r\n* Description: Create your WordPress shortcode.\r\n* Version: 1.0\r\n* Author: InkThemes\r\n* Author URI: https://inkthemes.com\r\n*/\r\n\r\n// Example 1 : WP Shortcode to display form on any page or post.\r\nfunctionform_creation(){\r\n?>\r\n<form>\r\nFirst name:<inputtype=\"text\"name=\"firstname\"><br>\r\nLast name:<inputtype=\"text\"name=\"lastname\"><br>\r\nMessage:<textareaname=\"message\"> Enter text here...</textarea>\r\n</form>]\r\n<?php\r\n}\r\nadd_shortcode(\'test\',\'form_creation\');\r\n?>
\r\n
\r\n
Output
\r\n
You need to place WordPress shortcode within square brackets in order to represent it on any page or post of the website. As you can see in the below image, code word test enclosed within square brackets.
\r\n
\r\n
This is how the form page appears on the front end.
\r\n
\r\n
WordPress Shortcode Example 2 – Display Text On Pages/Posts
\r\n
You can create shortcode to display text on any page or post of the website. The below code includes-
\r\n
\r\n
Plugin details
\r\n
wp_first_shortcode() contain the text that you want to display in front end.
\r\n
add_shortcode() function contain shortcode name first and calling of wp_first_shortcode() function as parameters.
\r\n
\r\n
\r\n
\r\n\r\n<?php\r\n/*\r\n* Plugin Name: WordPress ShortCode\r\n* Description: Create your WordPress shortcode.\r\n* Version: 1.0\r\n* Author: InkThemes\r\n* Author URI: https://inkthemes.com\r\n*/\r\n\r\n// Example 2 : WP Shortcode to display text on page or post.\r\nfunctionwp_first_shortcode(){\r\necho\"Hello, This is your another shortcode!\";\r\n}\r\nadd_shortcode(\'first\',\'wp_first_shortcode\');\r\n\r\n?>\r\n\r\n
\r\n
\r\n
Output
\r\n
You can insert a shortcode with code word first enclosed with square brackets.
\r\n
\r\n
This is how the text display in the post on front end.
\r\n
\r\n
WordPress Shortcode Example 3 – Share Pages/Posts On Twitter
\r\n
You can create shortcode to share your pages or posts on Twitter. The below code includes-
\r\n
\r\n
Plugin details
\r\n
ink_wp_shortcode() get the particular post or page that you want to share on Twitter.
\r\n
add_shortcode() function contain shortcode name twitter and calling of ink_wp_shortcode() function as parameters.
\r\n
\r\n
\r\n
\r\n\r\n<?php\r\n/*\r\n* Plugin Name: WordPress ShortCode\r\n* Description: Create your WordPress shortcode.\r\n* Version: 1.0\r\n* Author: InkThemes\r\n* Author URI: https://inkthemes.com\r\n*/\r\n\r\n// Example 3 : WP Shortcode to share post or page on Twitter.\r\nfunctionink_wp_shortcode($atts,$content=null)\r\n{\r\n$post_url=get_permalink($post->ID);\r\n$post_title=get_the_title($post->ID);\r\n$tweet= \'<astyle=\"color:blue; font-size: 20px;\"href=\"http://twitter.com/home/?status=Read\' . $post_title . \'at\' . $post_url . \'\">\r\n<b>Share on Twitter </b></a>\';\r\nreturn$tweet;\r\n}\r\nadd_shortcode(\'twitter\',\'ink_wp_shortcode\');\r\n?>\r\n\r\n
\r\n
\r\n
Output
\r\n
You can see in the below image, shortcode twitter is placed at the end of the post.
\r\n
\r\n
You can directly share the pages or posts on Twitter by click on the text Share on Twitter.
\r\n
\r\n
Conclusion
\r\n
I hope this tutorial is helpful to you and make you understand the concept that you need to use while creating a WordPress shortcode for your own purpose. You can create as many as shortcode you want and use it wherever you want.
\r\n
Moreover, you can also watch the video tutorial for this post, just check it out.
\r\n
Please do share your thoughts about the post and how much you find it useful to you.
\r\n\r\nDo you want to create your own custom widgets in WordPress? Widgets allow you to drag and drop elements into any sidebar or widget ready area of your website. In this article, we will show you how to easily create a custom WordPress widget.\r\n\r\n\r\n
What is a WordPress Widget?
\r\nWordPress widgets contain pieces of code that you can add to your website’s sidebars or widget ready areas. Think of them as modules that you can use to add different elements by using a simple drag and drop interface.\r\n\r\nBy default, WordPress comes with a standard set of widgets that you can use with any WordPress theme. See our beginner’s guide on how to add and use widgets in WordPress.\r\n\r\n\r\n\r\nWordPress also allows developers to create their own custom widgets. Many WordPress themes and plugins come with their own custom widgets that you can add to your sidebars.\r\n\r\nFor example, you can add a contact form, a custom login form, or a photo gallery to a sidebar without writing any code.\r\n\r\nHaving said that, let’s see how to easily create your own custom widgets in WordPress.\r\n
Video Tutorial
\r\n \r\n\r\n \r\n
\r\n
Subscribe to WPBeginner
\r\n\r\n\r\n
\r\nIf you don’t like the video or need more instructions, then continue reading.\r\n
Creating a Custom Widget in WordPress
\r\nBefore we get started, it would be best if you create a site-specific plugin where you will be pasting the widget code from this tutorial.\r\n\r\nYou can also paste the code in your theme’s functions.php file. However, it will only be available when that particular theme is active.\r\n\r\nIn this tutorial, we will create a simple widget that just greets visitors. Take a look at this code and then paste it in your site-specific plugin to see it in action.\r\n
\r\nAfter adding the code you need to head over to Appearance » Widgets page. You will notice the new WPBeginner Widget in the list of available widgets. You need to drag and drop this widget to a sidebar.\r\n\r\n\r\n\r\nNow you can visit your website to see it in action.\r\n\r\n\r\n\r\nNow let’s study the code again.\r\n\r\nFirst we registered the ‘wpb_widget’ and loaded our custom widget. After that we defined what that widget does, and how to display the widget back-end.\r\n\r\nLastly, we defined how to handle changes made to the widget.\r\n\r\nNow there are a few things that you might want to ask. For example, what’s the purpose wpb_text_domain?\r\n\r\nWordPress uses gettext to handle translation and localization. This wpb_text_domain and __e tells gettext to make a string available for translation. See how you can find translation ready WordPress themes.\r\n\r\nIf you are creating a custom widget for your theme, then you can replace wpb_text_domain with your theme’s text domain.\r\n\r\nWe hope this article helped you learn how to easily create a custom WordPress widget. You may also want to see our list of the most useful WordPress widgets for your site.\r\n\r\n
\r\n
','How to Create a Custom WordPress Widget','','publish','closed','closed','','how-to-create-a-custom-wordpress-widget','','','2017-12-23 22:43:37','2017-12-23 22:43:37','',0,'http://www.acctcrop.softwarewebdesign.com/?page_id=37',0,'page','',0),(38,1,'2017-12-23 22:43:37','2017-12-23 22:43:37','
\r\n\r\n
\r\n\r\n
\r\n
\r\n
\r\n\r\nDo you want to create your own custom widgets in WordPress? Widgets allow you to drag and drop elements into any sidebar or widget ready area of your website. In this article, we will show you how to easily create a custom WordPress widget.\r\n\r\n\r\n
What is a WordPress Widget?
\r\nWordPress widgets contain pieces of code that you can add to your website’s sidebars or widget ready areas. Think of them as modules that you can use to add different elements by using a simple drag and drop interface.\r\n\r\nBy default, WordPress comes with a standard set of widgets that you can use with any WordPress theme. See our beginner’s guide on how to add and use widgets in WordPress.\r\n\r\n\r\n\r\nWordPress also allows developers to create their own custom widgets. Many WordPress themes and plugins come with their own custom widgets that you can add to your sidebars.\r\n\r\nFor example, you can add a contact form, a custom login form, or a photo gallery to a sidebar without writing any code.\r\n\r\nHaving said that, let’s see how to easily create your own custom widgets in WordPress.\r\n
Video Tutorial
\r\n \r\n\r\n \r\n
\r\n
Subscribe to WPBeginner
\r\n\r\n\r\n
\r\nIf you don’t like the video or need more instructions, then continue reading.\r\n
Creating a Custom Widget in WordPress
\r\nBefore we get started, it would be best if you create a site-specific plugin where you will be pasting the widget code from this tutorial.\r\n\r\nYou can also paste the code in your theme’s functions.php file. However, it will only be available when that particular theme is active.\r\n\r\nIn this tutorial, we will create a simple widget that just greets visitors. Take a look at this code and then paste it in your site-specific plugin to see it in action.\r\n
\r\nAfter adding the code you need to head over to Appearance » Widgets page. You will notice the new WPBeginner Widget in the list of available widgets. You need to drag and drop this widget to a sidebar.\r\n\r\n\r\n\r\nNow you can visit your website to see it in action.\r\n\r\n\r\n\r\nNow let’s study the code again.\r\n\r\nFirst we registered the ‘wpb_widget’ and loaded our custom widget. After that we defined what that widget does, and how to display the widget back-end.\r\n\r\nLastly, we defined how to handle changes made to the widget.\r\n\r\nNow there are a few things that you might want to ask. For example, what’s the purpose wpb_text_domain?\r\n\r\nWordPress uses gettext to handle translation and localization. This wpb_text_domain and __e tells gettext to make a string available for translation. See how you can find translation ready WordPress themes.\r\n\r\nIf you are creating a custom widget for your theme, then you can replace wpb_text_domain with your theme’s text domain.\r\n\r\nWe hope this article helped you learn how to easily create a custom WordPress widget. You may also want to see our list of the most useful WordPress widgets for your site.\r\n\r\n
WordPress defines a class called wpdb, which contains a set of functions used to interact with a database. Its primary purpose is to provide an interface with the WordPress database, but can be used to communicate with any other appropriate database. The class source code is loosely based on the ezSQL class; written and maintained by Justin Vincent
Using the $wpdb Object
Warning: Methods in the wpdb() class should not be called directly. Use the global $wpdb object instead!
WordPress provides a global object variable, $wpdb, which is an instantiation of the wpdb class defined in /wp-includes/wp-db.php. By default, $wpdb is instantiated to talk to the WordPress database. To access $wpdb in your WordPress PHP code, declare $wpdb as a global variable using the global keyword, or use the superglobal $GLOBALS in the following manner:
// 1st Method - Declaring $wpdb as global and using it to execute an SQL query statement that returns a PHP objectglobal $wpdb;$results = $wpdb->get_results( \"SELECT * FROM {$wpdb->prefix}options WHERE option_id = 1\", OBJECT );// 2nd Method - Utilizing the $GLOBALS superglobal. Does not require global keyword ( but may not be best practice )$results = $GLOBALS[\'wpdb\']->get_results( \"SELECT * FROM {$wpdb->prefix}options WHERE option_id = 1\", OBJECT );
The $wpdb object is not limited to the default tables created by WordPress; it can be used to read data from any table in the WordPress database (such as custom plugin tables). For example to SELECT some information from a custom table called \"mytable\", you can do the following.
$myrows = $wpdb->get_results( \"SELECT id, name FROM mytable\" );
The $wpdb object can talk to any number of tables, but only to one database at a time; by default the WordPress database. In the rare case you need to connect to another database, you will need to instantiate your own object from the wpdb class with your own database connection information. For extremely complicated setups with many databases, consider using hyperdb instead.
A Warning
Some of the functions in this class take an SQL statement as input. You must SQL escape all untrusted values you incorporate into the SQL query to prevent SQL injection attacks. Check the documentation to see if the function you plan to use escapes SQL for you or expects it to be pre-escaped.
The get_var function returns a single variable from the database. Though only one variable is returned, the entire result of the query is cached for later use. Returns NULL if no result is found.
 <?php $wpdb->get_var( \'query\', column_offset, row_offset ); ?>Â
queryÂ
(string) The query you wish to run. Setting this parameter to null will return the specified variable from the cached results of the previous query.
column_offsetÂ
(integer) The desired column (0 being the first). Defaults to 0.
row_offsetÂ
(integer) The desired row (0 being the first). Defaults to 0.
Examples
Retrieve and display the number of users.
<?php$user_count = $wpdb->get_var( \"SELECT COUNT(*) FROM $wpdb->users\" );echo \"<p>User count is {$user_count}</p>\";?>
<?php// set the meta_key to the appropriate custom field meta key$meta_key = \'miles\';$allmiles = $wpdb->get_var( $wpdb->prepare( \" SELECT sum(meta_value) FROM $wpdb->postmeta WHERE meta_key =Â %s \", $meta_key) );echo \"<p>Total miles is {$allmiles}</p>\";?>
SELECT a Row
To retrieve an entire row from a query, use get_row. The function can return the row as an object, an associative array, or as a numerically indexed array. If more than one row is returned by the query, only the specified row is returned by the function, but all rows are cached for later use. Returns NULL if no result is found, consider this when using the returned value in arguments, see example below.
 <?php $wpdb->get_row(\'query\', output_type, row_offset); ?>Â
queryÂ
(string) The query you wish to run.
output_typeÂ
One of three pre-defined constants. Defaults to OBJECT.
OBJECT - result will be output as an object.
ARRAY_A - result will be output as an associative array.
ARRAY_N - result will be output as a numerically indexed array.
row_offsetÂ
(integer) The desired row (0 being the first). Defaults to 0.
Examples
Get all the information about Link 10.
$mylink = $wpdb->get_row( \"SELECT * FROM $wpdb->links WHERE link_id = 10\" );
The properties of the $mylink object are the column names of the result from the SQL query (in this example all the columns from the $wpdb->links table, but you could also query for specific columns only).
echo $mylink->link_id; // prints \"10\"
In contrast, using
$mylink = $wpdb->get_row( \"SELECT * FROM $wpdb->links WHERE link_id = 10\", ARRAY_A );
would result in an associative array:
echo $mylink[\'link_id\']; // prints \"10\"
and
$mylink = $wpdb->get_row( \"SELECT * FROM $wpdb->links WHERE link_id = 10\", ARRAY_N );
would result in a numerically indexed array:
echo $mylink[1]; // prints \"10\"
If there is no record with ID 10 in the links table, null will be returned. The following would then be false:
if ( null !== $mylink ) { // do something with the link return true;} else { // no link found return false;}
SELECT a Column
To SELECT a column, use get_col. This function outputs a one dimensional array. If more than one column is returned by the query, only the specified column will be returned by the function, but the entire result is cached for later use. Returns an empty array if no result is found.
 <?php $wpdb->get_col( \'query\', column_offset ); ?>Â
queryÂ
(string) the query you wish to execute. Setting this parameter to null will return the specified column from the cached results of the previous query.
column_offsetÂ
(integer) The desired column (0 being the first). Defaults to 0.
Examples
For this example, assume the blog is devoted to information about automobiles. Each post describes a particular car (e.g. 1969 Ford Mustang), and three Custom Fields, manufacturer, model, and year, are assigned to each post. This example will display the post titles, filtered by a particular manufacturer (Ford), and sorted by model and year.
The get_col form of the wpdb Class is used to return an array of all the post ids meeting the criteria and sorted in the correct order. Then a foreach construct is used to iterate through that array of post ids, displaying the title of each post. Note that the SQL for this example was created by Andomar.
<?php $meta_key1 = \'model\';$meta_key2 = \'year\';$meta_key3 = \'manufacturer\';$meta_key3_value = \'Ford\';$postids=$wpdb->get_col( $wpdb->prepare( \" SELECT key3.post_id FROM $wpdb->postmeta key3 INNER JOIN $wpdb->postmeta key1 ON key1.post_id = key3.post_id AND key1.meta_key =Â %s INNER JOIN $wpdb->postmeta key2 ON key2.post_id = key3.post_id AND key2.meta_key =Â %s WHERE key3.meta_key =Â %s AND key3.meta_value =Â %s ORDER BY key1.meta_value, key2.meta_value \", $meta_key1, $meta_key2, $meta_key3, $meta_key3_value) ); if ( $postids ) { echo \"List of {$meta_key3_value}(s), sorted by {$meta_key1}, {$meta_key2}\"; foreach ( $postids as $id ) { $post = get_post( intval( $id ) ); setup_postdata( $post ); ?> <p> <a href=\"<?php the_permalink()Â ?>\" rel=\"bookmark\" title=\"Permanent Link to <?php the_title_attribute();Â ?>\"> <?php the_title();Â ?> </a> </p> <?php } }?>
This example lists all posts that contain a particular custom field, but sorted by the value of a second custom field.
<?php// List all posts with custom field Color, sorted by the value of custom field Display_Order// does not exclude any \'post_type\'// assumes each post has just one custom field for Color, and one for Display_Order$meta_key1 = \'Color\';$meta_key2 = \'Display_Order\';$postids = $wpdb->get_col( $wpdb->prepare( \" SELECT key1.post_id FROM $wpdb->postmeta key1 INNER JOIN $wpdb->postmeta key2 ON key2.post_id = key1.post_id AND key2.meta_key =Â %s WHERE key1.meta_key =Â %s ORDER BY key2.meta_value+(0) ASC \", $meta_key2, $meta_key1) ); if ( $postids ) { echo \"List of {$meta_key1} posts, sorted by {$meta_key2}\"; foreach ( $postids as $id ) { $post = get_post( intval( $id ) ); setup_postdata( $post ); ?> <p> <a href=\"<?php the_permalink()Â ?>\" rel=\"bookmark\" title=\"Permanent Link to <?php the_title_attribute();Â ?>\"> <?php the_title();Â ?> </a> </p> <?php }}?>
SELECT Generic Results
Generic, multiple row results can be pulled from the database with get_results. The function returns the entire query result as an array. Each element of this array corresponds to one row of the query result and, like get_row, can be an object, an associative array, or a numbered array. If no matching rows are found, or if there is a database error, the return value will be an empty array. If your $query string is empty, or you pass an invalid $output_type, NULL will be returned.
 <?php $wpdb->get_results( \'query\', output_type ); ?>Â
queryÂ
(string) The query you wish to run.
output_typeÂ
One of four pre-defined constants. Defaults to OBJECT. See SELECT a Row and its examples for more information.
OBJECT - result will be output as a numerically indexed array of row objects.
OBJECT_K - result will be output as an associative array of row objects, using first column\'s values as keys (duplicates will be discarded).
ARRAY_A - result will be output as a numerically indexed array of associative arrays, using column names as keys.
ARRAY_N - result will be output as a numerically indexed array of numerically indexed arrays.
Since this function uses the $wpdb->query() function all the class variables are properly set. The results count for a \'SELECT\' query will be stored in $wpdb->num_rows.
Examples
Get the IDs and Titles of all the Drafts by User 5 and echo the Titles.
$fivesdrafts = $wpdb->get_results( \" SELECT ID, post_title FROM $wpdb->posts WHERE post_status = \'draft\' AND post_author = 5 \");foreach ( $fivesdrafts as $fivesdraft ) { echo $fivesdraft->post_title;}
 <?php $wpdb->insert( $table, $data, $format ); ?>Â
tableÂ
(string) The name of the table to insert data into.
dataÂ
(array) Data to insert (in column => value pairs). Both $data columns and $data values should be \"raw\" (neither should be SQL escaped).
formatÂ
(array|string) (optional) An array of formats to be mapped to each of the values in $data. If string, that format will be used for all of the values in $data. If omitted, all values in $data will be treated as strings unless otherwise specified in wpdb::$field_types.
Possible format values: %s as string; %d as integer (whole number); and %f as float. (See below for more information.)
After insert, the ID generated for the AUTO_INCREMENT column can be accessed with:
$wpdb->insert_id
This function returns false if the row could not be inserted. Otherwise, it returns the number of affected rows (which will always be 1).
Please note: The value portion of the data parameter\'s column=>value pairs must be scalar. If you pass an array (or object) as a value to be inserted you will generate a warning similar to \"mysql_real_escape_string() expects parameter 1 to be string, array given on line 880 in file /var/www/html/wp-includes/wp-db.php\".
Examples
Insert two columns in a row, the first value being a string and the second a number:
Replace a row in a table if it exists or insert a new row in a table if the row did not already exist.
 <?php $wpdb->replace( $table, $data, $format ); ?>Â
tableÂ
(string) The name of the table to replace data in.
dataÂ
(array) Data to replace (in column => value pairs). Both $data columns and $data values should be \"raw\" (neither should be SQL escaped).
formatÂ
(array|string) (optional) An array of formats to be mapped to each of the value in $data. If string, that format will be used for all of the values in $data. If omitted, all values in $data will be treated as strings unless otherwise specified in wpdb::$field_types.
Possible format values: %s as string; %d as integer (whole number); and %f as float. (See below for more information.)
If the length of a string element in the $data array parameter is longer that the defined length in the MySql database table, the insert will fail, this function will return false, but $wpdb->last_error will not be set to a descriptive message. You must ensure the data you wish to insert will fit in the database - do not assume the MySql will truncate the data.
After replace, the ID generated for the AUTO_INCREMENT column can be accessed with:
$wpdb->insert_id
This function returns a count to indicate the number of rows affected. This is the sum of the rows deleted and inserted. If the count is 1 for a single-row REPLACE, a row was inserted and no rows were deleted. If the count is greater than 1, one or more old rows were deleted before the new row was inserted. It is possible for a single row to replace more than one old row if the table contains multiple unique indexes and the new row duplicates values for different old rows in different unique indexes.
This function returns false if an existing row could not be replaced and a new row could not be inserted.
Examples
Replace a row, the first value being the row id, the second a string and the third a number:
(array) Data to update (in column => value pairs). Both $data columns and $data values should be \"raw\" (neither should be SQL escaped). This means that if you are using GET or POST data you may need to use stripslashes() to avoid slashes ending up in the database.
whereÂ
(array) A named array of WHERE clauses (in column => value pairs). Multiple clauses will be joined with ANDs. Both $where columns and $where values should be \"raw\".
formatÂ
(array|string) (optional) An array of formats to be mapped to each of the values in $data. If string, that format will be used for all of the values in $data.
where_formatÂ
(array|string) (optional) An array of formats to be mapped to each of the values in $where. If string, that format will be used for all of the items in $where.
Possible format values: %s as string; %d as integer (whole number) and %f as float. (See below for more information.) If omitted, all values in $where will be treated as strings.
Return values: This function returns the number of rows updated, or false if there is an error. Keep in mind that if the $data matches what is already in the database, no rows will be updated, so 0 will be returned. Because of this, you should probably check the return with false === $result
Examples
Update a row, where the ID is 1, the value in the first column is a string and the value in the second column is a number:
Attention:%d can\'t deal with comma values - if you\'re not using full numbers, use string/%s.
DELETE Rows
The delete function was added in WordPress 3.4.0, and can be used to delete rows from a table. The usage is very similar to update and insert. It returns the number of rows updated, or false on error.
(array) (required) A named array of WHERE clauses (in column -> value pairs). Multiple clauses will be joined with ANDs. Both $where columns and $where values should be \'raw\'.
Default: None
$where_format
(string/array) (optional) An array of formats to be mapped to each of the values in $where. If a string, that format will be used for all of the items in $where. A format is one of \'%d\', \'%f\', \'%s\' (integer, float, string; see below for more information). If omitted, all values in $where will be treated as strings unless otherwise specified in wpdb::$field_types.
The query function allows you to execute any SQL query on the WordPress database. It is best used when there is a need for specific, custom, or otherwise complex SQL queries. For more basic queries, such as selecting information from a table, see the other wpdb functions above such as get_results, get_var, get_row or get_col.
General Syntax
 <?php $wpdb->query(\'query\'); ?>Â
queryÂ
(string) The SQL query you wish to execute.
This function returns an integer value indicating the number of rows affected/selected for SELECT, INSERT, DELETE, UPDATE, etc. For CREATE, ALTER, TRUNCATE and DROP SQL statements, (which affect whole tables instead of specific rows) this function returns TRUE on success. If a MySQL error is encountered, the function will return FALSE. Note that since both 0 and FALSE may be returned for row queries, you should be careful when checking the return value. Use the identity operator (===) to check for errors (e.g., false === $result), and whether any rows were affected (e.g., 0 === $result).
Examples
Delete the \'gargle\' meta key and value from Post 13. (We\'ll add the \'prepare\' method to make sure we\'re not dealing with an illegal operation or any illegal characters):
$wpdb->query( $wpdb->prepare( \" DELETE FROM $wpdb->postmeta WHERE post_id =Â %d AND meta_key =Â %s \", 13, \'gargle\' ));
$wpdb->query( $wpdb->prepare( \" UPDATE $wpdb->posts SET post_parent =Â %d WHERE ID =Â %d AND post_status =Â %s \", 7, 15, \'static\') );
Protect Queries Against SQL Injection Attacks
For a more complete overview of SQL escaping in WordPress, see database Data Validation. It is a must-read for all WordPress code contributors and plugin authors.
All data in SQL queries must be SQL-escaped before the SQL query is executed to prevent against SQL injection attacks. The prepare method performs this functionality for WordPress, which supports both a sprintf()-like and vsprintf()-like syntax.
Please note: As of 3.5, wpdb::prepare() enforces a minimum of 2 arguments. [more info]
(string) The SQL query you wish to execute, with placeholders (see below).
value_parameterÂ
(int|string|array) The value to substitute into the placeholder. Many values may be passed by simply passing more arguments in a sprintf()-like fashion. Alternatively the second argument can be an array containing the values as in PHP\'s vsprintf() function. Care must be taken not to allow direct user input to this parameter, which would enable array manipulation of any query with multiple placeholders. Values cannot be SQL-escaped.
Placeholders
The query parameter for prepare accepts sprintf()-like placeholders. The %s (string), %d (integer) and %f (float) formats are supported. (The %s and %d placeholders have been available since the function was added to core in Version 2.3, %f has only been available since Version 3.3.) Any other % characters may cause parsing errors unless they are escaped. All % characters inside SQL string literals, including LIKE wildcards, must be double-% escaped as %%. All of %d, %f, and %s are to be left unquoted in the query string. Note that the %d placeholder only accepts integers, so you can\'t pass numbers that have comma values via %d. If you need comma values, use %f as float instead.
Examples
Add Meta key => value pair \"Harriet\'s Adages\" => \"WordPress\' database interface is like Sunday Morning: Easy.\" to Post 10.
Note that in this example we pack the values together in an array. This can be useful when we don\'t know the number of arguments we need to pass until runtime.
Notice that you do not have to worry about quoting strings. Instead of passing the variables directly into the SQL query, use a %s placeholder for strings, a %d placedolder for integers, and a %f as a placeholder for floats. You can pass as many values as you like, each as a new parameter in the prepare() method.
Show and Hide SQL Errors
You can turn error echoing on and off with the show_errors and hide_errors, respectively.
 <?php $wpdb->show_errors(); ?>  <?php $wpdb->hide_errors(); ?>Â
You can also print the error (if any) generated by the most recent query with print_error.
 <?php $wpdb->print_error(); ?>Â
Note: If you are running WordPress Multisite, you must define the DIEONDBERROR constant for database errors to display like so:  <?php define( \'DIEONDBERROR\', true ); ?>Â
Getting Column Information
You can retrieve information about the columns of the most recent query result with get_col_info. This can be useful when a function has returned an OBJECT whose properties you don\'t know. The function will output the desired information from the specified column, or an array with information on all columns from the query result if no column is specified.
 <?php $wpdb->get_col_info(\'type\', offset); ?>Â
typeÂ
(string) What information you wish to retrieve. May take on any of the following values (list taken from the ezSQL docs). Defaults to name.
name - column name. Default.
table - name of the table the column belongs to
max_length - maximum length of the column
not_null - 1 if the column cannot be NULL
primary_key - 1 if the column is a primary key
unique_key - 1 if the column is a unique key
multiple_key - 1 if the column is a non-unique key
numeric - 1 if the column is numeric
blob - 1 if the column is a BLOB
type - the type of the column
unsigned - 1 if the column is unsigned
zerofill - 1 if the column is zero-filled
offsetÂ
(integer) Specify the column from which to retrieve information (with 0 being the first column). Defaults to -1.
-1 - Retrieve information from all columns. Output as array. Default.
Non-negative integer - Retrieve information from specified column (0 being the first).
Clearing the Cache
You can clear the SQL result cache with flush.
 <?php $wpdb->flush(); ?>Â
This clears $wpdb->last_result, $wpdb->last_query, and $wpdb->col_info.
Class Variables
$show_errorsÂ
Whether or not Error echoing is turned on. Defaults to TRUE.
$num_queriesÂ
The number of queries that have been executed.
$last_queryÂ
The most recent query to have been executed.
$last_errorÂ
The most recent error text generated by MySQL.
$queriesÂ
You may save all of the queries run on the database and their stop times by setting the SAVEQUERIES constant to TRUE (this constant defaults to FALSE). If SAVEQUERIES is TRUE, your queries will be stored in this variable as an array.
ID generated for an AUTO_INCREMENT column by the most recent INSERT query.
$num_rowsÂ
The number of rows returned by the last query.
$prefixÂ
The assigned WordPress table prefix for the site.
$base_prefixÂ
The original prefix as defined in wp-config.php. For multi-site: Use if you want to get the prefix without the blog number appended.
Multi-Site Variables
If you are using Multi-Site, you also have access to the following:
$blogidÂ
The id of the current site (blog).
$siteidÂ
The id of the current network (formerly \"site\"). WordPress currently only supports one network per multi-site install, but that could change in future. See the following for more information:
The table contains additional comment information.
$termmetaÂ
The termmeta table contains the term meta values.
$termsÂ
The terms table contains the \'description\' of Categories, Link Categories, Tags.
$term_taxonomyÂ
The term_taxonomy table describes the various taxonomies (classes of terms). Categories, Link Categories, and Tags are taxonomies.
$term_relationshipsÂ
The term relationships table contains link between the term and the object that uses that term, meaning this file point to each Category used for each Post.
The Site table contains a list of the networks (previously known as \"sites\" in WPMU) that are set up in the installation (usually there is only one site listed in this table).
$sitemetaÂ
The Network Options (Site Meta) table contains any options that are applicable to the entire multisite installation.
WordPress defines a class called wpdb, which contains a set of functions used to interact with a database. Its primary purpose is to provide an interface with the WordPress database, but can be used to communicate with any other appropriate database. The class source code is loosely based on the ezSQL class; written and maintained by Justin Vincent
Using the $wpdb Object
Warning: Methods in the wpdb() class should not be called directly. Use the global $wpdb object instead!
WordPress provides a global object variable, $wpdb, which is an instantiation of the wpdb class defined in /wp-includes/wp-db.php. By default, $wpdb is instantiated to talk to the WordPress database. To access $wpdb in your WordPress PHP code, declare $wpdb as a global variable using the global keyword, or use the superglobal $GLOBALS in the following manner:
// 1st Method - Declaring $wpdb as global and using it to execute an SQL query statement that returns a PHP objectglobal $wpdb;$results = $wpdb->get_results( \"SELECT * FROM {$wpdb->prefix}options WHERE option_id = 1\", OBJECT );// 2nd Method - Utilizing the $GLOBALS superglobal. Does not require global keyword ( but may not be best practice )$results = $GLOBALS[\'wpdb\']->get_results( \"SELECT * FROM {$wpdb->prefix}options WHERE option_id = 1\", OBJECT );
The $wpdb object is not limited to the default tables created by WordPress; it can be used to read data from any table in the WordPress database (such as custom plugin tables). For example to SELECT some information from a custom table called \"mytable\", you can do the following.
$myrows = $wpdb->get_results( \"SELECT id, name FROM mytable\" );
The $wpdb object can talk to any number of tables, but only to one database at a time; by default the WordPress database. In the rare case you need to connect to another database, you will need to instantiate your own object from the wpdb class with your own database connection information. For extremely complicated setups with many databases, consider using hyperdb instead.
A Warning
Some of the functions in this class take an SQL statement as input. You must SQL escape all untrusted values you incorporate into the SQL query to prevent SQL injection attacks. Check the documentation to see if the function you plan to use escapes SQL for you or expects it to be pre-escaped.
The get_var function returns a single variable from the database. Though only one variable is returned, the entire result of the query is cached for later use. Returns NULL if no result is found.
 <?php $wpdb->get_var( \'query\', column_offset, row_offset ); ?>Â
queryÂ
(string) The query you wish to run. Setting this parameter to null will return the specified variable from the cached results of the previous query.
column_offsetÂ
(integer) The desired column (0 being the first). Defaults to 0.
row_offsetÂ
(integer) The desired row (0 being the first). Defaults to 0.
Examples
Retrieve and display the number of users.
<?php$user_count = $wpdb->get_var( \"SELECT COUNT(*) FROM $wpdb->users\" );echo \"<p>User count is {$user_count}</p>\";?>
<?php// set the meta_key to the appropriate custom field meta key$meta_key = \'miles\';$allmiles = $wpdb->get_var( $wpdb->prepare( \" SELECT sum(meta_value) FROM $wpdb->postmeta WHERE meta_key =Â %s \", $meta_key) );echo \"<p>Total miles is {$allmiles}</p>\";?>
SELECT a Row
To retrieve an entire row from a query, use get_row. The function can return the row as an object, an associative array, or as a numerically indexed array. If more than one row is returned by the query, only the specified row is returned by the function, but all rows are cached for later use. Returns NULL if no result is found, consider this when using the returned value in arguments, see example below.
 <?php $wpdb->get_row(\'query\', output_type, row_offset); ?>Â
queryÂ
(string) The query you wish to run.
output_typeÂ
One of three pre-defined constants. Defaults to OBJECT.
OBJECT - result will be output as an object.
ARRAY_A - result will be output as an associative array.
ARRAY_N - result will be output as a numerically indexed array.
row_offsetÂ
(integer) The desired row (0 being the first). Defaults to 0.
Examples
Get all the information about Link 10.
$mylink = $wpdb->get_row( \"SELECT * FROM $wpdb->links WHERE link_id = 10\" );
The properties of the $mylink object are the column names of the result from the SQL query (in this example all the columns from the $wpdb->links table, but you could also query for specific columns only).
echo $mylink->link_id; // prints \"10\"
In contrast, using
$mylink = $wpdb->get_row( \"SELECT * FROM $wpdb->links WHERE link_id = 10\", ARRAY_A );
would result in an associative array:
echo $mylink[\'link_id\']; // prints \"10\"
and
$mylink = $wpdb->get_row( \"SELECT * FROM $wpdb->links WHERE link_id = 10\", ARRAY_N );
would result in a numerically indexed array:
echo $mylink[1]; // prints \"10\"
If there is no record with ID 10 in the links table, null will be returned. The following would then be false:
if ( null !== $mylink ) { // do something with the link return true;} else { // no link found return false;}
SELECT a Column
To SELECT a column, use get_col. This function outputs a one dimensional array. If more than one column is returned by the query, only the specified column will be returned by the function, but the entire result is cached for later use. Returns an empty array if no result is found.
 <?php $wpdb->get_col( \'query\', column_offset ); ?>Â
queryÂ
(string) the query you wish to execute. Setting this parameter to null will return the specified column from the cached results of the previous query.
column_offsetÂ
(integer) The desired column (0 being the first). Defaults to 0.
Examples
For this example, assume the blog is devoted to information about automobiles. Each post describes a particular car (e.g. 1969 Ford Mustang), and three Custom Fields, manufacturer, model, and year, are assigned to each post. This example will display the post titles, filtered by a particular manufacturer (Ford), and sorted by model and year.
The get_col form of the wpdb Class is used to return an array of all the post ids meeting the criteria and sorted in the correct order. Then a foreach construct is used to iterate through that array of post ids, displaying the title of each post. Note that the SQL for this example was created by Andomar.
<?php $meta_key1 = \'model\';$meta_key2 = \'year\';$meta_key3 = \'manufacturer\';$meta_key3_value = \'Ford\';$postids=$wpdb->get_col( $wpdb->prepare( \" SELECT key3.post_id FROM $wpdb->postmeta key3 INNER JOIN $wpdb->postmeta key1 ON key1.post_id = key3.post_id AND key1.meta_key =Â %s INNER JOIN $wpdb->postmeta key2 ON key2.post_id = key3.post_id AND key2.meta_key =Â %s WHERE key3.meta_key =Â %s AND key3.meta_value =Â %s ORDER BY key1.meta_value, key2.meta_value \", $meta_key1, $meta_key2, $meta_key3, $meta_key3_value) ); if ( $postids ) { echo \"List of {$meta_key3_value}(s), sorted by {$meta_key1}, {$meta_key2}\"; foreach ( $postids as $id ) { $post = get_post( intval( $id ) ); setup_postdata( $post ); ?> <p> <a href=\"<?php the_permalink()Â ?>\" rel=\"bookmark\" title=\"Permanent Link to <?php the_title_attribute();Â ?>\"> <?php the_title();Â ?> </a> </p> <?php } }?>
This example lists all posts that contain a particular custom field, but sorted by the value of a second custom field.
<?php// List all posts with custom field Color, sorted by the value of custom field Display_Order// does not exclude any \'post_type\'// assumes each post has just one custom field for Color, and one for Display_Order$meta_key1 = \'Color\';$meta_key2 = \'Display_Order\';$postids = $wpdb->get_col( $wpdb->prepare( \" SELECT key1.post_id FROM $wpdb->postmeta key1 INNER JOIN $wpdb->postmeta key2 ON key2.post_id = key1.post_id AND key2.meta_key =Â %s WHERE key1.meta_key =Â %s ORDER BY key2.meta_value+(0) ASC \", $meta_key2, $meta_key1) ); if ( $postids ) { echo \"List of {$meta_key1} posts, sorted by {$meta_key2}\"; foreach ( $postids as $id ) { $post = get_post( intval( $id ) ); setup_postdata( $post ); ?> <p> <a href=\"<?php the_permalink()Â ?>\" rel=\"bookmark\" title=\"Permanent Link to <?php the_title_attribute();Â ?>\"> <?php the_title();Â ?> </a> </p> <?php }}?>
SELECT Generic Results
Generic, multiple row results can be pulled from the database with get_results. The function returns the entire query result as an array. Each element of this array corresponds to one row of the query result and, like get_row, can be an object, an associative array, or a numbered array. If no matching rows are found, or if there is a database error, the return value will be an empty array. If your $query string is empty, or you pass an invalid $output_type, NULL will be returned.
 <?php $wpdb->get_results( \'query\', output_type ); ?>Â
queryÂ
(string) The query you wish to run.
output_typeÂ
One of four pre-defined constants. Defaults to OBJECT. See SELECT a Row and its examples for more information.
OBJECT - result will be output as a numerically indexed array of row objects.
OBJECT_K - result will be output as an associative array of row objects, using first column\'s values as keys (duplicates will be discarded).
ARRAY_A - result will be output as a numerically indexed array of associative arrays, using column names as keys.
ARRAY_N - result will be output as a numerically indexed array of numerically indexed arrays.
Since this function uses the $wpdb->query() function all the class variables are properly set. The results count for a \'SELECT\' query will be stored in $wpdb->num_rows.
Examples
Get the IDs and Titles of all the Drafts by User 5 and echo the Titles.
$fivesdrafts = $wpdb->get_results( \" SELECT ID, post_title FROM $wpdb->posts WHERE post_status = \'draft\' AND post_author = 5 \");foreach ( $fivesdrafts as $fivesdraft ) { echo $fivesdraft->post_title;}
 <?php $wpdb->insert( $table, $data, $format ); ?>Â
tableÂ
(string) The name of the table to insert data into.
dataÂ
(array) Data to insert (in column => value pairs). Both $data columns and $data values should be \"raw\" (neither should be SQL escaped).
formatÂ
(array|string) (optional) An array of formats to be mapped to each of the values in $data. If string, that format will be used for all of the values in $data. If omitted, all values in $data will be treated as strings unless otherwise specified in wpdb::$field_types.
Possible format values: %s as string; %d as integer (whole number); and %f as float. (See below for more information.)
After insert, the ID generated for the AUTO_INCREMENT column can be accessed with:
$wpdb->insert_id
This function returns false if the row could not be inserted. Otherwise, it returns the number of affected rows (which will always be 1).
Please note: The value portion of the data parameter\'s column=>value pairs must be scalar. If you pass an array (or object) as a value to be inserted you will generate a warning similar to \"mysql_real_escape_string() expects parameter 1 to be string, array given on line 880 in file /var/www/html/wp-includes/wp-db.php\".
Examples
Insert two columns in a row, the first value being a string and the second a number:
Replace a row in a table if it exists or insert a new row in a table if the row did not already exist.
 <?php $wpdb->replace( $table, $data, $format ); ?>Â
tableÂ
(string) The name of the table to replace data in.
dataÂ
(array) Data to replace (in column => value pairs). Both $data columns and $data values should be \"raw\" (neither should be SQL escaped).
formatÂ
(array|string) (optional) An array of formats to be mapped to each of the value in $data. If string, that format will be used for all of the values in $data. If omitted, all values in $data will be treated as strings unless otherwise specified in wpdb::$field_types.
Possible format values: %s as string; %d as integer (whole number); and %f as float. (See below for more information.)
If the length of a string element in the $data array parameter is longer that the defined length in the MySql database table, the insert will fail, this function will return false, but $wpdb->last_error will not be set to a descriptive message. You must ensure the data you wish to insert will fit in the database - do not assume the MySql will truncate the data.
After replace, the ID generated for the AUTO_INCREMENT column can be accessed with:
$wpdb->insert_id
This function returns a count to indicate the number of rows affected. This is the sum of the rows deleted and inserted. If the count is 1 for a single-row REPLACE, a row was inserted and no rows were deleted. If the count is greater than 1, one or more old rows were deleted before the new row was inserted. It is possible for a single row to replace more than one old row if the table contains multiple unique indexes and the new row duplicates values for different old rows in different unique indexes.
This function returns false if an existing row could not be replaced and a new row could not be inserted.
Examples
Replace a row, the first value being the row id, the second a string and the third a number:
(array) Data to update (in column => value pairs). Both $data columns and $data values should be \"raw\" (neither should be SQL escaped). This means that if you are using GET or POST data you may need to use stripslashes() to avoid slashes ending up in the database.
whereÂ
(array) A named array of WHERE clauses (in column => value pairs). Multiple clauses will be joined with ANDs. Both $where columns and $where values should be \"raw\".
formatÂ
(array|string) (optional) An array of formats to be mapped to each of the values in $data. If string, that format will be used for all of the values in $data.
where_formatÂ
(array|string) (optional) An array of formats to be mapped to each of the values in $where. If string, that format will be used for all of the items in $where.
Possible format values: %s as string; %d as integer (whole number) and %f as float. (See below for more information.) If omitted, all values in $where will be treated as strings.
Return values: This function returns the number of rows updated, or false if there is an error. Keep in mind that if the $data matches what is already in the database, no rows will be updated, so 0 will be returned. Because of this, you should probably check the return with false === $result
Examples
Update a row, where the ID is 1, the value in the first column is a string and the value in the second column is a number:
Attention:%d can\'t deal with comma values - if you\'re not using full numbers, use string/%s.
DELETE Rows
The delete function was added in WordPress 3.4.0, and can be used to delete rows from a table. The usage is very similar to update and insert. It returns the number of rows updated, or false on error.
(array) (required) A named array of WHERE clauses (in column -> value pairs). Multiple clauses will be joined with ANDs. Both $where columns and $where values should be \'raw\'.
Default: None
$where_format
(string/array) (optional) An array of formats to be mapped to each of the values in $where. If a string, that format will be used for all of the items in $where. A format is one of \'%d\', \'%f\', \'%s\' (integer, float, string; see below for more information). If omitted, all values in $where will be treated as strings unless otherwise specified in wpdb::$field_types.
The query function allows you to execute any SQL query on the WordPress database. It is best used when there is a need for specific, custom, or otherwise complex SQL queries. For more basic queries, such as selecting information from a table, see the other wpdb functions above such as get_results, get_var, get_row or get_col.
General Syntax
 <?php $wpdb->query(\'query\'); ?>Â
queryÂ
(string) The SQL query you wish to execute.
This function returns an integer value indicating the number of rows affected/selected for SELECT, INSERT, DELETE, UPDATE, etc. For CREATE, ALTER, TRUNCATE and DROP SQL statements, (which affect whole tables instead of specific rows) this function returns TRUE on success. If a MySQL error is encountered, the function will return FALSE. Note that since both 0 and FALSE may be returned for row queries, you should be careful when checking the return value. Use the identity operator (===) to check for errors (e.g., false === $result), and whether any rows were affected (e.g., 0 === $result).
Examples
Delete the \'gargle\' meta key and value from Post 13. (We\'ll add the \'prepare\' method to make sure we\'re not dealing with an illegal operation or any illegal characters):
$wpdb->query( $wpdb->prepare( \" DELETE FROM $wpdb->postmeta WHERE post_id =Â %d AND meta_key =Â %s \", 13, \'gargle\' ));
$wpdb->query( $wpdb->prepare( \" UPDATE $wpdb->posts SET post_parent =Â %d WHERE ID =Â %d AND post_status =Â %s \", 7, 15, \'static\') );
Protect Queries Against SQL Injection Attacks
For a more complete overview of SQL escaping in WordPress, see database Data Validation. It is a must-read for all WordPress code contributors and plugin authors.
All data in SQL queries must be SQL-escaped before the SQL query is executed to prevent against SQL injection attacks. The prepare method performs this functionality for WordPress, which supports both a sprintf()-like and vsprintf()-like syntax.
Please note: As of 3.5, wpdb::prepare() enforces a minimum of 2 arguments. [more info]
(string) The SQL query you wish to execute, with placeholders (see below).
value_parameterÂ
(int|string|array) The value to substitute into the placeholder. Many values may be passed by simply passing more arguments in a sprintf()-like fashion. Alternatively the second argument can be an array containing the values as in PHP\'s vsprintf() function. Care must be taken not to allow direct user input to this parameter, which would enable array manipulation of any query with multiple placeholders. Values cannot be SQL-escaped.
Placeholders
The query parameter for prepare accepts sprintf()-like placeholders. The %s (string), %d (integer) and %f (float) formats are supported. (The %s and %d placeholders have been available since the function was added to core in Version 2.3, %f has only been available since Version 3.3.) Any other % characters may cause parsing errors unless they are escaped. All % characters inside SQL string literals, including LIKE wildcards, must be double-% escaped as %%. All of %d, %f, and %s are to be left unquoted in the query string. Note that the %d placeholder only accepts integers, so you can\'t pass numbers that have comma values via %d. If you need comma values, use %f as float instead.
Examples
Add Meta key => value pair \"Harriet\'s Adages\" => \"WordPress\' database interface is like Sunday Morning: Easy.\" to Post 10.
Note that in this example we pack the values together in an array. This can be useful when we don\'t know the number of arguments we need to pass until runtime.
Notice that you do not have to worry about quoting strings. Instead of passing the variables directly into the SQL query, use a %s placeholder for strings, a %d placedolder for integers, and a %f as a placeholder for floats. You can pass as many values as you like, each as a new parameter in the prepare() method.
Show and Hide SQL Errors
You can turn error echoing on and off with the show_errors and hide_errors, respectively.
 <?php $wpdb->show_errors(); ?>  <?php $wpdb->hide_errors(); ?>Â
You can also print the error (if any) generated by the most recent query with print_error.
 <?php $wpdb->print_error(); ?>Â
Note: If you are running WordPress Multisite, you must define the DIEONDBERROR constant for database errors to display like so:  <?php define( \'DIEONDBERROR\', true ); ?>Â
Getting Column Information
You can retrieve information about the columns of the most recent query result with get_col_info. This can be useful when a function has returned an OBJECT whose properties you don\'t know. The function will output the desired information from the specified column, or an array with information on all columns from the query result if no column is specified.
 <?php $wpdb->get_col_info(\'type\', offset); ?>Â
typeÂ
(string) What information you wish to retrieve. May take on any of the following values (list taken from the ezSQL docs). Defaults to name.
name - column name. Default.
table - name of the table the column belongs to
max_length - maximum length of the column
not_null - 1 if the column cannot be NULL
primary_key - 1 if the column is a primary key
unique_key - 1 if the column is a unique key
multiple_key - 1 if the column is a non-unique key
numeric - 1 if the column is numeric
blob - 1 if the column is a BLOB
type - the type of the column
unsigned - 1 if the column is unsigned
zerofill - 1 if the column is zero-filled
offsetÂ
(integer) Specify the column from which to retrieve information (with 0 being the first column). Defaults to -1.
-1 - Retrieve information from all columns. Output as array. Default.
Non-negative integer - Retrieve information from specified column (0 being the first).
Clearing the Cache
You can clear the SQL result cache with flush.
 <?php $wpdb->flush(); ?>Â
This clears $wpdb->last_result, $wpdb->last_query, and $wpdb->col_info.
Class Variables
$show_errorsÂ
Whether or not Error echoing is turned on. Defaults to TRUE.
$num_queriesÂ
The number of queries that have been executed.
$last_queryÂ
The most recent query to have been executed.
$last_errorÂ
The most recent error text generated by MySQL.
$queriesÂ
You may save all of the queries run on the database and their stop times by setting the SAVEQUERIES constant to TRUE (this constant defaults to FALSE). If SAVEQUERIES is TRUE, your queries will be stored in this variable as an array.
ID generated for an AUTO_INCREMENT column by the most recent INSERT query.
$num_rowsÂ
The number of rows returned by the last query.
$prefixÂ
The assigned WordPress table prefix for the site.
$base_prefixÂ
The original prefix as defined in wp-config.php. For multi-site: Use if you want to get the prefix without the blog number appended.
Multi-Site Variables
If you are using Multi-Site, you also have access to the following:
$blogidÂ
The id of the current site (blog).
$siteidÂ
The id of the current network (formerly \"site\"). WordPress currently only supports one network per multi-site install, but that could change in future. See the following for more information:
The table contains additional comment information.
$termmetaÂ
The termmeta table contains the term meta values.
$termsÂ
The terms table contains the \'description\' of Categories, Link Categories, Tags.
$term_taxonomyÂ
The term_taxonomy table describes the various taxonomies (classes of terms). Categories, Link Categories, and Tags are taxonomies.
$term_relationshipsÂ
The term relationships table contains link between the term and the object that uses that term, meaning this file point to each Category used for each Post.
The Site table contains a list of the networks (previously known as \"sites\" in WPMU) that are set up in the installation (usually there is only one site listed in this table).
$sitemetaÂ
The Network Options (Site Meta) table contains any options that are applicable to the entire multisite installation.
![](\"../pdfs/111.jpg\")
![](\"../pdfs/111Soil.jpg\")
![](\"../pdfs/124.jpg\")
![](\"../pdfs/124Soil.jpg\")
![\":)\"](\"https://pixel.wp.com/g.gif?v=ext&j=1%3A3.6.2&blog=62912367&post=335&tz=10&srv=danielnixon.org&host=danielnixon.org&ref=https%3A%2F%2Fwww.google.com%2Furl%3Fsa%3Dt%26rct%3Dj%26q%3D%26esrc%3Ds%26source%3Dweb%26cd%3D10%26ved%3D0ahUKEwjK7OaZpIHYAhWn7oMKHSTdDK4QFghqMAk%26url%3Dhttps%253A%252F%252Fdanielnixon.org%252Fhttp-security-headers%252F%26usg%3DAOvVaw3GvCT-djGBdkLEyoIL9G59&rand=0.9839345641189031\")
','Click Jacking','','publish','closed','closed','','click-jacking','','','2017-12-11 06:16:19','2017-12-11 06:16:19','',2,'http://www.acctcrop.softwarewebdesign.com/?page_id=17',0,'page','',0),(18,1,'2017-12-11 06:16:19','2017-12-11 06:16:19','![\"stopmalvertising.com\"](\"http://stopmalvertising.com/research/images/htaccessfile.png\" "\\"stopmalvertising.com\\"")
![\"htaccess](\"http://stopmalvertising.com/research/images/htaccess1.jpg\" "\\"htaccess")
![\"htaccess](\"http://stopmalvertising.com/research/images/htaccess2.jpg\" "\\"htaccess")
![\"](\"https://images.inkthemes.com/wp-content/uploads/2014/05/How-to-create-shortcode-in-WordPress.png\")
![\"apply](\"https://images.inkthemes.com/wp-content/uploads/2014/05/25.png\")
![\"form](\"https://images.inkthemes.com/wp-content/uploads/2014/05/36.png\")
![\"develop](\"https://images.inkthemes.com/wp-content/uploads/2014/05/41.png\")
![\"text](\"https://images.inkthemes.com/wp-content/uploads/2014/05/53.png\")
![\"twitter](\"https://images.inkthemes.com/wp-content/uploads/2014/05/61.png\")
![\"output](\"https://images.inkthemes.com/wp-content/uploads/2014/05/7.png\")
![\"user-15799\"](\"https://secure.gravatar.com/avatar/b87268bae4e7405c886b791c136f5645?s=81&d=https%3A%2F%2Fsecure.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D81&r=G\")
![\"How](\"http://cdn.wpbeginner.com/wp-content/uploads/2017/05/wpcreatewidget-1-180x180.png\" "\\"How")
![\"Creating](\"http://cdn.wpbeginner.com/wp-content/uploads/2017/05/wpcustomwidget.png\" "\\"Creating")
\r\n![\"WordPress](\"http://cdn.wpbeginner.com/wp-content/uploads/2017/05/wpwidgets.png\" "\\"WordPress")
\r\n\r\nWordPress also allows developers to create their own custom widgets. Many WordPress themes and plugins come with their own custom widgets that you can add to your sidebars.\r\n\r\nFor example, you can add a ![\"Custom](\"http://cdn2.wpbeginner.com/wp-content/uploads/2017/05/customwidget.png\" "\\"Custom")
\r\n\r\nNow you can visit your website to see it in action.\r\n\r\n![\"Previewing](\"http://cdn2.wpbeginner.com/wp-content/uploads/2017/05/widgetpreview.jpg\" "\\"Previewing")
\r\n\r\nNow let’s study the code again.\r\n\r\nFirst we registered the ‘wpb_widget’ and loaded our custom widget. After that we defined what that widget does, and how to display the widget back-end.\r\n\r\nLastly, we defined how to handle changes made to the widget.\r\n\r\nNow there are a few things that you might want to ask. For example, what’s the purpose
Hi,
Thank for your article, i already implement to my website except the “Content-Security-Policy†part.
Regards.
How can i set csp for non https header so that if i forget using non-https image, css or script, they won’t be load?
Really nice article very easy to understand, Thanks for sharing
Daniel, thank you for sharing your knowledge.
In addition to the headers discussed by you, you might be interested in how to setup the HPKP (Public-Key-Pins) header. See http://zinoui.com/blog/security-http-headers
great! Thanks for sharing this tut! my site mark B hehe
You should use apache httpd’s “Header always set†otherwise in case of HTTP status > 200 the headers aren’t set and someone can still exploit you by finding an 400 bad request/500 internal server error – which is very easy in apache.