Welcome Guest ( Log In | Register )

9 Pages V   1 2 3 > » 

Ivan Stamenov
Posted on: Mar 27 2013, 08:44 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Hi, urby. You already have such a example in examples folder.

Please take a look in the com-content.ini file. Here is the "view a category" case settings:

Код
[RUN]
view = category
moo_container = td.list-title
moo_title = a
link = a
inject = after | a


It defines multiple items, each of which has a title and a link URL. Each item resides in a TD tag with class "list-title". The title of an item can be found in the A tag within the TD. The link URL is defined within the same A tag. The mailorder link is injected after the A tag.

Here is the result:

Attached Image


Each "Order now" link is the resulting Mailorder link.


Each of your orderable items must have a HTML representation similar to the following:

Код
<h2 class="orderable_item">
     <a href="http://link-to-the-item/">Orderable item</a>
</h2>


Then you may set in your relevant .ini file something like:

Код
moo_container = h2.orderable_item
moo_title = a
link = a
inject = after | a


In short, there must be a link with the orderable item's link and title, wrapped in a H1, H2, DIV or other suitable element, possibly marked with a class name.
  Forum: Joomla Extensions · Post Preview: #5836 · Replies: 24 · Views: 5,193

Ivan Stamenov
Posted on: Mar 27 2013, 07:15 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Hi, Andrai!

This is a bug sad.gif Thank you for pointing it to us.

Here is how it can be fixed:

1. Using FTP client (e.g. Filezilla), open /components/com_sportspredictions/models/matches.php

2. To prevent the unpublished games from displaying to the user, find the following code (lines 61-64):
Код
$where = array(
    "g.date>'{$this->_now}'",
    "g.res_fina_equipe1 = '--'"
);


Replace it with:

Код
$where = array(
    'g.published=1',
    "g.date>'{$this->_now}'",
    "g.res_fina_equipe1 = '--'"
);


3. To prevent attempts for voting for unpublished games, find (on line 90):

Код
$this->_db->setQuery('SELECT id_mat FROM #__se_games WHERE id_mat IN ('.implode(',', $match_ids).') AND `date`>\''.$this->_now.'\'');


Replace it with:

Код
$this->_db->setQuery('SELECT id_mat FROM #__se_games WHERE id_mat IN ('.implode(',', $match_ids).') AND `date`>\''.$this->_now.'\' AND published=1');


Best regards,

Ivan
  Forum: Joomla Extensions · Post Preview: #5834 · Replies: 2 · Views: 1,341

Ivan Stamenov
Posted on: Mar 25 2013, 12:15 PM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Нов плъгин ще бъде публикуван за продажба до ден-два: Joomla User Authorisation Plugin. Той ще бъде наличен за Joomla 2.5 и нагоре.

Плъгинът ще позволява на собствениците лесно и бързо да добавят абонаментна система към своите сайтове.

Ако даден потребител има активен абонамент, той ще се логне успешно. В противен случай той ще бъде приканен да се абонира чрез нарочна форма за плащане и няма да му бъде позволено да се логне в сайта (въпреки, че е въвел валидни потребителско име и парола).

Плъгинът има вградена автоматична система за известяване, която позволява на потребителите с изтичащ абонамент автоматично да бъдат изпращани напомнителни имейли. Тази система изисква cron job-а на Payments for Joomla да е настроен и активен! Интервалите, на които съобщенията да бъдат пращани на съответните потребители, се задават в настройките на плъгина. По подразбиране тези интервали са съответно 3 дена и 1 ден преди изтичане на абонамента.

Другите две настройки към плъгина са:

  • VIP списък: списък от ID-та на потребители, разделени със запетаи. Тези потребители ще бъдат допускани да се логват и без абонамент.
  • Форма за абонамент и при успешен логин: Ако бъде зададена стойност "Да", формата за абонамент ще бъде налична и след успешен логин на абониран потребител, по този начин позоволявайки му да увеличи срока, за който е абониран.


Плъгинът в момента засяга единствено логването на потребители в сайта. Ако искате да действа и при логване в администрацията, коментирайте първите два реда от функцията onUserAuthorisation():

Код
//if (JFactory::getApplication()->isAdmin())
    //return $response;
  Forum: Джумла добавки · Post Preview: #5827 · Replies: 19 · Views: 14,314

Ivan Stamenov
Posted on: Mar 25 2013, 09:42 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


