sfW3studioCmsPlugin
1.1.4stable
for sf 1.2 and Propel
LGPL
W3studioCMS is a modern Open Source Web 2.0 Content Management System application designed to give the ability to manage the contents of a web site to people without any knowledge of web programming languages, i.e. HTML or PHP.
Imagine to browse any kind of website, as the one you are viewing now, then imagine the same page you are browsing that becomes editable in place, exactly how you see in in the frontend, for each content it contains: this is how W3studioCMS works. The changes you made are displayed in real time on the same page that you will publish at the end of your editing session by ajax transactions. There's nothing to imagine: here you really see what you get!
W3StudioCMS has no limitation design for the templates' layout: you can easily import any xhtml template and use it for your website. A complete tutorial will explain in detail how to import and use an existing template found in internet.
W3StudioCMS is totally Object Oriented, so you can easily customize the CMS for your needs, extending the core classes or adding new contents. It uses symfony as base framework, so all the benefits introduced by this powerful and great software are available in the CMS.
Developers
License
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.
When we speak of free software, we are referring to freedom of use,
not price. Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.
To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights. These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.
Finally, software patents pose a constant threat to the existence of
any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder. Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License. We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.
When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code with
the library.
We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers Less
of an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for many
libraries. However, the Lesser license provides advantages in certain
special circumstances.
For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it becomes
a de-facto standard. To achieve this, non-free programs must be
allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries. In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software. For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.
Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.
GNU LESSER GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a
copy of the library already present on the user's computer system,
rather than copying library functions into the executable, and (2)
will operate properly with a modified version of the library, if
the user installs one, as long as the modified version is
interface-compatible with the version that the work was made with.
c) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
d) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
e) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!
Changelog for release 1.1.4 - 07/01/2010
2010-01-06 - Version 1.1.4 Stable
1. giansimon: Fixed a bug in updateCombobox function od w3sTools client-side class.
2. giansimon: Fixed a bug related to the extruders.
2010-01-05 - Version 1.1.3 Stable
1. giansimon: The params to configure the extruders for control panel and menu manager has been defined as
aplication variables.
2010-01-04 - Version 1.1.3 Stable
1. giansimon: uploadify can now try to create the folders recursively when a folder doesn't exists
2. giansimon: added a client-side function to clear and fill a select tag.
2009-12-30 - Version 1.1.2 Stable
1. giansimon: frontend module has been totally separated from the backend.
2. giansimon: jquery support has been reviewed. The w3s_jquery_plugins has been added to app.yml to declare which are
the plugins that uses this framework so W3StudioCMS can manage them safety.
2009-12-24 - Version 1.1.1 Stable
1. giansimon: images folder was hardcoded, now uses the w3s_absolute_images_dir param for tiny_mce
2. giansimon: uploadifyPlugin- fixed a bad behaviour in windows
2009-12-22 - Version 1.1.0 Stable
- giansimon: w3sToolkit::linkConverter() has been deprecated and sobstituted by w3sLinkConverter object
2009-12-19 - Version 1.1.0 Stable
- giansimon: page number is no more displayed, when extensionMarkdown has to render only a page.
- giansimon: standard theme and relathed published files moved to plugin's data folder.
2009-12-18 - Version 1.1.0 Stable
- giansimon: fixed a bug in BaseW3sPageManager's deletePageContents() method
- giansimon: fixed a bug in BaseW3sContentManager's getDisplayContentForEditorMode() method which returns a
link in bad format
2009-12-17 - Version 1.1.0 Stable
- giansimon: fixed a bug when deleting a page: user parameter misses
2009-12-16 - Version 1.1.0 Stable
- giansimon: exceptions are now displayed
- giansimon: fixed a bug to load only the stylesheets related to current theme
- giansimon: publish result now display success message color, instead error message color
- giansimon: fixed link colors for menu manager stylesheet.
- giansimon: fixed view.yml config file for w3sExtensionMarkdownPlugin.
2009-12-15 - Version 1.1.0 Stable
- giansimon: default value for template_id_frontentd in w3s_group table is now 0. Fixed BaseW3sTemplateFrontend.class
to reflect this change.
- giansimon: fixed a bug with uploadify tool.
2009-12-14 - Version 1.1.0 Stable
- giansimon: fixed a bug that doesn't change the slot when the slot has any content inside
- giansimon: fixed a bug with BaseW3sRepeatedContentsBaseSite that doesn't save the right slot id when a new
content has to be added
2009-12-13 - Version 1.1.0 Stable
- giansimon: w3sExtensionMarkdownPlugin added to bundled plugins.
- giansimon: extra folder renamed to vendor folder.
2009-12-12 - Version 1.1.0 Stable
- giansimon: fixed xhtml element for the menu manager.
- giansimon: added button to hide/show the menu manager to control panel.
- giansimon: fixed a bug with w3sPagesManager.
2009-12-10 - Version 1.1.0 Stable
- giansimon: tinyMCE module has been renamed in w3sTinyMCE. Fixed the helper
- giansimon: added the idLanguage optional parameter to page delete() method. Pay attention that it is now the first
parameter instead the $op one.
- giansimon: removed the w3sExtensionCssDockPlugin plugin, which will be used when jQuery will be full implemented.
- giansimon: saveMenuWithActiveClass can adapt the menu on other pages as the one which is edited
2009-12-09 - Version 1.1.0 Stable
- giansimon: fixed saveMenuWithActiveClass which now works properly
2009-12-08 - Version 1.1.0 Stable
- giansimon: slotMapper: when a new mapping is saved, the mapped id slots are transferred to contentMapper table
- giansimon: added id_template_frontend to w3sGroup table, to separate the template in production to the new one
in the backend.
- giansimon: fixed repeated contents, which doesn't work properly.
- giansimon: fixed deleting repeated contents when a page is deleted
- giansimon: fixed a problem when the default image is added
- giansimon: fixed some css
2009-12-02 - Version 1.1.0 Stable
- giansimon: fixed a bug related to pages navigation in editor mode.
- giansimon: showLoader module removed
- giansimon: All core objects have been abstracted. The objects that implements the core objects has been deployed
with the bundled plugins that uses those objects. Ie: w3sTemplateEditor that implements BaseW3sTemplateEditor
belongs now to w3sExtensionBackendPlugin.
- giansimon: w3sWidget suffix for bundled plugin has been deprecated and it has been substituted by w3sExtension.
w3sWidget will be removed from 1.2.x releases.
- giansimon: Added w3s suffix to all modules
- giansimon: All modules has been "pluginized".
- giansimon: w3sWebSite module renamed to w3sFrontend module.
- giansimon: w3sWebEditor module renamed to w3sBacked module.
- giansimon: Preview action of webEditor module has been converted into w3sExtensionPreview standalone plugin.
- giansimon: Publish action of webEditor module has been converted into w3sExtensionPublisher standalone plugin.
- giansimon: LoadMenuManager action has been converted in w3sExtensionMenuManagerPlugin standalone plugin.
- giansimon: w3sToolkit renamed to w3sToolkit
2009-11-22 - Version 1.1.0 Stable
- giansimon: fixed a bug with image's paths
2009-11-22 - Version 1.1.0 Stable
- giansimon: added theme upgrade.
- giansimon: fixed a bug with image's editor when it has to open the standard image
- giansimon: fixed a bug with title and alt attributes in image's editor
- giansimon: fixed a bug when adding a content in a slot which hasn't any content inside
- giansimon: removed w3sPublishAssetsTask now managed by symfony's publish-assets task
2009-11-16 - Version 1.1.0 Release Candidate 2
- giansimon: fixed several bugs with template import.
- giansimon: removed the old menu manager which was rendering in a wrong place
- giansimon: removed control panel button from menu manager because it's no more required
2009-11-15 - Version 1.1.0 Release Candidate 2
- giansimon: fixed a bug with metatags.
- giansimon: fixed some bugs with the configuration of w3sUploadify plugin
- giansimon: added w3sExtensionMbExtruderPlugin
2009-11-13 - Version 1.1.0 Release Candidate 2
- giansimon: W3studioCms can now use both the orm and fast queries in mysql.
- giansimon: added orm management for languages, repeated contents and content's extensions
- giansimon: added content's extensions management
- giansimon: languages adding reviewed
2009-09-12 - Version 1.1.0 Release Candidate 1
- giansimon: Drawing slots in Control Panel is now OOP.
- giansimon: Added visual aid for slot repeated at language level
- giansimon: Fixed a bug when deleting the contents related to the page that is under deletion
- giansimon: Tested the most parts of the CMS
2009-09-10 - Version 1.1.0.Beta-2
- giansimon: w3sRepeatedContentsLanguage to manage repeated contents at language level is now completed.
- giansimon: Fixed a bug for w3sRepeatedContentsSite when a content is added on a slot repeated at site level which is not present on all themes
- giansimon: Edit a content can change both a W3sContent or a W3sContentMapper depending on the passed params.
- giansimon: Fixed a bug with slot's highlighting
2009-09-09 - Version 1.1.0.Beta-1
- giansimon: Adding and deleting languages are now executes with raw queries to speed up the process.
- giansimon: Fixed a bug with slot redraw after changed the slot's status
- giansimon: Fixed a bug when changing the status from site to group
- giansimon: Fixed a bug with slot's highlighting
- giansimon: Start implementation of w3sRepeatedContentsLanguage to manage repeated contents at language level
2009-09-07 - Version 1.1.0.Beta
- giansimon: Changed contents table
- giansimon: Added contents mapper table
- giansimon: Removed foreignContents classes, that have be replaced with repeatedContents classes
- giansimon: Moving routines has been revisioned, fixed and improved
- giansimon: Increased performance with repeteable slots for medium and larges sites
- giansimon: Pagelist has been paginated to increase performances and usability.
2009-08-12 - Version 1.0.4 Stable
- giansimon: fixed a bug for w3sExtensionDHTMLXVaultPlugin
2009-08-07 - Version 1.0.3 Stable
- giansimon: Javascripts for editor management reviewed
- giansimon: w3s_menu_manager.js moved to main js folder
- giansimon: w3s_menu_builder.js moved to w3sExtensionMenuPlugin
- giansimon: fixed a bug in setInteractiveMenus method
2009-08-05 - Version 1.0.2 Stable
- giansimon: fixed problem with redraw content after add or delete operations.
- giansimon: optimized page rendering.
- giansimon: fixed some problems with javascript routines.
- giansimon: fixed a problem with loading default data in the database.
2009-08-03 - Version 1.0.1 Stable
- giansimon: fixed problem with toolbar handler. Now buttons can be overrided.
- giansimon: added attribute id to all toolbar's buttons.
2009-07-31 - Version 1.0.0 Stable
- W3dgets plugins.
- Toolbars configuration files.
- Abstract factory to create contents and editors.
- Apps variables moved to settings.
- w3s_scripts folder removed.
- Bug fixing.
Other releases
Release 1.1.4 - 07/01/2010
2010-01-06 - Version 1.1.4 Stable
1. giansimon: Fixed a bug in updateCombobox function od w3sTools client-side class.
2. giansimon: Fixed a bug related to the extruders.
2010-01-05 - Version 1.1.3 Stable
1. giansimon: The params to configure the extruders for control panel and menu manager has been defined as
aplication variables.
2010-01-04 - Version 1.1.3 Stable
1. giansimon: uploadify can now try to create the folders recursively when a folder doesn't exists
2. giansimon: added a client-side function to clear and fill a select tag.
2009-12-30 - Version 1.1.2 Stable
1. giansimon: frontend module has been totally separated from the backend.
2. giansimon: jquery support has been reviewed. The w3s_jquery_plugins has been added to app.yml to declare which are
the plugins that uses this framework so W3StudioCMS can manage them safety.
2009-12-24 - Version 1.1.1 Stable
1. giansimon: images folder was hardcoded, now uses the w3s_absolute_images_dir param for tiny_mce
2. giansimon: uploadifyPlugin- fixed a bad behaviour in windows
2009-12-22 - Version 1.1.0 Stable
- giansimon: w3sToolkit::linkConverter() has been deprecated and sobstituted by w3sLinkConverter object
2009-12-19 - Version 1.1.0 Stable
- giansimon: page number is no more displayed, when extensionMarkdown has to render only a page.
- giansimon: standard theme and relathed published files moved to plugin's data folder.
2009-12-18 - Version 1.1.0 Stable
- giansimon: fixed a bug in BaseW3sPageManager's deletePageContents() method
- giansimon: fixed a bug in BaseW3sContentManager's getDisplayContentForEditorMode() method which returns a
link in bad format
2009-12-17 - Version 1.1.0 Stable
- giansimon: fixed a bug when deleting a page: user parameter misses
2009-12-16 - Version 1.1.0 Stable
- giansimon: exceptions are now displayed
- giansimon: fixed a bug to load only the stylesheets related to current theme
- giansimon: publish result now display success message color, instead error message color
- giansimon: fixed link colors for menu manager stylesheet.
- giansimon: fixed view.yml config file for w3sExtensionMarkdownPlugin.
2009-12-15 - Version 1.1.0 Stable
- giansimon: default value for template_id_frontentd in w3s_group table is now 0. Fixed BaseW3sTemplateFrontend.class
to reflect this change.
- giansimon: fixed a bug with uploadify tool.
2009-12-14 - Version 1.1.0 Stable
- giansimon: fixed a bug that doesn't change the slot when the slot has any content inside
- giansimon: fixed a bug with BaseW3sRepeatedContentsBaseSite that doesn't save the right slot id when a new
content has to be added
2009-12-13 - Version 1.1.0 Stable
- giansimon: w3sExtensionMarkdownPlugin added to bundled plugins.
- giansimon: extra folder renamed to vendor folder.
2009-12-12 - Version 1.1.0 Stable
- giansimon: fixed xhtml element for the menu manager.
- giansimon: added button to hide/show the menu manager to control panel.
- giansimon: fixed a bug with w3sPagesManager.
2009-12-10 - Version 1.1.0 Stable
- giansimon: tinyMCE module has been renamed in w3sTinyMCE. Fixed the helper
- giansimon: added the idLanguage optional parameter to page delete() method. Pay attention that it is now the first
parameter instead the $op one.
- giansimon: removed the w3sExtensionCssDockPlugin plugin, which will be used when jQuery will be full implemented.
- giansimon: saveMenuWithActiveClass can adapt the menu on other pages as the one which is edited
2009-12-09 - Version 1.1.0 Stable
- giansimon: fixed saveMenuWithActiveClass which now works properly
2009-12-08 - Version 1.1.0 Stable
- giansimon: slotMapper: when a new mapping is saved, the mapped id slots are transferred to contentMapper table
- giansimon: added id_template_frontend to w3sGroup table, to separate the template in production to the new one
in the backend.
- giansimon: fixed repeated contents, which doesn't work properly.
- giansimon: fixed deleting repeated contents when a page is deleted
- giansimon: fixed a problem when the default image is added
- giansimon: fixed some css
2009-12-02 - Version 1.1.0 Stable
- giansimon: fixed a bug related to pages navigation in editor mode.
- giansimon: showLoader module removed
- giansimon: All core objects have been abstracted. The objects that implements the core objects has been deployed
with the bundled plugins that uses those objects. Ie: w3sTemplateEditor that implements BaseW3sTemplateEditor
belongs now to w3sExtensionBackendPlugin.
- giansimon: w3sWidget suffix for bundled plugin has been deprecated and it has been substituted by w3sExtension.
w3sWidget will be removed from 1.2.x releases.
- giansimon: Added w3s suffix to all modules
- giansimon: All modules has been "pluginized".
- giansimon: w3sWebSite module renamed to w3sFrontend module.
- giansimon: w3sWebEditor module renamed to w3sBacked module.
- giansimon: Preview action of webEditor module has been converted into w3sExtensionPreview standalone plugin.
- giansimon: Publish action of webEditor module has been converted into w3sExtensionPublisher standalone plugin.
- giansimon: LoadMenuManager action has been converted in w3sExtensionMenuManagerPlugin standalone plugin.
- giansimon: w3sToolkit renamed to w3sToolkit
2009-11-22 - Version 1.1.0 Stable
- giansimon: fixed a bug with image's paths
2009-11-22 - Version 1.1.0 Stable
- giansimon: added theme upgrade.
- giansimon: fixed a bug with image's editor when it has to open the standard image
- giansimon: fixed a bug with title and alt attributes in image's editor
- giansimon: fixed a bug when adding a content in a slot which hasn't any content inside
- giansimon: removed w3sPublishAssetsTask now managed by symfony's publish-assets task
2009-11-16 - Version 1.1.0 Release Candidate 2
- giansimon: fixed several bugs with template import.
- giansimon: removed the old menu manager which was rendering in a wrong place
- giansimon: removed control panel button from menu manager because it's no more required
2009-11-15 - Version 1.1.0 Release Candidate 2
- giansimon: fixed a bug with metatags.
- giansimon: fixed some bugs with the configuration of w3sUploadify plugin
- giansimon: added w3sExtensionMbExtruderPlugin
2009-11-13 - Version 1.1.0 Release Candidate 2
- giansimon: W3studioCms can now use both the orm and fast queries in mysql.
- giansimon: added orm management for languages, repeated contents and content's extensions
- giansimon: added content's extensions management
- giansimon: languages adding reviewed
2009-09-12 - Version 1.1.0 Release Candidate 1
- giansimon: Drawing slots in Control Panel is now OOP.
- giansimon: Added visual aid for slot repeated at language level
- giansimon: Fixed a bug when deleting the contents related to the page that is under deletion
- giansimon: Tested the most parts of the CMS
2009-09-10 - Version 1.1.0.Beta-2
- giansimon: w3sRepeatedContentsLanguage to manage repeated contents at language level is now completed.
- giansimon: Fixed a bug for w3sRepeatedContentsSite when a content is added on a slot repeated at site level which is not present on all themes
- giansimon: Edit a content can change both a W3sContent or a W3sContentMapper depending on the passed params.
- giansimon: Fixed a bug with slot's highlighting
2009-09-09 - Version 1.1.0.Beta-1
- giansimon: Adding and deleting languages are now executes with raw queries to speed up the process.
- giansimon: Fixed a bug with slot redraw after changed the slot's status
- giansimon: Fixed a bug when changing the status from site to group
- giansimon: Fixed a bug with slot's highlighting
- giansimon: Start implementation of w3sRepeatedContentsLanguage to manage repeated contents at language level
2009-09-07 - Version 1.1.0.Beta
- giansimon: Changed contents table
- giansimon: Added contents mapper table
- giansimon: Removed foreignContents classes, that have be replaced with repeatedContents classes
- giansimon: Moving routines has been revisioned, fixed and improved
- giansimon: Increased performance with repeteable slots for medium and larges sites
- giansimon: Pagelist has been paginated to increase performances and usability.
2009-08-12 - Version 1.0.4 Stable
- giansimon: fixed a bug for w3sExtensionDHTMLXVaultPlugin
2009-08-07 - Version 1.0.3 Stable
- giansimon: Javascripts for editor management reviewed
- giansimon: w3s_menu_manager.js moved to main js folder
- giansimon: w3s_menu_builder.js moved to w3sExtensionMenuPlugin
- giansimon: fixed a bug in setInteractiveMenus method
2009-08-05 - Version 1.0.2 Stable
- giansimon: fixed problem with redraw content after add or delete operations.
- giansimon: optimized page rendering.
- giansimon: fixed some problems with javascript routines.
- giansimon: fixed a problem with loading default data in the database.
2009-08-03 - Version 1.0.1 Stable
- giansimon: fixed problem with toolbar handler. Now buttons can be overrided.
- giansimon: added attribute id to all toolbar's buttons.
2009-07-31 - Version 1.0.0 Stable
- W3dgets plugins.
- Toolbars configuration files.
- Abstract factory to create contents and editors.
- Apps variables moved to settings.
- w3s_scripts folder removed.
- Bug fixing.
Release 1.1.3 - 05/01/2010
2010-01-05 - Version 1.1.3 Stable
1. giansimon: The params to configure the extruders for control panel and menu manager has been defined as
aplication variables.
2010-01-04 - Version 1.1.3 Stable
1. giansimon: uploadify can now try to create the folders recursively when a folder doesn't exists
2. giansimon: added a client-side function to clear and fill a select tag.
2009-12-30 - Version 1.1.2 Stable
1. giansimon: frontend module has been totally separated from the backend.
2. giansimon: jquery support has been reviewed. The w3s_jquery_plugins has been added to app.yml to declare which are
the plugins that uses this framework so W3StudioCMS can manage them safety.
2009-12-24 - Version 1.1.1 Stable
1. giansimon: images folder was hardcoded, now uses the w3s_absolute_images_dir param for tiny_mce
2. giansimon: uploadifyPlugin- fixed a bad behaviour in windows
2009-12-22 - Version 1.1.0 Stable
- giansimon: w3sToolkit::linkConverter() has been deprecated and sobstituted by w3sLinkConverter object
2009-12-19 - Version 1.1.0 Stable
- giansimon: page number is no more displayed, when extensionMarkdown has to render only a page.
- giansimon: standard theme and relathed published files moved to plugin's data folder.
2009-12-18 - Version 1.1.0 Stable
- giansimon: fixed a bug in BaseW3sPageManager's deletePageContents() method
- giansimon: fixed a bug in BaseW3sContentManager's getDisplayContentForEditorMode() method which returns a
link in bad format
2009-12-17 - Version 1.1.0 Stable
- giansimon: fixed a bug when deleting a page: user parameter misses
2009-12-16 - Version 1.1.0 Stable
- giansimon: exceptions are now displayed
- giansimon: fixed a bug to load only the stylesheets related to current theme
- giansimon: publish result now display success message color, instead error message color
- giansimon: fixed link colors for menu manager stylesheet.
- giansimon: fixed view.yml config file for w3sExtensionMarkdownPlugin.
2009-12-15 - Version 1.1.0 Stable
- giansimon: default value for template_id_frontentd in w3s_group table is now 0. Fixed BaseW3sTemplateFrontend.class
to reflect this change.
- giansimon: fixed a bug with uploadify tool.
2009-12-14 - Version 1.1.0 Stable
- giansimon: fixed a bug that doesn't change the slot when the slot has any content inside
- giansimon: fixed a bug with BaseW3sRepeatedContentsBaseSite that doesn't save the right slot id when a new
content has to be added
2009-12-13 - Version 1.1.0 Stable
- giansimon: w3sExtensionMarkdownPlugin added to bundled plugins.
- giansimon: extra folder renamed to vendor folder.
2009-12-12 - Version 1.1.0 Stable
- giansimon: fixed xhtml element for the menu manager.
- giansimon: added button to hide/show the menu manager to control panel.
- giansimon: fixed a bug with w3sPagesManager.
2009-12-10 - Version 1.1.0 Stable
- giansimon: tinyMCE module has been renamed in w3sTinyMCE. Fixed the helper
- giansimon: added the idLanguage optional parameter to page delete() method. Pay attention that it is now the first
parameter instead the $op one.
- giansimon: removed the w3sExtensionCssDockPlugin plugin, which will be used when jQuery will be full implemented.
- giansimon: saveMenuWithActiveClass can adapt the menu on other pages as the one which is edited
2009-12-09 - Version 1.1.0 Stable
- giansimon: fixed saveMenuWithActiveClass which now works properly
2009-12-08 - Version 1.1.0 Stable
- giansimon: slotMapper: when a new mapping is saved, the mapped id slots are transferred to contentMapper table
- giansimon: added id_template_frontend to w3sGroup table, to separate the template in production to the new one
in the backend.
- giansimon: fixed repeated contents, which doesn't work properly.
- giansimon: fixed deleting repeated contents when a page is deleted
- giansimon: fixed a problem when the default image is added
- giansimon: fixed some css
2009-12-02 - Version 1.1.0 Stable
- giansimon: fixed a bug related to pages navigation in editor mode.
- giansimon: showLoader module removed
- giansimon: All core objects have been abstracted. The objects that implements the core objects has been deployed
with the bundled plugins that uses those objects. Ie: w3sTemplateEditor that implements BaseW3sTemplateEditor
belongs now to w3sExtensionBackendPlugin.
- giansimon: w3sWidget suffix for bundled plugin has been deprecated and it has been substituted by w3sExtension.
w3sWidget will be removed from 1.2.x releases.
- giansimon: Added w3s suffix to all modules
- giansimon: All modules has been "pluginized".
- giansimon: w3sWebSite module renamed to w3sFrontend module.
- giansimon: w3sWebEditor module renamed to w3sBacked module.
- giansimon: Preview action of webEditor module has been converted into w3sExtensionPreview standalone plugin.
- giansimon: Publish action of webEditor module has been converted into w3sExtensionPublisher standalone plugin.
- giansimon: LoadMenuManager action has been converted in w3sExtensionMenuManagerPlugin standalone plugin.
- giansimon: w3sToolkit renamed to w3sToolkit
2009-11-22 - Version 1.1.0 Stable
- giansimon: fixed a bug with image's paths
2009-11-22 - Version 1.1.0 Stable
- giansimon: added theme upgrade.
- giansimon: fixed a bug with image's editor when it has to open the standard image
- giansimon: fixed a bug with title and alt attributes in image's editor
- giansimon: fixed a bug when adding a content in a slot which hasn't any content inside
- giansimon: removed w3sPublishAssetsTask now managed by symfony's publish-assets task
2009-11-16 - Version 1.1.0 Release Candidate 2
- giansimon: fixed several bugs with template import.
- giansimon: removed the old menu manager which was rendering in a wrong place
- giansimon: removed control panel button from menu manager because it's no more required
2009-11-15 - Version 1.1.0 Release Candidate 2
- giansimon: fixed a bug with metatags.
- giansimon: fixed some bugs with the configuration of w3sUploadify plugin
- giansimon: added w3sExtensionMbExtruderPlugin
2009-11-13 - Version 1.1.0 Release Candidate 2
- giansimon: W3studioCms can now use both the orm and fast queries in mysql.
- giansimon: added orm management for languages, repeated contents and content's extensions
- giansimon: added content's extensions management
- giansimon: languages adding reviewed
2009-09-12 - Version 1.1.0 Release Candidate 1
- giansimon: Drawing slots in Control Panel is now OOP.
- giansimon: Added visual aid for slot repeated at language level
- giansimon: Fixed a bug when deleting the contents related to the page that is under deletion
- giansimon: Tested the most parts of the CMS
2009-09-10 - Version 1.1.0.Beta-2
- giansimon: w3sRepeatedContentsLanguage to manage repeated contents at language level is now completed.
- giansimon: Fixed a bug for w3sRepeatedContentsSite when a content is added on a slot repeated at site level which is not present on all themes
- giansimon: Edit a content can change both a W3sContent or a W3sContentMapper depending on the passed params.
- giansimon: Fixed a bug with slot's highlighting
2009-09-09 - Version 1.1.0.Beta-1
- giansimon: Adding and deleting languages are now executes with raw queries to speed up the process.
- giansimon: Fixed a bug with slot redraw after changed the slot's status
- giansimon: Fixed a bug when changing the status from site to group
- giansimon: Fixed a bug with slot's highlighting
- giansimon: Start implementation of w3sRepeatedContentsLanguage to manage repeated contents at language level
2009-09-07 - Version 1.1.0.Beta
- giansimon: Changed contents table
- giansimon: Added contents mapper table
- giansimon: Removed foreignContents classes, that have be replaced with repeatedContents classes
- giansimon: Moving routines has been revisioned, fixed and improved
- giansimon: Increased performance with repeteable slots for medium and larges sites
- giansimon: Pagelist has been paginated to increase performances and usability.
2009-10-22 - Version 1.0.5 Stable
- giansimon: fixed a bug for w3sWidgetLanguagesMenuPlugin when used in repeated contents
- giansimon: fixed some bugs with javascripts
- giansimon: current language is correctly selected in control panel
- giansimon: added the cascade.yml config handler to let bundled plugins override the symfony's plugins
- giansimon: w3sApplicationConfiguration.class for bundled plugins has been removed and replaced by
sfW3studioCmsPluginConfiguration.class. See INSTALL to learn more.
- giansimon: jQuery has been enabled to work togheter with propel.
- giansimon: Uploadify has been choosen as default files uploader.
2009-08-12 - Version 1.0.4 Stable
- giansimon: fixed a bug for w3sWidgetDHTMLXVaultPlugin
2009-08-07 - Version 1.0.3 Stable
- giansimon: Javascripts for editor management reviewed
- giansimon: w3s_menu_manager.js moved to main js folder
- giansimon: w3s_menu_builder.js moved to w3sWidgetMenuPlugin
- giansimon: fixed a bug in setInteractiveMenus method
2009-08-05 - Version 1.0.2 Stable
- giansimon: fixed problem with redraw content after add or delete operations.
- giansimon: optimized page rendering.
- giansimon: fixed some problems with javascript routines.
- giansimon: fixed a problem with loading default data in the database.
2009-08-03 - Version 1.0.1 Stable
- giansimon: fixed problem with toolbar handler. Now buttons can be overrided.
- giansimon: added attribute id to all toolbar's buttons.
2009-07-31 - Version 1.0.0 Stable
- W3dgets plugins.
- Toolbars configuration files.
- Abstract factory to create contents and editors.
- Apps variables moved to settings.
- w3s_scripts folder removed.
- Bug fixing.
Release 1.1.2 - 30/12/2009
2009-12-30 - Version 1.1.2 Stable
1. giansimon: frontend module has been totally separated from the backend.
2. giansimon: jquery support has been reviewed. The w3s_jquery_plugins has been added to app.yml to declare which are
the plugins that uses this framework so W3StudioCMS can manage them safety.
2009-12-24 - Version 1.1.1 Stable
1. giansimon: images folder was hardcoded, now uses the w3s_absolute_images_dir param for tiny_mce
2. giansimon: uploadifyPlugin- fixed a bad behaviour in windows
2009-12-22 - Version 1.1.0 Stable
- giansimon: w3sToolkit::linkConverter() has been deprecated and sobstituted by w3sLinkConverter object
2009-12-19 - Version 1.1.0 Stable
- giansimon: page number is no more displayed, when extensionMarkdown has to render only a page.
- giansimon: standard theme and relathed published files moved to plugin's data folder.
2009-12-18 - Version 1.1.0 Stable
- giansimon: fixed a bug in BaseW3sPageManager's deletePageContents() method
- giansimon: fixed a bug in BaseW3sContentManager's getDisplayContentForEditorMode() method which returns a
link in bad format
2009-12-17 - Version 1.1.0 Stable
- giansimon: fixed a bug when deleting a page: user parameter misses
2009-12-16 - Version 1.1.0 Stable
- giansimon: exceptions are now displayed
- giansimon: fixed a bug to load only the stylesheets related to current theme
- giansimon: publish result now display success message color, instead error message color
- giansimon: fixed link colors for menu manager stylesheet.
- giansimon: fixed view.yml config file for w3sExtensionMarkdownPlugin.
2009-12-15 - Version 1.1.0 Stable
- giansimon: default value for template_id_frontentd in w3s_group table is now 0. Fixed BaseW3sTemplateFrontend.class
to reflect this change.
- giansimon: fixed a bug with uploadify tool.
2009-12-14 - Version 1.1.0 Stable
- giansimon: fixed a bug that doesn't change the slot when the slot has any content inside
- giansimon: fixed a bug with BaseW3sRepeatedContentsBaseSite that doesn't save the right slot id when a new
content has to be added
2009-12-13 - Version 1.1.0 Stable
- giansimon: w3sExtensionMarkdownPlugin added to bundled plugins.
- giansimon: extra folder renamed to vendor folder.
2009-12-12 - Version 1.1.0 Stable
- giansimon: fixed xhtml element for the menu manager.
- giansimon: added button to hide/show the menu manager to control panel.
- giansimon: fixed a bug with w3sPagesManager.
2009-12-10 - Version 1.1.0 Stable
- giansimon: tinyMCE module has been renamed in w3sTinyMCE. Fixed the helper
- giansimon: added the idLanguage optional parameter to page delete() method. Pay attention that it is now the first
parameter instead the $op one.
- giansimon: removed the w3sExtensionCssDockPlugin plugin, which will be used when jQuery will be full implemented.
- giansimon: saveMenuWithActiveClass can adapt the menu on other pages as the one which is edited
2009-12-09 - Version 1.1.0 Stable
- giansimon: fixed saveMenuWithActiveClass which now works properly
2009-12-08 - Version 1.1.0 Stable
- giansimon: slotMapper: when a new mapping is saved, the mapped id slots are transferred to contentMapper table
- giansimon: added id_template_frontend to w3sGroup table, to separate the template in production to the new one
in the backend.
- giansimon: fixed repeated contents, which doesn't work properly.
- giansimon: fixed deleting repeated contents when a page is deleted
- giansimon: fixed a problem when the default image is added
- giansimon: fixed some css
2009-12-02 - Version 1.1.0 Stable
- giansimon: fixed a bug related to pages navigation in editor mode.
- giansimon: showLoader module removed
- giansimon: All core objects have been abstracted. The objects that implements the core objects has been deployed
with the bundled plugins that uses those objects. Ie: w3sTemplateEditor that implements BaseW3sTemplateEditor
belongs now to w3sExtensionBackendPlugin.
- giansimon: w3sWidget suffix for bundled plugin has been deprecated and it has been substituted by w3sExtension.
w3sWidget will be removed from 1.2.x releases.
- giansimon: Added w3s suffix to all modules
- giansimon: All modules has been "pluginized".
- giansimon: w3sWebSite module renamed to w3sFrontend module.
- giansimon: w3sWebEditor module renamed to w3sBacked module.
- giansimon: Preview action of webEditor module has been converted into w3sExtensionPreview standalone plugin.
- giansimon: Publish action of webEditor module has been converted into w3sExtensionPublisher standalone plugin.
- giansimon: LoadMenuManager action has been converted in w3sExtensionMenuManagerPlugin standalone plugin.
- giansimon: w3sToolkit renamed to w3sToolkit
2009-11-22 - Version 1.1.0 Stable
- giansimon: fixed a bug with image's paths
2009-11-22 - Version 1.1.0 Stable
- giansimon: added theme upgrade.
- giansimon: fixed a bug with image's editor when it has to open the standard image
- giansimon: fixed a bug with title and alt attributes in image's editor
- giansimon: fixed a bug when adding a content in a slot which hasn't any content inside
- giansimon: removed w3sPublishAssetsTask now managed by symfony's publish-assets task
2009-11-16 - Version 1.1.0 Release Candidate 2
- giansimon: fixed several bugs with template import.
- giansimon: removed the old menu manager which was rendering in a wrong place
- giansimon: removed control panel button from menu manager because it's no more required
2009-11-15 - Version 1.1.0 Release Candidate 2
- giansimon: fixed a bug with metatags.
- giansimon: fixed some bugs with the configuration of w3sUploadify plugin
- giansimon: added w3sExtensionMbExtruderPlugin
2009-11-13 - Version 1.1.0 Release Candidate 2
- giansimon: W3studioCms can now use both the orm and fast queries in mysql.
- giansimon: added orm management for languages, repeated contents and content's extensions
- giansimon: added content's extensions management
- giansimon: languages adding reviewed
2009-09-12 - Version 1.1.0 Release Candidate 1
- giansimon: Drawing slots in Control Panel is now OOP.
- giansimon: Added visual aid for slot repeated at language level
- giansimon: Fixed a bug when deleting the contents related to the page that is under deletion
- giansimon: Tested the most parts of the CMS
2009-09-10 - Version 1.1.0.Beta-2
- giansimon: w3sRepeatedContentsLanguage to manage repeated contents at language level is now completed.
- giansimon: Fixed a bug for w3sRepeatedContentsSite when a content is added on a slot repeated at site level which is not present on all themes
- giansimon: Edit a content can change both a W3sContent or a W3sContentMapper depending on the passed params.
- giansimon: Fixed a bug with slot's highlighting
2009-09-09 - Version 1.1.0.Beta-1
- giansimon: Adding and deleting languages are now executes with raw queries to speed up the process.
- giansimon: Fixed a bug with slot redraw after changed the slot's status
- giansimon: Fixed a bug when changing the status from site to group
- giansimon: Fixed a bug with slot's highlighting
- giansimon: Start implementation of w3sRepeatedContentsLanguage to manage repeated contents at language level
2009-09-07 - Version 1.1.0.Beta
- giansimon: Changed contents table
- giansimon: Added contents mapper table
- giansimon: Removed foreignContents classes, that have be replaced with repeatedContents classes
- giansimon: Moving routines has been revisioned, fixed and improved
- giansimon: Increased performance with repeteable slots for medium and larges sites
- giansimon: Pagelist has been paginated to increase performances and usability.
2009-10-22 - Version 1.0.5 Stable
- giansimon: fixed a bug for w3sWidgetLanguagesMenuPlugin when used in repeated contents
- giansimon: fixed some bugs with javascripts
- giansimon: current language is correctly selected in control panel
- giansimon: added the cascade.yml config handler to let bundled plugins override the symfony's plugins
- giansimon: w3sApplicationConfiguration.class for bundled plugins has been removed and replaced by
sfW3studioCmsPluginConfiguration.class. See INSTALL to learn more.
- giansimon: jQuery has been enabled to work togheter with propel.
- giansimon: Uploadify has been choosen as default files uploader.
2009-08-12 - Version 1.0.4 Stable
- giansimon: fixed a bug for w3sWidgetDHTMLXVaultPlugin
2009-08-07 - Version 1.0.3 Stable
- giansimon: Javascripts for editor management reviewed
- giansimon: w3s_menu_manager.js moved to main js folder
- giansimon: w3s_menu_builder.js moved to w3sWidgetMenuPlugin
- giansimon: fixed a bug in setInteractiveMenus method
2009-08-05 - Version 1.0.2 Stable
- giansimon: fixed problem with redraw content after add or delete operations.
- giansimon: optimized page rendering.
- giansimon: fixed some problems with javascript routines.
- giansimon: fixed a problem with loading default data in the database.
2009-08-03 - Version 1.0.1 Stable
- giansimon: fixed problem with toolbar handler. Now buttons can be overrided.
- giansimon: added attribute id to all toolbar's buttons.
2009-07-31 - Version 1.0.0 Stable
- W3dgets plugins.
- Toolbars configuration files.
- Abstract factory to create contents and editors.
- Apps variables moved to settings.
- w3s_scripts folder removed.
- Bug fixing.
Release 1.1.1 - 24/12/2009
2009-12-24 - Version 1.1.1 Stable
1. giansimon: images folder was hardcoded, now uses the w3s_absolute_images_dir param for tiny_mce
2. giansimon: uploadifyPlugin- fixed a bad behaviour in windows
2009-12-22 - Version 1.1.0 Stable
- giansimon: w3sToolkit::linkConverter() has been deprecated and sobstituted by w3sLinkConverter object
2009-12-19 - Version 1.1.0 Stable
- giansimon: page number is no more displayed, when extensionMarkdown has to render only a page.
- giansimon: standard theme and relathed published files moved to plugin's data folder.
2009-12-18 - Version 1.1.0 Stable
- giansimon: fixed a bug in BaseW3sPageManager's deletePageContents() method
- giansimon: fixed a bug in BaseW3sContentManager's getDisplayContentForEditorMode() method which returns a
link in bad format
2009-12-17 - Version 1.1.0 Stable
- giansimon: fixed a bug when deleting a page: user parameter misses
2009-12-16 - Version 1.1.0 Stable
- giansimon: exceptions are now displayed
- giansimon: fixed a bug to load only the stylesheets related to current theme
- giansimon: publish result now display success message color, instead error message color
- giansimon: fixed link colors for menu manager stylesheet.
- giansimon: fixed view.yml config file for w3sExtensionMarkdownPlugin.
2009-12-15 - Version 1.1.0 Stable
- giansimon: default value for template_id_frontentd in w3s_group table is now 0. Fixed BaseW3sTemplateFrontend.class
to reflect this change.
- giansimon: fixed a bug with uploadify tool.
2009-12-14 - Version 1.1.0 Stable
- giansimon: fixed a bug that doesn't change the slot when the slot has any content inside
- giansimon: fixed a bug with BaseW3sRepeatedContentsBaseSite that doesn't save the right slot id when a new
content has to be added
2009-12-13 - Version 1.1.0 Stable
- giansimon: w3sExtensionMarkdownPlugin added to bundled plugins.
- giansimon: extra folder renamed to vendor folder.
2009-12-12 - Version 1.1.0 Stable
- giansimon: fixed xhtml element for the menu manager.
- giansimon: added button to hide/show the menu manager to control panel.
- giansimon: fixed a bug with w3sPagesManager.
2009-12-10 - Version 1.1.0 Stable
- giansimon: tinyMCE module has been renamed in w3sTinyMCE. Fixed the helper
- giansimon: added the idLanguage optional parameter to page delete() method. Pay attention that it is now the first
parameter instead the $op one.
- giansimon: removed the w3sExtensionCssDockPlugin plugin, which will be used when jQuery will be full implemented.
- giansimon: saveMenuWithActiveClass can adapt the menu on other pages as the one which is edited
2009-12-09 - Version 1.1.0 Stable
- giansimon: fixed saveMenuWithActiveClass which now works properly
2009-12-08 - Version 1.1.0 Stable
- giansimon: slotMapper: when a new mapping is saved, the mapped id slots are transferred to contentMapper table
- giansimon: added id_template_frontend to w3sGroup table, to separate the template in production to the new one
in the backend.
- giansimon: fixed repeated contents, which doesn't work properly.
- giansimon: fixed deleting repeated contents when a page is deleted
- giansimon: fixed a problem when the default image is added
- giansimon: fixed some css
2009-12-02 - Version 1.1.0 Stable
- giansimon: fixed a bug related to pages navigation in editor mode.
- giansimon: showLoader module removed
- giansimon: All core objects have been abstracted. The objects that implements the core objects has been deployed
with the bundled plugins that uses those objects. Ie: w3sTemplateEditor that implements BaseW3sTemplateEditor
belongs now to w3sExtensionBackendPlugin.
- giansimon: w3sWidget suffix for bundled plugin has been deprecated and it has been substituted by w3sExtension.
w3sWidget will be removed from 1.2.x releases.
- giansimon: Added w3s suffix to all modules
- giansimon: All modules has been "pluginized".
- giansimon: w3sWebSite module renamed to w3sFrontend module.
- giansimon: w3sWebEditor module renamed to w3sBacked module.
- giansimon: Preview action of webEditor module has been converted into w3sExtensionPreview standalone plugin.
- giansimon: Publish action of webEditor module has been converted into w3sExtensionPublisher standalone plugin.
- giansimon: LoadMenuManager action has been converted in w3sExtensionMenuManagerPlugin standalone plugin.
- giansimon: w3sToolkit renamed to w3sToolkit
2009-11-22 - Version 1.1.0 Stable
- giansimon: fixed a bug with image's paths
2009-11-22 - Version 1.1.0 Stable
- giansimon: added theme upgrade.
- giansimon: fixed a bug with image's editor when it has to open the standard image
- giansimon: fixed a bug with title and alt attributes in image's editor
- giansimon: fixed a bug when adding a content in a slot which hasn't any content inside
- giansimon: removed w3sPublishAssetsTask now managed by symfony's publish-assets task
2009-11-16 - Version 1.1.0 Release Candidate 2
- giansimon: fixed several bugs with template import.
- giansimon: removed the old menu manager which was rendering in a wrong place
- giansimon: removed control panel button from menu manager because it's no more required
2009-11-15 - Version 1.1.0 Release Candidate 2
- giansimon: fixed a bug with metatags.
- giansimon: fixed some bugs with the configuration of w3sUploadify plugin
- giansimon: added w3sExtensionMbExtruderPlugin
2009-11-13 - Version 1.1.0 Release Candidate 2
- giansimon: W3studioCms can now use both the orm and fast queries in mysql.
- giansimon: added orm management for languages, repeated contents and content's extensions
- giansimon: added content's extensions management
- giansimon: languages adding reviewed
2009-09-12 - Version 1.1.0 Release Candidate 1
- giansimon: Drawing slots in Control Panel is now OOP.
- giansimon: Added visual aid for slot repeated at language level
- giansimon: Fixed a bug when deleting the contents related to the page that is under deletion
- giansimon: Tested the most parts of the CMS
2009-09-10 - Version 1.1.0.Beta-2
- giansimon: w3sRepeatedContentsLanguage to manage repeated contents at language level is now completed.
- giansimon: Fixed a bug for w3sRepeatedContentsSite when a content is added on a slot repeated at site level which is not present on all themes
- giansimon: Edit a content can change both a W3sContent or a W3sContentMapper depending on the passed params.
- giansimon: Fixed a bug with slot's highlighting
2009-09-09 - Version 1.1.0.Beta-1
- giansimon: Adding and deleting languages are now executes with raw queries to speed up the process.
- giansimon: Fixed a bug with slot redraw after changed the slot's status
- giansimon: Fixed a bug when changing the status from site to group
- giansimon: Fixed a bug with slot's highlighting
- giansimon: Start implementation of w3sRepeatedContentsLanguage to manage repeated contents at language level
2009-09-07 - Version 1.1.0.Beta
- giansimon: Changed contents table
- giansimon: Added contents mapper table
- giansimon: Removed foreignContents classes, that have be replaced with repeatedContents classes
- giansimon: Moving routines has been revisioned, fixed and improved
- giansimon: Increased performance with repeteable slots for medium and larges sites
- giansimon: Pagelist has been paginated to increase performances and usability.
2009-10-22 - Version 1.0.5 Stable
- giansimon: fixed a bug for w3sWidgetLanguagesMenuPlugin when used in repeated contents
- giansimon: fixed some bugs with javascripts
- giansimon: current language is correctly selected in control panel
- giansimon: added the cascade.yml config handler to let bundled plugins override the symfony's plugins
- giansimon: w3sApplicationConfiguration.class for bundled plugins has been removed and replaced by
sfW3studioCmsPluginConfiguration.class. See INSTALL to learn more.
- giansimon: jQuery has been enabled to work togheter with propel.
- giansimon: Uploadify has been choosen as default files uploader.
2009-08-12 - Version 1.0.4 Stable
- giansimon: fixed a bug for w3sWidgetDHTMLXVaultPlugin
2009-08-07 - Version 1.0.3 Stable
- giansimon: Javascripts for editor management reviewed
- giansimon: w3s_menu_manager.js moved to main js folder
- giansimon: w3s_menu_builder.js moved to w3sWidgetMenuPlugin
- giansimon: fixed a bug in setInteractiveMenus method
2009-08-05 - Version 1.0.2 Stable
- giansimon: fixed problem with redraw content after add or delete operations.
- giansimon: optimized page rendering.
- giansimon: fixed some problems with javascript routines.
- giansimon: fixed a problem with loading default data in the database.
2009-08-03 - Version 1.0.1 Stable
- giansimon: fixed problem with toolbar handler. Now buttons can be overrided.
- giansimon: added attribute id to all toolbar's buttons.
2009-07-31 - Version 1.0.0 Stable
- W3dgets plugins.
- Toolbars configuration files.
- Abstract factory to create contents and editors.
- Apps variables moved to settings.
- w3s_scripts folder removed.
- Bug fixing.
Release 1.1.0 - 22/12/2009
2009-12-22 - Version 1.1.0 Stable
- giansimon: w3sToolkit::linkConverter() has been deprecated and sobstituted by w3sLinkConverter object
2009-12-19 - Version 1.1.0 Stable
- giansimon: page number is no more displayed, when extensionMarkdown has to render only a page.
- giansimon: standard theme and relathed published files moved to plugin's data folder.
2009-12-18 - Version 1.1.0 Stable
- giansimon: fixed a bug in BaseW3sPageManager's deletePageContents() method
- giansimon: fixed a bug in BaseW3sContentManager's getDisplayContentForEditorMode() method which returns a
link in bad format
2009-12-17 - Version 1.1.0 Stable
- giansimon: fixed a bug when deleting a page: user parameter misses
2009-12-16 - Version 1.1.0 Stable
- giansimon: exceptions are now displayed
- giansimon: fixed a bug to load only the stylesheets related to current theme
- giansimon: publish result now display success message color, instead error message color
- giansimon: fixed link colors for menu manager stylesheet.
- giansimon: fixed view.yml config file for w3sExtensionMarkdownPlugin.
2009-12-15 - Version 1.1.0 Stable
- giansimon: default value for template_id_frontentd in w3s_group table is now 0. Fixed BaseW3sTemplateFrontend.class
to reflect this change.
- giansimon: fixed a bug with uploadify tool.
2009-12-14 - Version 1.1.0 Stable
- giansimon: fixed a bug that doesn't change the slot when the slot has any content inside
- giansimon: fixed a bug with BaseW3sRepeatedContentsBaseSite that doesn't save the right slot id when a new
content has to be added
2009-12-13 - Version 1.1.0 Stable
- giansimon: w3sExtensionMarkdownPlugin added to bundled plugins.
- giansimon: extra folder renamed to vendor folder.
2009-12-12 - Version 1.1.0 Stable
- giansimon: fixed xhtml element for the menu manager.
- giansimon: added button to hide/show the menu manager to control panel.
- giansimon: fixed a bug with w3sPagesManager.
2009-12-10 - Version 1.1.0 Stable
- giansimon: tinyMCE module has been renamed in w3sTinyMCE. Fixed the helper
- giansimon: added the idLanguage optional parameter to page delete() method. Pay attention that it is now the first
parameter instead the $op one.
- giansimon: removed the w3sExtensionCssDockPlugin plugin, which will be used when jQuery will be full implemented.
- giansimon: saveMenuWithActiveClass can adapt the menu on other pages as the one which is edited
2009-12-09 - Version 1.1.0 Stable
- giansimon: fixed saveMenuWithActiveClass which now works properly
2009-12-08 - Version 1.1.0 Stable
- giansimon: slotMapper: when a new mapping is saved, the mapped id slots are transferred to contentMapper table
- giansimon: added id_template_frontend to w3sGroup table, to separate the template in production to the new one
in the backend.
- giansimon: fixed repeated contents, which doesn't work properly.
- giansimon: fixed deleting repeated contents when a page is deleted
- giansimon: fixed a problem when the default image is added
- giansimon: fixed some css
2009-12-02 - Version 1.1.0 Stable
- giansimon: fixed a bug related to pages navigation in editor mode.
- giansimon: showLoader module removed
- giansimon: All core objects have been abstracted. The objects that implements the core objects has been deployed
with the bundled plugins that uses those objects. Ie: w3sTemplateEditor that implements BaseW3sTemplateEditor
belongs now to w3sExtensionBackendPlugin.
- giansimon: w3sWidget suffix for bundled plugin has been deprecated and it has been substituted by w3sExtension.
w3sWidget will be removed from 1.2.x releases.
- giansimon: Added w3s suffix to all modules
- giansimon: All modules has been "pluginized".
- giansimon: w3sWebSite module renamed to w3sFrontend module.
- giansimon: w3sWebEditor module renamed to w3sBacked module.
- giansimon: Preview action of webEditor module has been converted into w3sExtensionPreview standalone plugin.
- giansimon: Publish action of webEditor module has been converted into w3sExtensionPublisher standalone plugin.
- giansimon: LoadMenuManager action has been converted in w3sExtensionMenuManagerPlugin standalone plugin.
- giansimon: w3sToolkit renamed to w3sToolkit
2009-11-22 - Version 1.1.0 Stable
- giansimon: fixed a bug with image's paths
2009-11-22 - Version 1.1.0 Stable
- giansimon: added theme upgrade.
- giansimon: fixed a bug with image's editor when it has to open the standard image
- giansimon: fixed a bug with title and alt attributes in image's editor
- giansimon: fixed a bug when adding a content in a slot which hasn't any content inside
- giansimon: removed w3sPublishAssetsTask now managed by symfony's publish-assets task
2009-11-16 - Version 1.1.0 Release Candidate 2
- giansimon: fixed several bugs with template import.
- giansimon: removed the old menu manager which was rendering in a wrong place
- giansimon: removed control panel button from menu manager because it's no more required
2009-11-15 - Version 1.1.0 Release Candidate 2
- giansimon: fixed a bug with metatags.
- giansimon: fixed some bugs with the configuration of w3sUploadify plugin
- giansimon: added w3sExtensionMbExtruderPlugin
2009-11-13 - Version 1.1.0 Release Candidate 2
- giansimon: W3studioCms can now use both the orm and fast queries in mysql.
- giansimon: added orm management for languages, repeated contents and content's extensions
- giansimon: added content's extensions management
- giansimon: languages adding reviewed
2009-09-12 - Version 1.1.0 Release Candidate 1
- giansimon: Drawing slots in Control Panel is now OOP.
- giansimon: Added visual aid for slot repeated at language level
- giansimon: Fixed a bug when deleting the contents related to the page that is under deletion
- giansimon: Tested the most parts of the CMS
2009-09-10 - Version 1.1.0.Beta-2
- giansimon: w3sRepeatedContentsLanguage to manage repeated contents at language level is now completed.
- giansimon: Fixed a bug for w3sRepeatedContentsSite when a content is added on a slot repeated at site level which is not present on all themes
- giansimon: Edit a content can change both a W3sContent or a W3sContentMapper depending on the passed params.
- giansimon: Fixed a bug with slot's highlighting
2009-09-09 - Version 1.1.0.Beta-1
- giansimon: Adding and deleting languages are now executes with raw queries to speed up the process.
- giansimon: Fixed a bug with slot redraw after changed the slot's status
- giansimon: Fixed a bug when changing the status from site to group
- giansimon: Fixed a bug with slot's highlighting
- giansimon: Start implementation of w3sRepeatedContentsLanguage to manage repeated contents at language level
2009-09-07 - Version 1.1.0.Beta
- giansimon: Changed contents table
- giansimon: Added contents mapper table
- giansimon: Removed foreignContents classes, that have be replaced with repeatedContents classes
- giansimon: Moving routines has been revisioned, fixed and improved
- giansimon: Increased performance with repeteable slots for medium and larges sites
- giansimon: Pagelist has been paginated to increase performances and usability.
2009-10-22 - Version 1.0.5 Stable
- giansimon: fixed a bug for w3sWidgetLanguagesMenuPlugin when used in repeated contents
- giansimon: fixed some bugs with javascripts
- giansimon: current language is correctly selected in control panel
- giansimon: added the cascade.yml config handler to let bundled plugins override the symfony's plugins
- giansimon: w3sApplicationConfiguration.class for bundled plugins has been removed and replaced by
sfW3studioCmsPluginConfiguration.class. See INSTALL to learn more.
- giansimon: jQuery has been enabled to work togheter with propel.
- giansimon: Uploadify has been choosen as default files uploader.
2009-08-12 - Version 1.0.4 Stable
- giansimon: fixed a bug for w3sWidgetDHTMLXVaultPlugin
2009-08-07 - Version 1.0.3 Stable
- giansimon: Javascripts for editor management reviewed
- giansimon: w3s_menu_manager.js moved to main js folder
- giansimon: w3s_menu_builder.js moved to w3sWidgetMenuPlugin
- giansimon: fixed a bug in setInteractiveMenus method
2009-08-05 - Version 1.0.2 Stable
- giansimon: fixed problem with redraw content after add or delete operations.
- giansimon: optimized page rendering.
- giansimon: fixed some problems with javascript routines.
- giansimon: fixed a problem with loading default data in the database.
2009-08-03 - Version 1.0.1 Stable
- giansimon: fixed problem with toolbar handler. Now buttons can be overrided.
- giansimon: added attribute id to all toolbar's buttons.
2009-07-31 - Version 1.0.0 Stable
- W3dgets plugins.
- Toolbars configuration files.
- Abstract factory to create contents and editors.
- Apps variables moved to settings.
- w3s_scripts folder removed.
- Bug fixing.
Release 1.0.5 - 23/10/2009
2009-10-22 - Version 1.0.5 Stable
- giansimon: fixed a bug for w3sWidgetLanguagesMenuPlugin when used in repeated contents
- giansimon: fixed some bugs with javascripts
- giansimon: current language is correctly selected in control panel
- giansimon: added the cascade.yml config handler to let bundled plugins override the symfony's plugins
- giansimon: w3sApplicationConfiguration.class for bundled plugins has been removed and replaced by
sfW3studioCmsPluginConfiguration.class. See INSTALL to learn more.
- giansimon: jQuery has been enabled to work togheter with propel.
- giansimon: Uploadify has been choosen as default files uploader.
2009-08-12 - Version 1.0.4 Stable
- giansimon: fixed a bug for w3sWidgetDHTMLXVaultPlugin
2009-08-07 - Version 1.0.3 Stable
- giansimon: Javascripts for editor management reviewed
- giansimon: w3s_menu_manager.js moved to main js folder
- giansimon: w3s_menu_builder.js moved to w3sWidgetMenuPlugin
- giansimon: fixed a bug in setInteractiveMenus method
2009-08-05 - Version 1.0.2 Stable
- giansimon: fixed problem with redraw content after add or delete operations.
- giansimon: optimized page rendering.
- giansimon: fixed some problems with javascript routines.
- giansimon: fixed a problem with loading default data in the database.
2009-08-03 - Version 1.0.1 Stable
- giansimon: fixed problem with toolbar handler. Now buttons can be overrided.
- giansimon: added attribute id to all toolbar's buttons.
2009-07-31 - Version 1.0.0 Stable
- W3dgets plugins.
- Toolbars configuration files.
- Abstract factory to create contents and editors.
- Apps variables moved to settings.
- w3s_scripts folder removed.
- Bug fixing.
Release 1.0.4 - 12/08/2009
2009-08-12 - Version 1.0.4 Stable
- giansimon: fixed a bug for w3sWidgetDHTMLXVaultPlugin
2009-08-07 - Version 1.0.3 Stable
- giansimon: Javascripts for editor management reviewed
- giansimon: w3s_menu_manager.js moved to main js folder
- giansimon: w3s_menu_builder.js moved to w3sWidgetMenuPlugin
- giansimon: fixed a bug in setInteractiveMenus method
2009-08-05 - Version 1.0.2 Stable
- giansimon: fixed problem with redraw content after add or delete operations.
- giansimon: optimized page rendering.
- giansimon: fixed some problems with javascript routines.
- giansimon: fixed a problem with loading default data in the database.
2009-08-03 - Version 1.0.1 Stable
- giansimon: fixed problem with toolbar handler. Now buttons can be overrided.
- giansimon: added attribute id to all toolbar's buttons.
2009-07-31 - Version 1.0.0 Stable
- W3dgets plugins.
- Toolbars configuration files.
- Abstract factory to create contents and editors.
- Apps variables moved to settings.
- w3s_scripts folder removed.
Bug fixing.
0.9.0
1. Fixed some bugs.
---
sfW3studioCmsPlugin - Version 0.8.0.1
Giansimon Diblas 01/19/09:
1. Fixed a bug that occours when you save a menu with the "Set the class on each page" option
checked.
2. Fixed some problems related to usability with the Menu Builder editor.
---
sfW3studioCmsPlugin - Version 0.8.0.0
Giansimon Diblas 01/06/09:
1. Everything is now OOP.
2. The name of some modules has been changed so you have to update your enable modules.
3. The move system has been reviewed.
4. The projects import interface has been reviewed.
5. When you create a new template you can omit the three empty fields groupId:, pageId:, languageId:
6. Every project can be integrated with an extra directory that have to be called info,
where you can create a yml file with some useful information about your template. You
can also add an image to give a preview of the template. A detailed tutorial will be publish.
*--
sfW3studioCmsPlugin - Version 0.7.4.2
Giansimon Diblas 12/09/08:
Skins support added. Now everyone can create his own skin for W3studioCMS
Internet Explorer is now compatible. A problem with the menu builder remains, but it will be
fixed as soon as possibile.
Note: You might have problems to install the previous 0.7.4 versions. I made a mistake
with the data file of the default template. I apologize for the inconvenience.
Now it's definitively fixed.
*--
sfW3studioCmsPlugin - Version 0.7.4.1
Giansimon Diblas 11/30/08: Fixed minor bugs related to javascripts' refactoring
*--
sfW3studioCmsPlugin - Version 0.7.4
Giansimon Diblas 11/23/08: All the W3studioCMS' javascripts has been reviewed and refactored
*--
sfW3studioCmsPlugin - Version 0.7.2
Giansimon Diblas 11/08/08: The new version has been implemented through OOP
*--
sfW3studioCmsPlugin - Version 0.6.2
Giansimon Diblas 09/23/08: Fixed some problems related to paths due to recent changes of some application's paths
Giansimon Diblas 09/21/08: fileUploader moved to extra folder
Giansimon Diblas 09/21/08: sfGuardAuth moved to extra folder
*--
sfW3studioCmsPlugin - Version 0.6.1
0.6.1 - 09/20/2009 Giansimon Diblas: Changed the rendering of style sheet when the site will be published
*--
sfW3studioCmsPlugin - Version 0.6.0
0.6.0 - 09/16/2009 Giansimon Diblas: First release
Release 1.0.3 - 09/08/2009
2009-08-07 - Version 1.0.3 Stable
- giansimon: Javascripts for editor management reviewed
- giansimon: w3s_menu_manager.js moved to main js folder
- giansimon: w3s_menu_builder.js moved to w3sWidgetMenuPlugin
- giansimon: fixed a bug in setInteractiveMenus method
2009-08-05 - Version 1.0.2 Stable
- giansimon: fixed problem with redraw content after add or delete operations.
- giansimon: optimized page rendering.
- giansimon: fixed some problems with javascript routines.
- giansimon: fixed a problem with loading default data in the database.
2009-08-03 - Version 1.0.1 Stable
- giansimon: fixed problem with toolbar handler. Now buttons can be overrided.
- giansimon: added attribute id to all toolbar's buttons.
2009-07-31 - Version 1.0.0 Stable
- W3dgets plugins.
- Toolbars configuration files.
- Abstract factory to create contents and editors.
- Apps variables moved to settings.
- w3s_scripts folder removed.
Bug fixing.
0.9.0
1. Fixed some bugs.
---
sfW3studioCmsPlugin - Version 0.8.0.1
Giansimon Diblas 01/19/09:
1. Fixed a bug that occours when you save a menu with the "Set the class on each page" option
checked.
2. Fixed some problems related to usability with the Menu Builder editor.
---
sfW3studioCmsPlugin - Version 0.8.0.0
Giansimon Diblas 01/06/09:
1. Everything is now OOP.
2. The name of some modules has been changed so you have to update your enable modules.
3. The move system has been reviewed.
4. The projects import interface has been reviewed.
5. When you create a new template you can omit the three empty fields groupId:, pageId:, languageId:
6. Every project can be integrated with an extra directory that have to be called info,
where you can create a yml file with some useful information about your template. You
can also add an image to give a preview of the template. A detailed tutorial will be publish.
*--
sfW3studioCmsPlugin - Version 0.7.4.2
Giansimon Diblas 12/09/08:
Skins support added. Now everyone can create his own skin for W3studioCMS
Internet Explorer is now compatible. A problem with the menu builder remains, but it will be
fixed as soon as possibile.
Note: You might have problems to install the previous 0.7.4 versions. I made a mistake
with the data file of the default template. I apologize for the inconvenience.
Now it's definitively fixed.
*--
sfW3studioCmsPlugin - Version 0.7.4.1
Giansimon Diblas 11/30/08: Fixed minor bugs related to javascripts' refactoring
*--
sfW3studioCmsPlugin - Version 0.7.4
Giansimon Diblas 11/23/08: All the W3studioCMS' javascripts has been reviewed and refactored
*--
sfW3studioCmsPlugin - Version 0.7.2
Giansimon Diblas 11/08/08: The new version has been implemented through OOP
*--
sfW3studioCmsPlugin - Version 0.6.2
Giansimon Diblas 09/23/08: Fixed some problems related to paths due to recent changes of some application's paths
Giansimon Diblas 09/21/08: fileUploader moved to extra folder
Giansimon Diblas 09/21/08: sfGuardAuth moved to extra folder
*--
sfW3studioCmsPlugin - Version 0.6.1
0.6.1 - 09/20/2009 Giansimon Diblas: Changed the rendering of style sheet when the site will be published
*--
sfW3studioCmsPlugin - Version 0.6.0
0.6.0 - 09/16/2009 Giansimon Diblas: First release
Release 1.0.2 - 05/08/2009
2009-07-05 - Version 1.0.2 Stable
- giansimon: fixed problem with redraw content after add or delete operations.
- giansimon: optimized page rendering.
- giansimon: fixed some problems with javascript routines.
- giansimon: fixed a problem with loading default data in the database.
2009-07-03 - Version 1.0.1 Stable
- giansimon: fixed problem with toolbar handler. Now buttons can be overrided.
- giansimon: added attribute id to all toolbar's buttons.
2009-07-01 - Version 1.0.0 Stable
- W3dgets plugins.
- Toolbars configuration files.
- Abstract factory to create contents and editors.
- Apps variables moved to settings.
- w3s_scripts folder removed.
Bug fixing.
0.9.0
1. Fixed some bugs.
---
sfW3studioCmsPlugin - Version 0.8.0.1
Giansimon Diblas 01/19/09:
1. Fixed a bug that occours when you save a menu with the "Set the class on each page" option
checked.
2. Fixed some problems related to usability with the Menu Builder editor.
---
sfW3studioCmsPlugin - Version 0.8.0.0
Giansimon Diblas 01/06/09:
1. Everything is now OOP.
2. The name of some modules has been changed so you have to update your enable modules.
3. The move system has been reviewed.
4. The projects import interface has been reviewed.
5. When you create a new template you can omit the three empty fields groupId:, pageId:, languageId:
6. Every project can be integrated with an extra directory that have to be called info,
where you can create a yml file with some useful information about your template. You
can also add an image to give a preview of the template. A detailed tutorial will be publish.
*--
sfW3studioCmsPlugin - Version 0.7.4.2
Giansimon Diblas 12/09/08:
Skins support added. Now everyone can create his own skin for W3studioCMS
Internet Explorer is now compatible. A problem with the menu builder remains, but it will be
fixed as soon as possibile.
Note: You might have problems to install the previous 0.7.4 versions. I made a mistake
with the data file of the default template. I apologize for the inconvenience.
Now it's definitively fixed.
*--
sfW3studioCmsPlugin - Version 0.7.4.1
Giansimon Diblas 11/30/08: Fixed minor bugs related to javascripts' refactoring
*--
sfW3studioCmsPlugin - Version 0.7.4
Giansimon Diblas 11/23/08: All the W3studioCMS' javascripts has been reviewed and refactored
*--
sfW3studioCmsPlugin - Version 0.7.2
Giansimon Diblas 11/08/08: The new version has been implemented through OOP
*--
sfW3studioCmsPlugin - Version 0.6.2
Giansimon Diblas 09/23/08: Fixed some problems related to paths due to recent changes of some application's paths
Giansimon Diblas 09/21/08: fileUploader moved to extra folder
Giansimon Diblas 09/21/08: sfGuardAuth moved to extra folder
*--
sfW3studioCmsPlugin - Version 0.6.1
0.6.1 - 09/20/2009 Giansimon Diblas: Changed the rendering of style sheet when the site will be published
*--
sfW3studioCmsPlugin - Version 0.6.0
0.6.0 - 09/16/2009 Giansimon Diblas: First release
Release 0.9.0 - 15/03/2009
0.9.0
1. Fixed some bugs.
---
sfW3studioCmsPlugin - Version 0.8.0.1
Giansimon Diblas 01/19/09:
1. Fixed a bug that occours when you save a menu with the "Set the class on each page" option
checked.
2. Fixed some problems related to usability with the Menu Builder editor.
---
sfW3studioCmsPlugin - Version 0.8.0.0
Giansimon Diblas 01/06/09:
1. Everything is now OOP.
2. The name of some modules has been changed so you have to update your enable modules.
3. The move system has been reviewed.
4. The projects import interface has been reviewed.
5. When you create a new template you can omit the three empty fields groupId:, pageId:, languageId:
6. Every project can be integrated with an extra directory that have to be called info,
where you can create a yml file with some useful information about your template. You
can also add an image to give a preview of the template. A detailed tutorial will be publish.
*--
sfW3studioCmsPlugin - Version 0.7.4.2
Giansimon Diblas 12/09/08:
Skins support added. Now everyone can create his own skin for W3studioCMS
Internet Explorer is now compatible. A problem with the menu builder remains, but it will be
fixed as soon as possibile.
Note: You might have problems to install the previous 0.7.4 versions. I made a mistake
with the data file of the default template. I apologize for the inconvenience.
Now it's definitively fixed.
*--
sfW3studioCmsPlugin - Version 0.7.4.1
Giansimon Diblas 11/30/08: Fixed minor bugs related to javascripts' refactoring
*--
sfW3studioCmsPlugin - Version 0.7.4
Giansimon Diblas 11/23/08: All the W3studioCMS' javascripts has been reviewed and refactored
*--
sfW3studioCmsPlugin - Version 0.7.2
Giansimon Diblas 11/08/08: The new version has been implemented through OOP
*--
sfW3studioCmsPlugin - Version 0.6.2
Giansimon Diblas 09/23/08: Fixed some problems related to paths due to recent changes of some application's paths
Giansimon Diblas 09/21/08: fileUploader moved to extra folder
Giansimon Diblas 09/21/08: sfGuardAuth moved to extra folder
*--
sfW3studioCmsPlugin - Version 0.6.1
0.6.1 - 09/20/2009 Giansimon Diblas: Changed the rendering of style sheet when the site will be published
*--
sfW3studioCmsPlugin - Version 0.6.0
0.6.0 - 09/16/2009 Giansimon Diblas: First release
Release 0.8.2 - 27/01/2009
0.8.2
1. Fixed some bugs.
---
sfW3studioCmsPlugin - Version 0.8.0.1
Giansimon Diblas 01/19/09:
1. Fixed a bug that occours when you save a menu with the "Set the class on each page" option
checked.
2. Fixed some problems related to usability with the Menu Builder editor.
---
sfW3studioCmsPlugin - Version 0.8.0.0
Giansimon Diblas 01/06/09:
1. Everything is now OOP.
2. The name of some modules has been changed so you have to update your enable modules.
3. The move system has been reviewed.
4. The projects import interface has been reviewed.
5. When you create a new template you can omit the three empty fields groupId:, pageId:, languageId:
6. Every project can be integrated with an extra directory that have to be called info,
where you can create a yml file with some useful information about your template. You
can also add an image to give a preview of the template. A detailed tutorial will be publish.
*--
sfW3studioCmsPlugin - Version 0.7.4.2
Giansimon Diblas 12/09/08:
Skins support added. Now everyone can create his own skin for W3studioCMS
Internet Explorer is now compatible. A problem with the menu builder remains, but it will be
fixed as soon as possibile.
Note: You might have problems to install the previous 0.7.4 versions. I made a mistake
with the data file of the default template. I apologize for the inconvenience.
Now it's definitively fixed.
*--
sfW3studioCmsPlugin - Version 0.7.4.1
Giansimon Diblas 11/30/08: Fixed minor bugs related to javascripts' refactoring
*--
sfW3studioCmsPlugin - Version 0.7.4
Giansimon Diblas 11/23/08: All the W3studioCMS' javascripts has been reviewed and refactored
*--
sfW3studioCmsPlugin - Version 0.7.2
Giansimon Diblas 11/08/08: The new version has been implemented through OOP
*--
sfW3studioCmsPlugin - Version 0.6.2
Giansimon Diblas 09/23/08: Fixed some problems related to paths due to recent changes of some application's paths
Giansimon Diblas 09/21/08: fileUploader moved to extra folder
Giansimon Diblas 09/21/08: sfGuardAuth moved to extra folder
*--
sfW3studioCmsPlugin - Version 0.6.1
0.6.1 - 09/20/2009 Giansimon Diblas: Changed the rendering of style sheet when the site will be published
*--
sfW3studioCmsPlugin - Version 0.6.0
0.6.0 - 09/16/2009 Giansimon Diblas: First release
Release 0.8.0.1 - 19/01/2009
sfW3studioCmsPlugin - Version 0.8.0.1
Giansimon Diblas 01/19/09:
1. Fixed a bug that occours when you save a menu with the "Set the class on each page" option
checked.
2. Fixed some problems related to usability with the Menu Builder editor.
---
sfW3studioCmsPlugin - Version 0.8.0.0
Giansimon Diblas 01/06/09:
1. Everything is now OOP.
2. The name of some modules has been changed so you have to update your enable modules.
3. The move system has been reviewed.
4. The projects import interface has been reviewed.
5. When you create a new template you can omit the three empty fields groupId:, pageId:, languageId:
6. Every project can be integrated with an extra directory that have to be called info,
where you can create a yml file with some useful information about your template. You
can also add an image to give a preview of the template. A detailed tutorial will be publish.
*--
sfW3studioCmsPlugin - Version 0.7.4.2
Giansimon Diblas 12/09/08:
Skins support added. Now everyone can create his own skin for W3studioCMS
Internet Explorer is now compatible. A problem with the menu builder remains, but it will be
fixed as soon as possibile.
Note: You might have problems to install the previous 0.7.4 versions. I made a mistake
with the data file of the default template. I apologize for the inconvenience.
Now it's definitively fixed.
*--
sfW3studioCmsPlugin - Version 0.7.4.1
Giansimon Diblas 11/30/08: Fixed minor bugs related to javascripts' refactoring
*--
sfW3studioCmsPlugin - Version 0.7.4
Giansimon Diblas 11/23/08: All the W3studioCMS' javascripts has been reviewed and refactored
*--
sfW3studioCmsPlugin - Version 0.7.2
Giansimon Diblas 11/08/08: The new version has been implemented through OOP
*--
sfW3studioCmsPlugin - Version 0.6.2
Giansimon Diblas 09/23/08: Fixed some problems related to paths due to recent changes of some application's paths
Giansimon Diblas 09/21/08: fileUploader moved to extra folder
Giansimon Diblas 09/21/08: sfGuardAuth moved to extra folder
*--
sfW3studioCmsPlugin - Version 0.6.1
0.6.1 - 09/20/2009 Giansimon Diblas: Changed the rendering of style sheet when the site will be published
*--
sfW3studioCmsPlugin - Version 0.6.0
0.6.0 - 09/16/2009 Giansimon Diblas: First release
Release 0.8.0.0 - 12/01/2009
sfW3studioCmsPlugin - Version 0.7.4.2
Giansimon Diblas 01/06/09:
1. Everything is now OOP.
2. The name of some modules has been changed so you have to update your enable modules.
3. The move system has been reviewed.
4. The projects import interface has been reviewed.
5. When you create a new template you can omit the three empty fields groupId:, pageId:, languageId:
6. Every project can be integrated with an extra directory that have to be called info,
where you can create a yml file with some useful information about your template. You
can also add an image to give a preview of the template. A detailed tutorial will be publish.
*--
sfW3studioCmsPlugin - Version 0.7.4.2
Giansimon Diblas 12/09/08:
Skins support added. Now everyone can create his own skin for W3studioCMS
Internet Explorer is now compatible. A problem with the menu builder remains, but it will be
fixed as soon as possibile.
Note: You might have problems to install the previous 0.7.4 versions. I made a mistake
with the data file of the default template. I apologize for the inconvenience.
Now it's definitively fixed.
*--
sfW3studioCmsPlugin - Version 0.7.4.1
Giansimon Diblas 11/30/08: Fixed minor bugs related to javascripts' refactoring
*--
sfW3studioCmsPlugin - Version 0.7.4
Giansimon Diblas 11/23/08: All the W3studioCMS' javascripts has been reviewed and refactored
*--
sfW3studioCmsPlugin - Version 0.7.2
Giansimon Diblas 11/08/08: The new version has been implemented through OOP
*--
sfW3studioCmsPlugin - Version 0.6.2
Giansimon Diblas 09/23/08: Fixed some problems related to paths due to recent changes of some application's paths
Giansimon Diblas 09/21/08: fileUploader moved to extra folder
Giansimon Diblas 09/21/08: sfGuardAuth moved to extra folder
*--
sfW3studioCmsPlugin - Version 0.6.1
0.6.1 - 09/20/2009 Giansimon Diblas: Changed the rendering of style sheet when the site will be published
*--
sfW3studioCmsPlugin - Version 0.6.0
0.6.0 - 09/16/2009 Giansimon Diblas: First release
Release 0.7.4.2 - 10/12/2008
sfW3studioCmsPlugin - Version 0.7.4.2
Giansimon Diblas 12/09/08:
Skins support added. Now everyone can create his own skin for W3studioCMS
Internet Explorer is now compatible. A problem with the menu builder remains, but it will be
fixed as soon as possibile.
Note: You might have problems to install the previous 0.7.4 versions. I made a mistake
with the data file of the default template. I apologize for the inconvenience.
Now it's definitively fixed.
*--
sfW3studioCmsPlugin - Version 0.7.4.1
Giansimon Diblas 11/30/08: Fixed minor bugs related to javascripts' refactoring
*--
sfW3studioCmsPlugin - Version 0.7.4
Giansimon Diblas 11/23/08: All the W3studioCMS' javascripts has been reviewed and refactored
*--
sfW3studioCmsPlugin - Version 0.7.2
Giansimon Diblas 11/08/08: The new version has been implemented through OOP
*--
sfW3studioCmsPlugin - Version 0.6.2
Giansimon Diblas 09/23/08: Fixed some problems related to paths due to recent changes of some application's paths
Giansimon Diblas 09/21/08: fileUploader moved to extra folder
Giansimon Diblas 09/21/08: sfGuardAuth moved to extra folder
*--
sfW3studioCmsPlugin - Version 0.6.1
0.6.1 - 09/20/2009 Giansimon Diblas: Changed the rendering of style sheet when the site will be published
*--
sfW3studioCmsPlugin - Version 0.6.0
0.6.0 - 09/16/2009 Giansimon Diblas: First release
Release 0.6.2 - 23/09/2008
sfW3studioCmsPlugin - Version 0.62
Giansimon Diblas 09/23/08: Fixed some problems related to paths due to recent changes of some application's paths
Giansimon Diblas 09/21/08: fileUploader moved to extra folder
Giansimon Diblas 09/21/08: sfGuardAuth moved to extra folder
*--
sfW3studioCmsPlugin - Version 0.61
0.6.1 - 09/20/2009 Giansimon Diblas: Changed the rendering of style sheet when the site will be published
*--
sfW3studioCmsPlugin - Version 0.60
0.6.0 - 09/16/2009 Giansimon Diblas: First release
Release 0.6.1 - 20/09/2008
0.6.1 - 09/20/2009 Giansimon Diblas: Changed the rendering of style sheet when the site will be published
0.6.0 - 09/16/2009 Giansimon Diblas: First release
Release 0.6.0 - 16/09/2008
Overview
W3studioCMS is a modern Open Source web 2.0 Content Management System application, a software designed to give the ability to manage the contents of a web site to people without any knowledge of web programming languages as HTML or PHP.
Imagine to browse any kind of website, as the one you are viewing now, then imagine the same page you are browsing that becomes editable in place, exactly how you see in in the frontend, for each content it contains: this is how W3studioCMS works. The changes you made are displayed in real time on the same page that you will publish at the end of your editing session by ajax transactions. There's nothing to imagine: here you really see what you get!
W3StudioCMS has no limitation design for the templates' layout: you can easily import any xhtml template and use it for your website. A complete tutorial will explain in detail how to import and use an existing template found in internet.
W3StudioCMS is totally Object Oriented, so you can easily customize the CMS for your needs, extending the core classes or adding new contents. It uses symfony as base framework, so all the benefits introduced by this powerful and great software are available in the CMS.
What's new
Many changes has been introduced since 1.1.0 release. The most important is the full support for larges sites.
This functionality has been developed bypassing the ORM and executing raw queries when it is necessary to interact
with many records. This behaviour is managed by the w3s_big_sites_fast_sql, in the app.yml configuration file and by default, ORM is
deputated to manage those operations mentioned above. To bypass the ORM, put the option to true. At the moment
the only working adapter is for mySql database, so if you are using another one you have to write your own
queries.
The second major change introduced is a full reorganization of names. The most important is related to bundled
plugins, w3sWidgets, which has been renamed in w3sExtension to avoid confusion with symfony's widgets system
used in forms. w3sWidgets name has been deprecated but it will be supported untill 1.2.0 version will be deployed.
All the core objects have been abstractized, so they cannot be directly instanced, so the real object that instances
each class, has been put with the related plugin. In this way it will be much more simple for a developer to find
the target object to inspect/change/override.
The third major change is related to modules which have been moved to plugins. The only module which still exists
is webEditor for backward compatibility.
At last, content extensions are now managed by a new serie of objects which can be extended to add your own extensions
for your contents.
Actually the documentation for developers is very poor, so I'm going to write a lot of documentation after
the release of the 1.1.0 stable version to help users to learn faster and better how to use the CMS and for
developers to let them get the full control over the CMS.
1.1.4 Changes
This version doesn't introduces great changes to CMS but only fixes some behaviours:
- giansimon: uploadify can now try to create the folders recursively when a folder doesn't exists
- giansimon: added a client-side function to clear and fill a select tag.
- The parameters to configure the extruders for control panel and menu manager has been defined as aplication variables.
1.1.2 Changes
This version introduces two important features:
- The frontend module has been totally separed from the backend.
The jquery support has been fixed.
Untill 1.1.1 version some changes you made in the backend have immediatly ported to the frontend and in particular if you changed a page,
a language, metatags and images. Now this bad behaviour has been fixed. The sf_w3s_absolute_images_path_frontend has been introduced to
correctly manage assets.
Before this release the plugins that uses jquery are hardcoded into the code, so some problems occours if you want to use another jquery
plugin. The w3s_jquery_plugins has been added to app.yml to declare which are the plugins that uses this framework so W3StudioCMS
can manage them safety when autoloads plugins' javascripts. When you made a new plugin which requires jquery, you have to add an app.yml
file inside its config folder as follows:
all:
.settings:
w3s_jquery_plugins:
w3sExtensionMbMaskedGalleryPlugin: on
Information
If you have troubles with pear package, you can download the packed version from here.
Read the LICENSE document to learn your rights using this plugin, or click here.
Read the INSTALL document to find the instruction to setup the plugin, or click here.
Learn how to use W3studioCMS plugin, reading the quick start guide.
The full w3studioCMS manual is available here.
How to customize w3studioCMS
Add a new content and the editor to manage it
This tutorial will explain in detail to add a new Extension packed as a symfony's plugin to W3studioCms to extend the CMS creating a
new content to insert markdown files into your website and how to create a new editor to manage it. Every time you need a new content
for your website, it should be implemented as a new extension.
Create the plugin
The first thing is to create a new directory inside the plugins folder of your project and call it
w3sExtensionMarkdownPlugin. The plugin's name is very important and it has to be created following the rule
w3sExtension[Name]Plugin. This rule is mandatory. As explained, a W3StudioCMS' extension is simply a symfony's plugin,
so the structure of the plugin's folder should be familiar. Refer to Chapter 17 of symfony's book to learn more.
Create the content
Add a new folder called lib under the w3sExtensionMarkdownPlugin directory, then add a new class and call it
w3sContentManagerMarkdown.class.php. Open that file and add the following code:
class w3sContentManagerMarkdown extends BaseW3sContentManager
{
}
Examine the name of class: it has to be called following this rule: w3sContentManager followed by the name you
intend to give to that content, in this case Markdown.
This class extends the base class BaseW3sContentManager that manages the page's contents. This class requires you to define
three abstract methods: getDefaultValue(), which will display the default value when a new content
is added, getInteractiveMenu() which will return the interactive menu to manage that content by javascript
and getEditorName() which will return the name of the editor that will manage the content itself.
Add the following code that defines the required functions:
protected $defaultText = '<span style="font-weight:bold;">Markdown file: </span>';
public function getDefaultValue()
{
return $this->defaultText . w3sToolkit::toI18N('No file has been assigned yet');
}
public function getInteractiveMenu()
{
$editor = sprintf('activeEditor = new markdownEditor(%s, %s);', $this->content->getId(), $this->mapper->getSlotId());
return sprintf($this->defaultInteractiveMenu, $this->content->getId(), $this->mapper->getSlotId(), $editor);
}
public function getEditorName()
{
return 'Markdown';
}
In the getInteractiveMenu method, please notice the variable $activeEditor: it defines at client-side which is
the editor that W3studioCMS has to open when a user clicks it to manage the content. In this case
the client-side editor variable will be a markdownEditor.
BaseW3sContentManager class has three methods which display the content when it is in editor, preview mode
and when it has to be published. For this content we have to override them. Add the following code:
public function getDisplayContentForEditorMode()
{
return w3sToolkit::toI18N($this->defaultText . $this->content->getContent());
}
public function getDisplayContentForPreviewMode()
{
$markdown = new w3sMarkdown();
return $markdown->fromFile(sfConfig::get('app_w3s_markdown_dir') . DIRECTORY_SEPARATOR . $this->content->getContent());
}
public function getDisplayContentForPublishMode()
{
return sprintf('<?php $markdown = new w3sMarkdown(); echo $markdown->fromFile(sfConfig::get(\'sf_data_dir\') . DIRECTORY_SEPARATOR . \'markdown\' . DIRECTORY_SEPARATOR . \'%s\');?>', $this->content->getContent());
}
The code explains itself so I think there is no need to explain it in detail.
Every content is instanced by a class which uses an abstract factory design pattern to create the right content.
The content creation is made using the class suffix of every content, in this case the parameter to pass to this
class is Markdown, exactly the suffix used for the content's class.
This class is called w3sContentManagerFactory.class.php and it is stored in the w3sCore/lib/content directory.
Display the content into the actionMenu
Every content is created from the Actions menu, so a new button is required in that menu. To add that button,
add a new folder called config under the w3sExtensionMarkdownPlugin directory and create a new file called toolbar.yml under
that directory. Add the following code to the file:
actionMenu:
buttons:
0:
image: <?php echo sfConfig::get('app_w3s_web_skin_images_dir')?>/w3s_interactive_menu/[your image].png
caption: Insert a Markdown file
action: W3sContent.addContent('Markdown')
imageTextRelation: 0
imageParams:
size: 32x32
This script adds a custom button to the actionMenu, the menu used to add a new content to the page. This means that the name
of the section, actionMenu, is the toolbar menu which will be modified. A menu could have custom buttons only if it has a specific
option called custom. Please examine in the config folder of the W3studioCMS plugin how is declared this menu to learm more.
Focus on the action param: it calls a javascript action, in this case the addContent function of the
javascript W3sContent object and the argument passed is exactly the string Markdown which is the content class' suffix.
This param will be stored in the database so W3studioCMS will know which type of content must be edited.
At last remember to define the [your image] adding a new image to represent the button.
Store markdown files
A directory where the markdown files have to be placed is required, so it must be declared somewhere.
The best place to set this parameter is the app.yml file under the plugin's config directory. Create that file then
put this code inside:
all:
w3s_markdown_dir: %SF_DATA_DIR%/markdown
Don't forget to create the markdown folder under the data dir of your project.
Create the editor
To create a new editor add a new class under the lib folder and call it w3sEditorContentsMarkdown.class.php.
This class will extend the BaseW3sEditorContents class, which is the base class to create a new editor for contents.
<?php
class class w3sEditorContentsMarkdown extends BaseW3sEditorContents
{
}
When you are creating an editor, you have to declare a protected variable called $editorSkeleton to
define the editor's xhtml skeleton. If you forget this step an exception will be throwned. For this content
the skeleton needed to edit the content is made by a combobox filled with the markdown files readed from
the sf_data_dir/markdown folder, which has been declared in the app.yml file, with a button which will
insert the content into the page. Note that this editor is very poor but it has the scope to teach you
how to build a full working extension plugin for the cms. A more complex plugin to manage markdown files is already
bundled from 1.1 release version.
protected $editorSkeleton = // Declares the editor's skeleton
'<div id="w3s_markdown_container">
<table border=0>
<tr>
<th>%s</th>
<td>%s</td>
</tr>
<tr>
<th></th>
<td>
<input id="w3s_edit_content_btn" onclick="activeEditor.edit(); return false;" type="submit" value="%s" />
</td>
</tr>
</table>
</div>';
BaseW3sEditorContents requires the drawEditor abstract method which has to be impemented to
build a new extension. The drawEditor method is called by the renderEditor function in the w3sEditor
class, to render the editor. Here is the code:
public function drawEditor()
{
if (!is_dir(sfConfig::get('app_w3s_markdown_dir'))) mkdir(sfConfig::get('app_w3s_markdown_dir'));
$files = sfFinder::type('file')->maxdepth(0)->relative()->sort_by_name()->in(sfConfig::get('app_w3s_markdown_dir'));
$markdown = array_combine($files, $files);
return sprintf($this->editorSkeleton, sfContext::getInstance()->getI18N()->__('Choose the markdown file'),
select_tag('w3s_markdown_file', options_for_select($markdown)),
sfContext::getInstance()->getI18N()->__('Insert markdown'));
}
This function fills the $editorSkeleton placeholders with the needed values.
activeEditor.edit(); is the ajax function that saves the contentand it will be defined shortly.
Add ajax transaction
The last thing to do is to create a new object on the client-side to manage the content. The w3s_editor.js
is a ready-to-use class which contains the APIs to manage a new editor on client-side. Create a
directory called web under the plugin folder, them add a new one called js under the web folder just created
and create a new file inside called w3s_editor_markdown.js. Open it and add the following code:
var markdownEditor = Class.create(w3sEditor, {
});
This creates a new markdownEditor object that extends the w3sEditor object. This code is quite enough to open your
editor, but at least an edit function must be defined to override the standard one defined in the parent class.
Insert this code inside the object:
edit: function()
{
W3sContent.editContent($('w3s_markdown_file').value);
return false;
}
That's all. Simply the selected element of the combobox "w3s_markdown_file" is taken and it is passed to the
W3sContent.editContent which saves it into the database.
Add a stylesheet
You can still add a stylesheet file to give the editor a better look. Add a new directory called
css under the web folder and create a new file called w3s_markdown.css. Open it and add
the following code:
#w3s_markdown_container{
border:1px solid #666;
background-color: #fff;
padding: 4px;
}
#w3s_markdown_container td{
padding: 4px;
}
At last is necessary to format the markdown contents to display the code sections highlighted and formatted
with a font with a fixed width. Markdown uses pre and code to represent this kind of text, so create
a new file called markdown.css and add this code.
pre {
padding:0.5em 0 0.5em 1em;
margin-bottom: 10px;
background-color:#222;
overflow:auto;
line-height: 17px;
}
code {
font-size: 12px;
color:#fff;
font-family: "Bitstream Vera Sans Mono", monospace;
}
Add the markdown stylesheet to frontend
Pay attention now: the javascripts and the stylesheets are automatically loaded when you work in
editor mode, but they aren't in the frontend, so you have to enable them manually. Create a new
view.yml file under the config folder and add the following code:
all:
stylesheets: [/w3sExtensionMarkdownPlugin/css/markdown.css: { raw_name: true }]
This adds the markdown file to the frontend. Every web folder of the plugin will be symlinked or
copied into the web folder of your application, that's the reason of the path
/w3sExtensionMarkdownPlugin/css/markdown.css.
For this particular kind of content you need a markdown converter and a simply class to manage it:
you can find them into the bundled w3sExtensionMarkdownPlugin. Copy them into the plugin's lib folder.
That's all. Run the command symfony:publish-assets from the cli then clear the cache to make it works.
Now you have a new content for your CMS and a new editor to manage it.
Notes
A plugin extension could have modules as every symfony's plugin. Remember that these modules have to be enabled
manually in your settings.yml.
All the contents and the editors bundled with W3studioCMS plugin has been packed as Plugin Extension. They are
placed under the plugins folder of sfW3studioCmsPlugin: you should give a look and digg them to learn
more about extensions.
I hope you will find useful this plugin.
Enjoy!
Giansimon
Giansimon DIBLAS 
-
Make a donation -
"symfony" is a trademark of Fabien Potencier. All rights reserved.
