Forum Replies Created

Viewing 13 replies - 1 through 13 (of 13 total)
  • This thread looks a little old, but I’m having the same problem.

    My local development environment is working just fine. The staging environment for the client to look at, isn’t. It’s basically the same problem: I can’t expand any of the accordion items in the Menus area. There must be a javascript conflict happening somewhere, because on the left sidebar, the “dropdown” submenus don’t fly out when you hover over each menu item, if that makes sense. Again, in my local environment for this project it works just fine. I tried to see if there were any errors in the console using Chrome Dev Tools, but it says there aren’t any!

    Using version 2.0.5 sometimes works for me. Just make sure you have 2.0.5 on both import/export sites.

    https://www.dropbox.com/s/qe6imzyhm0bnlno/all-in-one-wp-migration.zip?dl=0

    Bump.

    I absolutely love this tool.

    It’s working perfectly on my local installations, but only on certain remote sites it sit there with “Done creating empty directory.”

    Is there a fix for premium support users? If there is, I’d gladly fork over the money for it…

    Thread Starter swthate

    (@swthate)

    Well it was a stupidly, easy fix.

    After renaming my template file to the correct spelling, I simply opened the page that uses that template in the WP Admin area and re-selected the correct template.

    Thread Starter swthate

    (@swthate)

    Sadly no.

    I’ve been switched to some other projects and haven’t thought of this one for quite a while. In another project I came across Advanced Custom Fields, and I’ll probably use that for creating galleries.

    Cheers!

    Thread Starter swthate

    (@swthate)

    No, I haven’t, but I did read this in another thread:

    (from mjshade)

    Hi,
    I was reading other forum posts about this problem and found a suggestion that worked and was easy to implement.
    In your functions.php file, find this line of code:

    add_filter( 'ext2type', 'minimatica_mime_types' );

    and replace it with this:

    add_filter( 'ext2type', 'minimatica_file_types' );

    This completely fixed the featured images problem for me.

    That solution worked. Sorry, should have posted about it in here, forgot about it! 🙂

    Hmm, I’m using Chrome. I’ve tested IE for some things, but haven’t tried it for this process yet.

    I’ve seen a number of “fixes” that say to click ‘select featured image’ in the left sidebar, but that confuses me. The only place I see that link available is at the very bottom of the right sidebar while I’m in the dashboard editing a page.

    I have noticed that even though it says it fails to upload, it actually is in the media library; however, when I go to a post or page and try to add media and try to browse to the media library, it says it is empty.

    Same issue for me after updating to 3.5

    It uploads the image, but then says there was an error. If I go to the media library the image shows up there, but when I go to add media inside a post, it doesn’t show me anything from the media library.

    Argh!

    I’m having the same problem right after the update.

    I’m not using any plugins at the moment, but am using a custom theme “minimatica”

    Thread Starter swthate

    (@swthate)

    Second link worked like a charm.

    Thanks!

    I’m having the same problem.

    However, I created the bucket from the S3 side. I couldn’t create it from within the plugin, it’d just re-load the same page and ask for a bucket.

    Thread Starter swthate

    (@swthate)

    Oh, wait, I think I figured it out. I was doing everything right, except for editing the wrong part of the line of code that site provided. 🙂

    Thread Starter swthate

    (@swthate)

    Thanks, that page does help a bit.

    I’m still having a little bit of trouble with it, though. I’ll list the things I want to change, maybe that’ll help a little more.

    1. This is for a funeral home website, so all the labels and text that show “comment” need to be changed to “tribute”. So, I went to where that page talked about changing the comment_field, hoping to easily change the <label for=”comment”> to <label for=”tribute”>. He gives a line of code to accomplish that, but I’m still confused as to where I put that line of code. Like I said, I’m not good in PHP, so I don’t always know what things may or may not be implied with it. I imagine I put the code inside the comment_form function, but is it nested in its own parameter, or what?

    2. Right now the comment form and the label for it are on the same line when the page is rendered, I just want to put a line break between the field label and the field itself. Or would that be simply solved by adding some CSS to the field itself and changing its display?

    3. I want to delete all the text that says “You may use these HTML tags and attributes: …”

    Sorry if I’m a little dense 🙂

    Thanks for the help so far, though!

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