text:
Sister cities of Yvetot
Hemmingen →
Lanark ←
Yvetot is a commune in the Seine-Maritime department in the Haute-Normandie region in northern France.
Content on this page is licensed under CC-BY-SA from the authors of the following Wikipedia pages: List of twin towns and sister cities in France, Yvetot. Note that the data on Wikipedia is highly unreliable. In many cases, sister cities are missing or wrongly listed. Some cities also have different levels of partnership. If you find an error, please make a correction on the relevant Wikipedia pages and cite your sources.


text:
Be the first to receive discounts to endurance races near you.
Sep 10, 2017 - Sep 11, 2017
1205 Craftsman Way, Suite 101
Everett, WA 98201
Running > 5k
Love Beer? Love Running?
Join us for an easy mostly-flat course along Everett's waterfront. Plus get one beer (or non-alcoholic beverage of your choice).
Register early. No refunds.

subset: commoncrawl


text:
19 Yehuda Hanasi St., POB 437, Netanya 4210300, Israel
Phone: 972-(0)9-862-4345
Email: firstname.lastname@example.com
Date(s) - 02/12/2015
9:00 am - 10:15 am
Categories No Categories
The aim of this Shiur (course) is to enable participants to relate personally to psalms in the Siddur and to other popular psalms. We will read the Psalms (Hebrew and English), discuss the text with reference to traditional commentary, and listen to classical compositions as well as modern settings.
Wednesdays, at 9am. The Shiur is given in English.


