Forum Replies Created

Viewing 13 replies - 16 through 28 (of 28 total)
  • Thread Starter sgb02

    (@sgb02)

    Thanks for working on this… ??

    a) Photo date – the date the photo was taken
    b) yes I have been experimenting with a plugin (MLA) that adds the standard post categories and tags, or custom taxonomies just for images. I think both approaches have merit, but leaning toward the custom taxonomy approach.

    Thread Starter sgb02

    (@sgb02)

    Thanks for the pointer. I was able to create a custom Attachment Metadata field based on a value uploaded by WP File Upload, using the approach described above.

    This helps, but I also want to update a standard post field for an image (e.g. post_title, post_content, post_excerpt) based on an uploaded value. Can you show how to do this with MLA?

    Thread Starter sgb02

    (@sgb02)

    I have found a plugin to assist with upload called WordPress File Upload, and done some testing. It appears to have the ability to add values during the image file upload, but they are mapped in a way that does not seem to be visible to MLA custom fields rules. Any suggestions?

    Thread Starter sgb02

    (@sgb02)

    Yes I defined the following fields:
    Title
    Caption
    Description
    Photo Date
    Categories
    Tags (separate with space)

    Can you show how to map to the standard image fields, categories, tags?

    Thread Starter sgb02

    (@sgb02)

    I think its better to perform multiple upload first, view uploaded images, and then add/edit the title, description, caption, tags, categories, etc

    The key word in the original request was “automatically” – to have the folders automatically created during the upload process.

    Wouldn’t be easier if your plugin told us what it was missing ?
    I executed the following query, but not sure if openssl and curl_multi_exec is enabled.
    Can you tell me what you think?

    $ curl -V
    curl 7.54.0 (x86_64-apple-darwin16.0) libcurl/7.54.0 SecureTransport zlib/1.2.8
    Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
    Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz UnixSockets

    Thread Starter sgb02

    (@sgb02)

    Chris,

    Thanks for the quick feedback.

    I just tried it, set [textarea* your-message] but didn’t work.
    C7 green box, sent the message, and email was received…

    From: test user01 <[email protected]>
    Subject: test 17
    Category: Other
    Message Body:
    akismet-guaranteed-spam

    ??
    no joy …

    Thread Starter sgb02

    (@sgb02)

    Hi Chris,

    I’m not exactly sure what you mean by “do your-message = akismet-guaranteed-spam”. According to the C7 site, I use: [text* your-name akismet:author] to cause Akisimet to check the name field.

    So for the tests mentioned in the last post, I tried several alternatives, but none of the below worked:
    [textarea* your-message akismet:akismet-guaranteed-spam]
    [textarea* your-message akismet:guaranteed-spam]
    [textarea* your-message akismet-guaranteed-spam]

    Can you provide the exact syntax you believe will work?

    Thread Starter sgb02

    (@sgb02)

    Followup on testing:
    For the above test case, although I received the green box with the message “THANK YOU FOR YOUR MESSAGE. IT HAS BEEN SENT”, and the message is recorded in Flamingo, I never actually received the email containing the message. So I did some more testing. Below are the results after several more test cases:

    If your-name contains viagra-test-123: Contact 7 shows orange box, WAS AN ERROR.
    If your-email contains viagra-test-123: C7 green box, email msg received.
    If your-subject contains viagra-test-123: C7 green box, No email, msg in Flamingo
    If your-message contains viagra-test-123: C7 green box, email received
    If your-message contains viagra: C7 green box, email received

    So, hopefully you two can figure out how to stop spam regardless of which field it appears in, however of all these, your-subject, and your-message seem most important.

    Thread Starter sgb02

    (@sgb02)

    I just finished conducting a test using the suggestion to add the tag akismet-guaranteed-spam to the your-message field. I also have the akismet:author and akismet:author_email tags applied to the your-name and your-email fields.

    Next I typed viagra-test-123 in every field that accepted text:
    your-name = viagra-test-123
    your-email = [email protected]
    your-subject = viagra-test-123
    your-message = viagra-test-123

    After clicking submit, I received the orange box indicating “THERE WAS AN ERROR TRYING TO SEND YOUR MESSAGE…”, as expected.

    After removing the value from viagra-test-123 from your-name and substituting a valid value, I submitted the form with the rest of the values as shown above. The result was I received the green box indicating that the message was successfully sent. This was not as expected – 3 other fields contained the viagra-test-123 value, so I was hoping all (or at least 1) fields would be flagged.

    Obviously this is not what we want. If Akismet is only checking the your-name field, this is far from a useful solution. I would appreciate any guidance on how to properly setup the contact forms to check all fields for spam.

    iThemes security has at least 2 file path settings in the settings tab (one for logs, and one for backups). Make sure that the file paths you set do actually exist.

    I have another theory after realizing that my admin user does not have the problem but another user with different privileges was having the problem.

    Most of the images and other changes that were previously successfully submitted were performed by the admin. But more recently I was using a different user with less privileges.

    I have the plug-in User Role Editor installed, and the user that was having the problem has a role based on Editor, but did not have the permission Manage Options checked.

    I tested by using two different computers to test: 1) one logged in as Administrator role to change permissions, 2) another logged in with Editor role to submit changes. I have able to successfully create or fix the problem by simply unchecking or checking the Manage Options permission in the User Role Editor.

    So at least my version of the problem can be fixed by checking the Manage Options permission for the role where you are having the problem.

    I am using: WP 3.5.1 User Role Editor 3.10 (and some other plug-ins).

    I would be interested in your thoughts on the above observations, and whether adding the above User Role Editor plug-in, and manipulating the Manage Options permission is the real cause/fix.

Viewing 13 replies - 16 through 28 (of 28 total)