A new plugin will be published in a day or two: Joomla User Authorisation Plugin. It will be available for Joomla 2.5 and above.

The plugin will allow the site owners to easily add and manage a subscription layer to their site.

If the user has an active subscription, he is allowed to login. Otherwise he is invited to use the subscription payments form in order to subscribe to the site and the login is denied (though valid username and password are presented).

The plugin has an automatic built-in notification system, allowing notification messages to be sent to the users, whose subscription is about to expire. This notifications system requires the Payments for Joomla cron job to be set. The intervals, on which the notifications are to be sent to the relevant users, are set in the plugin's settings. By default these are: 3 days before the subscription's expiration and 1 day before the subscription's expiration.

There are two more plugin settings:

  • VIP list: a comma separated list of user IDs. These won't be asked to pay for subscription.
  • Extend subscription message: if this is set to "Yes", the subscription payments form will be presented to the subscription owners upon successfull login too, allowing them to extend their subscription period.


The plugin is currently affecting only the front-end logins. If you want the back-end logins to be affected too, comment out the first two lines from the onUserAuthorisation() function like this:

Код
//if (JFactory::getApplication()->isAdmin())
    //return $response;
  Forum: Payments for Joomla · Post Preview: #5826 · Replies: 0 · Views: 3,656

Ivan Stamenov
Posted on: Mar 19 2013, 10:13 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Цитат(Julian @ Mar 15 2013, 08:55 AM) *
Hi Ivan,


Oh, then it is obvious and it should be easy to solve:
I live in germany and most emails have "AW:" or "WG:" in front.

In Terms of Multilingual I would suggest to create an option so the admin can freely change the "re" and adjust it to his needs.
However, is there a quick way I can add the german stuff too?

And about the topic:
The recent Kunena-version adds [Forumname] before the thread-title and (category) at the end of the subject of the eMail-notification.
Does PBEM sort that out or do I need to change the eMail-templates of kunena?

All the best, Julian!


Hi, Julian!

I've added a new setting in the admin (Reply tag), now you are able to set what the reply emails' subjects must start with. You may set this to AW, WG, RE, FWD or whatever you want. If an email subject starts with AW:, wg:, Re: or fWd: (case insensitive), the message will be threatened as a reply to the relevant topic.

About your second question - PBEM uses the Kunena's $message->sendNotification() function, so you should not have to modify the e-mail templates....

Best regards,
Ivan


New version is uploaded and available for download.
  Forum: Joomla Extensions · Post Preview: #5796 · Replies: 31 · Views: 9,748

Ivan Stamenov
Posted on: Mar 15 2013, 08:08 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Hi, Julian!

In order of your questions:

1) "Post as reply" must be set to "Yes" and the subject of your reply e-mail must start with either 're:' or 'fwd:' (case insensitive) + the thread's title. In such a case the PBM component will look for a thread with the given title and will add the reply to it.
E.g.: if "Post as reply" is set to yes and an e-mail with subject "Re: Yay! It's Friday!" is received, it will be added to the "Yay! It's Friday!" thread in the relevant forum.

2) This is a very good idea and probably this feature will be added in the next version. Unfortunately the current version does not support it and I don't know when the next one will pop up. However, if you or someone you know is keen in PHP, the component may be relatively easily tweaked to do this:
- add a definition of sh_t_happened($usr_mail, $error_message) function in the following file: /administrator/components/com_post_by_email/helpers/importers/com_kunena_init.php. This function will send the $error_message error message to the $usr_mail e-mail address.
- look in the /administrator/components/com_post_by_email/helpers/importers/com_kunena.php file. There are several $this->_output['err'][] = {error message} statements which gets executed when... sh_t happens. Append after these the relevant call to the mail sending function: sh_t_happened($usr_mail, {error message}). Note that the $usr_mail variable is already containing the message author's e-mail address at this point - there is no need to search for it.

3) If set to yes, the "Strip HTML tags" setting will use the PHP's strip_tags() function to remove all the HTML markup from the message's body prior to storing it in the database. As the e-mail will be posted to a forum thread, I think it is a good idea to turn it on.

Best regards,

Ivan
  Forum: Joomla Extensions · Post Preview: #5768 · Replies: 31 · Views: 9,748

Ivan Stamenov
Posted on: Mar 14 2013, 07:10 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Hello, Marcel!