text:
The Impact of Survey Choice on Measuring the Relative Importance of Social Security Benefits to the Elderly
Social Security Bulletin, Vol. 67, No. 2, 2007
This article provides insight into how measures of elderly economic well-being are sensitive to the survey data source. In Social Security Administration's publication Income of the Population 55 or Older, data are based on the national Current Population Survey (CPS). The preciseness of the survey statistics depends upon the willingness and ability of CPS respondents to answer questions accurately. This article contrasts income statistics calculated using the CPS and the Survey of Income and Program Participation (SIPP). Administrative data for Social Security benefits and SSI are also used to evaluate the accuracy of the income estimates.
The author is with the Division of Policy Evaluation, Office of Research, Evaluation, and Statistics, Office of Policy, Social Security Administration.
The findings and conclusions presented in the Bulletin are those of the authors and do not necessarily represent the views of the Social Security Administration.
The Social Security Administration (SSA) produces a popular statistical series, Income of the Population 55 or Older, to meet the demand for statistics on the receipt of income from various sources, income distributions, aggregate income, and poverty. This statistical series is based on data from the March Supplement to the Census Bureau's Current Population Survey (CPS).1 These statistics are affected by the selection of the CPS as its data source.
This article provides insight into how the data collected in the CPS affect measures describing the economic well-being of the elderly. Because Income of the Population 55 or Older is based on a survey, the accuracy of its statistics is dependent on the willingness and ability of CPS respondents to answer survey questions accurately. Different surveys have different strengths and weaknesses, and one method of assessing the differences is to compare one survey's data with those of other surveys. The article also compares statistics calculated using the CPS with another Census Bureau survey that is particularly strong at measuring income—the Survey of Income and Program Participation (SIPP).
Another method for determining the accuracy of survey data is to compare them with administrative data. The Census Bureau in collaboration with SSA has matched administrative records for the Social Security and Supplemental Security Income (SSI) programs to the SIPP and selected years of the CPS. Although administrative data are not used in Income of the Population 55 or Older, they are used in parts of this article to evaluate the accuracy of the reported data for Social Security benefits and Supplemental Security Income in both the CPS and the SIPP.
First, the major features of the CPS and SIPP are outlined, and a description of SSA's administrative data available to be matched to those two surveys is also given. The article then compares estimates from the SIPP and CPS of the proportion of the elderly receiving income from various sources. Next, administrative data for Social Security benefits and SSI are used to evaluate the accuracy of the estimates derived from the surveys. Finally, the conclusion discusses the tradeoffs involved in selecting a data source.
Data Sources Used in this Analysis
The Social Security Administration has been producing two series of publications on the income of the elderly and near-elderly—Income of the Population 55 or Older (IP55), since 1976 and Income of the Aged Chartbook, since 1990. Both series are derived from the March Supplement to the Current Population Survey, which is conducted annually by the U.S. Census Bureau. Another Census survey that asks more detailed questions regarding income is the Survey of Income and Program Participation. This analysis uses income data for 1996 because the SIPP match rate to administrative data declined considerably for the 2001 panel.2
Survey Data
Depending on their respective purposes, surveys may differ in many ways: the subjects covered, the questionnaire length and detail, the frequency of interviews, and the sample of the population surveyed are a few of the dimensions along which surveys may vary. The following descriptions of the CPS and SIPP outline some of the broader differences between the surveys that may influence differences in the statistics produced using their data.
Current Population Survey. The CPS is a monthly survey conducted by the Census Bureau and sponsored jointly with the Bureau of Labor Statistics. The CPS is a representative sample of the "civilian noninstitutional population." The survey has been conducted for more than 50 years and is used for official monthly unemployment and labor force statistics. Annual income data have been collected in the March Supplement since 1948, with information gathered concerning income received during the previous calendar year for approximately 35 cash and in-kind sources. Official estimates of income and poverty in the United States are based on the March Supplement (Herz 1996; U.S. Census Bureau 2005 and 2006). Table 1 summarizes major features of the CPS.
|Current Population Survey
(March 1997 Supplement)
|Survey of Income and Program Participation
(1996 panel)
|Sample size
|Approximately 50,500 households
|40,188 households
|Frequency of interviews
|Once per year for supplement
|Once every 4 months
|Income data
|About 35 cash and in-kind sources
|About 70 cash and in-kind sources
|Recall period
|Annual total for prior calendar year
|Totals for previous 4-month period (monthly reporting for most sources)
|Asset holdings data
|Home ownership
|Detailed inventory of real and financial assets and liabilities once each year
|SOURCE: U.S. Census Bureau (1999, 2001, 2005, and 2006).
This article uses the 1997 March Supplement to the CPS (then called the Annual Demographic Survey), which collected data for annual income received in 1996. Persons are designated as "65 or older" if they were at least age 65 as of the interview in March 1997. In SSA's two data series (cited earlier), aged units—classified as "65 or older"—are defined as follows:
- nonmarried persons 65 or older (in March 1997),
- or married couples in which either
- the husband is 65 or older, or
- the husband is younger than 55 and the wife is 65 or older (in March 1997).
Survey of Income and Program Participation. The SIPP is a longitudinal panel survey conducted by the Census Bureau. The survey is designed to collect data on sources and amounts of income to provide improved statistics on the distribution of income in the United States. The sample is also representative of the noninstitutional population. The first SIPP panel began in October 1983; subsequent panels have begun periodically with durations ranging from 2½ to 4 years. Data are collected on approximately 70 cash and in-kind sources of income (U.S. Census Bureau 2005 and 2006). Table 1 summarizes major features of the SIPP.
In this article, analysis of SIPP income data is based on information collected in the 1996 SIPP panel concerning income received during 1996. Persons classified as "65 or older" were at least age 64 as of the interview in March 1996. Aged units classified as "65 or older" were nonmarried persons 64 or older (in March 1996) or married couples in which the husband is 64 or older or the husband was younger than 54 and the wife was 64 or older (in March 1996).3
Administrative Data
The Social Security Administration administers two cash benefit programs: (1) Social Security, or Old-Age, Survivors, and Disability Insurance, and (2) Supplemental Security Income, the separate program for low-income aged and disabled persons. In this study, statistics based on administrative data refer to statistics based on a combination of survey-reported and administrative information. For matched survey records, self-reported data on program benefit receipt were replaced with Social Security's administrative data.4 Self-reported data from the survey were used for unmatched survey respondents. A slightly greater proportion of observations in the 1996 SIPP were matched with Social Security administrative records (85 percent of those aged 64 or older present in March 1996) than in the CPS (77 percent of those 65 or older).5
Social Security (OASDI). Survey-based Social Security benefit amounts have been replaced with the administrative amount of the Social Security benefit paid to the beneficiary plus the beneficiary's Medicare Part B premium (when the latter is applicable) in both the SIPP and the CPS.
Supplemental Security Income (SSI). Survey-based SSI payments have also been replaced by administrative payment amounts.6 The process is somewhat more complicated for the SSI program because there are federal and state components to SSI payments. The SIPP and the CPS treat this differently in their questionnaires: the SIPP asks specifically for federal payments and state payments separately; the CPS asks respondents for a single, combined SSI payment amount.
For states with federally administered state SSI payments, both federal and state SSI amounts were taken directly from administrative payment data files and were used to replace reported SSI payments for matched observations for both the SIPP and the CPS. For states without federally administered state SSI payments, the procedure was different for processing the SIPP and the CPS. For the SIPP, survey-collected federal payments were replaced by administrative data, and survey-based state payments were not changed. For the CPS, the survey-based SSI payment (combined state and federal) amount was replaced by administrative information.7
Impact of Survey Selection on Estimates of the Relative Importance of Social Security Benefits
Traditionally, economic resources for the elderly are expected to come from three sources: Social Security, pensions, and savings. Collectively these sources are referred to as the "three-legged stool" of retirement. If one or more of the "legs" are missing, the "stool" may not be able to provide adequate support during retirement, particularly if economic or health shocks occur. Therefore, elderly beneficiaries who receive all of their income from Social Security are considered economically vulnerable. Depending on whether the CPS or the SIPP was used, the proportion of elderly beneficiaries receiving all of their income from Social Security could appear quite different. In the CPS data for 1996, 17.9 percent of aged units 65 or older reported that all of their income came from Social Security benefits compared with only 8.5 percent in the SIPP.
The difference in results from the two surveys may be due in part to two factors: the survey recall period and the structure and detail of the questionnaires. First, respondents in the CPS are asked in March about income from the previous calendar year, while participants in the SIPP are asked about their income in 4-month intervals. Second, respondents in the SIPP are asked more detailed questions about their sources of income. For example, for questions involving asset income, SIPP respondents are asked if they own a particular asset and are then asked if they received income from that asset and how much; CPS respondents are only asked if they received a particular type of asset income and how much. These factors make participants in the SIPP more likely to report small and/or infrequently received amounts of income (U.S. Census Bureau 2006; Hurd, Juster, and Smith 2003).
Table 2 illustrates the differences in the percentages of aged units 65 or older reporting various sources of income. With the exception of earnings, respondents in the SIPP report receipt of income in every major category more often than respondents in the CPS. The gaps between the SIPP and the CPS are particularly large for asset income—especially interest—and private pensions.8 The large differences in reported receipt of asset income and pensions between the CPS and SIPP may be responsible for the differences in the proportions of beneficiary aged units who report receiving all of their income from Social Security.9
|Number of aged units (thousands)
|Percentage of aged units reporting—
|Retirement benefits a
|Social Security a
|Pensions a
|Public a
|Private a
|Asset income a
|Interest a
|Not interest a
|Public assistance a
|SSI a
|Other public assistance a
|Veterans' benefits a
|Unemployment compensation
|Workers' compensation b
|SOURCES: Author's calculations using the 1996 Survey of Income and Program Participation and March 1997 Current Population Survey.
|NOTES: Estimates are weighted.
|CPS = Current Population Survey; SIPP = Survey of Income and Program Participation; SSI = Supplemental Security Income.
|a. Difference between the surveys is significant at the 99 percent level.
|b. Difference between the surveys is significant at the 95 percent level.
According to Income of the Population 55 or Older (based on the CPS), the proportion of aged units 65 or older (referred to here as elderly aged units) reporting that they received all of their income from Social Security benefits rose from a low of 12 percent in 1990 to a high of 20 percent in 2002 (Chart 1). The receipt of asset income appears to be negatively correlated with the percentage of elderly aged units reporting that they received all of their income from Social Security since 1978, especially from 1990 through 2002 (Chart 2). From 1994 through 2002, receipt of asset income fell from 67 percent to 55 percent. The same observation does not hold for receipt of pension income, which hovered between 41 percent and 43 percent over the same period (Chart 3).10 As seen in these charts, restricting the comparison to beneficiary units does not alter the relationship between the estimates of elderly aged units who received asset income and elderly aged units who received Social Security as their sole source of income. This relationship is an indication that the difference in the reporting of asset income may be an important factor contributing to the divergence in measures of the relative importance of Social Security benefits between the CPS and the SIPP.
Percentage of aged units 65 or older reporting all income from Social Security, 1978–2004
Percentage of aged units 65 or older reporting asset income, 1978–2004
Percentage of aged units 65 or older reporting pension income, 1978–2004
Since it is more likely that small amounts of income are being overlooked by the CPS rather than by the SIPP, it is useful to consider the other income sources of beneficiary aged units that are receiving most, but not all, of their income from Social Security in the SIPP. Of those beneficiary aged units 65 or older receiving at least 95 percent, but not all, of their income from Social Security, 86.5 percent reported asset income, while only 11.5 percent reported pension income. Similarly, 82.2 percent of those receiving at least 90 percent, but not all, of their income from Social Security reported asset income, and 22.3 percent reported pension income, which again suggests that differences in the reporting of asset income may be responsible for the major portion of the discrepancies in the rates of complete reliance on Social Security between the two surveys.
In addition to the frequency of interviews and detail of the questionnaire, the effect of the order of questions in a survey can be significant. Hurd, Juster, and Smith (2003) examined the Health and Retirement Study (HRS) and Assets and Health Dynamics of the Oldest-Old (AHEAD) and compared waves that asked asset and income questions in separate components to waves that had a "merged" asset and income module. The merged module had questions about particular types of assets followed immediately by questions about income from the asset. They found that asset income was more likely to be reported for the "merged" format that was not able to be explained by an increase in reported assets. They suggested that asset income would be better reported in the CPS if questions about asset ownership preceded the questions about income from those assets.
Other studies have compared the CPS and SIPP with other benchmarks to determine the accuracy of their respective data. Roemer (2000) found that for 1996 the CPS underestimated aggregate income from Social Security and Railroad Retirement by 8 percent, SSI by 16 percent, pensions by 23 percent, and asset income by 29 percent. He also found that for 1996 the SIPP underestimated aggregate income by more than the CPS in these categories, except for pensions, which were underestimated by 14 percent, and SSI, which was overestimated by 1 percent. Koenig (2003) and Fisher (2005), however, found that the SIPP does a better job of classifying Social Security beneficiaries and SSI recipients than does the CPS. Czajka and others (2003) found that asset holdings in the 1996 SIPP were underestimated, which may indicate corresponding underestimates of asset income amounts in the SIPP. Taken together, the work of these authors suggests a difficult situation for analysis: the CPS is more likely than the SIPP to underestimate whether or not a source of income was received, while for those reporting receipt, the SIPP may be more likely than the CPS to underestimate the amount of income received by an individual.
Impact of Using Administrative Data in Place of Self-Reported Data on Estimates of the Relative Importance of Social Security Benefits
Several studies have evaluated the effect of substituting Social Security's administrative data for respondents' answers for income received from Social Security's Old-Age, Survivors, and Disability Insurance and SSI programs. Sears and Rupp (2003) and Huynh, Rupp, and Sears (2002) compared administrative data with SIPP-reported data, and Koenig (2003) and Fisher (2005) compared administrative data with reported data for both the CPS and the SIPP.11 These studies identified several sources of reporting error for both Social Security and SSI income amounts:
- The respondent does not report the income at all.
- The respondent misreports SSI payments as Social Security income or vice versa.
- The respondent reports the current monthly payment amount, which may differ from the payment received in the survey's retrospective time period.
- The respondent reports the amount received on the Social Security check, which is lower than the actual monthly benefit because it excludes the Medicare Part B premium deducted from the Social Security benefit.12
Koenig (2003) found that Social Security benefit amounts were more likely to be underreported in the 1996 SIPP than the March 1997 CPS because the SIPP was more likely to net out Medicare Part B premiums.13
For the administrative statistics in Tables 3 and 4, self-reported data have been replaced with Social Security's administrative data for matched observations. Self-reported data continue to be used for unmatched observations. Table 3 illustrates that the CPS reports slightly lower rates of receipt of Social Security benefits and SSI compared with administrative data, while the SIPP reports slightly higher rates of benefit receipt.14 Part of the variation between the two surveys after the substitution of administrative data may be due to the higher administrative match rate in the SIPP.15
The differences in the estimates of the relative importance of Social Security benefits from using administrative data are far smaller than the differences from using a different survey, as shown in Table 4.16 Misreporting SSI as Social Security benefits and vice versa can affect classification as a beneficiary and as a completely reliant beneficiary, changing estimates of complete reliance on Social Security benefits. Koenig (2003) found that the SIPP is less likely than the CPS to misclassify a person as a beneficiary. For matched elderly persons receiving all of their individual income from Social Security (with either reported or administrative data), Fisher (2005) found that the dominant problem with SIPP was the classification of nonbeneficiaries as Social Security beneficiaries. The CPS, however, was only slightly more likely to misclassify a Social Security beneficiary as a nonbeneficiary than vice versa. SSI payments were much more likely to be omitted or reported as Social Security benefits in the CPS than in the SIPP.17
|Retirement benefits
|Social Security
|Public assistance
|Supplemental Security Income
|SOURCES: Author's calculations using the 1997 Current Population Survey and the 1996 Survey of Income and Program Participation.
|NOTES: Estimates are weighted.
|CPS = Current Population Survey; SIPP = Survey of Income and Program Participation.
|90 percent or
more of
income from
Social Security
|100 percent of
income from
Social Security
|CPS reported
|CPS administrative
|SIPP reported
|SIPP administrative
|SOURCES: Author's calculations using the March 1997 Current Population Survey and 1996 Survey of Income and Program Participation.
|NOTES: Estimates are weighted.
|CPS = Current Population Survey; SIPP = Survey of Income and Program Participation.
|Aged units with negative earnings, asset income, or nonpositive total income are excluded.
The purpose of this exercise was to ascertain how the choice of data source affects our understanding of the resources available to the elderly. As demonstrated in this article, the selection of a data source is highly influential on the results; nevertheless, tradeoffs exist when choosing a source.
Several factors must be considered when selecting a survey. The CPS is timely, released within approximately 6 months of data collection, and used by other agencies for official statistics; however, it underreports receipt of income compared with the SIPP. The SIPP may identify recipients missed in the CPS, but panels have not started at regular intervals and the survey may soon be replaced.18 Other surveys, such as the Survey of Consumer Finances and the Panel Study of Income Dynamics, do not provide enough detailed information on individual income sources, do not have a large enough sample to support detailed distributions of the composition of income by demographic characteristics, or do not provide person-level data. In the cases of Income of the Population 55 or Older and Income of the Aged Chartbook, availability of timely data at regular intervals and the ability to work with person- and family-level data have led to the selection of the CPS as the underlying source of data.
Although administrative data are more accurate for income receipt, these data alone are not able to fully address important policy analysis questions. SSA's administrative data on Social Security benefits, SSI, and earnings are limited to information needed to operate its programs with limited demographic information.19
Matching administrative data with survey data also results in complicated tradeoffs. For example, the administrative data can be matched to the SIPP and the CPS only after the data linkages are made available to SSA following a significant processing period. Further, not all persons in the surveys can be matched to their administrative records. Even after the data are matched, the analyst must decide how to accommodate nonmatched respondents—whether nonmatched respondents should be dropped from the analysis or included using reported data. Using only matched respondents would introduce bias if these respondents differed systematically in any way from unmatched respondents. Either choice may lead to false movements in statistics over time if the proportions and/or characteristics of respondents that are matched change over time.
One conclusion that remains clear is that matching administrative data to survey data provides a strong tool in assessing the accuracy of self-reported income data. Based on the results presented here, the percentage of beneficiary aged units receiving 100 percent of their income from Social Security benefits may be overestimated when using the CPS. The statistic published in Income of the Population 55 or Older, 1996—17.9 percent of beneficiary aged units were completely reliant on Social Security in 1996—is much higher than the estimated 8.4 percent using SIPP and administrative data. Because this statistic is often used to make inferences about the well-being of the elderly, it is necessary to keep in mind the issues outlined in this article when interpreting the data.
1. The March Supplement is currently called the Annual Social and Economic (ASEC) Supplement. Before 2003, the Supplement was called the Annual Demographic Survey (ADS).
2. The more recent 2001 panel of SIPP was able to be matched to only approximately 60 percent of respondents as opposed to over 80 percent of respondents for the 1996 SIPP. Matched records will be discussed further in the Administrative Data subsection.
3. The classification of age 64 as of March 1996 as "65 or older" makes the sample comparable with the CPS sample, which is age 65 as of March 1997. This analysis uses the longitudinal core files for waves 1 through 4 of the 1996 panel of SIPP. For observations that were missing data, either because their first interviews did not collect information on January and/or February 1996 or because of the lack of an interview, the income data for the missing months were replaced with the individual's average income for the reported months. March 1996 weights were used for three reasons: (1) March 1996 is the first month in which all rotation groups were interviewed; (2) the 1996 calendar year weights would eliminate observations that had not been present the entire year, making attrition bias a concern; and (3) using the March 1996 weights excludes persons who entered the sample because of their association with an original survey respondent.
4. Survey records were matched if they had a valid Social Security number and an age within 5 years of the age on the administrative files.
5. An earlier study by Koenig (2003) also provides analysis of CPS and SIPP data matched to administrative records. The CPS match rate here is higher than that of Koenig's study because of the discovery in 2004 of additional survey identifiers matched to administrative records.
6. Social Security administrative data come from the monthly benefit credited from the Master Beneficiary Record (MBR), which is usually, but not always, the amount received by the beneficiary. Other studies have used the Payment History Update System (PHUS), which records the actual check amount. Discrepancies may arise between the MBR and the PHUS when payment for retroactive benefits is issued in a single check. Less than 1 percent of elderly observations had discrepancies between the MBR and PHUS. SSI administrative data come from the Supplemental Security Record (SSR).
7. Any state-administered state SSI amounts would be replaced with a value of zero during the substitution of administrative data into the CPS, resulting in the administrative estimate of SSI receipt for the CPS being a lower bound.
8. The statistics presented here were calculated using the most recent methodology from Income of the Population 55 or Older, 2002. Because small changes may have occurred in the data or the methods for calculating the statistics, the statistics presented here for the CPS may not match the statistics published in Income of the Population 55 or Older, 1996.
9. Beneficiary aged units are aged units in which the nonmarried person or at least one spouse of the married couple is receiving Social Security benefits.
10. Hungerford and others (2002) provide a more complete overview of the trends in income sources and the overall economic status of the elderly.
11. In these studies, SSA's administrative records are matched to survey reports using Social Security numbers provided during the interview. The administrative amounts of Social Security benefits and SSI payments can then be compared with the respondents' reported income.
12. Medicare Part B premiums are deducted from Social Security benefits before beneficiaries receive their payments, so the total benefit amount is generally higher than the check (or direct deposit) amount. Not all beneficiaries are enrolled in Medicare Part B, and other beneficiaries may have their premiums paid through other programs. Reporting only the net benefit makes it difficult, if not impossible, to reconstruct the gross benefit, all of which is counted as income.
13. Huynh, Rupp, and Sears (2002) had previously found that the 1996 SIPP reported net Social Security benefits.
14. Koenig (2003) provides a much more detailed study of beneficiary classification in the two surveys. Her study compares survey and administrative data rates of benefit receipt for persons able to be matched to the surveys. She found that both surveys classify Social Security beneficiaries well; over 95 percent of the beneficiaries in both surveys reported that they received Social Security benefits, with nearly 100 percent for the SIPP. Federally administered SSI was a problem for the CPS, however, with less than 70 percent of beneficiaries surveyed reporting SSI receipt; over 90 percent of the federally administered SSI beneficiaries in the SIPP did so. Both surveys incorrectly classified approximately 40 percent of Social Security nonbeneficiaries and 1 percent of respondents not receiving SSI as beneficiaries of these programs.
15. This variation between the surveys may occur if respondents providing a correct Social Security number differ systematically from respondents who do not. Differences may also arise between the surveys because SIPP was designed to provide data on income and government programs and oversamples lower-income persons to achieve this goal. Part of the variation may also be a result of differences in sampling methods.
All of the differences between the reported values for the CPS and the SIPP are statistically significant at the 95 percent level. After substituting administrative data, however, the difference between the surveys for Social Security is no longer statistically significant at the 95 percent level; the differences between the CPS and the SIPP for SSI and the higher-level categories of retirement benefits and public assistance remain statistically significant.
16. Differences between the CPS and SIPP are significant at the 99 percent level for both reported and administrative estimates.
17. Fisher (2005) also found that the estimates of the elderly in families receiving all of their income from Social Security did not change much after substituting in administrative data, but the changes to estimates of the elderly in beneficiary families receiving at least 90 percent of their income from Social Security were larger, particularly for the SIPP. The most probable explanation for this is that SIPP respondents were more likely to report their net benefits, while CPS respondents were more likely to report their gross benefits (Koenig 2003).
18. The SIPP is a panel data set that follows respondents for approximately 3 or 4 years. Many respondents drop out of the survey over time, potentially resulting in attrition bias when using later years in the same panel.
19. The substitution for earnings was not done in this article because administrative earnings data are available annually, not monthly as for Social Security benefits and SSI payments. Although this does not pose a problem with the CPS, it is unclear how to substitute administrative earnings data across months for persons not in the SIPP for the entire year or for persons entering or exiting a marital unit midyear. In addition, while most earnings are available on the administrative file, there may be other earned income that would be reported on a 1040, but not on a W-2 or Schedule SE form, or informal earnings that would not be reported on any administrative record. Additionally, the receipt of earnings does not appear to be misreported as often as the receipt of SSI or Social Security.
Czajka, John, J. Jacobson, and S. Cody. 2003. Survey estimates of wealth: A comparative analysis and review of the Survey of Income and Program Participation. Final report for the Social Security Administration (August 23).
Fisher, T. Lynn. 2005. Measurement of reliance on Social Security benefits. Paper presented at the Federal Committee on Statistical Methodology Research Conference, Washington, DC, November 15.
Herz, Diane. 1996. CPS: Overview. http://www.bls.census.gov/cps/overmain.htm (last modified May 9, 1996).
Hungerford, Thomas, M. Rassette, H. Iams, and M. Koenig. 2002. Trends in the economic status of the elderly, 1976–2000. Social Security Bulletin 64(3): 12–22.
Hurd, Michael, F. T. Juster, and J. P. Smith. 2003. Enhancing the quality of data on income: Recent innovations from the HRS. Journal of Human Resources 38(3): 758–772.
Huynh, Minh, K. Rupp, and J. Sears. 2002. The assessment of Survey of Income and Program Participation benefit data using longitudinal administrative records. The Survey of Income and Program Participation Report No. 238. Washington, DC: U.S. Census Bureau.
Koenig, Melissa. 2003. An assessment of the Current Population Survey and the Survey of Income and Program Participation using Social Security administrative data. Paper presented at the Federal Committee on Statistical Methodology Research Conference, Washington, DC, November 18.
Roemer, Marc. 2000. Assessing the quality of the March Current Population Survey and the Survey of Income and Program Participation income estimates, 1990–1996. http://www.census.gov/hhes/www/income/assess1.pdf (accessed June 2, 2005).
Sears, James, and K. Rupp. 2003. Exploring Social Security payment history matched with the Survey of Income and Program Participation. Paper presented at the Federal Committee on Statistical Methodology Research Conference, Washington, DC, November 18.
[SSA] Social Security Administration. 1998. Income of the Population 55 or Older, 1996. Washington, DC: Office of Research, Evaluation, and Statistics, Office of Policy.
U.S. Census Bureau. 1999. March 1997 Overview. Current Population Survey, technical documentation. http://www.census.gov/apsd/techdoc/cps/mar97/overview.html (last revised April 13, 1999).
———. 2000. Money income in the United States: 1999. Current Population Reports, P60-209.
———. 2001. Survey of Income and Program Participation users' guide. http://www.sipp.census.gov/sipp/usrguide/sipp2001.pdf (accessed April 12, 2005).
———. 2005. 2005 Annual Social and Economic Supplement. Current Population Survey, technical documentation. http://www.census.gov/apsd/techdoc/cps/cpsmar05.pdf (accessed May 26, 2006).
———. 2006. Introduction to SIPP: Comparison of SIPP with other surveys. Survey of Income and Program Participation. http://www.sipp.census.gov/sipp/vs.html (accessed May 26, 2006).


