Menu
▾
▴
[Apc-aa-coders] Changes in AA Subversion - 2010-02-09
|
From: Honza M. <hon...@ec...> - 2010-02-09 15:03:50
|
Hi,
today I submitted some changes in the Subversion. I didn't posted the changes
for some time, so I added the list of changes form the last published version
of AA 2.50.0
Many changes are related to newer approach to write site modules - the SEO
friendly predefined AA_SEO_Router. This is the site module configuration which
do not require sitemodule's controll file - all you can set in AA interface.
Many of our last websites are based on it. Like:
- http://dataplan.info
- http://biom.cz
- http://www.nadacevia.cz
- http://www.ekowatt.cz
- http://www.mpo-efekt.cz
- http://stopznasilneni.cz
- http://biofarma.cz
- http://padesatprocent.cz
(for more details please look into /include/router.class.php)
The listed changes are in Subversion trunk. If you are using last stable
branch of AA and want to switch to trunk version, then do:
svn switch https://apc-aa.svn.sourceforge.net/svnroot/apc-aa/trunk
and back to last stable branch:
svn switch https://apc-aa.svn.sourceforge.net/svnroot/apc-aa/branches/2.50.x
Current state of SVN trunk:
Stable - we run current code three weeks on one of our production server.
Last SVN Changes:
02/11/10 (honzam)
- new possibilities for sites which uses new site module AA_SEO_Router:
- new home - sitemodule now handles root of the web and fills
the variables as it was typed /{xlang}/ (/en/). {xlang} is filled
form site module's language setting
- new {xuser:xxxx} alias - auth user informations (of current user)
xxxx is - field to show ("headline........", "_#SURNAME_" ...)
- "id" for long id
- empty for username (of curent logged user)
(We do not use {user} in this case, since views with {user}
are not cached, but the views with {xuser} could be
(xuser is part of apc variable))
- easy way how to authenticate the user - send "username" and
"password" by POST to any page which uses sitemodule. The users
are authenticated from reader management slices. If OK, then
the {xuser} is filled and the url is switched to ok_url parameter
(if provided). Else the URL is switched to err_url (if provided)
and err=1 is set (acessible by {qs:err}).
xuser is stored in the cookies
Login From Ussage:
<form action="{go:xqs=}" method="post">
<fieldset>
<legend>Login, please</legend>
<div style="margin-right:150px; text-align:right;">
<label for="username">Username</label>
<input type="text" name="username" id="username"><br>
<label for="password">Password</label>
<input type="password" name="password" id="password">
</div>
</fieldset>
<input type="submit" value="Login" style="margin-left:200px;">
</form>
- cookies added to pagecache key for sitemodule.
- added possibility to specify top-right selectbox priority for all
modules - not only the slices
- new {htmltogglecss:<toggle1>:<toggle2>:<css_rule>} - creates the link
text1 (or text2) +/- toggle which displays/hides all elements
matching the css_rule (#id82422) in example:
{htmltogglecss:+:-:#id_#SITEM_ID}
- new
{htmlajaxtogglecss:<toggle1>:<toggle2>:<css_rule_hide>:<url_of_text>[:<css_rule_update>]}
like:
{htmlajaxtogglecss:+:-:#id_#SITEM_ID:/apc-
aa/view.php3?vid=33&cmd[33]=x-33-{_#SITEM_ID}}
creates the link text1 (or text2) +/- toggle which
loads+displays/hides all elements matching the css_rule (#id82422) in
our example. Optional <css_rule_update> rule matching the element(s)
to update if it is not the same as <css_rule_hide> (good for updating
table rows, where we want to show/hide tr, but update td)
- fixed {math} and decimals setting
- new {max:arg1[:arg2][:arg...]} and {min:...} returns maximum/minimum
- new {jsonstring:<any text>} encodes the string to use it within JSON
- new selected parameter for {options:<group_id>:<selected>} - html
<option>s for given constant group with selected option
- new possibility to "&" delimiters for {view.php3} instead of
standard "&" (Xinha visual editor changes the & to & so we do not
need to care, now)
- new {server:<param>} which prints $_SERVER variable
@see http://php.net/manual/en/reserved.variables.server.php
- new <param> parameter used as additional code to <img...>
{img:<url>:[<phpthumb_params>]:[<info>]:[<param>]}
{img:{img_url.........}::imgb:alt="Logo {_#HEADLINE}"}
- default JPEG thumbnail quality changed from 70 to 90 - means better
images with {img...}
- new _#GRP_INDX (index of a group on page (it begins from 0 on each
page))
and _#IGRPINDX (index of item within a group on page (it begins from
0 on each group))
aliases in views
- added view links under alias definition textarea, if contains
view.php3 reference
- automatical removing of confusing links from Related Item Selection
Window, when admin design is used
- new Form.Element.setValue() and unpackToForm() javascript functions
- simplified structure of extsess*.php3 and locsess.php3 include files
- fixed {ajax} and {live} widgets - fixed parameter order after move to
widget.class.php
- better caching for tree aliases - {itree}, ...
- experimental implementation of new {_:Shortcut:params} construct
- not supported, yet
11/02/09 (honzam)
- removed confusing "Category" menu entry in "Slice Settings"
(categories are edited in field setting)
- fixed "Modify Content" Item manager action
08/23/09 (honzam)
- new possibility to define forms through admin interface
(see "Slice Admin" - "Design" - "Forms")
- new possibility to entering related items into slice using above
mentioned forms, called through AJAX
(Two Boxes widget has this feature, now)
- removed maxcount restriction for number of related items
- easier usage of AA_Manager class
- generalized usage of AA_Object (and its storage into database)
and AA_Content. Any AA_Object is now very easiy editable
by AA_Manager; refactoring a bit
- zids now uses Iterator (PHP 5 needed)
- started usage of class autoloading
- new AA_Grabber_Form which uses the new standard way of input
the items to the database
- log viewer and searchlog viewer rewriten to AA_Manager class
instead of old tabeedit
- merged changes from v2.50.x branch ------------------------
08/22/09 (honzam)
- new possibility to copy the field definition from ANY slice
(see "Slice Admin -> Fields")
- new {itree:<tree-
string>:<nested_top>[:<content>[:<delimiter>[:<nested_bottom>]]]}
Displays field/alias of given item(s) in tree. It wors exactly as
{item} but the parameter order is more logical, so the {itree} is
the preffered way of displaying trees and breadscrumbs...
- new {treestring:<item_id>[:<relation_field>]}
{treestring:2a4352366262227383484784635362ab:relation.......1}
generates tree-string (as used in {itree}) based on item and its
relations
- new {(....)} syntax for deffered evaluation:
{item:6625:{(some text {headline........}...etc.)}}
This way you are able to pass {..} any aa_expressions to any function
instead of using just aliases there.
- new {qs:<varname>} which return url GET parameter:
returns Havel for http://example.org/cz/page?surname=Havel
- new {ifeq:<var1>:<var2>:<text>:<else_text>}
{ifeq:{xseo1}:about: class="active"}
If <var1> is equal to <var2>, then print <text>, else prints
<else_text>. <(else_)text> could contain _#1 and _#2 aliases
for <var1> and <var2>, but you can use any {} AA expression there.
- fixed display of informations about current user {user:...}
for fastcgi PHP version
08/17/09 (honzam)
- Site Module now you can use without any control-file, so you do not
need any PHP scripting at all. All you need is to select
AA_Router_Seo in "Router" field in Site Setting and specify
the slices, which are used within the Site Module. This means, that
AA_Router_Seo is now stbilized and standardized. See also new
possibilities useful here - {xid}, {xid:path}, {xid:1}, {go} and tree
posibilities of {item}
- new {go:<query-string>} - returns url based on current state (apc)
and query-string paramater (for AA_Router_Seo)
ussage:
{go:xseo1=faq&xseo2=questions}
(we used {go2url} custom function in previous versions of AA. {go}
function is however core function, now
- new {xid[:<level>]} - complement to {xseo1},.. variables
of AA_Router_Seo - returns id of the current item on specifield level
- {xid} - returns id of current item (the id of {xseo} item)
- {xid:1} - returns id of item on first level (the id of {xseo1}
item) for /cz/project/about-us returns id of "project" item
- {xid:path} - returns ids path of current item - like:
2587(2877(3004)) as used in {item...} syntax - good for
breadcrumbs: {item:{xid:path}: _#HEADLINE:: _#HEADLINK >}
- new possibility for {item} to display items in trees. In that case
you will use tree representation string, just like:
3234(3443-3678(3872-3664)-3223)-4045
The formating is then done through current <aa_expression> and
<delimiter>, but also through new <nested_top> and <nested_bottom>:
{item:<ids>:<aa_expression>[:<delimiter>[:<nested_top>[:<nested_bottom>]]]}
Used just like: {item:{xid:path}: _#HEADLINE:: _#HEADLINK >}
See wiki
(http://actionapps.org/documentation/?title=Syntax#.7Bitem.7D_Display_field.2Falias_of_given_item)
Update 08/22/09: use rather {itree} syntax, which has more logical
parameter order (due to backward compatibility of {item})
08/11/09 - (honzam)
- new {filelink:<url>:<text>} syntax - get link to file for download
(prints also file size and type) -
ussage: {filelink:{file............}:{text............}}
returns:
<a href="http://..." title="Document [PDF - 157 kB]">Document</a>
[PDF - 157 kB]
- better handling of text in {shorten} syntax
- new parameter lock=1 for polls.php used if we want something like
view for polls and we want the polls do not react to URL parameters.
Used maily if we want list more than one poll on one page
- better cleanup of tasks (from toexecute queue) - the taksk with
priority = 0. Such tasks are considered as undoabe. Note the priority
is decreased on each try of task execution.
08/01/09 (asanchez75)
- Added Shorcut to edit ITEM in AA finder. Search and show link to edit
directly link of item
Older changes you will find in CHANGES file:
http://apc-aa.svn.sourceforge.net/viewvc/apc-aa/trunk/CHANGES?view=markup
Volunteers, who will rewrite the changes from CHANGES file to
http://actionapps.org documentation are strongly welcomen.
Best,
Honza
|