It seems that the JavaScript fails for some reason. Could you please give us a link to a page where this happens?
  Forum: Joomla Extensions · Post Preview: #5762 · Replies: 4 · Views: 1,990

Ivan Stamenov
Posted on: Mar 12 2013, 08:31 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


There is a new version of the content plugin: 1.1.

It has a new parameter available for use in the ini file, called "run_only_at". It has the same syntax as the "skip" parameter and the opposite behavior, allowing to list only the pages you want the plugin to work at.
  Forum: Joomla Extensions · Post Preview: #5751 · Replies: 27 · Views: 42,275

Ivan Stamenov
Posted on: Mar 12 2013, 08:29 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Hi, urby.

I am sorry for the delay...

The new version is already available. There is a new parameter in the ini file, called "run_only_at". It has the same syntax as the "skip" parameter and the opposite behavior.
  Forum: Joomla Extensions · Post Preview: #5750 · Replies: 24 · Views: 5,193

Ivan Stamenov
Posted on: Mar 11 2013, 06:48 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Цитат(Samatyme @ Mar 10 2013, 04:53 PM) *
Yeah...I did figure that out, but it could not help much as the currency I wanted to use was not a recognized trading currency with PAYPAL.

Thanks for the reply...

SAMATYME



Hi, Samatyme.

The problem is, you must use a currency, recognized by PayPal (if you use the PayPal payment plugin)... Even if you display your prices in a different currency, after all, the client will be forced to use "PayPal" currency when doing the transaction.

Best regards,

Ivan
  Forum: Payments for Joomla · Post Preview: #5743 · Replies: 3 · Views: 2,429

Ivan Stamenov
Posted on: Mar 6 2013, 06:52 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Цитат(urby @ Mar 5 2013, 04:37 PM) *
Tnx now it show order button.

But its shows in every article on site. I want that is shown in only 1 article.
I want create article with lets say 5-6 products and that i have only in that article order button for every item. So 5-6 order buttons in 1 article.
Any help how to do it?

Thank you for fast ansver


Hi, urby.

Unfortunately there is a setting to tell on which article IDs the plugin should NOT work, but there is no setting to tell it on which IDs it SHOULD work.