text:
A group of concerned individuals petitioned the Worcester County Board of Education Tuesday to bring junior varsity football to Pocomoke High School (PHS).
While many board members openly supported the idea, they also cautioned the group that the process of bringing a football team to PHS would likely be long and have to take place in degrees.
"They [the kids] all want to play," said Howard Wilkinson parent of two children currently at Pocomoke Middle School.
Wilkinson explained to the assembly that his kids deserved the opportunity to play football on a school team once they reached PHS.
As of now, the only options for Pocomoke area students who wish to play football are programs like the Salvation Army Youth Club. Or, if a student is determined to play on a school team, Worcester County allows youths to attend any public school they wish, regardless of residence, as long as the individual can provide their own transportation.
This policy has resulted in many students transferring to nearby Snow Hill High School, just to take advantage of that school's football program.
However, the process can be trying on families who have to transport the student to and from school every day. Additionally, the transfer means having to adjust to a new school and new people, an experience which is often difficult to manage for students at that age.
While Worcester used to allow temporary, one semester transfers to students wishing to participate in other schools' sporting seasons, a relatively recent state athletic law has changed the rules.
"The school you play for, you have to graduate from," Superintendent Dr. Jon Andes explained to the assembly, meaning that students who transfer to Show Hill High School to play football are implying the intent to graduate from that school. If they were to return to PHS at any point, they would not be allowed to play on the Show Hill High football team again.
Such rules were cited by the group asking for a football program at PHS, including Salvation Army Youth Club Director Harvey Davis, who told the Board of Education that he saw more than enough commitment and dedication from Pocomoke players on his club team to justify giving the school its own program.
The board heard what the advocates were saying and seemed engaged in the discussion and exploring all options.
Several members shared their own memories of playing high school football and agreed that it was an opportunity for growth that all youths should have the chance to experience. However, the realities of bringing football to PHS, even just junior varsity, will be difficult to surmount.
"Football is a very expensive undertaking," said Andes. "It's probably one of the most expensive programs."
Board of Education President Bob Hulburd agreed, saying, "There are a lot of nuts and bolts and details that need to be worked out."
The board suggested taking the Stephen Decatur High School swim team as something of a model for what would need to be done at PHS. That team began at the club level after receiving a lot of support from students and parents and eventually evolved into a fully Decatur-endorsed program.
"You need to show the intent and commitment of the community," Board of Education Vice President Bob Rothermel said.
Rothermel recommended getting in touch with PHS administration, the PTA, and the community at large and coming back at the board's next meeting.
Wilkinson and his group got a head start on Rothermel's proposal when PHS Principal Tyrone Mills, who was in the audience, lent his support to the petition.
"I'd love to have football at Pocomoke High School," he said.


