test033
Forum Replies Created
-
Hello. I am not a representative of the ColorMag theme. It looks like you have a similar problem that I had, if I understood your situation correctly: https://ww.wp.xz.cn/support/topic/elementor-3-26-fatal-error-2/#post-18208207.
Or, try disabling caching in the Elementor plugin: https://ww.wp.xz.cn/support/topic/error-actualizacion-elementor-3-26-0/#post-18205220.
Maybe this will help you. Sorry for posting in your thread.
- This reply was modified 1 year, 5 months ago by test033.
Forum: Themes and Templates
In reply to: [ColorMag] Elementor 3.26 > fatal errorAfter updating Elementor to version 3.26.1, somehow the problem was barely fixed. Here is a screenshot: https://drive.google.com/file/d/1PCTh-FSAnW1fZdNQsKoIaQEbCH02_ZpZ/view?usp=sharing
But, there seems to be some compatibility issues between Elementor and ColorMag theme, because, to solve the problem, I had to completely rebuild the main page from scratch to solve the problem with the background and font color, which I pointed out on the screenshot above in the post. Although, there are a lot of issues with Elementor plugin updates, where on the forum, there are a lot of complaints about the latest Elementor 3.26 and 3.26.1 updates.
Probably, the issue can be considered resolved for now, although I would like more stability and better checking and testing of updates before they are rolled out by developers. Alas, this is a pipe dream…. Best of luck to you and thanks for your help.Forum: Themes and Templates
In reply to: [ColorMag] Elementor 3.26 > fatal errorHello.
Thank you, for providing the ColorMag 4.0.8 theme update and fixing the critical bug.
However, now there is a problem with the text color palette. White text on a red background, this has never happened before. I attach a screenshot: https://drive.google.com/file/d/1nJcHNiSamKvRC1aCyp8FZBbCU1BH3MHe/view Attempts to fix the text and remove the selection background through the Elementor page editor, it seems to cause a style conflict and the fixes are not saved. Example of a page with the problem on the screenshot: https://www.lovepets.com.ua/happy-owner/ Can this be fixed? Thank you in advance.
Hello.
The problem turned out to be that I had not mistakenly turned off HTTP authentication via .htpasswd for the test site, where I tried to enable HTTP authentication via your plugin.
On the test site (in the /feeds/ folder, as I wrote above.), I had the .htaccess file (it contained a link to the .htpasswd file in the hosting root) located in the /wp-admin/ folder.
Because of this, as I already realized, I had the following warning in the admin area (on a yellow background, I attach a screenshot): https://drive.google.com/file/d/1VmqUfClQiLJJ8bHrSunjqv2s-6qH50vy/view?usp=sharingAnd after renaming the .htaccess file in the /wp-admin/ folder and re-entering the admin, this message disappeared: https://drive.google.com/file/d/1f1-AdVdeidiT4s8_cZNgXu00qxvzgEgS/view?usp=sharing
It is important to note that I saw this message with a warning on a yellow background and by default I specified the login and password that was used via .htpasswd authentication. However, I understand there was a conflict.
I haven’t checked whether HTTP authentication works correctly now via your plugin. I’m afraid that again I will have to completely uninstall your plugin and re-configure everything. But I think the problem was in my wrong actions. Perhaps a way to reset this setting in case of failures could be technically implemented to eliminate the need to completely uninstall the plugin because of a single setting.
Thank you very much for your assistance with the issue. Please forgive me for creating extra work for you and forcing you to test a problem that I seem to have created myself.
And maybe it’s important, I have the wp-config.php file moved outside the domain name folder to the root of the account itself.
What I have in .htaccess, which is located in the root of the domain: https://drive.google.com/file/d/1ZC8KxLI_X_AAwvwflU3lhUJQ_bWIwIvd/view
And here’s what I have in the .htaccess file that is located in the WordPress installation package: https://drive.google.com/file/d/1_PxtV_ac2XxgZc-XF2oCeViLyarlVBB2/view?usp=sharing
Here’s the website address, maybe for a better understanding of the structure: https://www.lovepets.com.ua/feeds/
I should also add that now I was able to configure HTTP authentication by adding a .htaccess file with a link to .htpasswd (with login and password) to the /wp-admin/ folder and everything works. That is, the window with login and password request in the browser appears correctly. After entering, lets you into the administration further.
As for “Also if you have PHP installed as CGI you might have to contact hosting provider as below should be enabled.”, I will try to check with the hoster.
I have Ukrainian hosting: https://freehost.com.ua/
I have a shared hosting plan with Memcache support and dedicated RAM (hybrid between virtual hosting and virtual VPS, (line of virtual hosts: https://freehost.com.ua/unix/, MEGA tariff)). On the tariff, you can edit / create .htaccess and .htpasswd file.
As the hoster states, it works in a bundle of Apache + Nginx. Apache is responsible for working with dynamic content, and Nginx for static content.
Here are the parameters from phpinfo:
$_SERVER[‘SERVER_SOFTWARE’] Apache/2.4.54 (FreeBSD)
Server API CGI/FastCGIAnd maybe that’s important. I had the site installed not in the main directory, but in the main domain folder. That is: site.com/my-site/
It was in the /my-site/ folder that WordPress with the plugin was installed. Perhaps it makes a difference.Willing to provide more information if you need it. Thanks for developing the product and making it better.
Thank you so much. I did everything according to your above instructions and was able to completely uninstall the plugin and then successfully reinstall and activate it. Now, the HTTP authentication request does not appear. I have re-configured the plugin by enabling the features I need, leaving out only HTTP authentication.
In my situation, the topic can be considered solved. Thank you very much.
From my side, perhaps you need something to further improve / test the “HTTP Authentication” feature?
Hello. Thank you for your reply.
I used your link: https://pastebin.com/2xjufp5X. No results. After entering the data, it endlessly re-displays the login and password prompt.
Yes, “salt postfix” was activated.
“cookie based brute force” is not activated.What I did:
Removed .htpasswd
Replaced it with a standard .htaccess file.
Deleted the plugin folder at the path: /wp-content/plugins/all-in-one-wp-security-and-firewall via FTP.
Cleaned the .user.ini file of aiowps entries
Cleaned the wp-config.php file of aiowps entries
Removed the file /aios-bootstrap.php
Cleaned the database of entries mentioning aiowps
Cleared cache on the server and via Cloudflare
Tried to reinstall the plugin after that and after activating it, it gives again HTTP authentication with login and password request. When entering data, it displays the request again and so on endlessly.
The only option at the moment is to delete your plugin and not use it, because when activating the plugin, it is impossible to enter the admin area.Is it possible to solve the problem and continue to use your solution? Thank you in advance.
Forum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] Non-working site menu on AMPHello.
On https://www.lovepets.com.ua/animals/, the Astra theme is used: https://uk.ww.wp.xz.cn/themes/astra/
On https://www.lovepets.com.ua/blog/, the ColorMag theme is used: https://uk.ww.wp.xz.cn/themes/colormag/In your AMP plugin itself, the Swift theme is selected.
I attach the settings file of your plugin: https://drive.google.com/file/d/1cv1P7LnJB9lNRqYSr063e3PQ5nyjbSZd/view?usp=sharing.
The settings file of your plugin is the same on my two sites.
Through the method of disabling plugins, I was able to see that when the Simple Share Buttons Adder plugin (https://ww.wp.xz.cn/plugins/simple-share-buttons-adder/) is enabled, there is a problem with the display of social media buttons from the Simple Share Buttons Adder plugin. Ideally, as I understand it, they (buttons from Simple Share Buttons Adder plugin) should be hidden from AMP version. However, for some reason they (Simple Share Buttons Adder buttons) are visible and not very beautiful. At the moment, I disabled the Simple Share Buttons Adder plugin and the problem is solved. What else can I do to help solve the problem? Thanks in advance.
Screenshot with crooked button display, with Simple Share Buttons Adder plugin enabled: https://drive.google.com/file/d/1xYIZMsBvicyYmg84xpfa-Cs-D91oe3E4/view?usp=sharing
P.S..
Sorry, I’m writing through Google Translator.Please tell me. You seem to have the Swift theme installed on the AMP version? I have the same problem with the Swift theme: https://ww.wp.xz.cn/support/topic/css-syntax-error-in-style-amp-custom-tag/. Thanks in advance.
Forum: Plugins
In reply to: [Web Stories] Error “script amp-onerror”It might be helpful for someone to know the solution.
Conflict between CDN Enabler and Web Stories plugins, solved by exempting /v0.js
The solution is described here: https://ww.wp.xz.cn/support/topic/conflict-between-cdn-enabler-and-web-stories/#post-17310200
Thank you all for your participation in solving the problem.Forum: Plugins
In reply to: [CDN Enabler] Conflict between CDN Enabler and Web Stories?The problem was solved by adding /v0.js to an exception in the plugin settings.
Example of adding to exception: https://drive.google.com/file/d/1Yp9tF6NggDGyUledU0RZHin0GNIMDW47/view?usp=sharing
This topic is closed as resolved.
- This reply was modified 2 years, 4 months ago by test033.
Forum: Plugins
In reply to: [CDN Enabler] Conflict between CDN Enabler and Web Stories?Hello.
By disabling the CDN Enabler plugin / or by placing files with .js extension in exceptions – the problem disappears. Screen with correct work
As soon as you remove the .js extension from the exception or re-enable the plugin, the problem resumes. Screenshot with incorrect operation
The developer of Web Stories claims that the problem is yours: https://ww.wp.xz.cn/support/topic/error-script-amp-onerror-2/#post-17296198
I would like to solve the problem. Although, I see rarely answers here. Looks like the plugin is abandoned. It’s a pity…