The new version of the plugin disregards the "id" parameter in the {mailorder} tag - it gets it from the URL of the page. You should either use the older version or try the following (if you don't have many categories in your site):

1. Create a separate articles category which will hold the articles you want the mailorder button to be displayed in;
2. For each item to be ordered create a separate article and put it in the above mentioned category;
3. Put "view = category" and "skip = {list of category IDs}" instructions in the .ini file, replacing "{list of category IDs}" with a comma separated list of all the categories in your site except the ID of the category with the mailorder products.

I'll do my best to add the requested feature in a day or two. If you don't feel like experimenting, a new version will be available by Friday.


  Forum: Joomla Extensions · Post Preview: #5715 · Replies: 24 · Views: 5,193

Ivan Stamenov
Posted on: Feb 25 2013, 01:20 PM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


There was a bug in the content plugin of the newest version: SITE_ROOT was used instead of mo_conf.SITE_ROOT. To fix it, open
Код
/plugins/content/mailorder/assets/js/plugin.js


and replace on lines 30 and 39
Код
SITE_ROOT

with
Код
mo_conf.SITE_ROOT

(prepend "mo_conf." before "SITE_ROOT")
  Forum: Joomla Extensions · Post Preview: #5659 · Replies: 27 · Views: 42,275

Ivan Stamenov
Posted on: Feb 20 2013, 06:56 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Hi, boerenooi.

We don't need the login data for your site. You need to set up a cron job:

/administrator/components/com_post_by_email/cron.post_by_email.php

If you intend to call the cron file through HTTP, you need to comment out the following line both in the cron file and in the controller.php, function cron():

Код
if (!empty($_SERVER['REMOTE_ADDR'])) exit;
  Forum: Joomla Extensions · Post Preview: #5613 · Replies: 22 · Views: 3,958

Ivan Stamenov
Posted on: Feb 18 2013, 07:28 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Цитат(Vadim @ Feb 15 2013, 12:16 PM) *
You maybe one of top seo experts in the world rolleyes.gif no questions...

Buy I have a problem with your component, I want to use but have error.
Can you help me with Undefined offset: 1 in /home/______/public_html/plugins/content/seolinks.php on line 79?


Hi, Vadim!

You may supress the notice the following way:

1. Open the above mentioned file: /plugins/content/seolinks.php and go to line 79.
2. Prepend the '@' character before the list statement like this:

@list($parser,$pars) = explode('?', htmlspecialchars_decode($info['markup']));

Or here is another way:

1. Change lines 79 & 80 from:

Код
list($parser,$pars) = explode('?', htmlspecialchars_decode($info['markup']));
if (!empty($pars)) {


into

Код
$temp = explode('?', htmlspecialchars_decode($info['markup']), 2);
if (isset($temp[1])) {
       list($parser,$pars) = $temp;


  Forum: Seo Optimization · Post Preview: #5589 · Replies: 11 · Views: 2,501

Ivan Stamenov
Posted on: Feb 15 2013, 07:40 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Hi, Rossi!

I found the problem! The J1.5 version of PBM does not support the attachment container's title attribute, so instead of

Код
<img src="%s" title="%s" />


you should use

Код
<img src="%s" />


The second %s bugs the stuff. Here is the result:

Attached Image


Please note that the J1.5 versions of some components (PBM included) are discontinued...

Best regards,

Ivan
  Forum: Joomla Extensions · Post Preview: #5581 · Replies: 8 · Views: 2,158

Ivan Stamenov
Posted on: Feb 14 2013, 07:53 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Do you want "google images like" effect on all your pictures posted in all content items of your Joomla website with few clicks?

A new system plugin named "Image Zoom for Joomla" is released. Using jQuery, it is able to magnify certain images on the page when pointed with the mouse pointer.

Цитат
"Image Zoom for Joomla" plugin use separate and lightweight FREE jQuery plugin developed from 3D Web Design (our programmer Pavel Kukov). This jQuery plugin is free for use and under GPL v.2 license. Soon we will have examples and separate "more info" page on our website.


Parallel to the Joomla settings, it has a built-in INI files based settings system, which may be used to set different settings for the different types of pages.

If you take a look at http://3dwebdesign.org/ , the book links on start page are an example of how this plugin affects the images.


The idea: install plugin, configure image class settings (css class) and with 2-3 clicks all pictures posted in your website content will be with zoom effect. No css changes required, without changes in html code of content, only with 2-3 options in plugin configuration.

This can be done for all products pictures in Virtuemart or for all pictures posted in other component. Again with max. 2 minutes work.



You have options in plugin:
- to use enhanced ini settings or not
- to configure img class
- to configure scale factor of images
- to configure animation duration
- to configure two types of animation easing

Цитат
Note that if you want to use enhanced ini settings, you must configure it yourself. Terms for this plugin are: no free support for configuration over ini file! If you want, you can order paid configuration from us with price 5 usd for every next configured component.


Price of plugin: 9 usd. Purchase and download: http://3dwebdesign.org/images-zoom-joomla

Extension is for Joomla 2.5 only!
  Forum: Joomla Extensions · Post Preview: #5564 · Replies: 0 · Views: 3,616

Ivan Stamenov
Posted on: Feb 14 2013, 07:13 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Version 4.0 for Joomla 2.5 and 3.0 is released today.

As of version 4.0, the MicroFormatsVotes plugin (aka MFV) is now a system one. It is completely revised and has its settings system almost completely rebuilt. Its database structure remains unchanged (it uses the same SQL tables as the content MFV), so no information will be lost if you upgrade from a previous (content plugin) version.

  • The resulting rich snippets code is following the Google's specifications exactly, there are no more hidden items or offsets;
  • The new INI based settings system makes the MFV plugin extremely versatile and easy to extend. The only downside is, that you have to delete the settings cache files manually when doing changes in the INI settings (such a need should arise very rarely).
  • The new MFV is not affected by the Joomla's caching system, so you may use it with the Joomla cache enabled;
  • The new MFV may be set to work with every component in your site, you will (most likely) not have to alter component files and PHP code. Basic HTML reading skills are required, though. Or, for a small fee (5 USD per component), we may set it up for you.


In the config/examples/ subdirectory there are "ready to use" INI files for the following components:

  • com_content
  • com_k2
  • com_mtree
  • com_virtuemart (may require minor adjustments)


----------------
Fast install, short guide:
1) Install the plugin
2) Enable the plugin
3) Open plugins/system/microformatsvotes/config/examples/com_content.ini via FTP
4) Copy ini files to /plugins/system/microformatsvotes/config
5) Edit .ini file parameters, this part:
Код
[RUN]
view = article
#layout =
#task =
id_par = id
context = com_content.article
#skip
stars = 1
novote = 1
position = after </h2>
HTML_before = <div style="clear:both;margin:7px 0">
HTML_after = </div>


