Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 17 replies - 1 through 17 (of 17 total)
  • @tonyzeoli

    Participant

    All:

    Please note that your Ning export may be corrupted. Your LOCAL JSON file should be the same size as its sister file. According to Boone Gorges, the creator of the Ning to BuddyPress Importer, you can rename your -non-local file to LOCAL, as all the content in both should relatively be the same, with the following caveat:

    “-local.json files in the Ning export should be more or less identical to the non-local files, except that the local ones have relative links, which is especially relevant for inline images (which are stored in the /discussions/ directory).”

    The plug-in searches first for the “ning-discussions-local.json” file. If that is corrupted, then the process will not complete. Boone said that he could change it, but that would mean having to do a search and replace in mysql of the path set by the export.

    Tony Zeoli

    @tonyzeoli

    Participant

    Can anyone help me figure out why I’m getting a skipping error on the ning to buddypress importer. The developer says because the forum topic may not be associated with a category or group? Does that mean in Ning, all topics must be assigned to a category or group to come over to BuddyPress?

    Tony

    @tonyzeoli

    Participant

    We’re going to try and split the 14MB JSON Discussions Group file and see if that works. Looks like on LINE 97 of the php file that runs the importer, we’re getting caught up on the JSON file. So…we thinking that this is what it could be.

    @tonyzeoli

    Participant

    @hnla I have been following the thread, but it seems as if Boone’s been busy and he hasn’t been answering queries for a few days to a week. I’ve posted a number of times there and haven’t gotten a reply.

    I’m not sure about splitting the JSON file at this point. I know that he’s mentioned that before. I am going to try a few things. I think because we have some other plugins on the same hosted about on another install of wordpress, that might be the issue. Will try it and see.

    @tonyzeoli

    Participant

    @techguy, I just went through my 1and1 cpanel. It doesn’t give you that option. @umablue, with 1and1, the only way to switch to PHP5 is to use the “Add Handler” and “Add Type” strings in your htaccess file. 1and1 won’t fully switch to PHP 5 until end of Q3, according to their web site knowledge base. I’m using the strings, so I’m on PHP 5 already.

    I finally ran the Ning to BuddyPress importer. I had to turn off all other plug-ins in order to run it. Now that I’ve run it, I’m encountering a memory error on “Discussions,” which has a folder associated with it that’s 14 MB. Every where I turn with this Ning to BuddyPress migration there are issues. It’s quite challenging.

    @tonyzeoli

    Participant

    @techguy – I’ll visit the group and post my thoughts. Thanks.

    By the way, I also learned that you have to put the php.ini file in the root directory, and any other directory that runs php scripts, like wp-admin and possibly plugins. Once I put the php.ini file in root, the site worked, but not the admin. I put an additional file in wp-admin and was up and running again. So, php.ini, while it works, it must be placed strategically in root and dependent folders for it to over ride the host settings.

    @tonyzeoli

    Participant

    @tonyzeoli

    Participant

    Okay, so I knew about the php.ini settings in my work with WordPress. Silly me…I thought using that trick wouldn’t change the setting on 1and1, since the tech support told me that they had it set to 30 MB. Well…guess what? It worked. I set it to 128 and voila…instant BuddyPress. @UmaBlu, @techguy – you were both correct to let me know to use the php.ini setting. Thanks for that. I put the ini file in the top level, so that it sets the memory limit for all sites in the shared folder. Working just fine now. Whew!

    @tonyzeoli

    Participant

    Okay, I will try to add the php.ini file. I spoke to tech support at 1and1. They said even if you try to upgrade your php memory limit, they have it hard set to 30 MB. I used the “define” function in the wp-config file to set the memory limit, but I will try the php.ini file and see if that works. I’ve used it before and it’s worked for other sites, so maybe that’s the issue. My goal with this post though, was to get a handle on exactly how much memory BuddyPress needs to run efficiently at the base install level, with no content or users, and then understand why or why not it would need more memory based on new data in the database and increased user base.

    @tonyzeoli

    Participant

    The issue at GoDaddy shared hosting is that only so much memory is allocated to WordPress or WP/BP. On shared hosting, you aren’t going to get the performance you would on dedicated for VPS. I experienced incredibly slow load times with just WP, never mind BP on GoDaddy. I would move to a WordPress friendly host, like MediaTemple, who’s Grid Service offers up to 100 MB of php memory. You’ll need more php memory than 1and1 or GoDaddy offers in their shared packages to run BuddyPress. I’m already crapping out with Memory errors on 1and1, who won’t allot more php memory on a shared account. I’m assuming the same for GoDaddy. I’ve now moved 5 clients off GoDaddy with WordPress sites due to slow load times. They claim you should use WP-SuperCache to serve cached pages, but even then, the first time any user loads a cached page, it takes 3 to 5 seconds. From page to page to page, you’re crawling. I may be incorrect in saying that every user would experience that issue, but it could be accurate too.

    @tonyzeoli

    Participant

    You should be able to export your DB from GoDaddy using phpMyAdmin. I have done this and it works fine. You have to follow the instructions posted by mercime on the WordPress Codex.

    Now, if you are trying to IMPORT your DB the same way on a new host DB, hosts like 1and1 limit your MySQL upload to 2MB only. This means you have to use the command line with linux commands to perform a “mysqldump”. Performing this action, will backup your DB file to a folder. Then, you FTP it down to your desktop. Upload it to the folder on your new server and dump it into the new DB by performing a “mysql” action. You can find the commands in both links provided by mercime.

    We just exported and imported in this way from GoDaddy to 1and1. Took me a minute to figure out how to perform a mysql action, but once I learned how to do it, it was a breeze.

    What you might find, is that on your new host you don’t have enough php memory. That may be an issue. I’m facing that right now.

    @tonyzeoli

    Participant

    Can someone help me with this?

    @tonyzeoli

    Participant

    Has anyone figured out a Ning Forums to BBPress solution?

    @tonyzeoli

    Participant

    Right, thanks Symm2112 for the explanation. I am just starting back up learning about Buddypress and forgot the distinction. My install had been sitting dormant, but I’m on the move getting ready to convert everything over on my site.

    I will follow both your, r-a-y and windhamdavid’s instructions and see what I can come up with. The plugin method should be pretty easy to parse out the date ranges and import.

    @tonyzeoli

    Participant

    I set the memory to 128…so that’s not the issue. I’d like to know how I can export from mysql and import to buddypress and if the table structure is different. That would solve my issue without having to fight with this?

    @tonyzeoli

    Participant

    I’m having the same problem.

    I can see all my widgets and sidebars, but I can’t drag and drop my widgets.

    I found a post that recommended installed “User Google Libraries” plugin. I did that, but it’s still not working.

    @tonyzeoli

    Participant

    I need to reopen this thread to ask the group what I need to do when the Buddypress Import feature experiences a php memory failure halfway through the import.

    I was just importing the xml file and got to around 90 posts (I have over 500), then it crapped out.

    I updated the php.ini file in wp-admin for 128M, but I don’t think changing it to that high a setting on 1and1 helps at all. They state they have a max of 40, but I think they just put that out there and you can actually go over the limit, but I’m not sure.

    I know how to dump my mysql file from my WordPress database on my host. I’m just not sure what would happen if I imported the database from a general WordPress install to the database for a BuddyPress install.

    Here’s what I’m seeing after trying it twice. I see that it see the posts I’ve already added.

    88 Importing attachment http://netmix.com/wordpress/wp-content/uploads/2006/01/jam_markspoon1.jpg... (30 kB)
    89 Post Jam & Spoon's Mark Spoon Passes On already exists.
    90 Post Larry Heard's "Can You Feel It" vs. Martin Luther King's "I Have A Dream" Speech already exists.

    Fatal error: Out of memory (allocated 33554432) (tried to allocate 524297 bytes) in /homepages/7/d106361195/htdocs/netmix_home/wpmu/wp-admin/import/wordpress.php on line 143

    Anyone suggest and links that can help?

Viewing 17 replies - 1 through 17 (of 17 total)
Skip to toolbar