text:
SANTA ANA, Calif. — Neighbors say Isidro Garcia is a doting father, loyal husband and good provider for his family. That doesn't mean he's not all the things prosecutors say he is: an abusive rapist who kidnapped a 15-year-old girl and eventually made her his wife.
The narrative that unfolded around the couple this week in a Los Angeles suburb spans a decade, but the criminal case against Garcia centers on a three-month period when he is accused of grooming the teen through sexual abuse and taking her from her Santa Ana home.
Authorities focused on the early allegations of abuse because they occurred in the county and are not subject to a statute of limitations, according to Whitney Bokosky, deputy district attorney for Orange County. She said the charges may be amended or expanded as the case moves forward.
"Nobody is saying this girl was tied up in some basement somewhere. This was more of a mental kind of prison she was living in," Bokosky said.
Garcia, 41, is charged with rape, kidnapping and three counts of lewd acts on a child dating back to 2004.
A lawyer for Garcia, who is being held on $1 million bail, said the woman lied about being abused because the couple is separating.
Police say Garcia, who had been dating the girl's mother, drugged and abducted the victim, telling her that her family wasn't looking for her and that if she contacted authorities, she would be deported. In 2007, he forced her to marry and fathered a daughter, now 3, with her, police said.
Garcia was arrested Monday after the woman, now 25, went two blocks from her apartment to a police station in Los Angeles County's Bell Gardens and accused him of domestic violence. Authorities then connected her to a 2004 missing person report filed by her mother. Police have not identified the woman.
The story has transfixed many who wonder how the woman could keep quiet for so long, and it prompted comparisons to other high-profile kidnappings, including one involving three women who were locked up in Cleveland and broke free after about a decade.
While police said Garcia initially locked up the woman, she later got a job, had her own car and neighbors said they seemed like a loving couple.
Steve Meister, a criminal defense attorney and former Los Angeles County prosecutor, said the lack of charges stemming from the years the woman lived with Garcia and neighbors' reports that she appeared happy highlight potential challenges to her credibility.
"In any case, but especially a sexual assault case, you can't pick and choose what of the victim's story you want to believe. You either believe them or you don't," Meister said. "That's how district attorneys should analyze it because that is how a jury is going to see it."
Lawrence Rosenthal, a professor at Chapman University's Fowler School of Law, said he believes the victim's age and the statute of limitations influenced how prosecutors approached the case. Some prosecutors might have pursued additional rape charges, he said, but not all, adding that kidnapping carries a potential life sentence.
"Other prosecutors would say it is a waste of time — I've got a slam-dunk on plenty of serious charges," Rosenthal said, adding that he tells his law students to think about criminal cases like movies.
"I tell them you want to pick the frame of the film you think is the easiest to charge, and it may be the prosecutors have approached this case in the same way."
Since Garcia's arrest, neighbors of the couple have rushed to his defense, describing him as dedicated family man. Law enforcement officials have cautioned against blaming the victim.
The case bears some similarities to the story of Pennsylvania teen Tanya Kach, who ran away with a security guard and only broke away after spending years locked in a bedroom as his captive, said Lawrence H. Fisher, a lawyer who represented Kach in a civil suit and co-authored a book with her. The guard is now serving a five- to 15-year prison sentence after pleading guilty to sex assault and other charges in 2007.
In both cases, the public was initially elated to learn of the miracle recovery of a missing child but then began questioning the victim, he said.
"People have a hard time putting themselves in the victim's shoes," he said. "No matter what anyone has to say about this young lady out in California, she has nothing but a better future ahead of her."
Categories: -News-
Leave a Reply
You must be logged in to post a comment.


text:
* Shipping Cost is an estimate only - Final rate will be adjusted by Chive before your card is processed.
Please refer to the Shipping Information in the Help section.
Notify me when this product is available:
Order in multiples of 6 pieces per colour Order 48 pcs of more, receive a price break to £2.75 each (Mix and Match colours to reach 48 total) Material: Ceramic...
View full product details
© 2023 Chive UK Wholesale.
All rights reserved.


text:
Recent articles in the Guardian and other publications tells of strawbale "Council housing" in the UK. Council houses are a form of social housing. The local council builds the houses which are then offered at a subsidised rent to people who are unable to afford full rental values.
Straw houses are baling out council building plans
Straw Bale Council House, Lincolnshire
North Kesteven District Council page on Straw Council Houses
Building Research & Information, Volume 39, Issue 1, January 2011, pp. 51–65, ISSN 0961-3218


text:
Release Date: 2012 |
Xenophanes EMERITUS (2.5)Incredibly tepid and uncharacteristically dull, "Koi No Yokan" sees Deftones forget what h...Project (3)Beauty that assaults your ears for an hour, begging you to tell her she's pretty the whole...Deadwing42 (4.5)Colors explode across the spectrum of a new Deftones sound that explores beauty, brutality...NagasakiBomber (4)Many bands wish they were able to release an album as consistently jaw dropping as this on...
Flashmobba (4)With Koi No Yokan, Deftones master the art of blending textures heavy and light, forebodin...pbass0 (4.5)Continuing to blend beauty and primal aggression like no band before or after, Deftones re...Bwgrotha1s (4.5)Just another great CD you can have in your collection from the Deftones...BassDemon333 (4.5)Bursting at the seams with energy, aggression, and emotion, Koi No Yokan sits comfortably ...
AdamE (5)Deftones shed their superficial skin as an Alt-Metal band and finally show their textures ...DirEnRefused (2)Painful in my indifference....fiendish (4.5)Yeah, it's a Deftones release, but it ain't just another Deftones release. They've o...someguest (5)Love....
MezoIsMusic (4.5)"Koi No Yokan" is a truly beautiful Japanese concept that is untranslatable. It is the...Chinomaster182 (4)Deftones in their new record have managed to navigate the close gap between staying true t...GiantMan (3.5)Deftones remain at the top of their game, but still with room to grow....Timmah99 (3.5)Maybe they're getting tired....
stalinrules (2)Introducing: 2012's most overrated album....wwba (2)Extremely mediocre (I can't see why so many people overrate it) but it has a few decent mo...Nick Mongiardo (4)
good review
I hope this doesn't gets featured, even if it's a contributor review, too much Deftones D. sucking
going on lately.
Album Rating: 3.0pukka review, pos, not a fan of the band tho
Album Rating: 3.5 | Sound Offstyle over substance on a lot of this album
"style over substance on a lot of this album"
album needs more screams like the ones on royal and prince on diamond eyes. besides that, vocals are chinos best since white pony
Album Rating: 4.0 | Sound OffVery good review as always.
Need to give it another spin to rate it, but the first impression was good.
Album Rating: 3.5Yay, another review along the same lines as all the others...
First three songs suck, but the rest of the album is great.
Album Rating: 4.0lol
wish graphic nature didn't suck otherwise it'd be a 5
Album Rating: 4.0doesn't suck
Album Rating: 4.0boring
Album Rating: 4.4The only track that seems underwhelming to me is the last one.
Album Rating: 4.0like that's never happened before
Album Rating: 5.0 | Sound Off"@andcas, you should 5 it without listening like 150 people did before it was released."
Funnily enough there was a score wipe.
Album Rating: 2.0 | Sound Offcrap over crap
Album Rating: 4.5damn...
Album Rating: 4.2Great review Greg, pos. Finally there's some staff/contributors reviewing this. The album is great, most probably AOTY for me, even though Greenleaf's Nest Of Vipers it's still cool haha.
Album Rating: 4.4Thanks. I have a feeling (lol) it'll top many year-end lists. Not so sure it'll top mine though.
Album Rating: 4.5What Happened To You? has grown a lot on me actually. I didnt think it was much of a good closer when I first heard it but now I think its one of their best (although its still got nothing on Pink Maggit)
Album Rating: 4.4I agree with BassDemon. Pink Maggit is their best closer. There's no contest.
Bands: A B C D E F G H I J K L M N O P Q R S T U V W X Y Z


text:
point/center wrote:NDSportsFan wrote:Rib Fest in Fargo!
guy has to get a home equity loan to buy a rack a that...but yeah...that pretty much steals the show for selection quality. get a side of slaw for the summer time salmonella fix in 90 degree heat...does it get any better?
As long is there some cold ones to go with those ribs.


text:
Robert Downey Jr. has battled substance abuse problems for most of his life. But the actor's craft has never suffered. His talent has shown through in films such as Soapdish, Wonder Boys and Iron Man.
© 2023 Movie Fanatic
About Us | Copyright Inquiry | Privacy Policy | Contact Us
© 2023 Movie Fanatic
Sign up for our daily newsletter to receive personalized movie news for
No thanks. I hate movies.


