http://www.cotonti.com/docs/ext/themes/cotemplate_debug_mode

I am from Russia and I am in search of a programmer who can fix some Cotonti bugs on my website. In Russia there are very few Cotonti programmers, so I decided to ask here.

Thanks in advance.

Here's the plugin if anyone needs it: http://www.cotonti.com/datas/users/pagetpl_897.zip

Pfff, I've had this problem with several client websites where I wanted to use the system category for multiple pages with different TPL's.

Glad I stumbled upon that bit of code, guys!

Thanks.

Make a simple plugin. hook it on `page.main`. Code it as follows:

if ($cat['tpl'] == 'system') {
  $mskin = cot_tplfile(array('page', $cat['tpl'], empty($al) ? $id : $al));
}

use templates named as: `page.system.#alias.tpl` or `page.system.#id.tpl`  (where #alias and #id is alias or id of corresponding page), located in standard page.tpl folders.

Note1: be sure to use alias if it exists for current page
Note2: be sure not to use special symbols in page alias that can not be used as file name symbols

Glad I stumbled upon that bit of code, guys!

Thanks.

#37508 lukgoh:

Use extra fields instead?

Good idea really :) but have a extra field inside Siena ?

You can do want on the "Administration Panel> Extra fields> cot_users - Module Users" page

but have a extra field inside Siena ?

Sorry MecTruy, can you be a little clearer on what you are asking please?

Use extra fields instead?

Good idea really :) but have a extra field inside Siena ?

i don't want use avatar upload, i want get url avatar, for example i want upload my avatar other image site, later i want put this image link my profile !! how is i can do this ?

i did some code 

modules/users/inc/users.profile.php

    "USERS_PROFILE_AVATAR1" => "<input type=\"text\" class=\"text\" name=\"ruseravatar\" value=\"".htmlspecialchars($urr['user_avatar'])."\" size=\"32\" maxlength=\"255\" />",

but for save mysql, how is i can do ?
    

Speaking of cotonti.com in particular and similar sites, I would prefer Markdown over HTML as it is more simple than bbcode and not so junky as HTML. We can start using markItUp with Markdown for new pages on this site at any time, but all our existing pages are in HTML and cannot be converted to markdown. The same is true for forum posts, except for the bigger problem: we cannot use several types of markup in forums at the same time, all posts must be in the same format. So we can't use markdown on forums.

In forum software like SMF, a registered user is able to choose his prefered editor for composing new messages. This is something I definitely miss in cotonti from the beginning. In most cases I personally don't need a blowed message editor with all possible features, aspecially in forums and comment forms. If I need formating features, bbcode buttons like in the old markitup are good enough or even simple html. And as a blind user, simple text boxes are more accessible to my screen-reading software than complex browser apps, even if ckeditor is accessible in most parts.

As a matter of course this is only my personal opinion, but other users also might have special needs. So instead of one side wide editor I'd like to have my favorite editor selectable in user profile.

Steffen

I'm thinking of a plugin or module, similar to custom fields, that will be called "menu blocks".
User will be able to add global menu block (with rights), which will have support for inline editing.

I think I'll make in within a week or so if I don't stumble upon some large problems.

I haven't played with inline editing yet though.

I saw that there's a new version of CKeditor. It contains a very nice and clean moona skin that is very much alike the Redactorjs look&feel.

It also features support for inline editing.

I think I'm going to try to port it and do something with inline editing as well. Who's with me? :)

No, it's different from polls. Polls actually have several templates mixed in 1 file. What we propose here is having 1 template (1 MAIN block) for both adding and editing. Which is less work for coders.

@Macik

Yes, support for pade.add.tpl still should be there if the template exists. But by default it would fall back to page.edit.tpl otherwise.

As for hooks, I think they still should be different because some actions are done when a page is added for the first time but not when editing, and vice versa. But e.g. page.add.tags and page.edit.tags can be merged. In other words, each hook needs individual consideration.

Is there ability to use one function with different TPLs?  I speak about using 2 tpl - one for add and one for edit.

Or some compromise solution to pass TPL path as a parameter, so (when we adding a page) first we can check is there separate «add» template, otherwise use standart «edit» one.

By the way, is this merge consider any «add/edit.first/tags» hooks? Would it be backwards compatible so old plugins still works?

Pros:

• Maintain just page.edit.tpl instead of page.add.tpl and page.edit.tpl.
• Reduces code redundancy.

Cons:

• If you need different sets of fields for adding and editing a page, you need to use IFs in the template or still make 2 different templates for add and edit.

What do you think?

Looks cool anyway, if I decide to buy the commercial licence, I'll try to make a plugin for it :)

I propose to make localization of names of the plugins, as in the description of plugins.

Example (eng → rus)

"Forums" → "Форумы",
"Whos online" → "Кто онлайн?",
"Pages" → "Страницы" / "Стуктура".

If name is not localized, using default name (english). Sort plugins list in the admin by field "code".

If can't translate plugin name, localization may be based on transliteration.

Example (eng → rus)

"PhotoShop" → "Фотошоп",

"Windows" → "Виндовс".

Please vote! ;-)

http://redactorjs.com/

In general : Any request that can change data on the server which can be either GET or POST should have the XSS protection. Developers should be aware of this.

So everybody who uses GETs to alter data should add a protection.

nice article for the interested people: http://teamtreehouse.com/blog/the-definitive-guide-to-get-vs-post

If you still want to check every GET request for x, use cot_check_xg(). You can achieve this using a plugin that hooks into common.php.

I can add the x parameter using something like:

jsMainSettings.xfactor='theXtoken';
$(document).ajaxSend(function(evt, request, settings){
    var x=$.getUrlParameter(settings.url,'x');
    if (!x) { settings.url+='&x='+jsMainSettings.xfactor };
});

This was a small test I made in the console, I have made $.getUrlParameter and I have a global named jsMainSettings where I can put the $sys['xk'] thing in.
I think with this little coding i have covered ALL my ajax requests... :D
This example is not ready yet.. but it is just to show the idea

BIG Question:

There should be a piece in common.php like :

//======== Anti XSS addition =============
if ($_SERVER['REQUEST_METHOD'] == 'GET')
{
	if (empty($x)) {
		$x = sed_import('x', 'G', 'ALP');
	}
	if (!empty($x) && !defined('SED_NO_ANTIXSS') && !defined('SED_AUTH') && $x != $sys['xk'] && (empty($sys['xk_prev']) || $x != $sys['xk_prev'])) {
		sed_redirect(sed_url('message', 'msg=950', '', true));
	}
}
//===================================

where sed_redirect for AJAX - JSON should be something else i think... but you get my point !!

What procedure did you follow?