mamouneyya

I am having the same issue. Here is the detailed error message that I get when activating the plugin:

Plugin could not be activated because it triggered a fatal error.

Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /****/****/public_html/wp-content/plugins/wp-security-audit-log/classes/DB/ActiveRecord.php on line 62

WordPress Version: 4.1.1
PHP Version: 5.2.17

This could be a better approach:
tinymce.EditorManager.execCommand('mceAddEditor', false, id);

This is really the one missing feature of this wonderful plugin. The pop-up validation window and the need of page refresh after submitting the form are really old fashioned behaviors. Otherwise, the plugin has all of the needed features plus a superb admin interface that most developers don’t pay attention for, these days.

@keesiemeijer

What is this line exactly supposed to do?
$text = str_replace(']]>', ']]>', $text);
As I understand, it replaces every ]]> by ]]>, which are the same. If so, then it will do nothing, right?

Also, it seems to me that we could either use wp_trim_words(), or apply_filters(‘the_excerpt’, $text), but why using the both?

Man, you’re my hero! ??
I can confirm this works perfectly with Arabic names also.

Thank you from my heart! I’ll donate a few once I charge my credit card ??

Okay, I’m waiting. Thank you very much. This is an Arabic word if you want to test: ????? (and yes, it is supported everywhere in WP)

Sorry for the delayed feedback! Well, this works good except the long ugly ballon on mouse hover, which absolutely can be lived with..

Thanks for your time, shauno!

I am actually in a big trouble because of this! I have no idea what was I thinking of, but I’ve just realized that the same behavior is applicable to the field values! GOD.. how stupid I am! ?? Well, that actually makes the workaround of the freelancer that I mentioned previously completely useless!

shauno, I really know you’re busy, but I would be so thankful if you could direct me to any workaround.. even if I have to directly editing the plugin files, I would still be interested. I have to complete the project ASAP!

Actually, I see that NGG offers many scripts to choose from, not only Thickbox:
https://grab.by/b7ce
so maybe you can hook into another library we can use?

You can change the thumbnails size from plugin options, under Thumbnails tab. After saving your new dimensions there, you have to go to Manage Gallery page, check all of the galleries you have and re-generate their thumbnails.

shauno, I have another question when you have some time: How can I add the custom field values inside the pop-up windows of gallery images?

Thanks.

But, any change that will be made directly to a NGG file will be overwritten after every update for NGG plugin, right? If so, is there a better way to keep the changes safe?

A gallery within a gallery!? WE NEED TO GO DEEPER… Galleryception.

LOOOL ??

Okay, I see that there is actually a warning message when creating a new album:

Allowed characters for file and folder names are: a-z, A-Z, 0-9, -, _ )

but this is really silly. A robust plugin must not depend on users to not do a simple mistake like this. Also, it makes no sense to make users unable to create albums with Unicode labels for the directory name sake. The plugin can generate a name with random hash or whatever to use for the directory in case it was unable to use the user input, and keeps the Unicode name for the label that site guests see. At least, the plugin must check the name that was entered before creating a useless album that cannot be used at all.

UPDATE:
Hmm, looks like I got it. It seems that the plugin fails to encode Unicode names properly. The problem I was mentioning was mainly happening because of the improperly encoded (1) directory names and (2) DB paths that the plugin generates when creating an album using the name you originally set. Accessing the gallery directory via FTP I was seeing folders with names like:
%d8%aa%d8%ac%d8%b1%d9%88%d8%a8%d8%a9
and so the paths were configured inside ngg_gallery table in DB. I’ve just tried to test that with an album. I’ve directly renamed its folder and manually changed its path in DB using an Arabic name, and viola! all of the album photos become accessible.

By the way, the same thing is applicable when uploading photos. The plugin improperly encodes any non-ASCII characters using characters like %xx1, etc, so the photo/album becomes inaccessible.

Yeah. He actually didn’t touch your plugin at all. He only modified Public Uploader.