All of these parameters are described in manual file and the most important part is:
Код
position = after </h2>


This mean position where stars will be inserted. Plugin search for tag </h2> and insert stars after this tag (you must have h2 tag on page). If in HTML code of your pages are not present h2 tags, change </h2> with some other tag.

6. Delete the settings cache files manually when doing changes in the INI settings (such a need should arise very rarely).
----------------

How to show stars and votes on homepage?

In most of Joomla websites homepage of website is probably frontpage view. You need to activate frontpage view in your ini file. If your frontpage menu is something like this (clik on edit menu in admin to check):
Код
index.php?option=com_content&view=featured

you need to actvate in your ini file:
Код
view = featured


How to show stars on categories pages?
you need to actvate in your ini file:
Код
view = category


If category page is blog view:
Код
layout = blog
view = category



Цитат
And don't forget to change novote = 1 (mean no votes allowed) to novote = 0 (mean votes are allowed) and to delete again the settings cache files smile.gif


More details, regarding the update from versions before 4.0 and the INI files structure (step by step example included), are contained in the user manual: Attached File  manual.pdf ( 142.12K ) Number of downloads: 56



How this looks in Google now? 3D Web Design with microformats seo in Google.bg.
  Forum: Seo Optimization · Post Preview: #5563 · Replies: 138 · Views: 78,865

Ivan Stamenov
Posted on: Feb 12 2013, 10:06 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


New versions are released for both Joomla 2.5 and 3.0 (v.1.7.4 for joomla 2.5 and v.1.8.3 for Joomla 3.0).

If the sender's e-mail address is recognised as a Joomla user's e-mail address, the relevant user gets set as content item author. Otherwise the default author is used.
  Forum: Joomla Extensions · Post Preview: #5546 · Replies: 105 · Views: 79,151

Ivan Stamenov
Posted on: Feb 11 2013, 07:10 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Hello, Rossi!

The PBM component does not work with forwarded (or attached as .eml) messages. Could you please send us a newly created message with as many attachments as you wish? Then I will check what is happening.

Best regards,

Ivan
  Forum: Joomla Extensions · Post Preview: #5530 · Replies: 8 · Views: 2,158

Ivan Stamenov
Posted on: Jan 29 2013, 07:50 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


New Mail Order Pro for Joomla 3 and for Joomla 2.5 now is content plugin instead of older versions (component).

Цитат
Current version of plugin is v.1.2.2. Support of old Mail order version (component based) is discontinued from 23 September 2013!


New content plugin can be inserted to work everywhere you want, in every Joomla component. Examples for Mosets Tree and content are included in package. Now in Mail Order Pro package are: old version (component for joomla 1.5, for Joomla 2.5 and for Joomla 3.0) and new version (content plugin for Joomla 2.5).

Цитат
New system plugin to control in which component will work MailOrder is included for free in MailOrder package. This is great opportunity for all Joomla developers - plugin can be used to work in combination with every other content plugin, not only for our plugins.



I. What's new?

- You may use the MailOrder plugin everywhere on your site, in every component. All you need is to set the relevant INI file (and possibly the plg_system_plginvoker plugin – if you have the Joomla cache enabled or the component you are targeting does not invoke the content plugins itself). Setting the INI file for a component (which I see for the first time in my life) takes me 20 seconds;
- It now works with the Joomla cache enabled;
- It works way faster than the MailOrder component – almost everything is done using MooTools on the user's browser (the script is less than 3 kB), all the database queries are gone as well (except for these in the Joomla's core classes);
- There is no need to use the {mailorder} tag anymore (though you may, if you insist to);
- Instead of having one component with two plugins, there is only one plugin now;
- It has ReCaptcha support built-in.


II. Configuration.

There are two types of configuration settings, which are both shaping the plugin's behaviour:

a ) Conventional – the plugin's backend settings. Here you can set your preferred language, the text to be displayed above the order form (if any), where the order e-mails should be sent and the ReCaptcha settings.

b ) .INI files in the config/ subdirectory. These define where and how the plugin should work.

