I read, the phloor framework was abandoned.

When I upgrade from php 5.2 to php 5.3 and elgg 1.8.4 to elgg 1.8.13, then phloor menuitem produces heavy errors.

Someone else with this problem? What do I wrong?

@xsurf this "framework" causes too much problems than it can fix. like the developer said, move on.

Ok, thanks. But to quit phloor-menuitem is a real loss...

Anyone would like to make work phloor_menuitem work with elgg 1.8.13 :)

I think, many people need this... :/

@13net

What do you think about my question?

Would you please think about to make a version that works without your abandoned framework and that works with elgg 1.8.13 ? I think for you as the developer of this plugin it could be much easier to manage this, as for someone else. Many people would much appreciate this, I think.

There is someone told me per pn tried this, but could not manage.

Replacement for phloor_menuitem:

1) Menu Builder, Cold Trick for page

2) http://elgghacks.com/full-edit-sidebar/comment-page-1/#comment-12471 (for topbar & sidebar)

Need some effort, but works.

hmm just noticed in the screenshots 1 small feature i had missed before, this thangz need rescuing seriously; soo.. a littlle analysis of the frmwrk >. dinner ;oO and then we surf thru to to kiss up @ code..

And thanks again to pianist (elgg hacks) and to rvr for helping to can build a topbar & sidebar dropdown menu.

How about you both quit with the bickering before you make people with ban-power get involved.  I haven't been following along enough to know who did what, and I don't much care.  Civility is what matters, whoever thinks they're in the right - just let it go.  I don't want to see any further name calling or swearing, or banning will result.

@Matt Beckett: Yes, thanks.

One thing I want to say:

@13net: this plugin was one of the relevantest plugins and it is a real loss for much people which used it, and with elgg 1.8.13 now can't use anymore. There are a lot of people that can or want not play  with code (because they fear to make wrong). They miss this plugin.

There is a coder here, who some days ago wrote me in a message that he already tried, but could not manage to make your menuitem plugin work without your framework.

I'm not asking for me, cause you will understand that I found a working solution for the loss of phloor_menuitem, wich need some effort with code (I told this in former comment), but I managed this. It works without problems, it fills my needs.

So I'am asking you not for me, but for all people using phloor_menuitem.

I have not much money, but in this case I would give some money if it helps, because I sympathize with the people that can not or want not to code, and that with elgg 1.8.13 now have a huge loss to not can use phloor_menuitem anymore.

@xsurf It is not about money. The problem is the complexity (or mess) of the Phloor framework. There are some plugins that required the Phloor framework that I wanted to make framework-less but was not successful. This is a lesson here, about why 'frameworks' are not useful.

@costakisc Thanks for the PM, I would like to make some really useful News Plugin. Let's make it happen! I have the whole week booked but I will have some time during the weekend. I support your effort as a developer.

@xsurf @costakisc As a good will thing, I would like to ask you two to remove the comments posted here in the plugin page and in the other plugin page. Why? No, not because I want to 'hide' something, but because to keep the elgg community reputation clean and clear. I think we all can work together and hang out together. No need for fighting. Let's have a cup of coffee and dream on.

@all I'm gonna eat a subway.

@rjc

Ok, I will do this, after costakisc and DhrupDeScoop did this.

@xsurf if this plugin is important, put the code on github and start a discussion in Plugin Dev on how to fix it. Start by posting what error messages you get. No one owes you free work, but devs will offer help if you show you're willing to put in your time and do what you can, and are grateful.

Re: Phloor, on this site we criticize code constructively and respectfully. People pour hours of work into creating things and just give them away. It's that spirit that encourage all other plugin devs to do the same. There's nothing wrong with library plugins, though with autoloading this is less necessary: even if you use a class in 3 plugins only one will be loaded.

BTW some of you owe 13net an apology for having this little war on his plugin page. If he would like me to delete this mess I may be willing to do so.

Steve Clay 7 minutes ago

@xsurf if this plugin is important, put the code on github and start a discussion in Plugin Dev on how to fix it. Start by posting what error messages you get. No one owes you free work, but devs will offer help if you show you're willing to put in your time and do what you can, and are grateful.

If you had read this whole thread, you did know that I already did what I could, yet.

Thanks for the hint.

BTW some of you owe 13net an apology for having this little war on his plugin page. If he would like me to delete this mess I may be willing to do so.

That's ok, too.

Thanks.