I recently discovered these support forums and am hopeful that I can get some help with an issue I’m experiencing with the Bjork theme (version 0.2.4).
I’ve successfully set a favicon through both the WordPress FSE and the WordPress General Settings. It displays correctly in the backend (like on /wp-admin pages), but it doesn’t appear on the frontend of my website. I’ve already cleared my browser cache and the server cache via my hosting provider, and I’ve double-checked the theme settings to ensure the favicon is set correctly.
Unfortunately, despite all these efforts, the favicon remains absent on the frontend. My hosting provider attempted to assist me but mentioned that “it’s some parameter in the theme; I tried to force it directly from the theme functions, but it keeps getting removed.”
I would greatly appreciate your guidance or troubleshooting steps. Thank you in advance for your help!
]]>I’m trying to redirect:
https://example1.com/back/?redirect_to=https://example1.com/synthetic-customers-experiment-future-scenarios-without-violating-privacy/
To
https://example2.com/login/?redirect_to=https://example2.com/synthetic-customers-experiment-future-scenarios-without-violating-privacy/
Using Regular Expression or Contains
But the result is:
https://example2.com/login/?redirect_to=https%3A (string is cut off)
Can you help me?
Thank you very much
]]><?php
/*
Template Name: Movie Player
*/
get_header();
$url = isset($_GET['url']) ? esc_url($_GET['url']) : '';
if ($url):
? ? echo '<pre>';
? ? print_r($url); // Print the final URL for debugging
? ? echo '</pre>';
?> ?
? ? <video controls controlsList="nodownload">
? ? ? ? <source src="<?php echo $url; ?>" type="video/mp4">
? ? ? ? Your browser does not support the video tag.
? ? </video>
? ? <script>
? ? ? ? document.addEventListener('DOMContentLoaded', function() {
? ? ? ? ? ? const video = document.querySelector('video');
? ? ? ? ? ? video.addEventListener('contextmenu', function(e) {
? ? ? ? ? ? ? ? e.preventDefault(); // Disable right-click context menu
? ? ? ? ? ? });
? ? ? ? ? ? ?// Log the video URL to the console
? ? ? ? ? ? ?console.log("Video URL:", "<?php echo $url; ?>");
? ? ? ? });
? ? </script>
<?php
else:
? ? echo 'No video URL provided.';
endif;
get_footer();
This is the function that generates the presigned url in functions.php.
function handle_order_complete($order_id) {
? ? $order = wc_get_order($order_id);
? ? if ($order->has_status('completed')) {
? ? ? ? // Retrieve the bucket name and object key from environment variables
? ? ? ? $bucketName = 'ngop-movie';
? ? ? ? $objectKey = 'kot-2-movie.mp4';
? ? ? ? // Generate the pre-signed URL
? ? ? ? $presignedUrl = generate_presigned_url($bucketName, $objectKey);
? ? ? ? // Redirect the user to the movie player page with the pre-signed URL
? ? ? ? wp_redirect('https://kotthemovie.com/movie-stream?url=' . urlencode($presignedUrl));
? ? ? ? exit;
? ? }
}
In my video player page I retrieve the parameter from the url and use it as source in my video player to stream the video. It works fine locally with localhost but on my deployed wordpress site in wp engine I am not able to retrieve the parameter and add it to the source of the video. The video player doesn’t show at all. Can anyone please help me resolve this issue?
I want to remove the fixed text when using parameter, but it doesn’t have class to use css, can you support me?
I can find in the file and delete directly, but worry about the issue of updating later
Implemented Banner cookies and Consent mode v2 with CookieYes.
One doubt. Should URL parameters appear in the internal links for Google Analytics to track users without cookies, or is it the other way around and this happens when Consent Mode v2 is not properly implemented?
(These parameters was appearing at internal links after install CookieYes, but since we are set up fine the Google Consent Mode v2 they not appears).
Regards.
]]>e.g., in simple-page-access-restriction.php:172, if we add urlencode() to the home_url() .$_SERVER[‘REQUEST_URI’], it preserves the parameters.
$redirect_url = add_query_arg( $settings[‘redirect_parameter’], urlencode(home_url() . $_SERVER[‘REQUEST_URI’]), $redirect_url );
]]>Thanks a lot for your help
JA
]]>The site I’m managing is using ACF and the way it’s done is forcing me to use php templates for the page I want to host your Pretty Google Calendar.
Is it possible to include or call the code snippet from php?, how it should be done to use the parameters I want to use?
<code> [pretty_google_calendar gcal="[email protected]" locale="es"?show_title="true" use_tooltip="true" list_type="listCustom" custom_days="60" ] </code>
In ACF I’m using WYSIWIG Editor Field but I don’t know if there is another kind of Field I could use to properly embed the calendar to avoid the use of PHP.
Thanks again, and pretty great job you are doing!
]]>I’ve been using WP Fastest Cache for several years and appreciate its performance. However, I’ve noticed an issue with slower page loads when accessing pages through paid advertisements or Mailchimp newsletters, compared to direct or organic visits.
Upon investigation, I discovered that this slowdown is linked to the unique tracking parameters appended to URLs through platforms like Google Ads or Facebook ads.
For example, “https://www.webpage.com” might change to “https://www.webpage.com?tracking=1” for one user, and “https://www.webpage.com?tracking=2” for another, resulting in WP Fastest Cache generating a new cache for each unique URL, despite the actual page content remaining the same. This essentially negates the benefit of caching for users coming from paid ads, as they experience slower load times.
Could you guide me on how to configure WP Fastest Cache to ignore specific URL parameters and instead serve the cached version of the “base” URL?
Ideally, even when a URL like “https://www.webpage.com?tracking=1” is accessed, the cache for “https://www.webpage.com” should be used to speed up loading times, while still displaying the full URL with parameters in the address bar for analytics purposes.
Other caching plugins, such as WP Super Cache, offer a feature to ignore custom tracking parameters in their settings, enabling the cache to serve the base URL:
Best regards,
Emil
]]>