Advertisement:

Author Topic: Plugin problem with 3.0 update  (Read 2522 times)

Sirolist.com

  • Newbie
  • *
  • Posts: 45
  • [Running] - Osclass 3.0.1- Classic Theme
Plugin problem with 3.0 update
« on: July 13, 2012, 06:44:51 am »
I updated to 3.0, (and it's awesome!) Only problem i found so far is when i hover over the plugin manager in the admin panel, i have so many plugins they go out of the screen on the top and bottom. I can't scroll up or down to see them all. Another thing i noticed was the sip bits of code in the help areas aren't there anymore, so we can't ad plugins needing code to work right. Not sure if i'm missing something or not. Anyway. Any help would be cool. Thanks! And great job with the 3.0. i love it. I also switched to the US map theme. It working great.
« Last Edit: July 13, 2012, 06:48:21 am by sirobone »

garciademarina

  • Administrator
  • Hero Member
  • *****
  • Posts: 974
Re: Plugin problem with 3.0 update
« Reply #1 on: July 13, 2012, 01:25:20 pm »
Hi,

Since now, plugins can add menu&submenu sections to admin menu easily, future updates of plugins, menus can be placed where developer choose.

Quote
Another thing i noticed was the sip bits of code in the help areas aren't there anymore, so we can't ad plugins needing code to work right.

I don't understand what you say, can you explain me more?

Regards, I'm glad you like version 3.0

Sirolist.com

  • Newbie
  • *
  • Posts: 45
  • [Running] - Osclass 3.0.1- Classic Theme
Re: Plugin problem with 3.0 update
« Reply #2 on: July 13, 2012, 05:32:26 pm »
Okay, and what i mean about the snip bits of code was, when we get some plugins, we have to have a little bit of code to put where we want the plugin. I found some of the plugins codes pieces are still there, But like for the paypal plus plugin i can't find what code i'd need to put where i need it. I tried using the same code from the first paypal plugin i had. But its not seeming to work. I hope i'm not confusing. Once i learn terms better i'll probably start making sense. :)

Sirolist.com

  • Newbie
  • *
  • Posts: 45
  • [Running] - Osclass 3.0.1- Classic Theme
Re: Plugin problem with 3.0 update
« Reply #3 on: July 13, 2012, 05:41:38 pm »
Hi,

Since now, plugins can add menu&submenu sections to admin menu easily, future updates of plugins, menus can be placed where developer choose.

Is there a link showing how to do that? Making menus and sub menus? Or move around the plugins? Because right now i can't see half of them. Thanks! Sorry if these are stupid questions. 

Juan Ramón

  • Osclass Developer
  • Hero Member
  • *****
  • Posts: 2382
Re: Plugin problem with 3.0 update
« Reply #4 on: July 13, 2012, 07:55:53 pm »
You can find the documentation here: http://doc.osclass.org/Administrator_Menus

garciademarina

  • Administrator
  • Hero Member
  • *****
  • Posts: 974
Re: Plugin problem with 3.0 update
« Reply #5 on: July 13, 2012, 08:14:08 pm »
Hi,

Ok, some plugins needs to add some snippet of code inside file templates, the plugin help should have instructions if is needed.

For your paypal issues, try to search paypal issues on this forum.

Regards

Sirolist.com

  • Newbie
  • *
  • Posts: 45
  • [Running] - Osclass 3.0.1- Classic Theme
Re: Plugin problem with 3.0 update
« Reply #6 on: July 14, 2012, 12:45:53 am »
Okay, Thanks! Sorry for the newb questions. Just trying to get my site going right. It's all new to me. The php/coding part. So trying to get a grip on it. Anyway, thanks again.

Gigo

  • Newbie
  • *
  • Posts: 3
Re: Plugin problem with 3.0 update
« Reply #7 on: August 25, 2012, 01:38:40 am »
Hi,
Great plugin. Thx. I found that when you display items (file helper.php), you take value direct from field from table for this two variable (e_type and e_status), so they always in english. So I make small changes in your function get_realestate_attributes() in helper.php.
Code: [Select]
    if(@$detail['e_type'] != "") {
        // Igor added for displaying on all languages - start
        if(@$detail['e_type'] == 'FOR RENT') { $e_type='For rent'; }
        if(@$detail['e_type'] == 'FOR SALE') { $e_type='For sale'; }
        // Igor added for displaying on all languages - end
        $return['attributes']['type'] = array(
                 'label' =>__('Type', 'realestate_attributes')
                // Igor changed for displaying on all languages - start
                //,'value' => @$detail['e_type']
                ,'value' =>__($e_type, 'realestate_attributes')
                // Igor changed for displaying on all languages - end
            );
    }

and

Code: [Select]
    if(@$detail['e_status'] != "") {
        // Igor added for displaying on all languages - start
        if(@$detail['e_status'] == 'NEW CONSTRUCTION') { $e_status='New construction'; }
        if(@$detail['e_status'] == 'TO RENOVATE') { $e_status='To renovate'; }
        if(@$detail['e_status'] == 'GOOD CONDITION') { $e_status='Good condition'; }
        // Igor added for displaying on all languages - end
        $return['attributes']['status'] = array(
                 'label' =>__('Status', 'realestate_attributes')
                // Igor changed for displaying on all languages - start
                //,'value' => @$detail['e_status']
                ,'value' =>__($e_status, 'realestate_attributes')
                // Igor changed for displaying on all languages - end
            );
    }

Because that is static value, now it use language file to translate it to other languages.
Best regards

joseisaldana

  • Newbie
  • *
  • Posts: 9
Re: Plugin problem with 3.0 update
« Reply #8 on: December 26, 2012, 02:16:22 am »
Hi,
Great plugin. Thx. I found that when you display items (file helper.php), you take value direct from field from table for this two variable (e_type and e_status), so they always in english. So I make small changes in your function get_realestate_attributes() in helper.php.
Code: [Select]
    if(@$detail['e_type'] != "") {
        // Igor added for displaying on all languages - start
        if(@$detail['e_type'] == 'FOR RENT') { $e_type='For rent'; }
        if(@$detail['e_type'] == 'FOR SALE') { $e_type='For sale'; }
        // Igor added for displaying on all languages - end
        $return['attributes']['type'] = array(
                 'label' =>__('Type', 'realestate_attributes')
                // Igor changed for displaying on all languages - start
                //,'value' => @$detail['e_type']
                ,'value' =>__($e_type, 'realestate_attributes')
                // Igor changed for displaying on all languages - end
            );
    }

and

Code: [Select]
    if(@$detail['e_status'] != "") {
        // Igor added for displaying on all languages - start
        if(@$detail['e_status'] == 'NEW CONSTRUCTION') { $e_status='New construction'; }
        if(@$detail['e_status'] == 'TO RENOVATE') { $e_status='To renovate'; }
        if(@$detail['e_status'] == 'GOOD CONDITION') { $e_status='Good condition'; }
        // Igor added for displaying on all languages - end
        $return['attributes']['status'] = array(
                 'label' =>__('Status', 'realestate_attributes')
                // Igor changed for displaying on all languages - start
                //,'value' => @$detail['e_status']
                ,'value' =>__($e_status, 'realestate_attributes')
                // Igor changed for displaying on all languages - end
            );
    }

Because that is static value, now it use language file to translate it to other languages.
Best regards


thanks, was helpful