The rest of this section is dedicated to the INI files configuration.

By implementing the INI files configuration, we are now able to define a much more complex behavior in addition to speeding up the plugin's performance (the INI files are parsed only once, the plugin then reads the serialized data).

The only downside is, that when you make a change in an INI file, you need to manually delete the relevant serialized data .DAT file in the config/cache/ subdirectory in order for the updated settings to be applied. Such needs should arise very rarely, though.

So, how this stuff works?

1) When the plugin gets invoked, it retrieves the component's name from the page URL, i.e. com_component;
2) Then it looks for a com_component.dat file (containing the parsed settings for this component) in the config/cache/ directory. If found, goes to 5);
3) If com_component.dat is not found, it looks for com_component.ini in the config/ directory;
4) If com_component.ini is found, it gets parsed and the data is saved in a com_component.dat file within the cache directory. Otherwise the MailOrder plugin is not supposed to work with the com_component component (there is no .ini file) and it returns the control to the caller;
5) The plugin retrieves the com_component related settings, stored in the .dat file;
6) It checks whether and how it should behave in this particular view, task and layout. Then it processes the page, if needed.

OK, what is in these INI files?

The INI files consists of:
- header section (not required);
- at least one RUN section (REQUIRED);
- 0 or more CLEAR sections (not required)

The header section is used to assign default values to some of the ini parameters. If these parameters are met later in a RUN or CLEAR section, their default value will be overwritten with the later one (only for the section they are met in). The following parameters are recognized in the header (and RUN, and CLEAR) section:

data_in - a string, which defines in which object property to look for the {mailorder} tag into. Not required. Defaults to "text".
window_type – either “modal” or “hs”. Defines the window type of the order form: modal or highslide (“hs”)
window_w – integer, the window width (in pixels), defaults to 300.
window_h – integer, the window height (in pixels), defaults to 600.
formtpl – string, the name (w/o the txt extension) of the order form template. The templates reside in the assets/templates/ folder. They are the same as in the MailOrder component and will not be discussed here.
buy – integer, the index of the PLG_CONTENT_MAILORDER_BUY string to be used in the mail order link. The PLG_CONTENT_MAILORDER_BUY strings are defined in the plugin's language files.

The RUN section define the plugin's behavior in different view, task and layout URL combinations. It may contain any of the header section's parameters. It must contain at least one of these parameters:

view – string, the required value of the "view" page URL parameter, if any
layout – string, the required value of the "layout" page URL parameter, if any
task – string, the required value of the "task" page URL parameter, if any.

These define the conditions, that must be met by the page URL in order for this RUN section's data to be used to control the plugin's behavior.


Example 1:

Lets say we have a RUN section like this one:

Код
[RUN]
        view = category
        layout = blog
        … … …


and the following page is requested:

index.php?option=com_content&view=category&layout=list&task=display&id=1

The above RUN section will be ignored, because it requires the “layout” URL parameter to have value of “blog” (and we have “list”). The “task” URL parameter's value is ignored in our case, as it is not presented in this particular RUN section's definition.

The plugin will check the RUN sections in the order they are defined in the INI file. It will use the parameters, defined in the first RUN or CLEAR section, which run parameters (view, layout, task) match the requested URL.

The following RUN parameters control the plugin's behavior:

[REQUIRED!] moo_container - MooTools selector, marking the entity container. E.g.: if the entire entity resides in a DIV with class "item-page", you should set this to div.item-page; if the entire entity resides in a DIV with ID "item-container", you should set this to div#item-container;
[REQUIRED!] moo_title - MooTools selector, marking the element, which contains the entity title (relative to the container). E.g.: if the entity title happens to be a link, residing in the only H2 tag within the entity container, you should set this to h2 a ("Get the text from the A tag, which resides in a H2 tag, which on its side resides in the entity container");
skip - [type: int or string] | [URL parameter name]: [Comma separated list of values] On these values of the URL parameter the plugin won't process the content.
owner – string. You need to set this, if the order e-mail is set to be sent to the entity owner. Similar to the moo_title, this is a MooTools selector, marking either the user ID or the e-mail of the entity owner.
link – string. You need to set this, if there are more than one entity on the given page, e.g. list of products. Similar to the moo_title, this is a MooTools selector, marking the <a> tag, which contais the link to the entity. If not provided, the URL of the currently viewed page will be put in the order e-mail.
inject - [where] | [anchor selector] | [HTML, containing %s] . You might choose (wisely) not to use the {mailorder} tag, but to point the plugin to a location where you want it to put the "Order now" link for you. This can be done by using the "inject" setting:
[anchor selector] is a MooTools selector, marking the element (within the container), to which the "Order now" link will be attached;
[where] defines the way the "Order now" link will be attached to the anchor, i.e. “after”; Please see http://mootools.net/docs/core/Element/Element#Element:inject for more info.
[HTML, containing %s] is the HTML snippet, which will be attached to the anchor. If not set, it defaults to the link itself. Please use only single quotes! The %s will be replaced with the link itself.
All the "inject" elements must reside on a single row, separated by the pipe character "|".

