adaptistration

Yes, it finally connected. Your attention to this has been great but this sort of unreliability is still a showstopper at this point.

I appreciate that but you can see how this is simply not a reliable option for providers and agencies, correct?

5 min x 115 users = 9.5 hours of work time lost to unreliable service.

I’m sure you’ll agree this is nothing but a negative ROI.

I didn’t receive any notice about down time, so are there no status board or notification emails to opt into?

And no, still getting “creating site failed” error (and there’s no reference to that error in the documentation).

As of this morning, I keep getting a “creating site failed” error. I have been through all of the documentation and verified the SSL version of site names match etc.

I’m trying to decide if it’s worth moving over my 115 users I manage to SiteKit and frankly, the amount of time spent trying to troubleshoot tells me this plugin is nowhere near ready for use at a commercial level.

• This reply was modified 4 years, 11 months ago by adaptistration.

Just started experiencing the same issues here today.

Will do and thanks so much for the prompt replies!

Ah, interesting and good to know! Yes, I am using that plugin there as well (I manage the site for them). That seems to have done the trick, FWIW, it took adding attachment-medium size-medium to the source AO install exclusion.

Many thanks! That worked on those two embeds but I’m still experiencing the issue on a different wordpress embed, this is one is from a different site. You can see it still doesn’t load the image here: https://adaptistration.com/2019/06/04/musician-dress-codes-the-topic-with-staying-power/

I tried adding lazyload as well as attachment-medium size-medium but neither are working. Suggestions?

Experiencing the same issue here. Is there any way to either resolve this or make sure that pretty.css only attempts to load on pages that actually use the highlighter?

I experienced this as well and deselecting the remote login worked BUT attempting to access the primary domain was redirecting to an ?action=login&dm=5f361d501b7b55e… string.

So the homepage loads but it includes that redirect for logged in admins. Here are the domain settings for this install (lovethistown.org): https://www.screencast.com/t/euVsPNQAA

I don’t think the issue with not seeing all of the new tab functionality was ever resolved but my hunch is that’s moot for new users and limited to my unique situation.

Beyond that, yes not having it as a child menu item only, the optin, and the related upsell material were deciding factors.

And for how I use licensed plugins, I really need something that provides an easy way to manage licenses and installs as well as provides a way to create a default install settings or at least have an easy import/export function (so I don’t have to manually set each option across dozens of installs).

I was only using the one plugin. I can say that for most quality hosting providers, a CDN is bundled with the service in one way or another, but that’s just my own experience.

I completely understand and have noticed this trend and from the end user perspective, I’m never happy with this as a dev becasue this ends up either violating my client’s privacy policies or becomes one more thing they have to add. Likewise, I noticed the new version still created a top level menu item and that’s one more thing I really don’t need and could go in the “settings” or “tools” menu.

I hope you release a premium version soon, in the end I think it’s better for everyone involved as the whole freemium marketplace is rapidly becoming a disaster area ??

As a developer, I would much rather pay a license to a solid product that understands how to fit in a white label environment. That’s worth a premium to me (and I hope others in my position).

I just completed the update at the one install where it was still running and I now see a grant permissions permissions screen. I’d really rather not go through that if possible but at the very least, it does seem that the changes you’re pushing through now seem to be working better.

I now have to remove the plugin from this install and replace it with the other one. Thanks again for your responses!

Many thanks for following up, I appreciate that. I ended up having to switch to a different solution but up through the point where that happened, I was still experiencing those most recent issues, even after removing the plugin from the database manually then reinstalling.