Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • yah I tried it on 2.8.5 and same result

    After messing with it for a while I have some more information. It seems to just stop execution after a similar (but not the same) amount of progress on each attempt

    To isolate the problem I tried making a smaller import xml file. I’m importing a ton of tags so I removed all of the post <items> and just left the categories/tags in.

    The tags are in alphabetical order in the xml file and after the import stopped I checked my Post Tags to see how far it made it. I refreshed the database and tried again and checked again, and it stopped on the same letter of the alphabet but made it slightly further (by 4 or 5 tags). Each time it will run for about 10 seconds before I get the blank Import screen and progress is halted.

    This suggests that it’s some timeout issue with execution on the server. I tried changing the following php.ini values

    post_max_size = 64M
    upload_max_filesize = 64M
    max_execution_time = 600
    memory_limit = 64M

    The changes are reporting to have taken effect but there’s no difference in the import. Are there any other values that I should be increasing or do you have any other ideas as to why this might be happening?

    I have the exact same issue.

    Thread Starter mdisanto

    (@mdisanto)

    Thank you for the response! Those plugins didn’t quite do it however in investigating them I came across the “More Fields” plugin which solves the problem exactly. So if anyone else comes across this problem, check out More Fields.

    Thread Starter mdisanto

    (@mdisanto)

    desperation bump… any idea? Can’t seem to figure it out

    Thread Starter mdisanto

    (@mdisanto)

    ah! it worked, thank you!!

    Thread Starter mdisanto

    (@mdisanto)

    I tried running the $wp_rewrite->non_wp_rules helper function to generate the rule and it did give me something a bit different than what I had, but still no luck.

    New .htaccess looks like

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^archives/(.*) //?p=$1 [QSA,L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    Forum: Plugins
    In reply to: mysql_connect conflict
    Thread Starter mdisanto

    (@mdisanto)

    for anyone curious, I was able to get it working by giving the wordpress database user privileges to the secondary database. Then I used mysql_query – which reuses the wordpress db link by default – and defined the database explicitly in the sql command “SELECT * FROM dbname.table”

    So, while I couldn’t figure out, and still dont understand why mysql_connect wasn’t working, this is one possible workaround.

    Forum: Plugins
    In reply to: mysql_connect conflict
    Thread Starter mdisanto

    (@mdisanto)

    also, the username and password are different from what wordpress is using to connect to the main wordpress db. According to the docs mysql_connect should open a new link by default anyway if the user/pass is different.

    I tried globalizing $wpdb and ->select’ing my database, then switching back to the wordpress db, no luck. I tried regular mysql_select_db, same thing. I tried creating a new instance of the wpdb class and using its constructor to connect to my database, but again, same thing. Any database calls after any mysql_connect fail.

    Forum: Plugins
    In reply to: mysql_connect conflict
    Thread Starter mdisanto

    (@mdisanto)

    hmm I changed the line to

    $db = mysql_connect(“hostname”, “username”, “password”, true) or die(“Check DB connection settings”);

    but still having the same problem. Thanks for the quick response!

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