text:
This lush Spathiphyllum floor plant is a favorite variety because of its easy care requirements and deep green foliage. Small Measures approximately 29"-22"H. Medium Measures overall approximately 32"H x 27"L. Large Measures overall approximately 31"L-37"H.
Order by 10:00 AM EST for same day delivery!
* Fee charged in addition to the Standard Delivery Fee
Enter full name. We'll ask for delivery information at checkout.
Box of Assorted Chocolates.
Add a cute plush from our plush selection. Selected plush will vary.
18" Happy Birthday Mylar Balloon. Styles may vary.
18" Happy Anniversary Mylar Balloon. Styles may vary.
18" I Love You Mylar Balloon. Styles may vary.


text:
Robert "Joe" Brown
Verona, WI/Stockton, IL- Robert "Joe" Brown, age 80, was taken to his heavenly home on Wednesday, January 23, 2013. Joe was born in Stockton, IL on March 15, 1932 to Scott and Helen (Carroll) Brown. He married the love of his life, Salome J. Hicks on June 16, 1951. Joe worked as a car salesman for 48 years, proudly selling Lincoln-Mercury products for Gordie-Boucher in Madison and Janesville. His love and devotion to faith, family, friends and work was unprecedented. He also enjoyed sports, playing cards, golf, hunting, and living every day with enthusiasm and gratitude. Joe will be deeply missed by all who knew and loved him.
Joe is survived by his wife of 61 years; children, Pam (Michael) Grant, Dan (Rachel) Brown, Veronica (Jim) Savoie, Jean Brown (Brad) Ama; grandchildren, Luke and Emma Grant, Collin and Ryan Brown, Elie, Delaney, Mady and Sophie Savoie, Cria and Isaac Ama; Our beloved Joe is further survived by other loving relatives and many dear friends.
He was preceded in death by his parents; brother, Gene; sister, Mary Jeanette and niece Carol Waller.
A Mass of Christian Burial will be held at 1 p.m. on Saturday, January 26, 2013 at ST. ANDREW CATHOLIC CHURCH, 301 N. Main St., Verona, with Fr. William Vernon presiding. A visitation will be held before the Mass from 10 a.m. until 12:30 p.m. on Saturday, at the RYAN FUNERAL HOME, VERONA CHAPEL, 220 Enterprise Drive.
Very special thanks to all at Gordie-Boucher, St. Mary's Hospital-Janesville and U.W. Hospital-Madison, for their kindness and compassion in Joe's final days.


text:
U.S Treasury Bond Interest Rate History Since 1900
|U.S. Treasury Bond Interest Rate History
The graph above (click on image to expand) shows U.S. interest rates beginning in 1900. From 1953 onward, the rates are
10-year U.S. Treasury Note rates, plotted monthly; prior to 1953, they're the less granular.
Note: The graph has been updated through 2012. While the statistics below do not fully reflect market performance since the original publication date. I think the main points in the original analysis are still relevant. For the most recent 10-year rates, see the March, 2013 Market Update.
Highest, Lowest and Average Interest Rates Since 1900Since 1900 yields have ranged from a little less than 2%, to 15.3%; the average rate was 4.9%. However, the left hand side of this graph clearly represents a different world from the right hand side. Somewhere between the mid-50's and the mid-70's, rates became much more volatile.
From 1900 through 1959, interest rates ranged from the all-time low of a little less than 2.0% in 1941 to a high of 5.1% in 1921 -- a range from low to high of only 3.1%; the average rate was 3.3%. Since then, the range has been from the December 2008 financial panic low of 2.4% to the September 1981 "all-time" high of 15.3% -- a range of almost 13%; the average rate during that period was 6.7%.
The outstanding feature of this graph is clearly the 50 years beginning around 1960. During this period, we have seen yields go from less than 4% to more than 15%, and back again. The average rate has doubled, from 3.3% to 6.7%, and the range of rates has quadrupled! Are interest rates normally as consistent as they were from 1900 to 1960? Or, is the boom-bust cycle afterwards more typical? It's difficult to tell from this graph.
The Impact of Falling Interest Rates/Yields
What is clear is that "recent" history could seriously mislead investors who evaluate investment prospects by looking at the last 3, 5, 10, or even 25 years. Interest rates have declined more or less steadily for the last 30 years, from more than 15% to less than 3%. Falling yields are great for bond investors -- especially those buying intermediate or long-term bonds. These buyers receive higher than prevailing rates, and/or they benefit from appreciation in the price of their bonds caused by the falling rates (see Yield to Maturity & Interest Rate Risk).
Unfortunately, the returns that bond funds provide when rates are falling from 15% to 3% cannot be repeated if interest rates are already at 3%!
Is There a Bond Bubble? The Hidden Risk in Bond FundsIn October 2010, the yield on 10-year Treasury Notes was 2.54%, not far off the 2.4% low set during the financial panic near the end of 2008. These are historically low rates. To find comparable rates, you have to go back more than 50 years, to 1954. Even in the pre-1960 world, these would be below average interest rates.
Because of the relationship between yield and bond price, near all-time low interest rates mean near all-time high bond prices. It's a near certainty that bond prices can only go down from here -- though it won't necessarily happen immediately. As a result, not only are investors in intermediate and long-term treasury bond funds less likely to continue to benefit from falling rates, they are likely to see price decreases when rates increase.
How much impact could that have? Just to make the point (i.e., this is a completely hypothetical example), consider if 10-year interest rates were to immediately increase from 2.5% to the "100-year" average rate of 4.9%; holders of new bonds would see a price decrease of almost 20%. An increase to the more recent average of 6.7% would translate into a price decrease of closer to 30%.
Past Performance is not a Guarantee of Future ReturnsFund flows into bond funds have increased dramatically over the last two years. Investors in intermediate and long-term funds expecting a repeat of "recent" performance will be disappointed. Those seeking "safety" -- to avoid risk -- may well be equally disappointed. The out-performance of bonds over the last 10 (or 30, or ...) years does not mean that bonds are a better investment than the alternatives that they out-performed, only that bonds at the right price are.
Value matters.
How often have rates been below, say, 3%? See Analysis of 10-year Treasury Note Interest Rate History. It presents interest rate history as a histogram (frequency chart), and considers the potential impact of interest rates on the stock market and real estate.
July 25, 2012 Update: Treasury Interest Rates at All-Time Record LowsWe are experiencing the lowest interest rates in U. S. history -- even lower than they were during the Great Depression. On July 25, the U.S. Department of the Treasury 10-year constant maturity series closed at a new all-time low yield of 1.43%.
Why Did My Bond Fund Lag When Treasuries Rallied? discusses the difference in the impact of the falling rates on treasury returns vs. intermediate bond fund returns. For an additional discussion of "duration," see related materials below.
Related MaterialWhere Are Interest Rates Headed? My unique methodology for forecasting interest rates.
Popular Delusions: The Bull Case For Safe Havens by Dylan Grice, via Mauldin Economics. "Government bonds aren't always the market's safe haven..." (you'll need to subscribe, but it's free.)
Analyzing Treasury Interest Rates since 1900: historical likelihood of yield being above/below 2%, 3%, 4%, etc.; potential impact of rate changes on stock market & real estate.
10-Year T-Note Real Return History calculates the inflation-adjusted returns for hypothetical investors buying the same bonds used for the graph in this post.
Why Treasury Bonds Look So Risky Right Now: April 2012 article from Morningstar.
Yield to Maturity & Interest Rate Risk: for more on how to calculate the impact of rising interest rates on bonds.
The Importance of Duration: for more on the impact of changing interest rates, and how to estimate their impact.
Other 100-Year Posts
100 Years of Inflation Rate History: an overview of the impact of inflation.
100 Years of Real Estate Price History: Shiller's housing price index history, plus intro to the economics of real estate.
100 Years of Stock Market History: Similar perspective as this post on stock market.
Pre-1953: Robert Shiller "Irrational Exuberance" data, compiled based upon Sidney Homer's "A History of Interest Rates."
1953 forward: U.S. Government 10-Year Treasury Constant Maturity Rates (GS10 series).
Current U.S. Interest Rates: for the most recent rates for U.S. Treasuries from 1 month to 30 years.
For lists of other popular posts and an index of stock & bond-related posts, by subject area, see the sidebar to the left or the blog header.
Copyright © 2010. Last modified: 3/30/2013
Share This ArticleTo share via Facebook, Twitter, etc., see the top of the page.


