Forum Replies Created

Viewing 15 replies - 1 through 15 (of 77 total)
  • Thread Starter dzarelli

    (@dzarelli)

    Thanks for that! That was actually really close, but resulted in a 500 error on the site. I tried a few things and this is what ended up working for me:

    Renamed existing .htaccess to back it up, created new .htaccess file containing the following ONLY –

    RewriteEngine on
    RewriteCond %{HTTP_HOST} ^(.*)?blog [NC]
    RewriteRule ^(.*)$ https://blog.mydomain.com/$1 [R=301,L]

    So again, just a slight variation from what was in the article you linked. obviously, my existing instance doesn’t have a top-level domain (a .com or anything after the dns hostname) so if yours does you’d want to use that in line two. So if my original site was https://www.blog.com then the code would be:

    RewriteEngine on
    RewriteCond %{HTTP_HOST} ^(.*)?blog.com [NC]
    RewriteRule ^(.*)$ https://blog.mydomain.com/$1 [R=301,L]

    Anyway, thanks for pointing me in the right direction!

    Thread Starter dzarelli

    (@dzarelli)

    I fixed it. Apparently at some point the values for the fields changed. I confirmed the tag info was correct and used the comma/space as suggested. Looks like it’s working now. Thanks!

    Thread Starter dzarelli

    (@dzarelli)

    Sorry for the delayed response – I was on vacation.

    I changed the fields as you suggest. Example – {field:email_1525651248380}, {field:additional_email_optional_1527189629529} This didn’t seem to fix the issue.

    I still get the message “Your email action “Notification Email” has an invalid value for the “bcc” setting. Please check this setting and try again.” when submitting the form.

    Note – this worked for at least 2 years and nothing has changed in the configuration. Any advice?

    Thread Starter dzarelli

    (@dzarelli)

    I’ve resolved this issue. It was SELinux. It has to be enabled in our environment so we had to add a boolean. Alternatively if we didn’t need/want it enabled, simply disabling SELinux would’ve solved the issue as well –
    FYI – The commands to enable/disable SELinux are below
    enable:
    setenforce 1
    disable:
    setenforce 0

    A good way to test is to simple turn it off and try to run the wordpress setup wizard. If you can connect finish the setup and re-enable SELinux. If SELinux is the culprit, you will get an error establishing database connection error when you re-enable it.

    It’s probably important to note that SELinux provides important safety features and disabling it is kind of the lazy way to address the issue.
    I found this article that helped.
    https://techblog.jeppson.org/2016/10/install-wordpress-centos-7/

    and here is more information regarding SELinux and using booleans.
    https://wiki.gentoo.org/wiki/SELinux/Tutorials/Using_SELinux_booleans

    I hope this saves someone some time one day.

    • This reply was modified 5 years, 1 month ago by dzarelli.
    • This reply was modified 5 years, 1 month ago by dzarelli.
    Thread Starter dzarelli

    (@dzarelli)

    Additional content from my phpinfo. Sorry I forgot this on the last post and I can’t seem to edit it.

    Apache Version	Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.2.24
    Apache API Version	20120211
    Server Administrator	root@localhost
    Hostname:Port	ip-10-144-252-147.us-west-2.compute.internal:443
    User/Group	apache(48)/48
    Max Requests	Per Child: 0 - Keep Alive: on - Max Per Connection: 100
    Timeouts	Connection: 60 - Keep-Alive: 5
    Virtual Server	Yes
    Server Root	/etc/httpd
    Loaded Modules	core mod_so http_core mod_access_compat mod_actions mod_alias mod_allowmethods mod_auth_basic mod_auth_digest mod_authn_anon mod_authn_core mod_authn_dbd mod_authn_dbm mod_authn_file mod_authn_socache mod_authz_core mod_authz_dbd mod_authz_dbm mod_authz_groupfile mod_authz_host mod_authz_owner mod_authz_user mod_autoindex mod_cache mod_cache_disk mod_data mod_dbd mod_deflate mod_dir mod_dumpio mod_echo mod_env mod_expires mod_ext_filter mod_filter mod_headers mod_include mod_info mod_log_config mod_logio mod_mime_magic mod_mime mod_negotiation mod_remoteip mod_reqtimeout mod_rewrite mod_setenvif mod_slotmem_plain mod_slotmem_shm mod_socache_dbm mod_socache_memcache mod_socache_shmcb mod_status mod_substitute mod_suexec mod_unique_id mod_unixd mod_userdir mod_version mod_vhost_alias mod_dav mod_dav_fs mod_dav_lock mod_lua prefork mod_proxy mod_lbmethod_bybusyness mod_lbmethod_byrequests mod_lbmethod_bytraffic mod_lbmethod_heartbeat mod_proxy_ajp mod_proxy_balancer mod_proxy_connect mod_proxy_express mod_proxy_fcgi mod_proxy_fdpass mod_proxy_ftp mod_proxy_http mod_proxy_scgi mod_proxy_wstunnel mod_ssl mod_systemd mod_cgi mod_php7
    • This reply was modified 5 years, 1 month ago by dzarelli.
    Thread Starter dzarelli

    (@dzarelli)

    Thank you for the response. I think I have all the required php modules installed. PHP musqli looks like it’s installed. I ran a yum update and restarted things to see if that helped, but I’m still hitting the same issue. I ran the php script and it’s returning “Connection failed: Permission denied” however, from the same host, if I run “mysql -h blogtest-db.mydomain.com -u wordpresstest -p”, and use the same password I just specified in the script, I get access. Any thoughts on that? Below is the summary from my phpinfo if it helps. Thanks for helping out! I really appreciate it.

    System	Linux ip-10-144-252-147.us-west-2.compute.internal 3.10.0-862.3.2.el7.x86_64 #1 SMP Mon May 21 23:36:36 UTC 2018 x86_64
    Build Date	Oct 22 2019 11:28:54
    Server API	Apache 2.0 Handler
    Virtual Directory Support	disabled
    Configuration File (php.ini) Path	/etc/opt/remi/php72
    Loaded Configuration File	/etc/opt/remi/php72/php.ini
    Scan this dir for additional .ini files	/etc/opt/remi/php72/php.d
    Additional .ini files parsed	/etc/opt/remi/php72/php.d/10-opcache.ini, /etc/opt/remi/php72/php.d/20-bz2.ini, /etc/opt/remi/php72/php.d/20-calendar.ini, /etc/opt/remi/php72/php.d/20-ctype.ini, /etc/opt/remi/php72/php.d/20-curl.ini, /etc/opt/remi/php72/php.d/20-dom.ini, /etc/opt/remi/php72/php.d/20-exif.ini, /etc/opt/remi/php72/php.d/20-fileinfo.ini, /etc/opt/remi/php72/php.d/20-ftp.ini, /etc/opt/remi/php72/php.d/20-gd.ini, /etc/opt/remi/php72/php.d/20-gettext.ini, /etc/opt/remi/php72/php.d/20-iconv.ini, /etc/opt/remi/php72/php.d/20-json.ini, /etc/opt/remi/php72/php.d/20-ldap.ini, /etc/opt/remi/php72/php.d/20-mbstring.ini, /etc/opt/remi/php72/php.d/20-mysqlnd.ini, /etc/opt/remi/php72/php.d/20-pdo.ini, /etc/opt/remi/php72/php.d/20-phar.ini, /etc/opt/remi/php72/php.d/20-posix.ini, /etc/opt/remi/php72/php.d/20-shmop.ini, /etc/opt/remi/php72/php.d/20-simplexml.ini, /etc/opt/remi/php72/php.d/20-sockets.ini, /etc/opt/remi/php72/php.d/20-sqlite3.ini, /etc/opt/remi/php72/php.d/20-sysvmsg.ini, /etc/opt/remi/php72/php.d/20-sysvsem.ini, /etc/opt/remi/php72/php.d/20-sysvshm.ini, /etc/opt/remi/php72/php.d/20-tokenizer.ini, /etc/opt/remi/php72/php.d/20-xml.ini, /etc/opt/remi/php72/php.d/20-xmlwriter.ini, /etc/opt/remi/php72/php.d/20-xsl.ini, /etc/opt/remi/php72/php.d/30-mcrypt.ini, /etc/opt/remi/php72/php.d/30-mysqli.ini, /etc/opt/remi/php72/php.d/30-pdo_mysql.ini, /etc/opt/remi/php72/php.d/30-pdo_sqlite.ini, /etc/opt/remi/php72/php.d/30-wddx.ini, /etc/opt/remi/php72/php.d/30-xmlreader.ini, /etc/opt/remi/php72/php.d/30-xmlrpc.ini, /etc/opt/remi/php72/php.d/40-zip.ini, /etc/opt/remi/php72/php.d/50-mysql.ini
    PHP API	20170718
    PHP Extension	20170718
    Zend Extension	320170718
    Zend Extension Build	API320170718,NTS
    PHP Extension Build	API20170718,NTS
    Debug Build	no
    Thread Safety	disabled
    Zend Signal Handling	enabled
    Zend Memory Manager	enabled
    Zend Multibyte Support	provided by mbstring
    IPv6 Support	enabled
    DTrace Support	available, disabled
    Registered PHP Streams	https, ftps, compress.zlib, php, file, glob, data, http, ftp, compress.bzip2, phar, zip
    Registered Stream Socket Transports	tcp, udp, unix, udg, ssl, sslv3, tls, tlsv1.0, tlsv1.1, tlsv1.2
    Registered Stream Filters	zlib.*, string.rot13, string.toupper, string.tolower, string.strip_tags, convert.*, consumed, dechunk, bzip2.*, convert.iconv.*, mcrypt.*, mdecrypt.*
    Thread Starter dzarelli

    (@dzarelli)

    I’m out of office today and tomorrow but I will try to apply the permissions again recursively and I will let you know the outcome. Thanks!

    Thread Starter dzarelli

    (@dzarelli)

    Sorry, I inherited this instance. There is a pro version installed, but the license seems to be expired. I’m not sure how long it’s been expired, but it’s been at least the 2 years I’ve owned it.

    Thread Starter dzarelli

    (@dzarelli)

    Thanks for the reply András –

    I went ahead and set the folder permissions for /var/www/html to 777 prior to posting this to eliminate folder permissions from the equation. What else could I look at?

    Thread Starter dzarelli

    (@dzarelli)

    Hey Ed – Thanks for the response. We’re running PHP 7.2.14.

    Additional details –
    Linux version 2.6.32-754.10.1.el6.x86_64 ([email protected]) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-23) (GCC) CentOS release 6.6 (Final)

    Thread Starter dzarelli

    (@dzarelli)

    Thanks. Sorry for the late reply. We nuked the plugin and restored the previous version from our DR server. SO the issue was resolved rather quickly. However, I see the plugin still has updates available and I’m holding off on the until we can determine what caused the 500 errors. As for server logs. I would need to do some digging. The only error thrown on the front end was the 500 internal server error. Have you had any other reports of similar issues with the update? I’m seeing some other posts on the support forums. I also see another update was released 5 days ago. These were the only release notes I could find – https://theeventscalendar.com/announcing-the-events-calendar-4-8-0-1-event-tickets-4-10-0-1-and-event-tickets-plus-4-10-0-1/

    We are currently on 4.7.4. On WordPress 4.9.9 multisite

    Thanks!

    Thread Starter dzarelli

    (@dzarelli)

    Thanks for that. Submitted my request. You can close this ticket. Thanks

    Thread Starter dzarelli

    (@dzarelli)

    Specifically, these are the errors we are seeing when performing a PHP7.2 compatibility check.

    CM Answers Anonymous Posting
    FILE: /data/wordpress/wp-content/plugins/cm-answers-anonymous-posting/vendor/recaptchalib.php
    FOUND 4 ERRORS AFFECTING 3 LINES
    218 | ERROR | The constant “MCRYPT_MODE_CBC” is deprecated since PHP 7.1 and removed since PHP 7.2
    219 | ERROR | The constant “MCRYPT_RIJNDAEL_128” is deprecated since PHP 7.1 and removed since PHP 7.2
    221 | ERROR | Extension ‘mcrypt’ is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead
    221 | ERROR | Function mcrypt_encrypt() is deprecated since PHP 7.1 and removed since PHP 7.2; Use OpenSSL instead

    Please advise. Thank you.

    Thread Starter dzarelli

    (@dzarelli)

    Could you please advise me on the status of PHP 7.2 compatibility? I see you stated in our previous conversation that you will release a new version before 12/31/2018, but I do not see where a new version was released in over 1 month. We are using CM Answers Pro as well as CM Answers Anonymous Posting. It is active on a number of our blog sites and we are getting ready to upgrade PHP from 5.6 to 7.2. I need to know how this will impact the plugin before we proceed. Otherwise we’ll have to delete the plugin and find another solution. Please advise on the compatibility of your plugin with PHP 7.2.

    Thread Starter dzarelli

    (@dzarelli)

    Uninstalling due to lack of support.

Viewing 15 replies - 1 through 15 (of 77 total)