SocialEngine Blog

SocialEngine is the best way to create a unique community website. Let your friends, fans or customers geek out about anything you want.

SocialEngine PHP 4.3 Incoming

Hi everyone. As I type, our engineering team is 100% focused on building the upcoming (and very overdue) SE PHP 4.3 update. Here is exactly what we are adding with this update:

  • Various frontend improvements to the default theme
  • Adding any missing pages from the admin’s Layout Editor back to the page selector
  • Various improvements to private messaging, including a modal-based (popup) message composer, a check-all button in the inbox, and proper message searchability
  • Profile field-specific privacy options, so your members can give each field on their profile a unique privacy setting
  • Photo-uploading abilities for mobile browsers

We are also fixing these bugs:

  • Comment posting is problematic in IE9
  • Music files don’t play on all mobile devices
  • “Number of playlists” setting in music plugin’s admin section isn’t being applied
  • Sharing links from a SocialEngine-generated page on Facebook results in the page title appearing twice
  • Display bugs in the admin’s site-wide statistics area
  • Group discussions don’t always appear in group activity feeds
  • Multi-language issues with the Events plugin
  • Pagination breaks if more than 1 video widget is added on a single page

We’ve dropped everything else and the whole team is sprinting to get 4.3 ready by this Friday. There’s a small chance we’ll need to release on Monday, so our support team will be in full force to support anyone that has issues with the update. We know many of you have been waiting for 4.3 for a long time, and we’re sorry that it’s overdue.

Looking ahead to 4.4, we are also thinking about a possible SE PHP API (since it’s been requested quite a few times). For those of you hoping for an API, can you clarify: Do you want the API to be external-facing (e.g. a REST API), or an internal PHP API? Can you tell us what you’re looking to build on the API? This will really help us figure out how we can build the best API for everyone!

 

 

