- TutorialsFrom WPBakery to tagDiv Composer
I ordered the newspaper theme and install in word-press but when i install a plugin called ‘really simple ssl’ … to configure ssl … it it made a conflict to another plugin called yoast seo … i need a solution to solve this conflict
or if you can recommend for me another plugin for ssl that compatible with the theme
Unfortunately from a very old version like newspaper 4, you will have to re-create the pages, widgets and settings as there were too many changes between versions for the update to go seamlessly. Newspaper 8 compared to NP4 is like a whole new theme.
Thank you!
Hi there at TagDiv,
The backend of our WP-theme Newspaper 8 has slowed down to a 40 seconds-plus loading speed when editting or creating post, pages or opening the Media Library. Also starting up TagDiv Composer on a (new) page is extremely slow. We have tried everything we could find, like disabeling all the plugins and enabeling them one for one again. Allocating more memory through wp_config.php according to TagDiv specifications, etc. Nothing seems to work. Frontend of our site is flying (well, fast loading). Restored backups of website and database a few times also. We don’t know what we can do to fix this problem. Checked PHP memory: fine, Server specs: great, so we realy need some help here.
Our newswebsite http://www.regioonline.nl is online since January, 14th 2017 using the WP Newspaper theme. We have about 1.100 post to date and approx. 4.500 images. With the theme we use the following plugins: Akismet Anti-Spam, Autoptimize, Better Delete Revision (deactivated), Contact Form 7 & Contact Form 7 add confirm, Cookie Bar, HTML Import 2, Image Watermark, Oypo (deactivated), Physical Custom Upload Dir for Real Media Library, Really Simple SSL, Yoast SEO.
We have used WP Supercache several times, but that did nothing for us. Yesterday installed and used Better Delete Revision and cleaned out redundend revisions (and set max revisions to 2 in wp_config). WP_Memory is set to 64M (even tried 512M with was possible acoording to our webhost One.com). We have a large amount of space (500GB) for our site and 8xCPU from the server. Only thing we can think of is maybe a corrupted database, but we don’t know how to check that of fix it. Enabeling repair in WP_Config did not work.
Any help is much appreciated in advance!
HTTP/2 is supported for SSL sites only because of web browsers policy, not because of any web server configuration or policy. If HTTP/2 is enabled its enabled globaly. Your comment is good but like mine its starting to get off topic 🙂 I’m sure we can both agree this thread/problem has nothing to do with TagDiv software so I will sign off here and go grab a beer!
Yes, I am well aware having managed our own servers since 1996. However *most* web hosts are requiring https for http/2 as a standard with the ‘https everywhere’ movement.
Much like Google will be warning site visitors about “site not safe” for any website with an insecure form in October. Everybody *should* be moving to https. Period. We moved all our sites to https in 2004, not just the ecom systems on sites.
Obviously anybody who can read up on the topic knows that.
My point was that somebody trying to switch on http/2 on their server as a hosting client, where the server policy is to enforce https for http/2 will have errors and perhaps generate ‘port’ errors since there will be mis-match on secure/insecure ports, much like with mod_pagespeed couple years back (2013? wow time flies!) with mixed content.
server certificate does NOT include an ID which matches the server name
For example on a Plesk/ONYX server, “Make sure that SSL support is enabled for the web site in the Hosting Settings section of the domain. HTTP/2 is supported for SSL sites only, so non-SSL sites will continue to work under HTTP /1.x. That is a restriction of nginx web server and web browsers.”
My comment was intended for the OP who might not understand what he/she is actually doing with this process.
Cheers.
Technically speaking, HTTP/2 does not require https to work, its just that all of the ‘popular’ browsers decided that they would only recognise HTTP/2 if the connection was over TLS/SSL, in other words a url beginning https://
Thank you Chris and iisnet for suggestion.
Ngnix Error log :
2017/09/09 01:24:17 [emerg] 17449#0: invalid port in “|IP|:|PORT_80|” of the “listen” directive in /etc/nginx/nginx-vhosts.conf:2
2017/09/09 01:41:37 [notice] 27734#0: signal process started
2017/09/09 01:53:43 [emerg] 31974#0: “http2_recv_buffer_size” directive is not allowed here in /usr/local/directadmin/data/users/iphoneap/nginx.conf:158
2017/09/09 02:00:00 [emerg] 33430#0: “ssl_prefer_server_ciphers” directive is duplicate in /etc/nginx/nginx-defaults.conf:29
2017/09/09 02:02:25 [emerg] 34094#0: “http2_recv_buffer_size” directive is not allowed here in /etc/nginx/nginx-events.conf:3
2017/09/09 02:07:27 [emerg] 36405#0: “http2_recv_buffer_size” directive is not allowed here in /usr/local/directadmin/data/users/iphoneap/nginx.conf:165
2017/09/09 02:10:12 [notice] 37055#0: signal process started
2017/09/09 02:10:33 [emerg] 37086#0: “ssl_session_cache” directive is not allowed here in /etc/nginx/nginx.conf:32
2017/09/09 02:10:48 [emerg] 37102#0: “ssl_session_cache” directive is not allowed here in /etc/nginx/nginx.conf:33
2017/09/09 02:12:17 [emerg] 37739#0: “ssl_ciphers” directive is duplicate in /usr/local/directadmin/data/users/iphoneap/nginx.conf:165
2017/09/09 02:13:25 [emerg] 37758#0: “ssl_ciphers” directive is duplicate in /usr/local/directadmin/data/users/iphoneap/nginx.conf:165
2017/09/09 02:14:10 [notice] 37780#0: signal process started
Apache error log :
[Sat Sep 09 01:23:42.120248 2017] [lbmethod_heartbeat:notice] [pid 11995:tid 139905954351040] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 01:23:42.125643 2017] [mpm_event:notice] [pid 11995:tid 139905954351040] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 01:23:42.125796 2017] [core:notice] [pid 11995:tid 139905954351040] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 01:24:02.112928 2017] [mpm_event:notice] [pid 11995:tid 139905954351040] AH00491: caught SIGTERM, shutting down
[Sat Sep 09 01:24:03.016122 2017] [ssl:warn] [pid 15545:tid 140326462146496] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 01:24:03.016363 2017] [suexec:notice] [pid 15545:tid 140326462146496] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 01:24:04.018052 2017] [ssl:warn] [pid 15778:tid 140326462146496] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 01:24:04.018415 2017] [lbmethod_heartbeat:notice] [pid 15778:tid 140326462146496] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 01:24:04.023933 2017] [mpm_event:notice] [pid 15778:tid 140326462146496] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 01:24:04.023993 2017] [core:notice] [pid 15778:tid 140326462146496] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 01:25:05.290881 2017] [core:warn] [pid 15778:tid 140326462146496] AH00045: child process 15878 still did not exit, sending a SIGTERM
[Sat Sep 09 01:25:07.293462 2017] [core:warn] [pid 15778:tid 140326462146496] AH00045: child process 15878 still did not exit, sending a SIGTERM
[Sat Sep 09 01:25:09.296005 2017] [core:warn] [pid 15778:tid 140326462146496] AH00045: child process 15878 still did not exit, sending a SIGTERM
[Sat Sep 09 01:25:11.298634 2017] [core:error] [pid 15778:tid 140326462146496] AH00046: child process 15878 still did not exit, sending a SIGKILL
[Sat Sep 09 01:25:13.029095 2017] [ssl:warn] [pid 18343:tid 139953176242112] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 01:25:13.029744 2017] [suexec:notice] [pid 18343:tid 139953176242112] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 01:25:14.030280 2017] [ssl:warn] [pid 18344:tid 139953176242112] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 01:25:14.031241 2017] [lbmethod_heartbeat:notice] [pid 18344:tid 139953176242112] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 01:25:14.036995 2017] [mpm_event:notice] [pid 18344:tid 139953176242112] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 01:25:14.037132 2017] [core:notice] [pid 18344:tid 139953176242112] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 01:41:34.756846 2017] [mpm_event:notice] [pid 18344:tid 139953176242112] AH00491: caught SIGTERM, shutting down
[Sat Sep 09 01:41:35.024534 2017] [ssl:warn] [pid 26515:tid 140620780279744] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 01:41:35.024966 2017] [suexec:notice] [pid 26515:tid 140620780279744] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 01:41:36.023928 2017] [ssl:warn] [pid 26516:tid 140620780279744] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 01:41:36.024558 2017] [lbmethod_heartbeat:notice] [pid 26516:tid 140620780279744] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 01:41:36.028734 2017] [mpm_event:notice] [pid 26516:tid 140620780279744] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 01:41:36.028832 2017] [core:notice] [pid 26516:tid 140620780279744] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 01:42:01.932602 2017] [mpm_event:notice] [pid 26516:tid 140620780279744] AH00491: caught SIGTERM, shutting down
[Sat Sep 09 01:42:03.034675 2017] [ssl:warn] [pid 28477:tid 140484163475392] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 01:42:03.035083 2017] [suexec:notice] [pid 28477:tid 140484163475392] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 01:42:04.024878 2017] [ssl:warn] [pid 28633:tid 140484163475392] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 01:42:04.025532 2017] [lbmethod_heartbeat:notice] [pid 28633:tid 140484163475392] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 01:42:04.029876 2017] [mpm_event:notice] [pid 28633:tid 140484163475392] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 01:42:04.029980 2017] [core:notice] [pid 28633:tid 140484163475392] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 02:07:21.651181 2017] [mpm_event:notice] [pid 28633:tid 140484163475392] AH00491: caught SIGTERM, shutting down
[Sat Sep 09 02:07:23.034233 2017] [ssl:warn] [pid 35388:tid 139899561912256] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:07:23.034799 2017] [suexec:notice] [pid 35388:tid 139899561912256] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 02:07:24.027120 2017] [ssl:warn] [pid 35389:tid 139899561912256] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:07:24.027755 2017] [lbmethod_heartbeat:notice] [pid 35389:tid 139899561912256] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 02:07:24.031754 2017] [mpm_event:notice] [pid 35389:tid 139899561912256] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 02:07:24.031878 2017] [core:notice] [pid 35389:tid 139899561912256] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 02:28:35.783040 2017] [mpm_event:notice] [pid 35389:tid 139899561912256] AH00491: caught SIGTERM, shutting down
[Sat Sep 09 02:28:36.031744 2017] [ssl:warn] [pid 42717:tid 140341112342464] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:28:36.032293 2017] [suexec:notice] [pid 42717:tid 140341112342464] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 02:28:37.032200 2017] [ssl:warn] [pid 42718:tid 140341112342464] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:28:37.068635 2017] [lbmethod_heartbeat:notice] [pid 42718:tid 140341112342464] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 02:28:37.074005 2017] [mpm_event:notice] [pid 42718:tid 140341112342464] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 02:28:37.074120 2017] [core:notice] [pid 42718:tid 140341112342464] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 02:29:01.528582 2017] [mpm_event:notice] [pid 42718:tid 140341112342464] AH00491: caught SIGTERM, shutting down
[Sat Sep 09 02:29:02.029127 2017] [ssl:warn] [pid 44571:tid 140116376684480] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:29:02.029517 2017] [suexec:notice] [pid 44571:tid 140116376684480] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 02:29:03.024589 2017] [ssl:warn] [pid 44572:tid 140116376684480] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:29:03.025264 2017] [lbmethod_heartbeat:notice] [pid 44572:tid 140116376684480] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 02:29:03.029263 2017] [mpm_event:notice] [pid 44572:tid 140116376684480] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 02:29:03.029368 2017] [core:notice] [pid 44572:tid 140116376684480] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 02:37:01.302801 2017] [mpm_event:notice] [pid 44572:tid 140116376684480] AH00491: caught SIGTERM, shutting down
[Sat Sep 09 02:37:02.038732 2017] [ssl:warn] [pid 48959:tid 140679153174464] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:37:02.039366 2017] [suexec:notice] [pid 48959:tid 140679153174464] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 02:37:03.208799 2017] [ssl:warn] [pid 49033:tid 140679153174464] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:37:03.215742 2017] [lbmethod_heartbeat:notice] [pid 49033:tid 140679153174464] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 02:37:03.224586 2017] [mpm_event:notice] [pid 49033:tid 140679153174464] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 02:37:03.224711 2017] [core:notice] [pid 49033:tid 140679153174464] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 02:37:04.079119 2017] [mpm_event:notice] [pid 49033:tid 140679153174464] AH00491: caught SIGTERM, shutting down
[Sat Sep 09 02:37:05.024942 2017] [ssl:warn] [pid 50236:tid 140183365179328] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:37:05.025329 2017] [suexec:notice] [pid 50236:tid 140183365179328] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 02:37:06.024682 2017] [ssl:warn] [pid 50237:tid 140183365179328] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:37:06.025350 2017] [lbmethod_heartbeat:notice] [pid 50237:tid 140183365179328] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 02:37:06.029407 2017] [mpm_event:notice] [pid 50237:tid 140183365179328] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 02:37:06.029516 2017] [core:notice] [pid 50237:tid 140183365179328] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 02:38:01.674441 2017] [mpm_event:notice] [pid 50237:tid 140183365179328] AH00491: caught SIGTERM, shutting down
[Sat Sep 09 02:38:02.031666 2017] [ssl:warn] [pid 52084:tid 139651287865280] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:38:02.032251 2017] [suexec:notice] [pid 52084:tid 139651287865280] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 02:38:03.028882 2017] [ssl:warn] [pid 52085:tid 139651287865280] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:38:03.029525 2017] [lbmethod_heartbeat:notice] [pid 52085:tid 139651287865280] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 02:38:03.033530 2017] [mpm_event:notice] [pid 52085:tid 139651287865280] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 02:38:03.033676 2017] [core:notice] [pid 52085:tid 139651287865280] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 02:53:18.402870 2017] [mpm_event:notice] [pid 52085:tid 139651287865280] AH00491: caught SIGTERM, shutting down
[Sat Sep 09 02:53:19.024614 2017] [ssl:warn] [pid 57937:tid 140257448908736] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:53:19.025001 2017] [suexec:notice] [pid 57937:tid 140257448908736] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 02:53:20.024446 2017] [ssl:warn] [pid 57938:tid 140257448908736] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:53:20.025144 2017] [lbmethod_heartbeat:notice] [pid 57938:tid 140257448908736] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 02:53:20.029182 2017] [mpm_event:notice] [pid 57938:tid 140257448908736] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 02:53:20.029274 2017] [core:notice] [pid 57938:tid 140257448908736] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 02:54:02.940309 2017] [mpm_event:notice] [pid 57938:tid 140257448908736] AH00491: caught SIGTERM, shutting down
[Sat Sep 09 02:54:04.027340 2017] [ssl:warn] [pid 60097:tid 139656345204672] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:54:04.027742 2017] [suexec:notice] [pid 60097:tid 139656345204672] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Sep 09 02:54:05.029765 2017] [ssl:warn] [pid 60098:tid 139656345204672] AH01909: http://www.example.com:8081:0 server certificate does NOT include an ID which matches the server name
[Sat Sep 09 02:54:05.030538 2017] [lbmethod_heartbeat:notice] [pid 60098:tid 139656345204672] AH02282: No slotmem from mod_heartmonitor
[Sat Sep 09 02:54:05.035379 2017] [mpm_event:notice] [pid 60098:tid 139656345204672] AH00489: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips configured — resuming normal operations
[Sat Sep 09 02:54:05.035488 2017] [core:notice] [pid 60098:tid 139656345204672] AH00094: Command line: ‘/usr/sbin/httpd’
[Sat Sep 09 10:09:57.219760 2017] [proxy_fcgi:error] [pid 60164:tid 139655249704704] [client 127.0.0.1:25420] AH01071: Got error ‘Primary script unknown\n’, referer: http://ping.rootblog.com/rpc.php
[Sat Sep 09 10:09:57.224718 2017] [proxy_fcgi:error] [pid 60164:tid 139655041206016] [client 127.0.0.1:25424] AH01071: Got error ‘Primary script unknown\n’, referer: http://ping.rootblog.com/rpc.php
[Sat Sep 09 11:01:34.982918 2017] [proxy_fcgi:error] [pid 60164:tid 139654831408896] [client 127.0.0.1:34114] AH01071: Got error ‘Primary script unknown\n’, referer: http://ping.rootblog.com/rpc.php
[Sat Sep 09 11:01:34.996518 2017] [proxy_fcgi:error] [pid 60164:tid 139654537692928] [client 127.0.0.1:34118] AH01071: Got error ‘Primary script unknown\n’, referer: http://ping.rootblog.com/rpc.php
[Sat Sep 09 11:50:19.836039 2017] [proxy_fcgi:error] [pid 60179:tid 139655114635008] [client 127.0.0.1:42496] AH01071: Got error ‘Primary script unknown\n’, referer: http://ping.rootblog.com/rpc.php
[Sat Sep 09 11:50:19.877037 2017] [proxy_fcgi:error] [pid 60179:tid 139654894348032] [client 127.0.0.1:42500] AH01071: Got error ‘Primary script unknown\n’, referer: http://ping.rootblog.com/rpc.php
[Sat Sep 09 13:01:58.035685 2017] [proxy_fcgi:error] [pid 46079:tid 139654835709696] [client 127.0.0.1:53248] AH01071: Got error ‘Primary script unknown\n’, referer: http://ping.rootblog.com/rpc.php
[Sat Sep 09 13:01:58.041250 2017] [proxy_fcgi:error] [pid 46079:tid 139654846199552] [client 127.0.0.1:53252] AH01071: Got error ‘Primary script unknown\n’, referer: http://ping.rootblog.com/rpc.php
[Sat Sep 09 13:18:11.781190 2017] [proxy_fcgi:error] [pid 46079:tid 139654269257472] [client 127.0.0.1:55580] AH01071: Got error ‘Primary script unknown\n’, referer: http://ping.rootblog.com/rpc.php
[Sat Sep 09 13:18:11.785528 2017] [proxy_fcgi:error] [pid 46079:tid 139654825219840] [client 127.0.0.1:55584] AH01071: Got error ‘Primary script unknown\n’, referer: http://ping.rootblog.com/rpc.php
yes, my site use HTTPS (SSL) along with PHP 7.1. Thank you for your advice . I will check server error log.
Hello,
I know this question might not fully relate to you but I thought of asking you as well.
Yesterday I bought an SSl certificate for my but it still doesn’t display
the padlock and https on the browser.
According to my hosting service, Hostgator, this is what they say, ‘There are non-secure items on your website and this is the reason you are receiving the orange lock. This can be fixed by updating your image and page links to include the HTTPS prefix. Once all non-secure items are updated, this should fix the broken padlock.’
Well I was wondering whether there’s a solution you know, or a plugin that can fix this issue.
Thank you
Nevein
I have a problem. I have created custom code, with .class, for many modules at home. Some of these classes are to increase the title font size. The problem is that from the mobile with the plug-in Tag Div Mobile theme activated, it continues to load those classes and the font size come out disproportionate, for example.
Is there a way for mobile to ignore the custom code classes I have applied to the modules in the desktop/ normal version?
Or:
Is there any option for the mobile to load another alternative homepage that I would create expressly without applying custom code to the modules
The problem only affects the homepage
Hi, I have just installed the Newspaper theme and are currently working on the set-up in a staging enviroment. I have enabled SSL, but there is a strange mixed content error message that is giving me some trouble.
In source code under:
<!– Header style compiled by theme –>
There is a code section that looks like this:
.td-menu-background,
.td-search-background {
background-image: url(‘http://153449-www.web.tornado-node.net/wp-content/uploads/2017/09/10.jpg’);
}
So obvious this is the cause of the mixed content error, but I cant really find the settings that apply for this specific code. I have tried almost every setting and combinations of settings in the theme admin section with no luck.
I need some advice on this matter.
/ Daniel
I need some guidance on what is/is not affected by updating. The help documentation and videos are ambiguous, imo good examples of information being provided by people who already know the answers and find it difficult to put themselves in the mindset of people who don’t. My points may seems obvious to tech people, but are not to me, and judging by the number of post-update-panic-posts in the forums, they are not to many other users too.
For me, upgrading to 8.0 went from the quick and easily hour set aside indicated by the video, to a weekend of my life I will never see again. I want to avoid the same again. By example in your docs it says “Once you activate a different theme, delete the Newspaper theme. Don’t worry, your content will not be lost.” The documentation also mentions code. But nowhere does it mention the effect on the hugely important and time consuming settings?
So i would appreciate it if you could clarify which of these headings will be affected by updating (and ideally any steps to be taken post update). I’ve started with the two I think I am clear on …
EFFECT OF UPDATING
Bespoke Code (including, but not necessarily limited to, anything entered into theme panel/custom code and theme panel/mobile theme/custom code): All will be overwritten. Must be copied out and re-applied.
Content (posts and pages): No effect, all will be retained.
Theme Panel Settings (all under header, footer, ads, layout and misc): ??? (if they are affected can the export/import settings tool be used – it states ‘to copy to another server’, and does not specify whether it would work between different theme versions. Is there anything not included in that settings export?
Mobile Theme: ???
Visual and TagDiv Pagebuilder elements used on posts & pages: ???
Demo Theme: ???
Licence key/activation: ???
METHOD OF UPDATING
in the documentation it gives alternative methods of updating, without any indication any are better than others. However i have noticed that in the forum when problems occur it is often stated that people should re-upgrade using the ftp method. does this indicate that the ftp method is more stable/reliable way of updating? I expect many of us will go for what appears the easiest method (wordpress) but if we knew ftp was a better way would jump through the extra hoops to do it that way.
I hope you can see that armed with that information I can see whether the benefits of an upgrade are worth the potential hassle, and also get a better idea of the realistic time it will take.
Thank you.
Hi awesome people at TagDiv,
I still have ‘Newspaper theme’ installed on my primary website and I am indeed proud of it. It still looks much better than any other news/magazine themes available in the market.
But with the recent advancement in the content industry, there are few features which are slowly becoming the MUST for all the modern day’s news websites and I am sad to say that TagDiv team works very slow with the updating the theme with major feature enhancements.
I know that whenever we ask about the feature updates, the team says that they have a lot of bug backlogs, security features, and other fixes to look at before actually adding any new features to combat the modern website needs and features adopted by other websites.
But then, it’s kind of sad because it means that either your current themes are highly imperfect ( so you always need more time for the improvements, security fixes) or the developers are very slow in the developments process.
I am sure that the first option is totally untrue since your themes are really highly stable, bug-free and awesome but then I have to think about the second option to blame the slow process of adding new feature updates.
The reason I am saying this more emphatically is because almost after 2 months of purchasing ‘NewsPaper theme’ , I had purchased a new theme called ‘Bimber’ by ‘BringThePixel’ team and I must say that within 6-7 months of having them for one of my projects, they have made lots and lots of super awesome feature updates that I am still only dreaming here with NewsPaper ( alongwith fixing old issues)
After almost every two months, they do some major updates. In their very recent major update ( today itself), they have also included ‘Auto Load Next Post’ along with many other new features. Here is one snapshot of their very recent update list:

There are hundreds of threads here asking for the ‘Auto load next post’ feature in newspaper theme. I have also noticed that now many major news sites like thenextweb.com, vice.com, Quint.com etc. have already included ‘Auto-load next post’ in last two months on their site. With millions of social media users on the internet. People are now more used to the habit of keep scrolling endlessly for news/contents till they find something interesting and hence it’s almost mandatory now for other news sites as well for more traffic and low bounce rate.
Many other features like ‘creating trivia, personality quizzes, more robust ad-management, sticky share buttons, watermarks can also make our Newspaper theme super awesome.
Newspaper theme has always been Payoneer in bringing the most advanced features needed to bring more traffic, stability and optimisation to the news/magazine theme industry and I do want TagDiv to continue this culture of being the best and top-notch.
So, please please work on new features, at-least this ‘Auto load next post’ thing to not let us feel inferior in the current content world. Also, if possible, make a page for the public roadmap of the features you want to include in the future updates where users/members can upvote to prioritize the features for the next update. In the start-up world, this culture of making a public roadmap is very much famous and really helpful in creating a more robust and user-friendly product/tools/services.
Hope you understand and take this message positively.
Looking forward to the good news 🙂 #LoveForTagDiv
Thank you.
Getting this error while to install the required plugin.
The plugin does not have a valid header.
Download failed. cURL error 60: SSL certificate problem: self signed certificate
Thanks Chris.. It worked flawlessly!
Hi @Lordemma,
Okay – Solution found (for me anyway). This was the specific issue in my case, though it may not be specific to your issues. I also had some other peripheral issues that were specific to the use of SSL on my site, which were mitigated by ensuring that I had “https” set in the Settings->General->Wordpress URL settings in the WP Dashboard (you might like to look into this if you have other issues with the TAGDiv composer showing blank pages).
In all cases – with respect to the saving loop – my issues were all related to the “.user.ini” file.
The problem with the Saving Loop was actually with WordFence (in my case), which is not installed as a plugin in this particular case, but in another installation on the same host, which was installed in the default “public_html” directory. This installation of WP is in a subdirectory, but the “.user.ini” file which is created in the default “public_html” directory overrides things.
In all cases, WordFence adds the following to the “.user.ini” file:
; Wordfence WAF
auto_prepend_file = ‘/public_html/wordfence-waf.php’
; END Wordfence WAF
Removing this, solved the issue.
Of course, it will create other issues for the site that uses WordFence, but I will have to resolve that another way.
For now, and in case anyone else may have run into similar issues – this is the solution that worked for me.
I suppose it makes an argument for putting all WP installations into their own subdirectories. For whatever reason, the original installation of the main domain in this case, was installed in the PUBLIC_HTML directory by default, and this was the source of the issue.
Hope this might help anyone with a similar issue.
*update*
If you are using WordFence – you can check to ensure your ‘Whitelist’ IP addresses and so forth to ensure your WordFence installation is not blocking your access.
@lordemma – I spent a very long time trying multiple solutions to this problem, so if you haven’t solved it yet, let me know, as perhaps some of things I experienced and have gone through can be of assistance to you in solving your issue.
Can someone please tell me how do I edit the social networks section found in the theme panel? It asks for unique URL for whichever social network icons I want in the top menu and in the footer. The problem is with the URL redirection. For instance, if the unique URL for TOMMY on Instagram is instagram.com/tommy and if I enter the same in the space available for Instagram unique URL in social networks then it does not opens the Instagram page. Clicking on the Instagram social icon (whether in the top menu or footer) throws a 404 error because it tries to go the URL: yoursite.com/instagram.com/tommy or yoursite.com/tommy which of course does not exist because it tries to find that page within the blog instead of opening the Instagram page. This applies to every unique URL that I put in the social networks section, it actually never opens the specific social networking site whereas the social counter plugin works flawlessly. Please throw some light on this aspect and show what am I missing here.

Thank you!
Hi,
I’ve been trying to send emails from the site but get the following error message. And also get error message stating unable to send mails while signing up as new user.
“Test Message Sent
The result was:
bool(false)
The full debugging output is shown below:
object(PHPMailer)#739 (76) {
[“Version”]=>
string(6) “5.2.22”
[“Priority”]=>
NULL
[“CharSet”]=>
string(5) “UTF-8”
[“ContentType”]=>
string(10) “text/plain”
[“Encoding”]=>
string(4) “7bit”
[“ErrorInfo”]=>
string(638) “The following From address failed: support@answersby.com : MAIL FROM command failed,Authentication Required. Learn more at
https://support.google.com/mail/?p=WantAuthError 188sm5791238pgd.20 – gsmtp
,530,5.5.1SMTP server error: MAIL FROM command failed Detail: Authentication Required. Learn more at
https://support.google.com/mail/?p=WantAuthError 188sm5791238pgd.20 – gsmtp
SMTP code: 530 Additional SMTP info: 5.5.1SMTP server error: MAIL FROM command failed Detail: Authentication Required. Learn more at
https://support.google.com/mail/?p=WantAuthError 188sm5791238pgd.20 – gsmtp
SMTP code: 530 Additional SMTP info: 5.5.1”
[“From”]=>
string(21) “support@answersby.com”
[“FromName”]=>
string(17) “AnswersBy support”
[“Sender”]=>
string(0) “”
[“ReturnPath”]=>
string(0) “”
[“Subject”]=>
string(63) “WP Mail SMTP: Test mail to vishnuprakash.a@sutherlandglobal.com”
[“Body”]=>
string(68) “This is a test email generated by the WP Mail SMTP WordPress plugin.”
[“AltBody”]=>
string(0) “”
[“Ical”]=>
string(0) “”
[“MIMEBody”:protected]=>
string(69) “This is a test email generated by the WP Mail SMTP WordPress plugin.
”
[“MIMEHeader”:protected]=>
string(395) “Date: Tue, 29 Aug 2017 19:35:44 +0000
To: vishnuprakash.a@sutherlandglobal.com
From: AnswersBy support
Subject: WP Mail SMTP: Test mail to vishnuprakash.a@sutherlandglobal.com
Message-ID: <61716cf89477db026f2a7a83fce15072@mypremiumsupport.com>
X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
”
[“mailHeader”:protected]=>
string(0) “”
[“WordWrap”]=>
int(0)
[“Mailer”]=>
string(4) “smtp”
[“Sendmail”]=>
string(18) “/usr/sbin/sendmail”
[“UseSendmailOptions”]=>
bool(true)
[“PluginDir”]=>
string(0) “”
[“ConfirmReadingTo”]=>
string(0) “”
[“Hostname”]=>
string(0) “”
[“MessageID”]=>
string(0) “”
[“MessageDate”]=>
string(31) “Tue, 29 Aug 2017 19:35:44 +0000”
[“Host”]=>
string(14) “smtp.gmail.com”
[“Port”]=>
string(3) “465”
[“Helo”]=>
string(0) “”
[“SMTPSecure”]=>
string(3) “ssl”
[“SMTPAutoTLS”]=>
bool(true)
[“SMTPAuth”]=>
bool(false)
[“SMTPOptions”]=>
array(0) {
}
[“Username”]=>
string(0) “”
[“Password”]=>
string(0) “”
[“AuthType”]=>
string(0) “”
[“Realm”]=>
string(0) “”
[“Workstation”]=>
string(0) “”
[“Timeout”]=>
int(300)
[“SMTPDebug”]=>
bool(true)
[“Debugoutput”]=>
string(4) “echo”
[“SMTPKeepAlive”]=>
bool(false)
[“SingleTo”]=>
bool(false)
[“SingleToArray”]=>
array(0) {
}
[“do_verp”]=>
bool(false)
[“AllowEmpty”]=>
bool(false)
[“LE”]=>
string(1) ”
”
[“DKIM_selector”]=>
string(0) “”
[“DKIM_identity”]=>
string(0) “”
[“DKIM_passphrase”]=>
string(0) “”
[“DKIM_domain”]=>
string(0) “”
[“DKIM_private”]=>
string(0) “”
[“DKIM_private_string”]=>
string(0) “”
[“action_function”]=>
string(0) “”
[“XMailer”]=>
string(0) “”
[“smtp”:protected]=>
object(SMTP)#851 (14) {
[“Version”]=>
string(6) “5.2.22”
[“SMTP_PORT”]=>
int(25)
[“CRLF”]=>
string(2) ”
”
[“do_debug”]=>
bool(true)
[“Debugoutput”]=>
string(4) “echo”
[“do_verp”]=>
bool(false)
[“Timeout”]=>
int(300)
[“Timelimit”]=>
int(300)
[“smtp_transaction_id_patterns”:protected]=>
array(3) {
[“exim”]=>
string(21) “/[0-9]{3} OK id=(.*)/”
[“sendmail”]=>
string(29) “/[0-9]{3} 2.0.0 (.*) Message/”
[“postfix”]=>
string(35) “/[0-9]{3} 2.0.0 Ok: queued as (.*)/”
}
[“smtp_conn”:protected]=>
resource(308) of type (stream)
[“error”:protected]=>
array(4) {
[“error”]=>
string(24) “MAIL FROM command failed”
[“detail”]=>
string(118) “Authentication Required. Learn more at
https://support.google.com/mail/?p=WantAuthError 188sm5791238pgd.20 – gsmtp
”
[“smtp_code”]=>
string(3) “530”
[“smtp_code_ex”]=>
string(5) “5.5.1”
}
[“helo_rply”:protected]=>
string(222) “250-smtp.gmail.com at your service, [40.83.185.163]
250-SIZE 35882577
250-8BITMIME
250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-CHUNKING
250 SMTPUTF8
”
[“server_caps”:protected]=>
array(8) {
[“EHLO”]=>
string(14) “smtp.gmail.com”
[“SIZE”]=>
string(8) “35882577”
[“8BITMIME”]=>
bool(true)
[“AUTH”]=>
array(6) {
[0]=>
string(5) “LOGIN”
[1]=>
string(5) “PLAIN”
[2]=>
string(7) “XOAUTH2”
[3]=>
string(17) “PLAIN-CLIENTTOKEN”
[4]=>
string(11) “OAUTHBEARER”
[5]=>
string(6) “XOAUTH”
}
[“ENHANCEDSTATUSCODES”]=>
bool(true)
[“PIPELINING”]=>
bool(true)
[“CHUNKING”]=>
bool(true)
[“SMTPUTF8”]=>
bool(true)
}
[“last_reply”:protected]=>
string(138) “530-5.5.1 Authentication Required. Learn more at
530 5.5.1 https://support.google.com/mail/?p=WantAuthError 188sm5791238pgd.20 – gsmtp
”
}
[“to”:protected]=>
array(1) {
[0]=>
array(2) {
[0]=>
string(36) “vishnuprakash.a@sutherlandglobal.com”
[1]=>
string(0) “”
}
}
[“cc”:protected]=>
array(0) {
}
[“bcc”:protected]=>
array(0) {
}
[“ReplyTo”:protected]=>
array(0) {
}
[“all_recipients”:protected]=>
array(1) {
[“vishnuprakash.a@sutherlandglobal.com”]=>
bool(true)
}
[“RecipientsQueue”:protected]=>
array(0) {
}
[“ReplyToQueue”:protected]=>
array(0) {
}
[“attachment”:protected]=>
array(0) {
}
[“CustomHeader”:protected]=>
array(0) {
}
[“lastMessageID”:protected]=>
string(55) “<61716cf89477db026f2a7a83fce15072@mypremiumsupport.com>”
[“message_type”:protected]=>
string(5) “plain”
[“boundary”:protected]=>
array(3) {
[1]=>
string(35) “b1_61716cf89477db026f2a7a83fce15072”
[2]=>
string(35) “b2_61716cf89477db026f2a7a83fce15072”
[3]=>
string(35) “b3_61716cf89477db026f2a7a83fce15072”
}
[“language”:protected]=>
array(19) {
[“authenticate”]=>
string(35) “SMTP Error: Could not authenticate.”
[“connect_host”]=>
string(43) “SMTP Error: Could not connect to SMTP host.”
[“data_not_accepted”]=>
string(30) “SMTP Error: data not accepted.”
[“empty_message”]=>
string(18) “Message body empty”
[“encoding”]=>
string(18) “Unknown encoding: ”
[“execute”]=>
string(19) “Could not execute: ”
[“file_access”]=>
string(23) “Could not access file: ”
[“file_open”]=>
string(33) “File Error: Could not open file: ”
[“from_failed”]=>
string(35) “The following From address failed: ”
[“instantiate”]=>
string(36) “Could not instantiate mail function.”
[“invalid_address”]=>
string(17) “Invalid address: ”
[“mailer_not_supported”]=>
string(25) ” mailer is not supported.”
[“provide_address”]=>
string(54) “You must provide at least one recipient email address.”
[“recipients_failed”]=>
string(45) “SMTP Error: The following recipients failed: ”
[“signing”]=>
string(15) “Signing Error: ”
[“smtp_connect_failed”]=>
string(22) “SMTP connect() failed.”
[“smtp_error”]=>
string(19) “SMTP server error: ”
[“variable_set”]=>
string(30) “Cannot set or reset variable: ”
[“extension_missing”]=>
string(19) “Extension missing: ”
}
[“error_count”:protected]=>
int(3)
[“sign_cert_file”:protected]=>
string(0) “”
[“sign_key_file”:protected]=>
string(0) “”
[“sign_extracerts_file”:protected]=>
string(0) “”
[“sign_key_pass”:protected]=>
string(0) “”
[“exceptions”:protected]=>
bool(true)
[“uniqueid”:protected]=>
string(32) “61716cf89477db026f2a7a83fce15072”
}
The SMTP debugging output is shown below:
2017-08-29 19:35:44 Connection: opening to ssl://smtp.gmail.com:465, timeout=300, options=array (
)
2017-08-29 19:35:45 Connection: opened
2017-08-29 19:35:45 SMTP -> get_lines(): $data is “”
2017-08-29 19:35:45 SMTP -> get_lines(): $str is “220 smtp.gmail.com ESMTP 188sm5791238pgd.20 – gsmtp
”
2017-08-29 19:35:45 SERVER -> CLIENT: 220 smtp.gmail.com ESMTP 188sm5791238pgd.20 – gsmtp
2017-08-29 19:35:45 CLIENT -> SERVER: EHLO mypremiumsupport.com
2017-08-29 19:35:45 SMTP -> get_lines(): $data is “”
2017-08-29 19:35:45 SMTP -> get_lines(): $str is “250-smtp.gmail.com at your service, [40.83.185.163]
”
2017-08-29 19:35:45 SMTP -> get_lines(): $data is “250-smtp.gmail.com at your service, [40.83.185.163]
”
2017-08-29 19:35:45 SMTP -> get_lines(): $str is “250-SIZE 35882577
”
2017-08-29 19:35:45 SMTP -> get_lines(): $data is “250-smtp.gmail.com at your service, [40.83.185.163]
250-SIZE 35882577
”
2017-08-29 19:35:45 SMTP -> get_lines(): $str is “250-8BITMIME
”
2017-08-29 19:35:45 SMTP -> get_lines(): $data is “250-smtp.gmail.com at your service, [40.83.185.163]
250-SIZE 35882577
250-8BITMIME
”
2017-08-29 19:35:45 SMTP -> get_lines(): $str is “250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
”
2017-08-29 19:35:45 SMTP -> get_lines(): $data is “250-smtp.gmail.com at your service, [40.83.185.163]
250-SIZE 35882577
250-8BITMIME
250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
”
2017-08-29 19:35:45 SMTP -> get_lines(): $str is “250-ENHANCEDSTATUSCODES
”
2017-08-29 19:35:45 SMTP -> get_lines(): $data is “250-smtp.gmail.com at your service, [40.83.185.163]
250-SIZE 35882577
250-8BITMIME
250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
250-ENHANCEDSTATUSCODES
”
2017-08-29 19:35:45 SMTP -> get_lines(): $str is “250-PIPELINING
”
2017-08-29 19:35:45 SMTP -> get_lines(): $data is “250-smtp.gmail.com at your service, [40.83.185.163]
250-SIZE 35882577
250-8BITMIME
250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
250-ENHANCEDSTATUSCODES
250-PIPELINING
”
2017-08-29 19:35:45 SMTP -> get_lines(): $str is “250-CHUNKING
”
2017-08-29 19:35:45 SMTP -> get_lines(): $data is “250-smtp.gmail.com at your service, [40.83.185.163]
250-SIZE 35882577
250-8BITMIME
250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-CHUNKING
”
2017-08-29 19:35:45 SMTP -> get_lines(): $str is “250 SMTPUTF8
”
2017-08-29 19:35:45 SERVER -> CLIENT: 250-smtp.gmail.com at your service, [40.83.185.163]
250-SIZE 35882577
250-8BITMIME
250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-CHUNKING
250 SMTPUTF8
2017-08-29 19:35:45 CLIENT -> SERVER: MAIL FROM:
2017-08-29 19:35:45 SMTP -> get_lines(): $data is “”
2017-08-29 19:35:45 SMTP -> get_lines(): $str is “530-5.5.1 Authentication Required. Learn more at
”
2017-08-29 19:35:45 SMTP -> get_lines(): $data is “530-5.5.1 Authentication Required. Learn more at
”
2017-08-29 19:35:45 SMTP -> get_lines(): $str is “530 5.5.1 https://support.google.com/mail/?p=WantAuthError 188sm5791238pgd.20 – gsmtp
”
2017-08-29 19:35:45 SERVER -> CLIENT: 530-5.5.1 Authentication Required. Learn more at
530 5.5.1 https://support.google.com/mail/?p=WantAuthError 188sm5791238pgd.20 – gsmtp
2017-08-29 19:35:45 SMTP ERROR: MAIL FROM command failed: 530-5.5.1 Authentication Required. Learn more at
530 5.5.1 https://support.google.com/mail/?p=WantAuthError 188sm5791238pgd.20 – gsmtp
2017-08-29 19:35:45 The following From address failed: support@answersby.com : MAIL FROM command failed,Authentication Required. Learn more at
https://support.google.com/mail/?p=WantAuthError 188sm5791238pgd.20 – gsmtp
,530,5.5.1SMTP server error: MAIL FROM command failed Detail: Authentication Required. Learn more at
https://support.google.com/mail/?p=WantAuthError 188sm5791238pgd.20 – gsmtp
SMTP code: 530 Additional SMTP info: 5.5.1
“
Please use these guides to properly implement ssl:
http://www.wpbeginner.com/wp-tutorials/how-to-add-ssl-and-https-in-wordpress/
https://css-tricks.com/moving-to-https-on-wordpress/
https://yoast.com/dev-blog/move-website-https-ssl/
https://forum.tagdiv.com/topic/moving-to-ssl/
Thanks.
For more info, I would prefer not to disable my SSL cert in exchanging for downloading, pls help and advise, thanks very much
Hi admin supports,
Just purchased the newspaper theme and downloading the required plugin, however, systems said:
“Downloading install package from https://mydomain.com/wp-content/themes/Newspaper/includes/plugins/td-composer.zip…
Download failed. cURL error 60: SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed”
Would you pls advise how to fix it? Thanks
Michael
hello sir/madam
earlier i had different theme on my wordpress, running successfully, and opening with https:// not it shows unsecured error and open in http:// i searched it is due to some images in my site which are-
Total number of items: 113
Number of insecure items: 6
Insecure URL: http://www.newsineer.com/wp-content/uploads/2017/08/8.jpg
Found in: https://www.newsineer.com/
Insecure URL: http://www.newsineer.com/wp-content/uploads/2017/08/logo-mobile.gif
Found in: https://www.newsineer.com/
Insecure URL: http://www.newsineer.com/wp-content/uploads/2017/08/logo-header.gif
Found in: https://www.newsineer.com/
Insecure URL: http://www.newsineer.com/wp-content/uploads/2017/08/newspaper-rec728.jpg
Found in: https://www.newsineer.com/
Insecure URL: http://www.newsineer.com/wp-content/uploads/2017/08/newspaper-rec300.jpg
Found in: https://www.newsineer.com/
Insecure URL: http://www.newsineer.com/wp-content/uploads/2017/08/logo-footer.png
Found in: https://www.newsineer.com/
please tell me how to remove this completely.
thank you !
Thanks,
I made all modifications and my hosting provider made all necessary changes according to your guide. But the problem persist. It is strange that only this selection (Modules MX and other Blocks – Article Title) is loading endlessly.
Could it be something else?
Theme panel > Theme Fonts > Modules MX and other Blocks – Article Title endlessly loading and doesn’t show