dekket

I have fixed this by changing just a few places in the code spanning three files, so this is quite a simple fix to include in the next release.

I finally found the answer myself. Posting it here for anyone who stumbles across this in the future.

It’s two parts essentially:

1) I need the global $switched to be defined.
2) The variable for blog id can’t be $blog_id because that’s reserved.

The above code should thus be the following.

php
require_once( "../wp-load.php" );

global $switched;
$blog_id_target = 2;
switch_to_blog($blog_id_target);

$lang = 'en';

$new_pr = wp_insert_post(
    array(
        'post_author'   => 1,
        'post_status'   => 'publish',
        'post_type'     => 'pressreleases',
        'post_date'         => $this->publish_date,
        'post_content'      => $this->body,
        'post_title'        => $this->title,
        'tax_input'         => array(
            'pr_categories'     => $this->pr_category_id
        )
    )
);
var_dump( get_current_blog_id() ); // This returns (int)2, just like it should.
restore_current_blog();

Also worthy to note:

I’m running the wp_insert_post() within another function, which is within a custom class. $switched needs to be present there as well, and the switch_to_blog() must also be called within that function.

Smart Image Resize – https://www.ads-software.com/plugins/smart-image-resize/

Hello.

Thinking about it some more, I realized that would be the only reasonable explanation, so I dug slightly further. Turns out the z-index I had set to 9999 was on an inner container, not an outer container which also needed a higher z-index. So yea, that solved the issue ??

@bnfw unfortunately, since this multisite will be expanding rapidly and there’s already a 40-step process in cloning a new one and changing everything that needs changing, adding an import-step to it would be problematic :-/

Also, as far as I could see, the export functionality isn’t officially supported?

@peikgabriel Nope, not for me at least.

I’m having the same issue. Has anyone solved this yet?

The follow-up on www.ads-software.com forums are nearly non-existant.

@wpinsider-1 No it is not unfortunately, but the Starter Theme designed for it, is: https://www.ads-software.com/themes/visual-composer-starter/

I think you should test it out, because it is used by a lot of people, just like the predecessor Visual Composer Page Builder.

I did that already (I should have mentioned that), but it didn’t work unfortunately.

Hello @mbrsolution

No this is not correct.

VCWB is a Page Builder and is used solely by website administrators. It’s launched *from within* the backend, but launches as a Front-End editor. There’s a video of how it operates here: https://visualcomposer.com/.

So even though I’m logged in as an administrator, the Simple Membership plugin is preventing me from editing the page.

Given the huge amount of users that VCWB has, I figured this would be a worthwhile compatibility.

Hello @johndcoy.

I solved the problem last night.
Turns out there was an issue with a deprecated function in the checkout page belonging to the child theme which hijacked the checkout process when it wasn’t supposed to. At least that’s what it looks like after reading about it.

I will think twice about using these forums again though, since publishing of the URL caused my client to receive a scam email where someone called Jane Tancinco used the info to try and get my client to “buy” a solution. A way of solving that would be to keep the URL from everyone except the plugin creator/support personnel.

• This reply was modified 6 years, 6 months ago by dekket.
• This reply was modified 6 years, 6 months ago by dekket.

@igestalten

It doesn’t actually remove it, but that is essentially the effect of it. At least, that is how Datainspektionen here in Sweden is interpreting it. Cookies contain personally identifiable information (PII) readable by a site, and thus that site has access to PII.

Sure, I can tell a visitor to delete their cookies, but that isn’t the issue. The issue is consent before a cookie is saved.

Anywho, I’m pretty done with this discussion, and it’s the wrong forum for it anyways.

@catapult_themes As I clearly stated previously, that is perfectly fine. No one is forcing you to do anything.

My sole point was that because GDPR effectively removes the ‘cookie law’ and instead adds A LOT more to it, this plugin should either be removed (because it doesn’t aid compliance is ANY way AND can lead website devs into a false sense of compliance,) or it needs further development.

That being said, it’s a shame you have no further plans for it, because like @simon3333 said, there’s a giant hole in the market for a premium plugin and since this IS well-developed, it could be huge.

Just my cents. I wish you well.

• This reply was modified 6 years, 11 months ago by dekket.

That’s fine. But then it’s null and void because, well, GDPR removes the cookie law and replaces it with something even stricter.

@karmatosed If people are experiencing it as a page builder, it’s a page builder.

If it’s not supposed to be a page builder, but people experience it as such, you’ve done something wrong.