francoc30

Hi @wpinsider-1 , Thanks for the clarification. The last time I need to create Paypal button was a year ago. I used the Hosted button process then. My production system is on 4.2.4. In that version, this Hosted button is still available in Setting->Payment Setting tab. That’s why I am a little confused. I suppose I can still use it.

Since my Pro is not up-to-date, I am marking this “resolved”.

Hi @wfpeter, No I have not tested with only WF being the plugin activated. I only found out WF caused the Customize error when I reactivated my plugins one at a time from the Plugin listing.

The conflict did not affect the frontend which all pages were displayed properly. It only caused the critical error at the backend when the Customize of the theme was clicked. All other plugins opened up with no problem. My php error log has limited capacity. The entries when the error occurred is no longer available. I should have reviewed the error log when that happened.

Addition: I just activated WF then clicked on Customize and view the Browser Developer info: In the Console, the red entry is

GEThttps://ccpst.com/wp-admin/customize.php?return=/wp-admin/plugins.php?plugin_status=all&paged=1&s

From the Network tab, the status is 500 with the following entry: customize.php?return=/wp-admin/plugins.php?plugin_status=all&paged=1&s

Also I check php error log for this particular activation and find this entry:

20230227T123647: ccpst.com/wp-admin/customize.php

mmap() failed: [12] Cannot allocate memory

mmap() failed: [12] Cannot allocate memory
PHP Fatal error: Out of memory (allocated 208314368) (tried to allocate 2097152 bytes) in /serverpath/public_html/test/wp-includes/functions.php on line 4247

• This reply was modified 2 years ago by francoc30. Reason: Add more information
• This reply was modified 2 years ago by francoc30.

I am referring to this. In the updated version there is no such thing, just the API setup. I may have missed something. Please advise.

<<All the existing buttons will continue to work. However, if you want to create a new button for membership, then you should use the new ones (since PayPal wants users to use these new ones in the future).>>

If the former buttons I created will still work that is what I need to know.  If I have to use API setup for future payment buttons, then I will do that.  It just that the former setup is so much simpler.

After updating to latest version, the Create New Button is no longer available. There is no way I can use the old way to create new Buy Now button.

If I use the new way API method to create a new button, will both the old and the new buttons coexist and continue to work?

Ok then. It is good to know there is no adverse consequences from the cause of the message. Thanks for your investigation and explanation. Great support. I will close this thread as resolved.

Hi @webulous, I don’t know if there are two cron jobs running at the same time. I have not scheduled any cron jobs myself other than the scheduled Preload process in WPO. Even that since I am using the WPO free version, I cannot specify the time when Preload is to be run. There may be other cron jobs running that I have no control over.

As for a visitor browsed my site manually during the scheduled preload run and caused the error, I found it difficult. Preloading is just a process visiting a site automatically and under normal circumstances there would be more than one human visitors visiting a site in any given time, with or without the preloading happening at the same time. If such situation causes the error, then this should be remedied in the codes. I do use UptimeRobot to visit my site once every five minutes.

No I have not moved my site to another hosting provider.

All that being said, when these errors occurred, what are the consequences? What are the impacts on the cache preload or caching as a whole? Will they stop the preload process and render an incomplete cache asset? Or/and something else?

Thanks, looking forward to the response.

Noop, WPO is the only cache plugin installed. There is no active cache program on the server either.

Hi @imagely, Thanks for your reply and info. I dug deeper into the issue and found the problem was caused by a setting from another plugin. It is not related to NGG. Thanks again.

Hi @giuse, Thanks for looking into the issue. Events Manager support is not active since they made a big update last year. The problem I encountered was not FDP’s as I found later. Originally, my issue was the display of shortcode of NextGen Gallery and Simple Membership instead of the proper content. I found out that it was caused by the string I used in Front End url in FDP. The one in NextGen Gallery is now ok, but the one in Simple Membership is still a problem. My site is bilingual, but the profile page always displays the English version even when the Chinese version is intended. This may not be an FDP setting issue. But you may have some insights. Here are the two strings I used in the Front End url tab.

*zh/member-info/?swpm_member_id* ; *en/member-info/?swpm_member_id*

In the Post Type tab, there is an Event type. In the Event row, I deselected all the unnecessary plugins and saved the setting. Next time I visited this setting, all plugins were checked. I repeated this twice and each time all plugins were enabled again later. Is this due to the rewrite of rules of Events Manager? I am no expert and have no clue what this rules rewrite is all about, and how this affects FDP. If you don’t mind giving me some guidance.

Thanks for the reply. I did check the change log and saw no particular reason that would cause the issue. I did further investigation and found the cause which I resolved now.

Anyway, to be consistent with WP practice, I think users expect to see all previous version of any plugin to be listed at the repository. Thanks again. You are always very helpful.

Okay, I’ll dig deeper to check. Thanks for your time.

Hi @mbrsolution , I troubleshooted by deactivating all plugins except SWPM and Redirect addon. I even disable Google Recaptcha on the login form. Changed the theme to Twenty Twenty Three and to Twenty Twenty Two. None of these changes solve the issue. Here is the bland post-login screen. There was no redirect.

https://share.getcloudapp.com/llug8KG2

The deactivated plugins include the cache plugin. There is no server side plugin. I have not made any changes on the server. I don’t know whether or not my hosting provider has made any changes.

• This reply was modified 2 years, 2 months ago by francoc30.

Correction, the language B pages settings did not save as set. I was mistaken on my second message. The issue is there and not disappear.