Jim
Forum Replies Created
-
Forum: Plugins
In reply to: [PayPal for WooCommerce] Won’t return to staging site after PayPalThank you for the suggestion. I tried again defining both variables or only WP_SITEURL, this time resetting permalinks after. Unfortunately same results as before.
I will work with hosting support and see if they have a solution.
- This reply was modified 7 years, 10 months ago by Jim.
Forum: Themes and Templates
In reply to: [GeneratePress] wrapping issueThanks Tom, this is food for thought. As I understand the max-width refers to the window width. Problem is the images vary a lot in width, so I imagine a max-width I pick will be too wide for some and possibly too narrow for others. I’ll play with it and see how it goes. Thanks!
Forum: Plugins
In reply to: [PayPal for WooCommerce] Won’t return to staging site after PayPalThanks, that was a good suggestion and I had high hopes, but alas . . .
If I define both WP_HOME and WP_SITEURL, or only WP_HOME, to the URL of the staging site, the site breaks, some kind of redirection error.
So I defined only WP_SITEURL. The site worked in general, but the same problem with payments as before.
I appreciate you trying to help!
Forum: Plugins
In reply to: [PayPal for WooCommerce] Won’t return to staging site after PayPalThank you for the extensive reply. I would really love to be able to test this in my staging environment. Is there someplace in the plugin where I could temporarily hard-code the return domain for staging? I know it’s not the ideal solution but at this point I need a simple fix.
***********
By the way, I’ve noticed lately, whenever I’m on the settings page for Paypal for Woocommerce – Express Checkout, I see near the top of the settings window a portion of a php warning. It also shows up in the php_errorlog whenever I’m in that settings page:
[19-Jul-2018 12:39:03 UTC] PHP Warning: mysqli_real_escape_string() expects parameter 2 to be string, array given in /home/cookand3/staging/3/wp-includes/wp-db.php on line 1102
The plugin doesn’t seem to call this directly, but maybe indirectly?
Forum: Plugins
In reply to: [WooCommerce] Customer can’t log outIt now appears this was some kind of staging/database issue. When we pushed staging to live, the site was redirecting back to staging. The host support cleaned out the staging URLs wherever they were stored, and now I can log out normally.
Sorry for the hassle.
Forum: Plugins
In reply to: [WooCommerce] Customer can’t log outI investigated the Cloudflare settings. Flexible SSL was on, so I turned it off. Also purged the Cloudflare cache, set it to development mode, and played with Cloudflare caching level (basic, simple, aggressive). Nothing I did changed the behavior.
Forum: Plugins
In reply to: [WooCommerce] Customer can’t log outThanks. The only caching set up is a static cache (although I don’t know if staging is cached in any case). I disabled that in cpanel, cleared cookies+cache on the browser again, even opened a new browser tab, but no luck. 🙁 Puzzling.
- This reply was modified 7 years, 11 months ago by Jim.
Forum: Plugins
In reply to: [WooCommerce] Customer can’t log outMy WC Status:
### WordPress Environment ### Home URL: https://www.staging1.cookandconnect.com Site URL: https://www.staging1.cookandconnect.com WC Version: 3.4.3 Log Directory Writable: ✔ WP Version: 4.9.7 WP Multisite: – WP Memory Limit: 768 MB WP Debug Mode: – WP Cron: ✔ Language: en_US External object cache: – ### Server Environment ### Server Info: Apache PHP Version: 7.0.30 - We recommend using PHP version 7.2 or above for greater performance and security. How to update your PHP version PHP Post Max Size: 128 MB PHP Time Limit: 120 PHP Max Input Vars: 3000 cURL Version: 7.59.0 OpenSSL/1.0.2k SUHOSIN Installed: – MySQL Version: 5.6.36-82.1-log Max Upload Size: 128 MB Default Timezone is UTC: ✔ fsockopen/cURL: ✔ SoapClient: ✔ DOMDocument: ✔ GZip: ✔ Multibyte String: ✔ Remote Post: ✔ Remote Get: ✔ ### Database ### WC Database Version: 3.4.3 WC Database Prefix: wp_ MaxMind GeoIP Database: ✔ Total Database Size: 23.80MB Database Data Size: 15.98MB Database Index Size: 7.82MB wp_woocommerce_sessions: Data: 0.02MB + Index: 0.02MB wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.05MB wp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB wp_woocommerce_order_itemmeta: Data: 0.06MB + Index: 0.03MB wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB wp_aws_cache: Data: 0.08MB + Index: 0.00MB wp_aws_index: Data: 0.06MB + Index: 0.00MB wp_bm_user_location: Data: 0.02MB + Index: 0.02MB wp_bp_activity: Data: 0.02MB + Index: 0.16MB wp_bp_activity_meta: Data: 0.02MB + Index: 0.03MB wp_bp_groups: Data: 0.02MB + Index: 0.05MB wp_bp_groups_groupmeta: Data: 0.02MB + Index: 0.03MB wp_bp_groups_members: Data: 0.02MB + Index: 0.09MB wp_bp_messages_messages: Data: 0.02MB + Index: 0.03MB wp_bp_messages_meta: Data: 0.02MB + Index: 0.03MB wp_bp_messages_notices: Data: 0.02MB + Index: 0.02MB wp_bp_messages_recipients: Data: 0.02MB + Index: 0.08MB wp_bp_notifications: Data: 0.02MB + Index: 0.11MB wp_bp_notifications_meta: Data: 0.02MB + Index: 0.03MB wp_bp_xprofile_data: Data: 0.02MB + Index: 0.03MB wp_bp_xprofile_fields: Data: 0.02MB + Index: 0.08MB wp_bp_xprofile_groups: Data: 0.02MB + Index: 0.02MB wp_bp_xprofile_meta: Data: 0.02MB + Index: 0.03MB wp_commentmeta: Data: 0.02MB + Index: 0.03MB wp_comments: Data: 0.05MB + Index: 0.09MB wp_defender_lockout: Data: 0.02MB + Index: 0.00MB wp_defender_lockout_log: Data: 0.02MB + Index: 0.00MB wp_hook_list: Data: 0.02MB + Index: 0.00MB wp_links: Data: 0.02MB + Index: 0.02MB wp_options: Data: 2.28MB + Index: 0.09MB wp_pmxe_exports: Data: 0.22MB + Index: 0.00MB wp_pmxe_google_cats: Data: 0.39MB + Index: 0.00MB wp_pmxe_posts: Data: 0.02MB + Index: 0.00MB wp_pmxe_templates: Data: 0.02MB + Index: 0.00MB wp_postmeta: Data: 4.52MB + Index: 0.75MB wp_posts: Data: 3.52MB + Index: 0.22MB wp_pv_commission: Data: 0.02MB + Index: 0.00MB wp_revslider_css: Data: 0.13MB + Index: 0.00MB wp_revslider_layer_animations: Data: 0.02MB + Index: 0.00MB wp_revslider_navigations: Data: 0.02MB + Index: 0.00MB wp_revslider_sliders: Data: 0.02MB + Index: 0.00MB wp_revslider_slides: Data: 0.02MB + Index: 0.00MB wp_revslider_static_slides: Data: 0.02MB + Index: 0.00MB wp_rg_form: Data: 0.02MB + Index: 0.00MB wp_rg_form_meta: Data: 0.02MB + Index: 0.00MB wp_rg_form_view: Data: 0.02MB + Index: 0.03MB wp_rg_incomplete_submissions: Data: 0.02MB + Index: 0.02MB wp_rg_lead: Data: 0.02MB + Index: 0.03MB wp_rg_lead_detail: Data: 0.02MB + Index: 0.06MB wp_rg_lead_detail_long: Data: 0.02MB + Index: 0.00MB wp_rg_lead_meta: Data: 0.02MB + Index: 0.05MB wp_rg_lead_notes: Data: 0.02MB + Index: 0.03MB wp_signups: Data: 0.08MB + Index: 0.06MB wp_stream: Data: 1.17MB + Index: 0.39MB wp_stream_meta: Data: 2.02MB + Index: 4.27MB wp_termmeta: Data: 0.02MB + Index: 0.03MB wp_terms: Data: 0.02MB + Index: 0.03MB wp_term_relationships: Data: 0.02MB + Index: 0.02MB wp_term_taxonomy: Data: 0.02MB + Index: 0.03MB wp_usermeta: Data: 0.08MB + Index: 0.06MB wp_users: Data: 0.02MB + Index: 0.05MB wp_wcv_feedback: Data: 0.02MB + Index: 0.00MB wp_wc_booking_relationships: Data: 0.02MB + Index: 0.03MB wp_wc_download_log: Data: 0.02MB + Index: 0.03MB wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB wp_weforms_entries: Data: 0.02MB + Index: 0.02MB wp_weforms_entrymeta: Data: 0.02MB + Index: 0.03MB wp_wpuf_subscribers: Data: 0.02MB + Index: 0.02MB wp_wpuf_transaction: Data: 0.02MB + Index: 0.06MB wp_wsluserscontacts: Data: 0.02MB + Index: 0.02MB wp_wslusersprofiles: Data: 0.02MB + Index: 0.03MB ### Post Type Counts ### acf-field: 2 acf-field-group: 1 attachment: 63 bookable_person: 6 bp-email: 16 customize_changeset: 17 nav_menu_item: 18 page: 35 post: 6 postman_sent_mail: 250 product: 44 revision: 296 shop_coupon: 1 shop_order: 21 shop_order_refund: 1 shop_order_vendor: 50 wc_booking: 62 wpuf_contact_form: 1 wpuf_forms: 1 wpuf_input: 24 ### Security ### Secure connection (HTTPS): ✔ Hide errors from visitors: ✔ ### Active Plugins (1) ### WooCommerce: by Automattic – 3.4.3 ### Settings ### API Enabled: ✔ Force SSL: ✔ Currency: USD ($) Currency Position: left Thousand Separator: , Decimal Separator: . Number of Decimals: 2 Taxonomies: Product Types: booking (booking) external (external) grouped (grouped) simple (simple) variable (variable) Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog) exclude-from-search (exclude-from-search) featured (featured) outofstock (outofstock) rated-1 (rated-1) rated-2 (rated-2) rated-3 (rated-3) rated-4 (rated-4) rated-5 (rated-5) ### WC Pages ### Shop base: #4 - /kitchens/ Pending Bookings: #5 - /cart/ Checkout: #6 - /checkout/ My account: #7 - /my-account/ Terms and conditions: #145 - /terms-of-service/ ### Theme ### Name: Twenty Seventeen Version: 1.6 Author URL: https://wordpress.org/ Child Theme: ❌ – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme WooCommerce Support: ✔ ### Templates ### Overrides: –Forum: Plugins
In reply to: [PayPal for WooCommerce] Won’t return to staging site after PayPalHmm, here is a reply from Siteground about this. Maybe they handle staging differently from some hosting companies, probably for good reason, but it makes it hard to test payments. The only thing I found to work was WooCommerce Paypal Checkout plugin, which doesn’t really go to the Paypal site but puts Paypal in a modal window, so I guess there is no return to do.
From Siteground:
Thank you for contacting our Help Desk.The URLs for your WordPress application are not changed on the staging copy, meaning that when a staging copy is created staging1.cookandconnect.com still has the domain cookandconnect.com setup within the database. The tool then uses multiple Apache modules to modify the header information along with rewriting all URLs on a server level to stagingN.domain.tld as an example(in your case staging1.cookandconnect.com).
This is done so we can ensure the WordPress application does not have any URL or domain related issues once it is pushed to live. If a plugin or other website component requires the use of the WordPress base URL as it is set within the database and settings of the application it is likely that this could trigger errors and potentially redirects to the live site, as their functionality could inadvertently be bypassing the setup of the staging tool.
With this in mind, I would advise you to consult this issue with the plugin developers to see if there is an alternative way to resolve this issue, as we highly discourage changing the URLs of the staging copy as this could lead to issues when the site is live.
If there is no other alternative, we can try to change the base URLs of your WordPress application in the staging copy, however as I mentioned this is not advised.
Forum: Plugins
In reply to: [PayPal for WooCommerce] Won’t return to staging site after PayPalThank you Oliver, that’s what I was wondering.
JimForum: Plugins
In reply to: [PayPal for WooCommerce] Won’t return to staging site after PayPalA bit more info: I checked the log, and it is indeed sending Paypal the URL of the live site:
[RETURNURL] => https://www.cookandconnect.com/wc-api/WC_Gateway_PayPal_Express_AngellEYE/?pp_action=get_express_checkout_detailsSame with the Cancel URL.
Ahh, I see. I didn’t know that setting noindex in TSF would remove them from the sitemap. And apparently I would set noindex in TSF even if WooCommerce also does it, just to keep them out of the sitemap.
Actually I found a bunch of additional pages that would be bad landing pages or make no sense to index, so I added those too.
Thank you!
OK, finally I found about resetting the sitemap cache by changing a plugin setting and saving. It works now!
I managed to find a clue in a previous answer and replaced the message when logged in as follows:
add_filter('wppb_login_message', 'fp_change_login_message', 10, 3); function fp_change_login_message($logged_in_message, $user_id, $display_name){ $newmsg = "You are logged in as " . $display_name . "<br>"; $newmsg = $newmsg . "<a href='https://forestpathology.org/wp-login.php?action=logout&redirect_to=https%3A%2F%2Fforestpathology.org'>Log Out</a>"; $newmsg = $newmsg . " | " . "<a href='https://forestpathology.org/edit-profile/'>Edit Profile</a>"; return $newmsg; }That’s working surprisingly well, except the $display_name is not showing as the selected display name, it is the user name. The correct display name shows in the back end and in Profile Builder’s Edit Profile page.
Thanks
Thanks for the explanation. I managed to create the page and put the [wpuf_dashboard] shortcode there, then put links to it in the pages where you submit and view the posts.
If that code is available anywhere for putting an edit link in the author’s posts, I would appreciate a link.