Many plugins not working with Osclass 3.3.2

[SmaRTeY]

Just try to keep it simple... yet effective   

[tomshaft]

I believe in K.I.S.S OR in other words keep it so even I can understand it and that IS asking a lot.

I'll tell an important reason for my suggestion. It would help take the pressures and complaints off the core devs. They do a fantastic job but many seem to think Dev's somehow have 30 hours in a day and can't understand why their/Our little problem is not at the very top of the dev's list. Things like that. If someone does not like the pace that a "fix" is going they/we can do something about it like JOIN the apropriate team and contribute instead of complain.

Tom

[kristian9]

Specific plugin errors for me:

realestate attributes plugin (Version:3.2.5) - problem with search in 3.3.2 (Bender)

Have to activate: "Show only specified filters" to show up in search page

When i activate search-sidebar and search for specific things in an realestate ad there is no result.

------------

3.3.2 Bender: Social bookmark plugin (Version:1.1.1), when activated, fancybox dont' work in IE 11 (OK in Chrome, Firefox...)

[Aficionado]

This is a very complicated way. Information is hard to be followed.

[kristian9]

Example:  I have made an realestate ad which include "heating" (picture one)

When I do a search for "heating" an hit "apply" (picture two), I get no result.

This is working in version 3.2.2, not in 3.3.2  (in my case)

[tomshaft]

Anything done along these lines must be done separate from this forum.
A team working on their project must stay focused without the distractions of a public forum.

Tom

[teseo]

Hi,

Agreed, some separated space is much needed to work calmly, this is too anarchic.  An opportunity like that thread recently opened by _CONEJO to try and address the apparent problem of communication with core devs becomes a discussion on SEO matters,  and this, having this title, is like a open invitation for all kind of complaints about this or that specific plugin.

But as the problem seems to be precisely lack of time on the core devs side, I think the best course of action is we non-core devs should organize ourselves on our own, for instance creating an external forum where only devs (core and non-core) are invited to participate.

Regards

[SmaRTeY]

I agree, the SEO part (which I ofcourse could not resist) IS breaking focus on things that need to be done first. Actually I think the 'damage' is really not that bad and with some joined effort and a structure easy to follow I am pretty sure things can be updated pretty fast, maybe faster than we think.

I also think there's a need for maybe a pw thread for those joining a community team for the soul purpose of updating code of themes/plugin one step at a time. OsClass dev team can do a review and we can use some testers who test according to some kind of test script, nothing special but just an easy overview of things to test like a checklist.

_CONEJO already mentioned WHAT bug info should be delivered making is easier to duplicate and fix.

Here's my thoughts on process, open for all suggestions and remarks:
0) baseline = OsClass 3.3.2.
1) create a fix list based on new test done by 4-eyes, 1 browser-set.
2) prioritise

• Themes: Bender -> Others
• Plugins: official -> un-official

3) work in pairs, fix & test
4 )final review & update downloads by dev team? (either official or unofficial components)
5) next item on the 'fix list'

Rule#1
NO additions, just making sure the theme/plugin works OOB 100% with OSC 3.3.2
Rule#2
Community team needs ONE (available) contact within dev team that is able to help answering questions or explain things if needed.
Rule#3
Commitment to get quality result 

[tomshaft]

Teseo,
Exactly. I set up the SMF as an example. Maybe it should be hosted by the core devs but that as the idea. See one of my posts in this thread back a few.... If it is not a closed to public system nothing wlil get done.

Tom

[tomshaft]

If core dev's agree then maybe each or a pair within a team work as Smrtkey stated - On one item. Check for quality/Fix, then move one to another item within that teams focus. If as example the theme team has 6 members that would be 3 themes being worked on at any given time. Same for plugins. As for core testers that falls more under core dev team to assign chores.
Honestly SEO maybe should also be something under core devs. If they want a dedicated team fine.

I have nothing to contribute myself but thoughts I have when thinking other thoughts and those thoughts are from a man with little brain to think.... I just hate to see the complains about what is and will be a very fine script.

Tom

[s51]

.
Hi Osclass friends ...

1.)
@Eric write
>>Rule#1
>>NO additions, just making sure the theme/plugin works OOB 100% with OSC 3.3.2
This is the pure (and correct) testing form, - and I,ll support it 100%   
- -


2.)
I just bought the name Osclass for my country, * NOTE READ CAREFULLY LATER * what I do with the name
and also bought a reasonable fast server space for it (same server-provider where I know Osclass run perfect)
.
Medio-Late next week, I have put a completely raw Osclass 3.3.2 up - with the build in bender
Then I set up five FTP entries - and five Admin entries - to a start - if more needed - we raise OKAY
-
And then we start serious testing, in the hope of:
#1 Get a flawless running osclass
#2 Get a flawless running bender & modern theme
#3 Get a flawless basics language translation
#4 Get a flawless running of the 5 most used plugins (urghhh har to decide)
-
This must be the minimum requirement to start a serious testing association group 
- -

3.) *
If some of you good Osclass friend wants to help with the above,
please drop me a PM - and then we'll take it from there. - OKAY.
- -

4.)
Concerning the name: Osclass
As long as the domain is being used for test purposes, - who ,,only-help,, Osclass - I,ll pay,
if there is no longer need for it - I accrue rights automatically goes to Osclass in Spain (the Team)   
- -


Regards.:/ s51
.

[SmaRTeY]

If we can get this up and runnign and people are commited and have some time things can go really fast and be a lot of fun seeing the system get better and just something to look at with a smile.... 

[tomshaft]

I feel strongly all decisions to be left to the core devs.
If this is to happen, where, when, team leaders, etc.

[SmaRTeY]

Hi S51,

that is as far as I am concerned a very nice gesture and constructive way to start! 

I think number 1 is focus on theme(s) including language / CSS and define a browser set/versions for which to guarantee success.
(including the much hated IE) hehe

Let's do an official "WHO IS IN" ? to see what persons here are willing to put time in this?

And imo every 'group' (2 or more) should have at least 1 person who really knows PHP/js coding.

[design]

you describe the purpose of github--except github is open to more developers that happen by. I figured out github, you guys can!

perhaps it's best we have a closed forum here for "us" so we can speak more frankly about what we are seeing in these forums.

from my observations-only being here since OCT, is that what we fix issues by ourselves and they are not being implemented into the core and core theme so the frustration of not having it fixed promptly is ____ to everyone.

--- for instance, I just uploaded a new install and the header/search has not been fixed yet - wth?! the core now has an auto update- why are we not using it?

point is...
will these fixes ever get fixed regardless where we test it -github or otherwise?