text:
The Shuttle Radar Topography Mission (SRTM) has produced the first high-resolution, near-global elevation dataset of Earth. In recognition of this achievement, and as an illustration of the data, the United States Library of Congress now displays a "solid terrain model" of Los Angeles and adjacent mountainous terrain. The model was created by carving a high-density foam block using computer-guided drills that referenced the SRTM dataset. The block was then covered with a Landsat satellite image using computer-guided paint guns that referenced both the Landsat image and the SRTM dataset. The view shown here mimics the actual model on display at the Library of Congress and was generated from the same satellite image and elevation data sets.
The model shows the Pacific Ocean and Santa Monica Mountains along the Malibu Coast (lower left), San Fernando Valley (left center), downtown Los Angeles (bottom center), San Gabriel and Pomona Valleys (lower right), San Gabriel Mountains (right center to far right), and part of the Mojave Desert (upper right). Colors are enhanced true color with added topographic shading, and elevation differences are exaggerated 1.5 times. The view is toward the north-northwest.
The Los Angeles region was chosen for the Library of Congress model because it illustrates so many ways that topography affects the daily lives of people. The region consists of a coastal plain, inland valleys, mountains up to 3068 meters (10,064 feet), and a desert interior. Topography blocks the landward influence of marine airmasses here such that summer temperatures often differ by 40 degrees Fahrenheit (22 C) across this region at a given moment even at similar elevations. Temperatures also typically cool with rising elevation, and winter storms drop most of their moisture in the mountains, leaving little rainfall for areas further inland, thus creating the deserts.
Topography also controls the land use pattern. The mountains are mostly very rugged, which greatly limits urban expansion. Similarly, major transportation routes are limited to a few mountain passes. Water supply to the city and drainage away from it both follow paths largely dictated by topography. Radio, television, and cell phone transmission towers are all sited with topography in mind to maximize coverage.
Its climate and scenic mountain surroundings have been a major part of the appeal of the Los Angeles region as it has grown into one of the world's largest cities over the past 150 years. But the topography that has created this environment also results from and leads to significant natural hazards. The tall mountains result from tectonic compression and uplift of Earth's crust along a kink in the San Andreas fault. (The fault is seen here as a straight boundary between the Mojave Desert and the San Gabriel Mountains.) Major earthquakes occur on the San Andreas fault every few centuries. Damaging earthquakes also occur on other faults across the region several times in a typical human lifespan. Most of these faults were first recognized by their impact upon the topographic pattern. Meanwhile, wildfires are common in the chaparral covered hills and mountains, and topography affects the fire's path (burning more readily upslope) as well as our ability to fight it. After a fire, rainfall from winter storms often strips exposed soil, accumulates it as mudflows in rugged canyons, and dumps it into the adjacent valleys which are now heavily urbanized. Topography is indeed important in the lives of the people of Los Angeles.
Landsat has been providing visible and infrared views of the Earth since 1972. SRTM elevation data substantially help in analyzing Landsat images by revealing the third dimension of Earth's surface, topographic height. The Landsat archive is managed by the U.S. Geological Survey's Eros Data Center (USGS EDC).
Elevation data used in this image were acquired by the Shuttle Radar Topography Mission (SRTM) aboard the Space Shuttle Endeavour, launched on February 11, 2000. SRTM used the same radar instrument that comprised the Spaceborne Imaging Radar-C/X-Band Synthetic Aperture Radar (SIR-C/X-SAR) that flew twice on the Space Shuttle Endeavour in 1994. SRTM was designed to collect three-dimensional measurements of the Earth's surface. To collect the 3-D data, engineers added a 60-meter-long (200-foot) mast, installed additional C-band and X-band antennas, and improved tracking and navigation devices. The mission is a cooperative project between the National Aeronautics and Space Administration (NASA), the National Geospatial-Intelligence Agency (NGA) of the U.S. Department of Defense (DoD), and the German and Italian space agencies. It is managed by NASA's Jet Propulsion Laboratory, Pasadena, Calif., for NASA's Earth Science Enterprise, Washington, DC.
Size: Block length 120 kilometers (74 miles), block width 60 kilometers (37 miles) Location: 34.2 degrees North latitude, 118.3 degrees West longitudeOrientation: View North-Northwest, 1.5 times vertical exaggerationImage Data: Landsat bands 3, 2, 1 as red, green, blue, respectively, plus elevation shading. Date Acquired: February 2000 (SRTM), May 4, 2001 (Landsat)


