Fahrenhe1t

You should be able to go to Users, edit the user, look for the “Two-Factor Options” section, then uncheck the “Enabled” checkmark. Then click “Update Profile” at the bottom of the page to save.

Hi @melchoyce , thank you for following up! Actually, I have to admit that the team has been putting in work on Gutenberg and it really shows. Thanks for the tip on placing inline images; that seems to work now. It has taken awhile to get used to, but it seems to finally have most of the functionality of the Classic Editor…so much so that I was able to remove the Classic Editor plugin from my site. Gutenberg also has the Classic Editor block, which was a nice edition (but is getting used less and less).

One bit of feedback I have has to do with the toolbar during editing. I have a 2K monitor and when I edit a post in full screen, there is a ton of blank, unused space in the toolbar (https://he1t.net/images/gutenberg_space.png). It would be nice if all the toolbar options hidden in the dropdowns and vertical ellipsis expanded out if the users’ resolution is wide enough. It would also be helpful to see all the available options in the toolbar without having to try and find options (since there are two dropdowns next to each other, the caret and the ellipsis).

I think Gutenberg could have stayed in beta a bit longer while functionality was being added to it to match the Classic Editor. Forcing users onto Gutenberg without having 1-to-1 functionality was very frustrating. I can only imagine the panic and anger folks had when they could not accomplish simple tasks they were able to do with the Classic Editor. I hope we’ve all learned something from this exercise. I imagine I’ll have to change this review. Thanks again!

Looks like contributors can’t create an embed on standard posts or pages either. Not sure how the role permissions changed. I saw there is a plugin (PublishPress Capabilities) that can reset role permissions to default; would that break LDD Directory Lite?

Hi, I tried adding this to a site-specific functions plugin, but it didn’t work. The user (who is an editor) pastes the embed code in the text field, and it removes the text upon save. It also gives an error now about “The backup of this post in your browser is different from the version below.”

LDD Directory Lite

I tried changing the get_role('contributor'); to editor as well.

Thanks, that helped me narrow it down, and I was able to edit that out using Genesis Simple Edits.

Sure: https://2lit.family/listing/sixx711/

Scratch that…I do have the File Away shortcode generator. When editing a page, you have to click the “Toolbar Toggle” button on the end, then the File Away icon shows up below it:

I don’t have a File Away shortcode generator on my pages either (I’m guessing it’s an issue with my Genesis theme). From within the plugin options, I looked at the Tutorial tab, and chose the “FileAway Attributes” tutorial. That gives you all the options for manually inserting shortcode. For example, you could insert:

[fileaway base="1" directories="on" flightbox="videos"]

Try it and report back! It only takes a couple of minutes to load and configure a page.

Thanks for the follow up. I changed my review to 4 stars, 5 upon completion of the feature. It doesn’t look like rating is being reflected yet, I’ll follow up.

Feature request for the future: would it be easier to create a CSS class that could be applied to images that would force Simple Lightbox to view them? Might be easier than building custom plugins for each image type. Cheers!

Regular Expressions are intense, but I think I found a lazy one that works. My URL has “CGIProxy.fcgi” in it, so I was able to put in this line in the custom plugin, and it works:

$ptn = '(CGIProxy\\.fcgi)';

Thanks! Solved.

Cool, looks like this will provide a solution. I’m wondering about the URI format though, is this a regular expression? I’m not exactly sure the formatting to match the URL above. Thanks for your response!

Seems like an issue with NextGen; you’d have to see why NextGen is loading an image when it’s not supposed to. I can’t imagine RSP would call another plugin that it does not know about.

I may have fixed this issue (at least it works on my plugin). The problem is in the file rsvp_frontend.inc.php. You’ll have to edit it and add a small change, then upload it back to your server.

On line 709, you’ll find this code:

$wpdb->query($wpdb->prepare("INSERT INTO ".ASSOCIATED_ATTENDEES_TABLE."(attendeeID, associatedAttendeeID)
 SELECT ".$newAid.", associatedAttendeeID
 FROM ".ASSOCIATED_ATTENDEES_TABLE."
 WHERE attendeeID = ".$attendeeID));

I replaced the last line with this:

$wpdb->query($wpdb->prepare("INSERT INTO ".ASSOCIATED_ATTENDEES_TABLE."(attendeeID, associatedAttendeeID)
 SELECT ".$newAid.", associatedAttendeeID
 FROM ".ASSOCIATED_ATTENDEES_TABLE."
 WHERE attendeeID = ".$attendeeID, $_POST['attendeeID']));

Basically adding the “, $_POST[‘attendeeID’]” within the query. After I uploaded the modified file, I stopped getting the error.

I tried contacting the plugin creator to get some feedback on the fix, but never heard back. It seems like the plugin may be dead. I moved on to Ninja Forms which has most of the functionality here. Maybe this helps someone else.