The CLEAR sections define on which pages the plugin should only remove the {mailorder} tag, if found. Here is an example for the com_content component:

Код
[CLEAR]
view=category
layout=blog
data_in = introtext


Translated: “If the requested page's URL contains view=category and layout=blog, clear the {mailorder} tag from each article's introtext property.”


III. Step by step example.

Lets set up the MailOrder plugin to work with com_component (having FireFox browser with FireBug installed helps a lot). As I tend to simplify my efforts, I won't use the {mailorder} tag and my articles will remain unchanged. I will use the inject settings instead.

We'll do it on a Joomla 2.5 based site with Beez2 site template (the default one).

Here we go:

1. Decide which component you are targeting (com_content);

2. Using a FTP client, create an INI file with the component's name in the /plugins/content/mailorder/config/ directory (com_content.ini). Open it for editing.

3. If needed, at the top of the ini file put your default settings (see the heading sections description):

Код
window_type = modal
window_w = 400
window_h = 750
formtpl = default
buy = 1



4. Decide on which pages you want the “Order now” buttons to appear, e.g.:

- when an user views an article;
- when an user views an entire category, but only if the category is with “list” layout.

When an user views an article, it accesses an URL like (I shortened the article's alias in order to be able to put the URL on a single row):

index.php?option=com_content&view=article&id=2890:abd7...&catid=30&Itemid=601

What are the “run” settings?

view: article
layout: N/A
task: N/A

We have only view presented. Lets start our RUN section:

Код
[RUN]
view = article


Now we must define the required settings moo_container and moo_title. Here FireBug helps a lot. Right-click on the article's title and select “Inspect with FireBug” (if you don't have FireBug, you may do this step by using the browser's source viewer). Find the element, which contains the whole article. In our case this is a <div class="item-page"> element. The article's title is contained within a link in a h2 tag. So we have in our RUN section:

Код
moo_container = div.item-page
moo_title = h2 a (Find H2 within the container, the find A within H2 and get its contents)


Next we must define our “Order now” link (see the inject syntax above). I want it to be positioned directly below the article's title and to look like a button:

[where] : “after” the anchor (http://mootools.net/docs/core/Element/Element#Element:inject)
[anchor selector]: this is the title, so the selector is the same as moo_title – h2 a
[HTML, containing %s]: This the “Order now” link, contained within a div, which is styled to look somewhat like a button (remember – use only single quotes): <br /><div style='background-color:#ffaaaa;padding:7px;border:1px solid black;border-radius:5px;display:inline'>%s</div>. You may define CSS styles, related to the “Order now” link containers, and simply put the %s in such a container, e.g.: <div class='order-now'>%s</div>

The whole line should read:

Код
inject = after | h2 | <br /><div style='background-color:#ffaaaa;padding:7px;border:1px solid black;border-radius:5px;display:inline'>%s</div>


If we want to disable the “Order now” link for certain articles, we need to use the skip setting. The URL parameter, pointing to a certain article, is id and it is an integer. So we should use something like:

Код
skip = int | id: 2889, 2906, 3008, 1756


Put it all together:

Код
[RUN]
view = article
moo_container = div.item-page
moo_title = h2 a
inject = after | h2 | <br /><div style='background-color:#ffaaaa;padding:7px;border:1px solid black;border-radius:5px;display:inline'>%s</div>
skip = int | id: 2889, 2906, 3008, 1756


And the result:







When an user views an entire category in “list” layout, the URL looks like this:

/index.php?option=com_content&view=category&layout=list&id=30&Itemid=601

What are the “run” settings?

view: category
layout: list
task: N/A

Hense:

Код
[RUN]
view = category
layout = list


The articles' links are contained in a table, each article occupies a single row. We are interested only in the row's cell which contains the article's title. Again using firebug, we find those cells to have the “list-title” class assigned to them. The article's title is contained within an A tag in the TD cell. So:

Код
moo_container = td.list-title
moo_title = a


I want the “Order now” link to be positioned after the article's title. As I want only the link to be displayed, there is no need to define a HTML container:

Код
inject = after | a


Here we have more than one entity on the page and using the page's URL is not suitable for us anymore – it points to the entity collection and not the single entity ordered. We must point to the entity's link within the entity container in moo_container. This is easy, as the link is contained in the same A element, holding the entity (article)'s title:

Код
link = a


Put together:

Код
[RUN]
view = category
layout = list
moo_container = td.list-title
moo_title = a
inject = after | a
link = a


As a result we have an “Order now” link for each article on the page:



As we don't use the {mailorder} tag, there is no need to define any CLEAR sections.


If you have Joomla cache enabled (content plugins are not processed) or the component you intend to use the MailOrder plugin with does not invoke content plugins, you need to get the plg_system_plginvoker plugin. It works with INI files in a way, very similar to the described here. Its sole purpose is to invoke certain plugins (it is not restricted to content ones only).
  Forum: Joomla Extensions · Post Preview: #5487 · Replies: 12 · Views: 16,012

Ivan Stamenov
Posted on: Jan 21 2013, 10:51 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


The message should read "processed" instead of "imported" as this number is exactly the number of processed messages (not the imported ones).

Does the message gets actually imported? Is there an article created?

If yes, I will need admin & FTP access to your site in order to investigate what is happening.
  Forum: Joomla Extensions · Post Preview: #5450 · Replies: 15 · Views: 2,563

Ivan Stamenov
Posted on: Jan 21 2013, 07:05 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Our component relies on the pop3 class to connect and retrieve the messages, associated (only) with the account details, provided by you in the PBE entry settings.

In the case I was talking about, using the account credentials for one of the e-mails, the pop3 class was given access to all the e-mail boxes and the messages within them. It has something to do with the e-mail server settings and nothing to do with our component.
  Forum: Joomla Extensions · Post Preview: #5448 · Replies: 15 · Views: 2,563

Ivan Stamenov
Posted on: Jan 21 2013, 06:52 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Hi, domto!

You are absolutely right! It is the /components/com_joomgallery/views/detail/tmpl/default.php file that needs to be altered. I've updated the install guide.

Thank you for your help!
  Forum: Seo Optimization · Post Preview: #5447 · Replies: 6 · Views: 3,541

Ivan Stamenov
Posted on: Jan 18 2013, 08:21 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Hi, strychnine!

Цитат
Any ideas where I should look?


blink.gif My bad...

/includes/modules/microformatsvotes.php, line 169:

Change

Код
<meta itemprop="category" content="'.implode(' &gt; ', $mfv_category).'">'.htmlspecialchars($mfv_product->fields['categories_name']).'" />


into

Код
<meta itemprop="category" content="'.implode(' &gt; ', $mfv_category).'" />
  Forum: Online Shops · Post Preview: #5437 · Replies: 45 · Views: 28,783

Ivan Stamenov
Posted on: Jan 18 2013, 07:03 AM


Advanced User
****

Group: Advanced Member
Posts: 218
Joined: 15-April 11
Member No.: 761


Hello, Knerkin.

In short, yes.

A few months ago we had a similar problem with another user. She had five different e-mail addresses, hosted by a single service provider. Each address has been assigned to a different PBE entry. When importing the PBE entries, the messages in all the e-mail boxes were imported in the first PBE entry's category.

The reason was, that though the e-mail boxes had different names, the mail server of the service provider returned all the messages (in all the boxes) when PBE was importing only the first one.

Best regards,

Ivan
  Forum: Joomla Extensions · Post Preview: #5436 · Replies: 15 · Views: 2,563

9 Pages V   1 2 3 > » 

New Posts  New Replies
No New Posts  No New Replies
Hot topic  Hot Topic (New)
No new  Hot Topic (No New)
Poll  Poll (New)
No new votes  Poll (No New)
Closed  Locked Topic
Moved  Moved Topic
 

RSS Lo-Fi Version Time is now: 22nd September 2018 - 09:30 PM
Clicky Web Analytics