Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • @memovera01
    I think your setup may be wrong for this on your tutorial. The whole purpose of using this plugin is to use one code base and just have it “simulate” other networks without having to copy 27 files. The way you have it set up, if you update (for example) WP 3.01 to 3.1, your networked sites will break because it will be using the older versions of those files that you told people to copy over.

    I’ve successfully installed this plugin and not created a directory nor copied any files whatsoever, it’s mostly setting up the proper DNS and apache (or nginx or whatever you use) records properly.

    Since it hasn’t been discussed yet on this thread, if you have multiple sites and using a vhost setup, for example I had site1.com on it’s own wordpress install, and site0.com on it’s own. In the DNS settings, I just created a wildcard for site0.com:
    Name: *
    Data: your-IP-here
    Type: A (record, can use CNAME as well)

    Using Ubuntu and Apache2, I had to update the vhosts pointer for site1.com to point to site0.com’s directory. Then disable site1.com using
    >a2dissite site1.com
    This allows you to re-enable it to point to the new directory since I made changes to the available-sites file for site1.com, which is site0.com’s directory:
    >a2ensite site1.com
    With this done, I just create the new network with the plugin, and it’s there ready to access. No files copied, no directories created.

    Thread Starter laneallen

    (@laneallen)

    Do you have any experience with php or jQuery?

    I have very limited knowledge of either; I’m just an idea person and a designer. I do work with a programmer though, do you need help with this?

    Thread Starter laneallen

    (@laneallen)

    I just can’t understand the musts of creating a custom post type for every form instead of having a unique page when you can select which form’s submitions you would like to see… I’ve never tried it before, but I think that the generation of custom post types dynamically its very complicated

    The generation of the custom post type is to store the data relevant to the form, which wouldn’t limit being to place any particular form in other pages. The process of this concept is being able to reuse the data being gathered which would make this plugin a cornerstone for multiple other tasks that it could accomplish. Maybe I’m misunderstanding your comment there, but creating a custom post type that is attached to a form doesn’t limit the forms placement in other pages/posts, rather, it allows the managing of the data being collected in one location on the backend.

    Example:
    Feedback form creates a custom post type “Feedback”, other plugins can then tie into this data, export selected feedback as a testimonial section, or even a ticketing system, crm system, or X need. Now, if the data is just emailed, then the possibilities to reuse this data is eliminated for other uses; not to mention that, let’s say, a larger organization is running a site, the data being sent has to get shuffled to multiple sources that need access to this data. But the whole purpose of running a site, especially as a CMS, is to manage said content in one system.

    If this plugin allowed collecting data to a custom post type, you’d have yourself a very powerful tool that could be used in countless ways, and could be a cornerstone into a ton of other powerful cms related features brought to WordPress. That’s just my two cents though.

    Thread Starter laneallen

    (@laneallen)

    Actually, Google Chrome is having problems with all ajax calls within BuddyPress, so this is probably not related with BuddyPress Followers.

Viewing 4 replies - 1 through 4 (of 4 total)