text:
Show Responsive Columns in Posts with Widgets
Do you want to arrange widgets horizontally? If so, this plugin may be the solution for you.
Add desired widgets to the custom sidebar the plugin creates and set up an auto-insert.
If you are a developer and looking for an easy way to render some outputs in responsive columns, this plugin will be handy. Pass your arrays to the plugin filter. Then the plugin will take care of it for you.
How It Works
- Add widgets.
- Enter the number of columns.
- Enable Auto-insert or insert the shortcode.
Displays Widgets in Columns
The plugin will let you display widgets horizontally with a grid system. This is the main feature of the plugin.
Responsive Design for Mobile Visitors
When the browser width changes, it automatically adjusts the layout. This is important for tablet and mobile visitors.
Set Number of Columns per Row
You can flexibly set the number of columns in each row.
Set Number of Columns by Screen Width
Flexibly set the number of columns by browser width. In other words, you can control the number of columns for particular screen widths.
Show Responsive Columns Everywhere
Take advantage of the Auto-insert feature which automatically inserts the defined widget box to your desired location. You don't have to use the shortcode.
PHP code and Shortcode
Use PHP code in the theme template or the shortcode in posts.
Default Sidebars Integration
Sidebars defined by your theme also can be displayed in columns.
Create Complex Columns
Achieve more advanced complex design by taking advantage of the options that the plugin provides.
Nesting Sidebars
This is widgets in widget functionality. With the widget that the plugin provides, the whole sidebar contents can be embedded as a widget item into another sidebar.
Column Span
Column spans are configurable so that you can set wider widget areas.
For Developers
Custom Array
If you can code, you can pass an array to the plugin's filter so that your array contents can be rendered in multiple columns instead of widgets.
See more.
Basic Three Steps
- Go to Appearance > Widgets. You'll see a new custom sidebar box named Responsive Custom Widgets.
- Add widgets to it.
- To display the added widgets in a post, there are mainly two different means.
Option A: add the shortcode in the post.
Option B: use the auto-insert feature by enabling the Enable Auto-insert option in the plugin setting page, New / Edit.
Specify Different Number of Columns in Each Row
By default, the widgets are displayed in 3 columns. It can be changed by setting the columns parameter.
[responsive_column_widgets columns="4"] will display the widgets in 4 columns.
Optionally, if you like to change the number of columns in each row, use sequential numbers separated by commas.
For instance,
[responsive_column_widgets columns="3,2,5"] will show the widgets in 3 columns in the first row, 2 columns in the second, and 5 to the third. Change the numbers accordingly for your needs.
To set the number of columns for each screen max-width, use the pipe (|) character as the delimiter and place the width in pixel followed by a colon (:). Omit the width for no limitation. For instance,
[responsive_column_widgets columns="5 | 800: 4 | 600 : 2 | 480: 1"] will show the widgets in 5 columns when the browser widths is greater than 800, and 4 when the browser width is 800 to 601, and 2 when the browser width is 600 to 481, and 1 when the browser width is less than or equal to 480.
Use PHP code for Themes
The widget box can be displayed outside post/pages. Putting a PHP code into the theme is one way of doing it. Use the
ResponsiveColumnWidgets() function.
For instance,
<?php if ( function_exists( 'ResponsiveColumnWidgets' ) ) ResponsiveColumnWidgets( array( 'columns' => 5 ) ); ?> will display the widgets in 5 columns.
There are other parameters besides columns.
- columns – the number of columns to show. Default: 3. If you want to specify the number of columns in each row, put the numbers separated by commas. For instance, 3, 2, 4 would display 3 columns in the first row and 2 columns in the second row and four columns in the third row and so on. The rest rows follow the last set number. To set the number of columns by screen max-width, use the colon(:) character after the width, and use the pipe (|) character to delimit each set of number of columns. If the pixel is omitted, it is considered no limit. If the pipe delimiter is not present, the plugin will add 600: 1 internally by default.
column value | pixel: column value | pixel: column value | ...
The following example displays widgets in 5 column when the browser width is greater than 800, and four when the width is 601 to 800, and three when the width is 481 to 600, and one when the width is 1 to 480.
5 | 800: 4 | 600: 3 |480: 1
- sidebar – the ID of the sidebar to show. Default: responsive_column_widgets. For the twenty-twelve theme, sidebar-1, would show the default first sidebar contents.
- maxwidgets – the allowed number of widgets to display. Set 0 for no limitation. Default: 0.
- maxrows – the allowed number of rows to display. Set 0 for no limitation. Default: 0.
- omit – the numbers of the widget order of the items to omit, separated by commas. e.g. 3, 5 would skip the third and fifth registered widgets.
- showonly – the numbers of the widget order of the items to show, separated by commas. e.g. 2, 7 would only show the second and seventh registered widgets. Other items will be skipped.
- label – the label name of the widget box. Default: Responsive Column Widgets.
- colspans – the column spans. This determines how wide the specified widget item is.
widget index - column span, widget index - column span, widget index - column span, ...
The following parameter value of colspans will set the first widget with 3 column space and the fourth widget with two column space and the seventh takes four column space. Unspecified widget items will have one column span.
1-3, 4-2, 7-4
To set them by screen max-width, like the columns parameter, use the colon(:) character after the width in pixel, and use the pipe (|) character to delimit each set of column spans. If the pixel is omitted, it is considered no limit. These widths need to correspond to the value passed to the columns parameter. e.g.
1-3, 4-2, 7-4 | 600: 1-2, 3-2, 7-3 | 480: 1-2
If the column span exceeds the set number of max column, the column span will follow the max column. Note that the widget index of omitted widgets will not be considered(counted) in the widget index of this parameter.
- cache_duration – the cache lifespan in seconds which determines how long the cache remains. Default: 0. e.g.
- call_id – this is for developers. This is used to identify the callback when a plugin hook is used so that the callback method assigned to the hook can know if it is theirs or not. This parameter does not affect the style based on the parameter values.
Render Custom Array in Multiple Columns
If you are a developer, you can render array contents that hold string values in multiple columns with responsive design.
Let's take a look at an example. First, insert this shortcode in a post or a page.
[responsive_column_widgets call_id="days" columns="7"]
The value for the call_id parameter can be any string that identifies the call.
Now we need to hook into the RCW_filter_widget_output_array filter so that we can intervene the process of plugin's rendering widgets. It accepts two parameters. The first one will be the output array and the second one is the parameter array.
In the callback function for the filter, we check if the parameter call_id holds the correct value. You should change the value to suite your needs, which should be unique and not conflict with others.
add_filter( 'RCW_filter_widget_output_array', 'RCW_CustomArrayOutput', 10, 2 );
function RCW_CustomArrayOutput( $aOutput, $aParams ) {
if ( ! isset( $aParams['call_id'] ) ) {
return $aOutput;
if ( 'days' === $aParams['call_id'] ) {
return array( 'Sunday', 'Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday', 'Saturday' );
return $aOutput;
This will display the days in 7 columns. The plugin will generate the CSS rules based on the parameter values. And the rules will be inserted inside the body tag.
If you like to insert the style in the head tag, use the ResponsiveColumnWidgets_EnqueueStyle function. Tell the function that which parameters are going to be used.
add_filter( 'wp_loaded', 'RCW_CustomArrayAddStyle' );
function RCW_CustomArrayAddStyle() {
if ( function_exists( 'ResponsiveColumnWidgets_EnqueueStyle' ) ) {
ResponsiveColumnWidgets_EnqueueStyle( array( 'columns' => "7" ) );
Note that
'call_id' => 'days' can be omitted. The other parameters should not be omitted.
For cases that the shortcode is not used, you can use the ResponsiveColumnWidets() function.
$aYourArray = array( 'a', 'b', 'c', 'd' );
if ( function_exists( 'ResponsiveColumnWidets' ) ) {
array( 'columns' => 4 ),
This will output
a, b, c, d in four columns.
Video Tutorials
- Upload
responsive-column-widgets.phpand other files compressed in the zip folder to the
- Activate the plugin through the 'Plugins' menu in WordPress.
How to Use
Go to the Other Notes section.
- Installation Instructions
- Upload
responsive-column-widgets.phpand other files compressed in the zip folder to the
- Activate the plugin through the 'Plugins' menu in WordPress.
How to Use
Go to the Other Notes section.
- Upload
- How do I get started?
Go to Appearance > Widgets and add widgets to the plugin's custom sidebar box. Then use the shortcode in a post. That's it. If you still cannot figure it out, take the screenshots of the wp-admin/widgets.php page and the page of the post you added the shortcode. And request a support with the screenshots.
- How do I customize the style?
You can add your rules to the classes named .responsive_column_widget_box .widget. Go to the widget box's edit page and enter your custom rules in the Custom CSS section or define it in your theme's style.css.
.responsive_column_widget_box .widget {
padding: 4px;
line-height: 1.5em;
background-color: #EEE;
- Are there video instructions?
Yes. Hope this helps.
- Is it possible to create multiple widget boxes?
Yes, with Pro.
- It seems the plugin conflicts with my theme. Can you help?
It happens occasionally. Please ask for support with a link to your live site and the screenshots. In most cases, it can be solved by adjusting CSS rules causing the conflicts.
- Up to how many columns can I create
You can set up to 12 columns.
- I have a feature request. Would you listen?
Sure. Please post it in the forum or the comment section of the plugin page.
Contributors & Developers
"Responsive Column Widgets" is open source software. The following people have contributed to this plugin.Contributors
"Responsive Column Widgets" has been translated into 2 locales. Thank you to the translators for their contributions.
Translate "Responsive Column Widgets" into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
1.2.7 – 06/10/2018
- Fixed a compatibility issue with PHP 7.1 which caused an error of illegal string offset.
- Fixed a WordPress notice,
Notice: get_screen_icon is deprecated since version 3.8.0., appeared in setting pages.
1.2.6 – 12/16/2016
- Fixed a compatibility issue with WordPress 4.7 that caused a warning
wp_kses_js_entities is deprecated.
1.2.5 – 12/22/2015
- Fixed a compatibility issue with PHP 7 which caused a fatal error.
1.2.4 – 11/29/2015
- Added an icon in the setting page which appears when no widget is added.
1.2.3 – 05/06/2015
- Fixed a compatibility issue with WordPress 4.2 that category terms were not listed in the widget box definition page.
1.2.2 – 04/25/2015
- Fixed a compatibility issue with WordPress 4.2 in plugin setting pages.
1.2.1 – 03/09/2015
- Fixed a bug with a zero left-margin inherited from different screen widths.
1.2.0 – 01/14/2015
- Fixed an issue that columns were not properly displayed in Internet Explorer 8.
- Tweaked the layout of the plugin setting page.
- Optimized the performance.
1.1.12 – 10/13/2014
- Changed some option names.
- Fixed a PHP warning undefined constant WPLANG.
- Fixed a PHP warning
Warning: strpos() empty delimiter....
1.1.11 – 04/22/2014
- Tweaked: the styling of the plugin admin setting page.
- Changed: the tab label
General Optionsto
Generalin the plugin admin setting page.
- Changed: the default option
Delay Sidebar Registrationto be checked by default.
1.1.10 – 04/19/2014
- Fixed: a bug that column margins were not calculated correctly in different set max-widths.
1.1.9 – 02/21/2014
- Added: the option to delay sidebar registration.
- Added: the Serbo-Croatian language file.
220.127.116.11 – 01/08/2013
- Fixed: a compatibility issue with the Twenty Fourteen theme.
- Tweaked: the styles of the setting pages of the plugin for WordPress v3.8.
126.96.36.199 – 10/01/2013
- Fixed: a compatibility issue with Twenty Thirteen.
18.104.22.168 – 09/14/2013
- Fixed: the minimum required WordPress version number to 3.3.
- Fixed: a bug that comma delimited option values could not be saved as of 1.1.7.
18.104.22.168 – 09/09/2013
- Fixed: an issue that when an integer is passed to the columns or colspans parameter with the the ResponsiveColumnWidgets() function, the parameter value did not get recognized.
- Added: the second parameter to the ResponsiveColumnWidgets() function that enables to render custom array in responsive columns.
- Fixed: a bug undefined object error occurred when a cache is expired.
1.1.8 – 09/05/2013
- Added: the call_id parameter that does not affect the CSS rules based on parameter values.
- Added: the RCW_filter_widget_output_array filter that enables to render custom PHP array in responsive columns.
- Fixed: an issue that the page load gets too slow in the plugin's setting pages.
188.8.131.52 – 08/18/2013
- Fixed: the warning, Notice: Undefined property: ResponsiveColumnWidgets_AutoInsert::$arrClassSelectors…
18.104.22.168 – 08/17/2013
- Fixed: the warning, Strict standards: Only variables should be passed by reference in …\wp-content\plugins\responsive-column-widgets\classes\ResponsiveColumnWidgets_Option_.php on line 367.
- Fixed: the warning, Strict standards: Only variables should be passed by reference in …\wp-content\plugins\responsive-column-widgets\classes\ResponsiveColumnWidgets_StyleLoader.php on line 55.
- Fixed: the warning, Strict standards: Declaration of ResponsiveColumnWidgets_Admin_Page_Framework_Walker_Category_Checklist::start_el() should be compatible with Walker::start_el(&$output, $object, $depth = 0, $args = Array, $current_object_id = 0) in …\wp-content\plugins\responsive-column-widgets\classes\ResponsiveColumnWidgets_Admin_Page_Framework.php on line 2593.
- Fixed: a bug that a log file was created when WP_DEBUG is true.
184.108.40.206 – 08/06/2013
- Fixed: an issue that the page in widgets.php freezes in IE in WordPress 3.6.
- Tweaked: the plugin's JacaScript script loaded in the widgets.php page.
- Changed: the Responsive Column Widget Box widget form selector option to have the first item with the empty value which prevents unwanted sidebar dependency conflicts.
- Fixed: a bug that orphaned sidebars named Inactive Sidebar (not used) appeared in the select option items of the plugin's Responsive Column Widget Box widget's form after switching the theme.
- Fixed: a bug that the error "FATAL ERROR: MAXIMUM FUNCTION NESTING LEVEL OF '100' REACHED, ABORTING!" occurs when a sidebar dependency conflict occur with the sidebar encapsulation functionality and added an plugin error message instead.
- Fixed: a bug introduced in 1.1.7 that undefined index warnings and errors with array_filter() occur when a theme's sidebar is used instead of the plugin's widget box.
220.127.116.11 – 08/01/2013
- Fixed: a typo of the newly added option description in v1.1.7 in the New/Edit settings page.
220.127.116.11 – 07/30/2013
- Fixed: a bug that options were not loaded properly after updating to 1.1.7.
1.1.7 – 07/30/2013
- Added: the Container Background Color, Container Paddings, and Widget Box Maximum Width options.
- Changed: not to go to the Manage tab page when editing a widget box setting.
- Changed: the sidebar class selector to have own div element enclosing the widget box output. Accordingly the users who were using the CSS rule with the class selector such as
.responsive_column_widgets_box.responsive_column_widgets { ... }shuold change it to
.responsive_column_widgets .responsive_column_widgets_box.
- Added: the Widget Box Beginning Tag and Widget Box Ending Tag options.
1.1.6 – 06/29/2013
- Updated: the Japanese translation.
- Updated: the POT file.
- Added: the Clear Caches option in the General Options setting page.
- Added: the cache_duration parameter, which sets the cache for the widget box's output.
- Fixed: a bug that caused importing widget boxes to fail.
- Tweaked: the code to reduce one database query performed with the Auto-insert feature when no widget box item enables it.
126.96.36.199 – 06/27/2013
- Tweaked: the code to reduce the number of database queries performed in the settings pages.
- Tweaked: the code to reduce the used memory size in the settings pages.
184.108.40.206 – 06/26/2013
- Tweaked: the code to reduce the number of database queries performed in the settings pages of the plugin.
188.8.131.52 – 06/25/2013
- Fixed: a bug that updating the options in the General Options page removed a license value for the Pro version.
18.104.22.168 – 06/25/2013
- Tweaked: the layout in the settings pages.
- Added: the Execute Shortcodes in Widget Boxes option.
- Added: the RCW_filter_widgetbox_output filter that applies to the widget box outputs.
18.104.22.168 – 06/23/2013
- Added: the Minify CSS Code option.
18.104.22.168 – 06/16/2013
- Updated: the POT file.
- Fixed: a bug that the registered code with a blank parameter was listed twice in the Enqueue Styles in Head Tag option area in the setting page.
- Tweaked: the style for Twenty Thirteen 0.1.
1.1.5 – 06/14/2013
- Added: the colspans parameter.
126.96.36.199 – 06/03/2013
- Tweaked: to return the passed value for filters of the Auto-Insert feature if it is not a string.
- Supported: Twenty Thirteen 0.1.
188.8.131.52 – 05/18/2013
- Tweaked: the administration object not to load if non-admin pages are loaded.
- Tweaked: the plugin not to load when accessed directly.
- Fixed: a bug that a freeze occurred in the widgets.php page in IE.
220.127.116.11 – 05/17/2013
- Added: the option to enable/disable the Responsive Column Widget Box widget.
- Added: the ability for the ResponsiveColumnWidgets() function to be called without a parameter.
1.1.4 – 05/13/2013
- Fixed: a bug that updating the options in the General Options page caused the Areas to Load and Class Selector Names values to be empty.
- Fixed: an issue that images in the plugin setting pages sometimes did not load properly.
- Reduced: the memory usage in the plugin setting pages for servers with PHP below 5.3.
- Added: the Debug Mode option.
1.1.3 – 05/10/2013
- Added: the widget that encapsulates a sidebar.
18.104.22.168 – 04/29/2013
- Changed: the base style to use the parent class selector of the sidebar ID, which was removed in 1.1.2.
- Added: the option to enqueue styles to avoid style tags to be embedded in the body tag.
1.1.2 – 04/27/2013
- Added: the ability to load CSS rules without the scoped attribute for the ones with the Auto-Insert option.
- Changed: the method of rendering widget boxes not to use display:none for different screen max-widths.
220.127.116.11 – 04/23/2013
- Added: the option to decide whether ID attributes should be removed or not.
- Fixed: an issue that updating option items of the General Options removed some of the internal settings.
- Added: the edit icon in the Manage page.
18.104.22.168 – 04/22/2013
- Tweaked: user input sanitisation for string option values including Number of Columns and Class Names.
- Tweaked: the CSS rules for widget box rows.
1.1.1 – 04/21/2013
- Fixed: a typo in the setting page, Min to Max.
- Fixed: an issue that a custom number of columns with the parameter of the percentage offset for column numbers caused a row not to start from the very first column when there was a widget with longer height than the other widgets in the previous row.
- Added: the ability to specify the number of columns by screen max width.
- Deprecated: (Breaking Change) the parameter of the percentage offset for column numbers to support the ability to directly specify the number of columns by screen max width.
- Removed: the ID attribute from the default Widget Beginning Tag value.
- Added: (Breaking Change) the ability to automatically remove ID attributes from the rendered widget HTML code.
- Fixed: an issue that scoped style tag contained a white space in the name attribute value.
1.1.0 – 04/14/2013
- Added: the RCW_filter_base_styles filter that enables to modify the plugin's base CSS rules.
- Added: the CSS rules, width: auto; height: auto;, to the responsive_column_widgets_box class.
- Added: the option for the timing of loading the plugins' CSS base rules.
- Changed: from loading the CSS file in the header but to insert the CSS rules as text to support variadic class attribute names.
- Added: the options for specifying the class name attributes for the CSS rules.
- Added: the options for selecting the areas to load the plugin CSS rules.
1.0.9 – 04/07/2013
- Added: the ability to load the plugin CSS rules in login pages. To display the widget box in the login page, either use the PHP code or set the custom filter in the Auto-Insert section of the plugin admin page.
- Added: the ability to add custom filter/action hooks for the widget box auto-insertion.
- Added: the ability to restrict the widget box auto-insertion by category, post-id, post-type, and page-type.
- Added: the ability to disable the widget box auto-insertion by category, post-id, post-type ( post, page, custom post types ), and page-type ( archives, search, 404, etc. ).
- Fixed: a bug in the Information page that the sub menu list items were displayed with bullet marks in WordPress 3.4.x.
- Renewed: (Breaking Change) the entire Auto-Insert section of the plugin admin page. Accordingly, the previous auto-insert options should be reconfigured.
- Removed: (Breaking Change) the responsive_column_widget_area class attribute. Those who have been using it, should simply change it to responsive_column_widget_box instead.
126.96.36.199 – 04/05/2013
- Tweaked: the form data sanitisation functionality for the numeric sequence values with the comma delimiter.
- Changed: the class attribute name for each column from, col, to responsitve_column_widgts_column, in order to avoid being too generic which may result on conflicts with other plugins or themes.
- Fixed: a bug the responsitve_column_widgts_column_1 class attribute was not displayed correctly introduced in 220.127.116.11.
220.127.116.11 – 04/04/2013
- Fixed: typos in plugin admin pages.
- Added: the class attributes, responsitve_column_widgts_column_{n} and responsitve_column_widgts_row_{n}, to each div tag containing a widget, where _{n} indicates the position of the column and row.
220.127.116.11 – 04/01/2013
- Fixed: a bug that the notification which appears when no added widget is added appeared in other plugin pages.
126.96.36.199 – 03/25/2013
- Fixed: a bug that the WordPress version 3.4.x or below got Fatal error: Cannot make non static method SimplePie::sort_items() static in class ResponsiveColumnWidgets_SimplePie_ in …/wp-content/plugins/responsive-column-widgets/classes/ResponsiveColumnWidgets_SimplePie_.php on line 21.
22.214.171.124 – 03/24/2013
- Fixed: a typo in the plugin admin page footer.
- Updated: the information page.
- Changed: the requirement check to perform only upon the plugin activation from loading the plugin admin page.
184.108.40.206 – 03/23/2013
- Fixed: the warning that occurred in debug mode in a Not Found page, Undefined property: WP_Query::$post.
22.214.171.124 – 03/21/2013
- Fixed: a bug that the widget box was inserted below the comment form regardless of whether the option was checked or not.
1.0.8 – 03/20/2013
- Fixed: a bug that when multiple widget boxes with different sidebar IDs were present in one page, only the first widget box's custom style was loaded; the other custom styles' set to each box did not load.
- Fixed: a bug that when multiple widget boxes with different sidebar IDs were present in one page, only the first widget box was responsive; the responsive rules did not apply to the other widget boxes.
- Added: the ability to auto-insert the widget box into the comment form section.
- Fixed: the warning that occurred in some servers, "Parameter 1 to ResponsiveColumnWidgets_Startup() expected to be a reference, value given in …/wp-includes/plugin.php on line 406."
184.108.40.206 – 03/19/2013
- Added: a warning message when there is no widget added to the widget box in the edit page.
- Added: the setting to attempt to override the memory limit for PHP set by the server.
- Added: the Japanese translation.
- Added: the localization support with the text domain, responsive-column-widgets.
1.0.7 – 03/18/2013
- Added: the ability to disable the auto-insert option for both footer and posts/pages by post IDs and the checkbox for the front page.
- Added: the ability to auto-insert the widget box into post and pages above/below the contents.
- Fixed: a minor bug that merging with the default option values did not perform correctly when the subject option key had a null value.
184.108.40.206 – 03/13/2013
- Raised: the required WordPress version to 3.2 from 3.0.
- Fixed: an issue that the user with a custom access level could not change the options.
- Fixed: minor typographical errors in the setting page.
- Added: the sanitisation functionality for option values with delimiters including Numbers of Columns, Omitting Widgets, Show-only Widgets, Width Percentage Offsets, and Additional Allowed HTML Tags.
- Added: the requirement check which includes PHP version to 5.2.4 or higher.
- Tweaked: the code to load the pages faster in the admin pages.
1.0.6 – 03/11/2013
- Fixed: a bug that saving in the General Options page redirected to the Manage page in the plugin admin pages.
- Added: the ability to set custom style rules per widget box.
1.0.5 – 03/09/2013
- Added: the ability to automatically insert the widget box in the footer if the option is checked in the setting page.
- Fixed: a bug that the same ID attribute was applied to the aside tags.
- Changed: a filter name that the plugin internally uses to make the names consistent.
126.96.36.199 – 03/04/2013
- Changed: the Access Rights option not to appear for members other than administrators.
220.127.116.11 – 03/04/2013
- Added: some base files for plugin extensions.
- Added: an action hook for plugin extensions.
- Fixed: a bug that the default widget box options could not be retrieved properly in the table of the Manage tab page when the option initialization was performed.
184.108.40.206 – 03/04/2013
- Fixed: a bug that when settings are saved in one of the pages and the other pages settings get erased introduced since supporting the alternatives of array_replace_recursive().
184.108.40.206 – 03/04/2013
- Fixed: a bug that debug output appeared after submitting the form in General Options page.
126.96.36.199 – 03/04/2013
- Fixed: typos and applied minor description changes to the parts not clear enough.
184.108.40.206 – 03/03/2013
- Fixed: the parts using array_replace_recursive() which is incompatible with below PHP 5.3.
18.104.22.168 – 03/03/2013
- Fixed: an issue that the server below PHP 5.3 got Fatal error: Call to undefined function array_replace_recursive().
184.108.40.206 – 03/03/2013
- FIxed: the version number in the main file.
22.214.171.124 – 03/03/2013
- Fixed: a bug in the file name which contains case-mismatch with the include/require statement, which caused a fatal error during the activation.
1.0.4 – 03/03/2013
- Added: the ability to reset all saved option values.
- Added: the ability to set custom HTML tags to be posted in the setting page.
- Added: the Access Rights option in the setting pages.
- Changed: the default value of the offsets parameter to 600:12, which is 100% compatible with the versions prior to 1.0.3.
- Added: the ability to set the options without the parameters; the saved option values in the setting page will be used.
- Added: the ability to set a custom message when no widget is added.
- Added: the ability to set opening/closing HTML code in front of the widget output and title.
- Added: the ability to specify the widget box by label name.
- Added: the setting pages under the Appearance menu.
1.0.3 – 02/28/2013
- Changed: (Breaking Change) the default number of columns to 3 from 1.
- Added: the ability to flexibly change the number of columns by pixel width with the offsets parameter.
1.0.2 – 02/23/2013
- Added: an additional class attribute to the enclosing div tag named "widget-area," which helps to match the site's sidebar style.
- Added: an enclosing div tag with the class attribute named "widget," which helps to match the site's sidebar style.
- Cleaned: some code.
- Changed: the misleading class attribute name, responsive_column_widgets_newrow, to responsive_column_widgets_firstcol.
- Fixed a minor issue in the stylesheet.
- Added the parameter options including, maxwidgets, maxrows, omit, showonly.
- Added the ability to set the number of columns to show in each row.
- Initial Release