Forum Replies Created

Viewing 9 replies - 31 through 39 (of 39 total)
  • Hi,

    Hmmmm. Interesting. I hadn’t run into that, but only because I probably added the image first. (just recently began using this great plugin).

    I tried it the way you said, and you’re right, you can get into a position of not being able to get at the text layer. What I had to do was go into the slider settings/slider general options and set the start height to something really big so that I could move the image around to expose the text. Once I was able to get at the text layer again, I changed its z-index to 99 so that it stayed on top and then set the height back to original value.

    mstep,

    To make image darker….

    I setup with ‘slider options’ with no image and background color of black. Then, I clicked ‘add image’ (layer) and in its CSS, added: opacity:0.70;

    It’s allowed the black background to come through. Obviously you can adjust the 0.70 to your needs.

    Hope that helps.

    Thread Starter fwdcar

    (@fwdcar)

    I was hoping they would too because I always felt I was just missing something, and something simple at that.

    I read elsewhere that the addition of another plugin – MU domain mapping – would possibly allow this, however when I looked into it, it hadn’t been updated in a while and was only compatible with WP up to 4.0.

    As far as a deal breaker for the plugin, it’s still providing the ability to cleanly have a single codebase and single DB for multiple primary domains, it’s just that separate primary domains need to be in their own network. I can live with that for the benefits I get.

    Thread Starter fwdcar

    (@fwdcar)

    no tinus I did not. I concluded that since i was using the multi-network plugin, it wanted to use the siteID (which is really the network id) from the table wp_blogs, in the internal url rewriting process. So, it seems that if one needs a site with its own domain name (not a sub-domain or sub-directory) than it has to be a new network. Add a new network, give it the domain name and it automatically creates its first site within that network with that domain name.

    Hope this helps

    Check out this thread….not 100% sure, but it sounds like the same problem I’m having – i.e., simple edit of a network orphans other sites.

    same problem?

    fwdcar

    (@fwdcar)

    UPDATE:
    I can 100% of the time create network.zero (orphaned) sites.

    Start out with 1 network.
    Add a couple sites to it.
    Add another network.
    Immediately edit that new network (you don’t need to make any changes, just click update).

    The result is that any sites that you have under the first network will be orphaned, and their respective wp_#_options tables will have network.zero for their URLs.

    Maybe it’s just something I have going on here…if it is, I have no idea what it might be. Any ideas would be appreciated.
    Thanks.

    fwdcar

    (@fwdcar)

    I’ve had this happen to me several times recently. It seemed to be correlated to some site movement and network deletions. Anyway, only way I found to repair it was via manual DB manipulation. The network.zero URLs are in the siteurl and home columns of a blog’s respective ‘options’ table. For example, blog ID 9 will have a wp_9_options table(amongst other). Update those 2 columns with the correct URL. You’ll have to do that for each blog that has been orphaned. And be ready to do it again, as I’ve had to fix mine a few times in the last week while trying to figure out the cause. I can tell you that it’s not the forgetting to comment out the line in wp_config.php. Mine had been commented out the whole time.

    Hope this helps.

    Thread Starter fwdcar

    (@fwdcar)

    Thanks for the reply NDx. The adding, then editing of the site to new URL sure seemed to work as planned, but going either to the site or the dashboard produces an error:

    “Error establishing a database connection”
    …..
    “Could not find site zzzzzzzzzz. Searched for table wp_blogs in database zzzzzzzz. Is that right?”
    (…..And yes this was all right)

    Looking in wp_blogs, the new site is there (blog ID 18), and all 10 tables for a site are there (for example: wp_18_options, etc.).

    All my other sites, including some in that same network, work just fine, so I know it’s not a ‘true’ DB connection issue.

    I’ll keep poking around…it must be something simple and right under my nose here.

    any ideas?
    Thanks again….

    Thread Starter fwdcar

    (@fwdcar)

    sorry – typo in my post. Should of had an equal sign like this:
    For example: Network 1 – site1=abc.com and site2=xyz.com.

Viewing 9 replies - 31 through 39 (of 39 total)