40 Comments

  1. Posted February 11, 2013 at 7:14 pm | Permalink

    hiding the blog link and complaints in the footer is not the way to go. smh

  2. Sean Arani
    Posted February 11, 2013 at 7:47 pm | Permalink

    As a user of SE PHP, I just wanted to let you know that I much rather seeing a post such as this one letting us know that the update will be delayed, than be left in the dark hoping it’ll happen at some point and wondering if we’ve been completely forgotten about. The simple act of keeping us informed does a lot of good, I promise. Thank you for the post.

    • Posted February 11, 2013 at 8:08 pm | Permalink

      Thanks! We are serious about getting this out as quickly as possible, but just don’t want to leave people hanging over the weekend when we have lower support ticket handling capacity. We are already making really good progress on the items above and might actually be able to fit more in for the release.

  3. Tony Harrell
    Posted February 11, 2013 at 8:07 pm | Permalink

    Any REST API that will aid improve with the development of mobile app (namely IOS/Android) interfacing with SE PHP.

    • Dan
      Posted February 12, 2013 at 12:07 am | Permalink

      I second that.

    • FrancoB
      Posted February 12, 2013 at 12:25 am | Permalink

      Plus if we had a native PHP Block in the Layout Editor to use with API calls then that would do super cool!!!

  4. Posted February 11, 2013 at 8:50 pm | Permalink

    PLEASE – do something about SPAM!!! It’s killing us. We get a TON of spammer sign-ups every single day (over a hundred). And somebody has to sit there and manually delete each one.

    Please give us a custom-field we can create on sign-up where we ask a question of our choosing, and specify the correct answer. This is the only thing spambots can’t beat. The google captcha is totally worthless. It doesn’t even slow them down anymore.

    Another thing that would be hugely helpful is if we could assign whatever rights we specify to moderators. Like let us assign the ability to approve or reject new sign-ups to certain moderators… so the site owner doesn’t have to be burdened with doing all the work.

    Thanks!

  5. FrancoB
    Posted February 12, 2013 at 12:24 am | Permalink

    Great news! Just one thing, please tell me you are rewriting the whole photo upload section and not just abilities for mobile browsers. Having Flash for uploading is super bad. Most people do not even install Flash when they get a new PC/Laptop.

    • Godrifle
      Posted February 12, 2013 at 9:59 am | Permalink

      Please eliminate flash everywhere. We live in an HTML5 world. For example, multifile upload can now be had with the inclusion of one attribute in the HTML:

    • Posted February 12, 2013 at 6:30 pm | Permalink

      You can’t just remove flash – the entire internet runs on it and to say that people do not install it is crazy. Without it, users wouldn’t be able to enjoy any flash enabled websites, in which there are millions

  6. Dan
    Posted February 12, 2013 at 12:38 am | Permalink

    Hallelujah, now was that so hard? Can you please more just a few more often give us some clarity about delays, it’s so frustrating to be kept in the dark. How long does it take to write a blog like this 5 minutes…. Anyway I still have a some hope left for this product, especially if you guys would build an API like you mentioned in this blog.

    What also keeps me having hope are the 3rd party developers, I want to take my hat off for the 3rd party developers that still take this product serious, special thanks to the SocialEngineAddons team who just released a very rock solid multiple listing types plugin and for soon releasing a mobile plugin, you guys rock!

    • FrancoB
      Posted February 12, 2013 at 1:44 am | Permalink

      I will be spending over $2000 on 3rd party plugins and SE plugins over the next month or 2 but will only be doing this once I have a proper stable SE core site up and running. No point investing more till SE-PHP is working 100%. So not updating SE-PHP they are not only hurting themselves but also 3rd party developers.

      • Dan
        Posted February 12, 2013 at 1:50 am | Permalink

        You have a point there, I’m still in a custom development phase so I have not tested the script for the usual bugs jet. But from reading the complaints it seems like a mess at the moment.

  7. FrancoB
    Posted February 12, 2013 at 2:12 am | Permalink

    Since you mentioned “Various frontend improvements to the default theme” are you looking at updating it to a responsive web design? Since more and more people are viewing our sites with tablets like the iPad etc.

  8. Posted February 12, 2013 at 7:41 am | Permalink

    PLEASE – do something about SPAM!!! It’s killing us. We get a TON of spammer sign-ups every single day (over a hundred). And somebody has to sit there and manually delete each one.

    Please give us a custom-field we can create on sign-up where we ask a question of our choosing, and specify the correct answer. This is the only thing spambots can’t beat. The google captcha is totally worthless. It doesn’t even slow them down anymore.

    Another thing that would be hugely helpful is if we could assign whatever rights we specify to moderators. Like let us assign the ability to approve or reject new sign-ups to certain moderators… so the site owner doesn’t have to be burdened with doing all the work.

    Also, when we manually approve new sign-ups – it doesn’t show up in the main newsfeed when we’ve approved a new member. That really needs to be fixed. Or else figure out some way for us to stop the spammers without having to resort to manual approval.

    Thanks!

    • FrancoB
      Posted February 12, 2013 at 11:58 am | Permalink

      Are you using the Blog plugin?

      • Posted February 12, 2013 at 1:22 pm | Permalink

        Hi Franco, yes I am. If you’re going to suggest that that’s the problem – you could well be right. Because after they sign up (and I accidentally manually approve them) that’s the place they go to post.

    • Posted February 12, 2013 at 12:26 pm | Permalink

      Absolutely spam is something that needs to be sorted out. A custom field would sort this out once and for all and would stop at about 90% of spam.

      And make a lot of your users very happy

    • Ryan Olson
      Posted February 12, 2013 at 4:50 pm | Permalink

      I will share with you what I have done. I use NGINX on my webserver. With that you can Geo-block various countries. Depending on your sites needs, you may not be able to do this but. I was able to block China, Ghana, and the Phillipines, and that cut my spam down from 100/day to 1 a week. if you want more information on how to do this feel free to let me know and I will send you some links. My site has over 40,000 active members so I understand the need to block spam. There is also similar solutions for people using Apache.

    • HIFIDEV
      Posted February 12, 2013 at 5:23 pm | Permalink

      I think im being blocked, but if you get this Jonathan. Try SpamTrawler.
      Thanks

    • Posted February 15, 2013 at 2:08 am | Permalink

      It looks like my prev. comment was deleted. Check our plugin called Moderator Toolbox. It was designed to delegate some admin power to a group of moderators.

  9. Godrifle
    Posted February 12, 2013 at 9:59 am | Permalink

    I would like to see an internal API.

  10. Posted February 12, 2013 at 12:02 pm | Permalink

    This is what of the best posts I have seen from you folks in months. It shows commitment.

  11. Posted February 12, 2013 at 12:13 pm | Permalink

    This has really made my day, we had already started preparing for the worst and were contemplating having to hire a SE/PHP developer to help us resolve the issues we have been experiencing with our site.

  12. Posted February 12, 2013 at 12:52 pm | Permalink

    We need that the API can help us create an App Store where people can submit their own app.

  13. Posted February 12, 2013 at 1:09 pm | Permalink

    Focus in better CHAT please and asap!

  14. sebas77
    Posted February 12, 2013 at 1:14 pm | Permalink

    test

  15. Osei
    Posted February 12, 2013 at 1:31 pm | Permalink

    finally something i can look forward to and i’ll like to see the external face api

  16. Posted February 12, 2013 at 1:41 pm | Permalink

    expected by all fantastic already underway

  17. Renaldo Sanchez
    Posted February 12, 2013 at 2:37 pm | Permalink

    Thank You for keeping us informed. That is all we ask. Thanks again :)

  18. Ryan Olson
    Posted February 12, 2013 at 4:48 pm | Permalink

    We DEFINATELY need a REST API. A lot of us want to develop mobile apps and other external functions that will allow us better integration with our site(s). I for one think the existing apps out there for SE are “ok” but they are not what some of your larger sites want when we are wanting a custom solution.

  19. HIFIDEV
    Posted February 12, 2013 at 5:20 pm | Permalink

    am I being blocked from comments? I have posted over 4 comments within the last few updates and have not seen one at all!!

  20. Villara
    Posted February 12, 2013 at 5:25 pm | Permalink

    Hi,
    we’re still on 4.24 (all other releases were too buggy and not interesting enough!). Is an update to 4.3 even possible?
    BTW: still waiting since 3.0 for that PayPal modification where you can just specify page_style and return URL.
    Never going to happen I guess.

  21. PiRi
    Posted February 18, 2013 at 8:20 pm | Permalink

    Thank You. I stand corrected. My apologizes.

  22. Simon
    Posted February 20, 2013 at 4:17 pm | Permalink

    Now that’s a look forward. Thank you for this blog post.

    I Suggest to create a read / write REST API with OAUTH 2.0 Auth. for security.

    Target: Create Mobile and or Desktop Apps for Socialengine and also integrate Socialengine Content in i.e. wordpress.

    A modular API System would be cool. By modular I think of a System, which gives 3rd party plugin developers the possibility to add an API for their plugins, too. This way we could also activate / deactivate the api only for plugins / functions we need (to save Server ressources).

    You can also add the possibility to limit the number of API requests (so Ressources can also be saved)

    The API should be a Json API (because it is faster than xml), maybe xml, too.

    Later an internal API would also be nice but an external API is more important sor the start in my opinion.

    Annother idea concerning speed: Maybe you could add the possibility to add multiple databases and to allocate the different database tables? Just an idea. Theres is something familar for WordPress Multi site.

    Well hope this helps. Thank you for this post, the release of SE V4.3 and that you are open to discussions about an API – it is an important point – really.

    All the best

    Simon

  23. louda80
    Posted February 2, 2014 at 8:19 am | Permalink

    Hi,

    In my humble opinion, it’s will be good to have both APIs, with the requirement that the first one is an extended version of the other as opposed to two distinct sets of code.

    About the external one. Use cases are multiple:

    – implementing a mobile app. on top of socialengine and not based on a “simple” webview

    – displaying and using socialengine’s date (ex.: user’s event) in another webservice

    – implementing non-visual feature with another language that PHP (i.e.: importing and synchronising events calendars … )

    -providing an API for to your clients’ partners.

    -…

    There is plenty of features that requires a JSON API and not an internal API

    Also, it’s important to underline that the “new” model for modern web apps is similar to old Client/Server architecture but this time the Client is the browser with JavaScript, CSS, and HTML; while the Server is RESTful JSON services.

    Regards.

    • Posted February 3, 2014 at 9:20 am | Permalink

      Great feedback, Thanks for taking the time to detail this out. It’s extremely helpful to share with our devs.

  24. Corey Toolis
    Posted February 11, 2014 at 10:28 am | Permalink

    I could really use a rest API

  25. 旁观
    Posted August 3, 2015 at 10:28 pm | Permalink

    I found this thread. Not sure where Socialengine is on REST API. I hope you guys made good progress on this project. I think to your product’s future, such an API is absolutely necessary, especially with Zapier and other vendor all going into REST API. It would enable your solution to expand so much quicker. I found that Drupal is planning to integrate with Zapier. Drupal Commons is an real threat to Socialengine if you do not have an API offered soon.

    • Shivani
      Posted August 5, 2015 at 1:45 am | Permalink

      Hello, currently, we don’t have any plan to work on such an API. But yes, such a Social API has already been developed by one of our 3rd party developers “iPragmatech Solutions”. Also, one such API is being developed by another developer “SocialEngineAddOns”. You may look into these options and make a decision accordingly. Hope that helps!

Post a Comment

Your email is kept private. Required fields are marked *

*
*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>