Page Multi avatar ?

Kingsley	#1 16. Januar 2012, 10:12
Donator Thanked: 7 mal	http://www.cotonti.com/extensions/files-media/pagemavatar How exactly does this work? Call the same way as pageavatar? The problems I have with it: Although installed and all tags added to the corresponding tpls, it still says the page edit tags are missing. When I try to upload images it doesn't do anything but return to the pageadd/pageedit.

lukgoh	#2 16. Januar 2012, 14:43
Members Thanked: 12 mal	I don't have a computer to check this at the minuet, but take a look at the plugins php files to see what tags it is assigning. For example see where is says something like $t assign -> "TAG_NAME" = what the tag is/does. Then just make sure you have the same tags in your tpl file. I hope this helps, hopefully I will get my computer sorted and will be able to have a proper look. Luke.

Kingsley	#3 16. Januar 2012, 15:26
Donator Thanked: 7 mal	strange thing is, when I go to edit page, the output of the plugin is visible. I can select file(s), add file (s), but it doesn't upload. it returns to the edit page. in stead of publishing the page.

lukgoh	#4 16. Januar 2012, 16:52
Members Thanked: 12 mal	Is the folder it is uploading to writable?

Trustmaster

#5 16. Januar 2012, 18:45

Administrators
Thanked: 265 mal

Here are some example tags usage for this plugin.

In page.add.tpl, just this:

XML/XHTML

        
              {PAGEADD_FORM_MAVATAR}

In page.edit.tpl it's a bit more complex:

XML/XHTML

        
              <ul>
    <!-- BEGIN: PAGEMAVATAR_ROW -->
    <li><em>{PAGEEDIT_FORM_MAVATARTITLE}:</em> {PAGEEDIT_FORM_MAVATARFILE} {PAGEEDIT_FORM_MAVATAR} {PAGEEDIT_FORM_MAVATARDELETE}</li>
    <!-- END: PAGEMAVATAR_ROW -->
</ul>

In page.tpl it's something like this:

XML/XHTML

        
          
          
              
              <!-- IF {PAGE_MAVATAR.1} -->
<a href="{PAGE_MAVATAR.1}" title="{PAGE_MAVATARDESC.1}">
    <img src="{PAGE_M__MAVATAR.1}" alt="{PAGE_MAVATARDESC.1}" />
</a>
<!-- ENDIF -->
<!-- IF {PAGE_MAVATAR.2} -->
<a href="{PAGE_MAVATAR.2}" title="{PAGE_MAVATARDESC.2}">
    <img src="{PAGE_M__MAVATAR.2}" alt="{PAGE_MAVATARDESC.2}" />
</a>
<!-- ENDIF -->
<!-- IF {PAGE_MAVATAR.3} -->
<a href="{PAGE_MAVATAR.3}" title="{PAGE_MAVATARDESC.3}">
    <img src="{PAGE_M__MAVATAR.3}" alt="{PAGE_MAVATARDESC.3}" />
</a>
<!-- ENDIF -->
<!-- IF {PAGE_MAVATAR.4} -->
<a href="{PAGE_MAVATAR.4}" title="{PAGE_MAVATARDESC.4}">
    <img src="{PAGE_M__MAVATAR.4}" alt="{PAGE_MAVATARDESC.4}" />
</a>
<!-- ENDIF -->

            

        
      

May the Source be with you!

Kingsley	#6 16. Januar 2012, 19:44
Donator Thanked: 7 mal	Ah, begin and end tags.. now it works. thx Trust.. Maybe a good idea to create a template for downloads? so this kind of stuff is accessable?

Trustmaster	#7 17. Januar 2012, 06:54
Administrators Thanked: 265 mal	Full templates might be confusing to find the parts that you need, so I added these example pieces to plugin's page. May the Source be with you!

Mr G.	#8 17. Januar 2012, 07:21
Contributors Thanked: 2 mal	or check comments on author's website http://translate.google.com/translate?hl=pl&sl=ru&tl=en&u=http%3A%2F%2Flittledev.ru%2Fcotontifolio%2Fpage-multi-avatar.html

Kingsley	#9 17. Januar 2012, 14:48
Donator Thanked: 7 mal	#32707 Trustmaster: Full templates might be confusing to find the parts that you need, so I added these example pieces to plugin's page. that's what I more of less meant.. Added 1 minute later: #32711 Mr G.: or check comments on author's website http://translate.google.com/translate?hl=pl&sl=ru&tl=en&u=http%3A%2F%2Flittledev.ru%2Fcotontifolio%2Fpage-multi-avatar.html and that would have helped what? still dont see the simple examples on how to use it.

