SocialEngine Blog

SocialEngine PHP 4.2.9p1 Patch Released

Hey SE PHP site builders – we’ve just released a new patch that should fix the issues you’ve reported with the last release of SE PHP.  You can grab it from your client dashboard. Issues fixed in the patch:

  • IE commenting bug where you could not comment when using IE 8 or greater
  • Ordering of comments were wrong when viewing item pages
  • Announcements not showing up correctly
  • CSS breaking when in development mode for some themes (including default theme in a fresh install)
  • Two untranslated language phrases
  • Page validation errors caused by “parent_content_id” set to “0″ on some server configs.
  • Exceptions caused by $address being an empty string on some server configs.

As always, please make a *complete* backup of your site before you upgrade and be sure you know how to restore your backup. Avoid upgrading your site while it’s live – either take it down temporarily for maintenance or upgrade during inactive hours. We are continuously seeing SE PHP site builders run into problems when they don’t upgrade properly and their users are left hanging. Please plan ahead if you have an active site!

We know there’s more to improve in SE PHP. Please let us know in the comments if we’ve missed any bugs in this release and we’ll start hacking at them right away. If you are dealing with bugs, please be absolutely sure they are in the original SocialEngine codebase and not caused by third-party addons, or interactions between third-party addons. The majority of issues reported are being caused by these addons, so again, definitely check to make sure that the bug is originating from the original codebase, and we’ll get on it!

 

  • Ryan Olson

    Alex,

    I really wish you would not have closed the comments. I think it was a forum of people ACTUALLY being responsive to you and you need to hear responses to your comments. You sit here and tell us that self hosting is dying. OK, maybe for the mom and pop shops, but what of us who invested a LOT of money into dedicated hardware? Currently, I run a male-only adult fetish site with over 10,000 active members. I have a dedicated Nginx web server, a dedicated Percona MySQL Database Server, a Dedicated Memcached Server, and 2 other servers for Flash Media and Webcam chat. THEN I have a dedicated development box.

    The point I am trying to make is this. When I started my site I talked to you and Char about 2 years ago when 3.x was out. You both told me you were excited by your 4.x product coming out. You showed me the demo and I was so impressed with your work that I invested into your product. I have then invested in custom development and your supported developers (Hire-Experts, Radcodes, SocialEngineExperts).

    Then when something hits the fan I come to your developers for help. I am ignored for 2 days and then finally get a response that the problem is Hire-Experts. I go to them and talk to them about the situation and they say, thats impossible because you approve their plugins. So I call your company and get a male support engineer at your company who RIPS ME APART saying I pay 50$ for support what do I expect to get. I offer him a HELL OF A LOT MORE MONEY and he says “I wish more people were like you”.

    The point I am making is this… Your product has a HUGE base of users. Your cloud product does not work for adult sites for a MULTITUDE of reasons, and the 3rd party development of it is limited at best. Your flagship product is what you and Char both knew what the move in the industry and you used to rival phpfox and other CMS apps out there. Now, you are left in the dust with a crap load of customers who are upset, angry, and even downright pissed off (FYI I am pissed off). All we are asking you to do is clean up the problems, give us an API so some of us can have a reasonable time creating mobile apps cause the ones out there now are garbage, and most importantly, take care of us. Again, if money is the issue, I must tell you that other companies charge yearly support fees… guess what, I am more than happy to pay for it if it means you will get back to the product that made your company.

    I have to admit one other thing on a personal note. It is nice to see YOU are posting on the blog and not Jasper. He was not good for your company and he was not helpful in making your customers feel wanted. If you do not want to make PHP anymore. Tell us and help us move to another platform. Just come out and tell us you are done with it and create a FULL migration tool for PHPFox or something else that we can all move to and leave you behind. If you want us as customers and want us to actually pay up for what we want, tell us. All we want is what we have been asking for since day 1 of 4.x and for you to stop releasing sub-par updates that leave us with more problems. And in case you have not noticed…. PEOPLE AGREE WITH ME!

    • kelvin

      I Agree with you 1000000000% …. Tell them. They are only listening but not hearing. Maybe they will hear this time.

      • freddy24

        They are not listening… They are making this up as they go along. When CLOUD came out, they gave us all sorts of promises… “yes. sephp is still our priority…”, “yes. we’ve got exciting plans for the future of sephp…” “blah, blah, blah…”

        Now we get a blog post. Self-managed communities are dead. WTF?

        This spells the dead of sephp!

        JUST GIVE US A FULL EXPORT SCRIPT FOR PHPFOX SO WE CAN GET THE HELL OUT OF THIS PLACE AND RID OURSELVES OF THIS CRAP SOFTWARE!!!!

        • Nick Swartz

          I don’t think It’s bad software, It’s better than most in my opinion because you have more options and developers, I don’t care for API much that should be done after all bugs are dead, I hear there are a lot more bugs to kill. Time will tell! Maybe Cloud will bring more resources, I’m sure they could find more support representatives who know code well.

        • http://twitter.com/ashcross Ash Cross

          This really isn’t bad software. I think, actually, that SocialEngine suffers from a bad community who often don’t have the skills to work around problems. It’s been hard work, but my site generally runs smoothly and is very responsive, running on just 2 clouds servers: a web app and a database one. Having said that, I do question the fact that we have to pay to get support about problems *caused* by SocialEngine, which should work out of the box. I think some of the features have been almost forgotten, with few advances across video, forum and group plugins, for example. We need more payment gateways beyond PayPal and options for HTML5 (non-Flash) video. Migrating to better technology in some areas, like a better JavaScript framework, might also give the software a bit of fresh life behind the scenes. However, in general, SocialEngine is solid software and the criticisms are, even by the standards of online commenting, some of the most disproportionate that I’ve ever had the misfortune to read. SocialEngine won’t have the resources of Google, so give them a break. Webligo, for your part, engage with the community better, treat bugs and usability with particular attention, and start evolving existing features such as video and billing. For a start, get JIRA to handle issues and bugs and let the community submit these bugs so they can see progress on them. These comments sections aren’t good for tracking progress and people think you’re not progressing. Be more transparent.

          • es7

            I agree. Software isn’t that bad as it may sound from comments.

            In along term it might be a good idea to think about jquery and zend framework 2. But such things will require serious amount of resources.

            If you are looking for non-flash video check our plugin Media Projects http://webhive.com.ua/store/product.php?id_product=43

            We have option to keep mp4 version of videos for iOS devices. Also support for different video formats is wider than in default video plugin.

    • Chinmoy

      Well, I’ve sent them two tweets with general pre-sell questions and they ignored both!!

    • Zach

      They need to hear us…………we should have our own place to network between us SE PHP site owners to share knowledge and help each other out!

  • sebas77

    Good patch, I am willing to help you reporting several bugs, but my comments do not pass the moderation

  • http://www.paleoresources.com/ Julien

    Well, I am actually satisfied with the directions you have posted in the blog post where the comments are now closed.

    It seems clear that:

    1) you don’t have much resources in the company at all

    2) you have made the choice to prioritize Cloud versus PHP

    So there seems to be 2 paths forward:

    1) the old one, where you overpromise, try to deliver new features, and end up delivering buggy updates with not much new features

    2) the one you have chosen, where you are clear you won’t add features, but will focus on cleaning the code base and fixing the many remaining bugs

    The first path was never going to work, no matter what people want to believe, you just don’t have the resources to do it properly.

    With this second, things could actually work out ok if you do a good job to optimize the codebase, and leave it to the third-party devs to add features. They do it well right now!

    Setting such a goal is much more realistic, and gives me a bit more confidence that you will actually hit it.

    Doing a proper realease announcement for a patch version is also much better, compared to having to hunt in the comments when you release a patch :-)

    So, all in all, I think you made the right choice, and am more confident on such a roadmap.

    For all other customers: please stop whining endlessly. The situation sucks, no doubt about it, but I much prefer this path forward to the other obvious alternative which is to leave the product die proper. For x number of reasons, they don’t have much resources to dedicate to SE PHP. Sucks, but that’s the situation today. If we continue to just be negative and ask for features, it’s just useless. And at this point, I actually prefer to have the features implemented by third-party devs who are doing a great job at supporting their customers.

    And for what it’s worth, I also had a good look at PHPfox, but it’s still an inferior product in terms of add-ons and flexibility, at least for my needs. So for me, a migration to PHPfox is just not option, so I disagree 100% to those who say they would like a migration tool!

  • http://www.facebook.com/profile.php?id=787175036 Kev Gahan

    i geting this error when i go into themes and seam have lots all custom settings

    Parse error: syntax error, unexpected T_RETURN in /home//public_html/application/themes/grid-gray/manifest.php on line 1

    • Jazzman

      I’ve had this error and I am on version 4.2.7. I haven’t made any changes to the core, it just happens.

      • http://www.facebook.com/profile.php?id=787175036 Kev Gahan

        i fixed the issue by copying the old application/themes/ back into the dir, just them files from
        4.2.9 so far it works with no issue

  • http://twitter.com/BeckieCannons Beckie Cannons

    Hi All,

    I too have invested quite some money into SE4 – not including all my personal time too. Thank-fully I don’t need to make money or need see an ROI from my ‘hobby’ in supporting my community. But the SE situation is really frustrating and makes me angry.

    I love cloud – I think it will be the way forward. But how can I have any confidence in a providers’ cloud infrastructure and service that has a moving strategy and also doesn’t deliver stable releases to existing non-cloud customers? Why would I risk moving into this cloud platform?

    Right now, I’m dependent on my own skills (limited as they are) and a “watch and wait” approach on when to upgrade (currently on 4.2.7 or was it 4.2.6). This is also risky, but I know the risks.

    I’m happy(ish) where I am right now with SE (it would be no better with phpFox and the others) – but I can’t see the future with SE and my confidence is low. I get the resource issues, I get SE are not FB/Google etc. and people have to make money – but there must be a business model that works better than this – as people are not happy, new customers will not be gained, and existing customers will migrate away over the coming months/years.

    I want to love you again SE – please help me love you!

    Beckie

  • http://twitter.com/WebHiveTeam WebHive Team

    Guys, thanks for a long-awaited patch and attention to SE PHP.
    I can’t agree that demand for self-hosted community software is declining. Check out trends
    http://www.google.com/trends/explore#q=socialengine,%20phpfox,%20buddypress
    Declining started for SocialEngine when you stopped active development of SE PHP, announced SE Cloud and released it.

    That’s pretty sad, because SocialEngine 4 is still way better than competitors. Give it nice support and push it ahead – demand will show up.

    Currently there are few issues. I will try to provide very constructive feedback, and list possible solutions as well:

    1. Bugs in SocialEngine, bug reporting
    A lot of people complain about the same bugs and list them on your blog and on socialenginecamp.com. Some are fixed in fast patches (but SE released as the same version) and some aren’t.

    How to solve: Let them track what was fixed and report new issues. Any simple reporting system for clients and developers only. Kick people out for non-constructive stuff and feature requests. Leave bug reports only.

    2. 3rd party plugins (speed)
    I have never seen a recommendation to pick plugins carefully or not to install more than 10 plugins. When we check our support tickets sometimes we see more than 30 plugins installed – that is a complete overkill.

    How to solve: Make an article with recommendations on choosing plugins, review some fast plugins and feature them for free, ask developers to include server requirements for each plugin.

    3. Performance
    You still recommend arvixe hosting for new customers. They either put people on a shared hosting or on VPS that’s not optimized for SocialEngine completely
    http://community.socialengine.com/post/14133/why-arvixe-is-a-recommended-hosting-for-sephp
    As a result a half of your clients try them and think SE itself is slow.

    How to solve: Make more specific recommendations. For example, community up to 1000 members, no video or chat – 1 GB VPS from linode (APC settings, mysql settings, apache settings), or community up to 10K members with video processing – other solution. You can even make special pre-set Amazon linux distro settings. It won’t be perfect setup for everyone, but a perfect starting point. Or contact hosting company that can do it, so you can recommend them.

    How about making better caching functionality that will make static versions for most popular pages (ex. home) and will update those pages based on settings? Something like “quick cache” or “super cache” plugins for WordPress. 3rd party developers will start to use it as well.

    4. Improvements.
    Yes, there may be compatibility issues with 3rd party plugins if you change the core.

    How to solve: I’m answering as a 3rd party developer. Let us know what’s planned and give us early access so we can upgrade our plugins. We will do the rest.

    Notice, I have not mentioned neither API nor some mindless AJAX functionality. Only basic things for the core and the infrastructure.

    You did a really great work with SE4! It’s a nice mature platform, proven in production. Invest a bit more time into it. Most of points I’ve mentioned won’t require a lot of resources but will pay off and resolve current situation.

    Eugene (WebHive team)

    • http://setweaks.com/ seTweaks

      Great post Eugene! We don’t see such constructive comments here.

    • sebas77

      WebHive team, the real problem about 3rd party plugin is the core part. It is enough to install 3-4 different plugins from different companies that the js will explode! The js code is usually not even minified…

    • http://www.hire-experts.com/ Hire-Experts Team

      Thanks Eugene! Great suggestions and we fully agree with you.

    • Dan

      Good to see 3rd party Dev teams are stepping to the plate to, and of course, you guys need to protect your business also.

      I’m looking forward to a reply from the SE Team, lets have this discussion right here right now before it’s fading away….

      Lets put our heads together
      Where do we start, what’s the plan?
      What bug tracking system is suitable to use and who takes the lead for this?
      And how do we keep track and follow up new issues?

    • sebas77

      Error tracking is something I have been asking for ages! I now evolved the request in moving the entire code to an open source platform. For me, the only solution.

    • sebas77

      About the optimization, we optimized some very heavy queries, we use apc cache and we enabled mod_pagespeed…now SE is blazing fast on a crap (shared) machine (however we have not many users, but the difference compared to the original SE speed was amazing)

  • http://www.facebook.com/drago.duller Drago Duller

    Eugene has brought up an interesting point. It could be that “SE’s” self-hosted communities numbers have declined due to the growing complaints from existing users regarding their experience with the platform. In my humble opinion the blog link in your header, which is maybe 75%
    complaints from disgruntled SEphp owners, could be a contributing factor. Marketing has changed dramatically with social media. Your product is not what YOU say it is anymore, it’s what the PEOPLE say it is. I do not agree with the users who are constantly bashing you looking for free modifications they’ve deemed “necessary” in the form of updates. Updates should consist of bug fixing and core improvements. If you want special features, do it yourself or hire someone. Adding trivial features instead of squashing bugs just doesn’t make sense. I am an SE license holder and I too have invested thousands with 3rd party plugins. I am interested to see how you approach this delicate matter and will stand behind you (not in front of you with the bashers) to see how it unfolds. One last thing, Don’t forget to up vote if you still believe in SE . Down vote if you’re a weenie. :)

    • sebas77

      yeah that’s by sure..I know people that chose PhpFox over SE just reading these comments

  • Chinmoy

    In the previous blogpost, you promised to talk about SE PHP API. I can’t find the word API in this blogpost.

    To everyone: SE PHP seems to be dead as meat. Looks like they are abandoning it slowly. I’m guessing their investors are forcing them for this move as the hip-word ‘Cloud’ brings more money.

  • http://twitter.com/sandyvolunteer In The Wake Of Sandy

    Lots of positive comments here, I woke up feeling the same way as some of these people here in that, bug fixes and solidifying an existing project is a lot better than promising E-MC2 and other great new developments monthly, that would drive anyone insane. I have multiple projects going and people rely on me to make massive leaps and ‘change’ in what ‘is’. When you have more than one thing going and a small visionary team it can be easy to get lost in it. I’m glad you all are taking a stance, an honest stance with yourselves, it’s something I’ve personally had to do many times in life in order to make slow and steady yet solid progress – Danny

  • Jazzman

    Hi SE,

    I usually don’t post much here unless I have something constructive to say because I don’t believe in bashing. But I must say your approach to this whole company restructuring is a bit unsettling for most of us and no, I’m not angry.

    I do understand that companies must continue making products or services in order to stay afloat. Believe me, I have a business background, so I completely understand the reason for Cloud. But at the same time, leaving your existing customers in the dust may actually hurt you in the long run.

    Now, it may be that you are working on solidifying SE PHP but so far that’s kind of up in the air, so it leaves us wondering what we should do. I personally do not believe in hoping from one platform to the next, to the next. I’ve tried them all and I decided to stick with yours.

    Like other Webmasters here, I have spent thousands on third-party plugins and I am also developing my own plugins (in fact, I don’t even have a site yet). So logic would tell you that someone doesn’t spend thousands on a project to then put it on a VPS. So many of us DO have a vested interest in the success of this platform, for some of us is not just a little hobby that we play with (no pun intended to anyone). Also, your developers, then ones that make your software shiner, are simply left in limbo because they have no idea what you’ll do next.

    The only thing that I would personally ask is that you truly make an effort in getting the core rock solid so we can actually have a platform that we can “stand” on and rely upon. Instead of coming up with features that are already developed by third parties, you should concentrate on the part you can actually control, the core.

    Once that happens, third-party developers can still continue creating plugins and expanding from there. But they can’t really do this right now if the core they work with is broken, it would be like adding a new coat of paint to a car which engine is leaking, makes no sense.

    Also, this mentality that self-hosted communities are declining is a bit inaccurate to say the least. It is not that they are declining, is the fact that most people are so disgruntled at your software/company that they decide to go somewhere else. Do you truly believe that a new potential customer that reads all these comments will decide to purchase from your company, Cloud or PHP? I wouldn’t. True or not, reviews do matter to people when deciding on a product (blog comments are reviews). It is a matter of customer retention and sadly to say, you are not doing much in that department.

    Fix the core, and if you do decide to sunset PHP, then go out with a bang, at your highest, instead of your lowest.

    Not a sermon or a lecture, just a thought on where many of us are coming from. Try to put yourself in our shoes for a moment and let us know how you would feel.

    Thanks.

  • skidpics

    Can we get the social connect added to the signup page or as a widget there? It’s not really apparent to connect with the services, even for signup..

  • skidpics

    DEV mode still strips theme CSS

  • http://twitter.com/ashcross Ash Cross

    It’s obvious what should happen. Make SocialEngine open source and let the community take over. Webligo can remain in place as corporate steward and brand owner. Then people can buy a license to receive premium support from Webligo or buy the hosted version in the cloud. Or even have an open source and a premium version of the SocialEngine self-hosted software.

  • Molecular

    Hello SE team I wish you all a very happy new year. I hope you are taking good notes this year. It is imperative that you listen to the needs of your customers. Please slow down and take a moment to re-prioritize what is necessary. You have a great platform; do not abandon it; developing is crucial. We are still looking forward features within the core like API, ability to capture a profile picture with a web cam and many more. Here is an excerpt from your blogs which we are still waiting for ”

    Search Overhaul – Updates include making custom pages searchable, adding search to the forum area, creating search functionality on the browse groups page, developing a global search widget, and making plugin search widgets customizable.

    Improved Messaging – Improvements will feature a popup window to compose messages rather than a new page, the ability for announcements to target specific users, the ability to resend confirmation emails, and options for the admin to send messages to all members in a specific Network, Profile Type, or Member Level”.

  • Pencho

    During the upgrade process in admin area from 4.2.9 —-> 4.2.9p1,

    socialengine4.2.9p1.tar……Extract ……….. error: No packages found in archive

    what’s that … it’s not possible to upgrade

  • bryce

    hello, after doing my update I 4.2.9p1 meetings always a problem with the basic themes that offer I receive this error message when I click on it, you have a solution?

    cordially

    Bryce

    Parse error: syntax error, unexpected T_RETURN in /home/brycesas/public_html/pays-de-fayence.com/application/themes/quantum-green/manifest.php on line 2

  • http://twitter.com/sebify Sebastiano Mandalà

    visibility test, please ignore

  • http://www.facebook.com/profile.php?id=787175036 Kev Gahan

    i fixed the issue by copying the old application/themes/ back into the dir, just them files from
    4.2.9 so far it works with no issue

    • bryce

      hello and thank you for your reply but I do not understand, is there a fix or should I download copy a change in my code?? because on my site it still does not work?

      Cordially.
      Bryce

      2013/1/16 Disqus

  • sebas77

    Yes SocialEngine Open source! I said that many times already…but it looks like SE does not like to hear it

  • Stepan

    wow I expected about 30 new features and what you posted here should be “point #31 – small bug fixes”.

  • sebas77

    Hi,

    since you asked for it I want to start to share the list of bugs that I am pretty sure are related to SE code, however I cannot now prove it since I cannot test the socialengine demo platform anymore.
    Most of the bugs are currently related to the Events Plugin, the following bugs are the ones that we are experiencing right now:
    - If we limit the visibility options of whatever event field to one choice only, when the user creates a new event, the user will not be able to choose any option for that specific field. This is fair, but the system will choose a random value instead of the one selected in the admin panel
    - A discussion created in an event cannot be modified (this could be a tinymce integration issue)
    - The event discussion feeds are created on the site wall, but not on the event wall (even if the “object” option is flagged)
    There are also some design issues, but those are not bugs, and I do not think you would have the time to improve them anyway…

  • sebas77

    this is maybe not a bug, but it is seen as bug for my users: the notifications are not bunched together. If many notifications are relative to a single page, they are not cleared at once when the user sees the page! This is quite annoying and a bug under the design point of view. No one 3rd party developer could develop a plugin to fix it?

  • FrancoB

    SocialEngine PHP 4.2.9p1 Patch: Having problems uploading photos using FireFox. The progress bar runs till 100% then just does nothing. Same thing happens when uploading photos in the wall. But when you look in the albums the photo shows up. Everything works ok in Google Chrome.

    • FrancoB

      I have tested uploading a photo in the Wall and Albums on all the latest browsers and here are my results:

      [MAC OS]

      Firefox <- Does NOT work!

      Chrome <- WORKS PERFECT!

      Safari <- Does NOT work!

      Opera <- Does NOT work!

      [Windows 7]

      Internet Explorer <- Does NOT work!

      Firefox <- Does NOT work!

      Chrome <- WORKS PERFECT!

      Opera <- Does NOT work!

      Looks like the dev guys at SE only used one browser type to do testing????

      • FrancoB

        Ok after a few support tickets to SE here is how to fix this bug:

        1) Disable the “HTML Compression” on the Performance & Caching page in your Admin Panel.
        2) Disable mod_security on the server.

        Thanks to Matthew from SE for the info.

        PS: But hope that both these settings are fixed and are able to be enabled again in SE4.3 as they are needed on a busy site.

        • Renaldo Sanchez

          Just by doing this “1) Disable the “HTML Compression” on the Performance & Caching page in your Admin Panel.” It works now. Hopefully all be fix on 4.3 if we ever get it. Thanks for the info.

        • http://www.facebook.com/superiorOATH Hazy Kate

          Please do not listen to FrancoB. DO NOT DISABLE MOD SECURITY. They do not fix security holes. I recently upgraded my Apache and forgot to reenable Mod_security. Within 3 days I had Phishing sites, Root Kit’s and other crap uploading using their unsecure PHP Upload methods. No one should disable Mod_Security. If the product can not work without it, then move on to another.

          • FrancoB

            As I said Hazy Kate. Both of these features need to be enabled on a busy
            site. Just passing on the info supplied to me from SE support as any
            help or information to fix bugs are very hard to come by!!!!

  • saii

    WTF….! Tday the pop up messaging was to be released…u uprofessional guys…fit for nothng…why the hell u delay…..we spent so much money on ur shit…..huh
    so sick of u guys

  • http://www.facebook.com/JonathanRojasGarcia Jonathan Rojas Garcia

    I am having a ton of performance issues with 4.2.9 and this patch didn’t do much to alleviate the problems loading up pages that my users are reporting or speeding up things. When is the next release coming out? and I hope performance is your main priority.

  • plexaz

    I tried to make this as succinctly
    as possible but a lot had to be said.

    Just my take on the subject: SE-PHP
    (facebook-ish) business model from what I could tell was to build a
    white-label product to could make your own while building a profitable
    social network at a low start-up cost. The 3rd party company’s added enhancements
    and truly one could end up with an all-inclusive product that
    rocked!

    Once a license (se-php) was sold,
    the only way I could see Webligo making money
    from current customers was by the $50 dollar support fee. I
    arrived to this conclusion because we never had an official place we could go
    as a community to report issues that were true bugs and therefore had to pay a
    support fee to get them resolved. To be fair, I did pay support fees to get
    answers to the location of code to make custom changes; not all the time was my
    $50 going towards bug fixes.

    So, my final thought on this part- because
    facebook is so, “the norm” now I believe social networking is here to stay and
    I also believe that people, by shear use of facebook will be even more willing
    to look at joining niche sites that interest them. (You can only see pictures
    of your high-school “girl” friends for so long before you think….”Yes,
    you are sexy and we all know it…now stop posting pictures of yourself!”.
    …I digress.

    SE-Cloud (pinterest-ish) produces an
    endless (on-going monthly fee) income therefore, it would seem that they are very
    excited to come up with a business model that truly will see an ongoing
    dividend for the company and the customer.

    My final thought on this part-
    Yeah….maybe pinterest is cool now but what will it be in 2 or 3 years? Will
    we get tired of “re-post” just like we might be getting tired of
    facebook? I don’t know but if we do, will the true value come full circle back
    to custom niche social networks?

    I think the big question here is–
    has Webilgo moved on from SE-PHP? And you know, I clearly remember
    that awesome high-energy, heart-pumping night that SE4 launched. It
    was magical to everyone involved. Everyone put out positive vibes of
    the highest magnitude that night and in the days after. It was remarkable. I
    want that again and I think Webligo will too. I don’t think they have moved on
    and if they think they have, it is only temporary in my opinion.

    That excitement of the SE-PHP launch a few years back- that
    is where they (Webligo) are with SE-Cloud, but the difference is that we, the
    “SE-PHP” owners did not come along on the ride this time because we
    are still in the “fix” mode or in some cases “idealism”
    mode with our sites.

    Here is my hope and final message–
    to those very smart and very caring (and they are) SE team, please think about
    a merger between what you are learning with the SE-Cloud business model and
    what you know to be areas of enhancement with SE- PHP to build the
    ultimate environment and give us back the high energy, high customer communication,
    and high hopes for a better tomorrow in our business ventures. We are, as you
    know, a highly energetic and creative group of people that want you
    to have success as much as we want to have success in our own right. Give us
    that message and you will not only win us back (I think I speak for us all) but
    we will stand by you as we did before. We want to feel the excitement of
    something to come…..

    Something like, SEPHPu
    (SocialEngineUltimate V1.0)

    Thank you,
    Plexaz

  • Edward

    My conclusion ……………………we are ready to pay more……. for the improvements of se-php. 90% of the people like self hosted …….. there wont be any less demands if you guys boot up with the developments. …. please vote the comment make them aware friends.

  • http://twitter.com/milo_sa Milan

    After upgrading to 4.2.9p1 from 4.2.6 or 7 (cant quite remember) my homepage takes up to 30 seconds or more to load. Subsequent page loads might be fast, but not always. Thought it was a server issue (dedicated not virtual) so have upgraded to a quad core from dual core and the problem persists. I can therefore only assume its something in the update.

    Going to try migrate to an older version and see if that helps, but pointless if I cant upgrade. Site is still in development phase with only a few invited members to have a play, so there is no load whatsoever.

    Just for interest sake, my new quad core server where I am the only one testing/using it, shows the following in awstats …

    3 Unique Visitors, 6 Visits, 3600 pages, 4210 hits and 4.22 MB. All from 6 visits?

  • Ryan Olson

    Well people I think it is time we face the facts. Socialengine PHP is dead. I am looking at starting a site where SE PHP people can discuss alternative solutions and migration scripts. If SE wishes to let us know where our January bug update is maybe we can get hope, but this is just too much.