Kingsley

#9 17. Januar 2012, 14:48

Donator
Thanked: 7 mal

#32707 Trustmaster:
Full templates might be confusing to find the parts that you need, so I added these example pieces to plugin's page.

that's what I more of less meant..

Added 1 minute later:

#32711 Mr G.:
or check comments on author's website

http://translate.google.com/translate?hl=pl&sl=ru&tl=en&u=http%3A%2F%2Flittledev.ru%2Fcotontifolio%2Fpage-multi-avatar.html

and that would have helped what? still dont see the simple examples on how to use it.

Mr G.	#10 18. Januar 2012, 10:12
Contributors Thanked: 2 mal	last comment has a link to theme where tags are used. Just download and check files i.e. page.catalog.tpl

Kingsley	#11 18. Januar 2012, 12:30
Donator Thanked: 7 mal	@ Mr G. I'm sorry, but that kind of information shouldn't belong in comments. Plugin developer helps himself when he gives an example on how to integrate/operate his/her plugin. It shouldn't be a 'quest'. All I am saying is that when the developers publish plugins, they should do that in one particular format. So that info is understandable and instantly applicable for newcomers (growth is important, even for small communities like Cotonti) and recognizable for community members and returning peepz (coming from LDU/Seditio). Especially when the plugin DB isn't centralized, but divided over multiple sites. That makes in kinda prudent to have a unified format.

Kingsley

#11 18. Januar 2012, 12:30

Donator
Thanked: 7 mal

@ Mr G.

I'm sorry, but that kind of information shouldn't belong in comments. Plugin developer helps himself when he gives an example on how to integrate/operate his/her plugin. It shouldn't be a 'quest'.

All I am saying is that when the developers publish plugins, they should do that in one particular format. So that info is understandable and instantly applicable for newcomers (growth is important, even for small communities like Cotonti) and recognizable for community members and returning peepz (coming from LDU/Seditio).

Especially when the plugin DB isn't centralized, but divided over multiple sites. That makes in kinda prudent to have a unified format.

McDuck	#12 18. Januar 2012, 15:23
Members Thanked: 3 mal	That was my comment on the site developer. You're absolutely right: each published a plugin must be sufficiently documented to use his novice. The root problem is that for most authors to write plugins - a hobby, to whom they give their personal time (which is never enough), and the motivation to write the documentation does not exist. I could not unequivocally and categorically answer the question, what is worse: the lack of the necessary plug-in free access, or availability, but undocumented.

McDuck

#12 18. Januar 2012, 15:23

Members
Thanked: 3 mal

That was my comment on the site developer.
You're absolutely right: each published a plugin must be sufficiently documented to use his novice.
The root problem is that for most authors to write plugins - a hobby, to whom they give their personal time (which is never enough), and the motivation to write the documentation does not exist.
I could not unequivocally and categorically answer the question, what is worse: the lack of the necessary plug-in free access, or availability, but undocumented.

Kingsley	#13 18. Januar 2012, 15:56
Donator Thanked: 7 mal	I am totally not commenting on the work the developers produce (and the time spend. Am gratefull for it). All I am saying thet the likelyhood of their plugin being used on live sites raises significantly with a proper example/documentation. In this example, I would never had guessed that there was a begin and end tag. Simply expected it to function like the pageavatar (single) plugin. (mostly due to the almost indentical name). Don't see me commenting on that as a bad thing. It merely was a suggestion, in favor of the plugin writer..
Dieser Beitrag wurde von Kingsley (am 18. Januar 2012, 16:05, vor 13 Jahre) bearbeitet

Kingsley

#13 18. Januar 2012, 15:56

Donator
Thanked: 7 mal

I am totally not commenting on the work the developers produce (and the time spend. Am gratefull for it). All I am saying thet the likelyhood of their plugin being used on live sites raises significantly with a proper example/documentation. In this example, I would never had guessed that there was a begin and end tag. Simply expected it to function like the pageavatar (single) plugin. (mostly due to the almost indentical name).

Don't see me commenting on that as a bad thing. It merely was a suggestion, in favor of the plugin writer..

Dieser Beitrag wurde von Kingsley (am 18. Januar 2012, 16:05, vor 13 Jahre) bearbeitet