ibiza69
Forum Replies Created
-
We could solve the situation creating individual Views for each Source.
We don´t know what happened as we had these feeds working since years ago and today all this happened….
Thank you.
More things, we have 3 individual feeds in a page (separated), we have 3 jobs sites (IBIZA, MALLORCA and MENORCA). Today when we refreshed them, they went all mixed:
Feed 1: has information mixed from feed 1, feed 2 and feed 3.
Feed 2: has information mixed from feed 1, feed 2 and feed 3.
Feed 3: has informatiuon mixed from feed 1, feed 2 and feed 3.
So, when a client/visitor wants to see as we have before today job offers from IBIZA for example, they cannot see only IBIZA job offers, they are all mixed with MENORCA and MALLORCA too.
All feeds have individual URL/shortlink feed:
[wp-rss-aggregator feeds=”trabajar-mallorca”]
[wp-rss-aggregator feeds=”trabajar-menorca”]
[wp-rss-aggregator feeds=”trabajar-ibiza”]
The only thing we did its to Refresh feeds 🙁
How can we fix this situation?
No problem, we have found at your plugin section: DISPLAY EDIT > PERSONALIZATION > SOURCE NAME (Font name prefix) and in DISPLAY EDIT > PERSONALIZATION >Publish date (Publication date prefix & Publication date format) the way for updatin the frontend translation into spanish.
So if the translation file doesn´t work, we have found the formula to translate what users see on the frontend. Thank you.
Hi @hendcorp sorry for writting back. We are facing an small problem, the fronside plugin sentences are in english and we have selected at Loco Translate the spanish version as we do with our other websites that we use Loco Translate, but not your plugin, but in this case, your plugin is still in english. Any idea why this happens?
The sentences that we wanted to have translated and that we have translated are:
Source:
Published on:
But there is no way to have them updated into spanish. We do not use any cache plugin, we don´t use them at all.
Thank you once more for your time and attention.
Forum: Plugins
In reply to: [Widgets for Google Reviews] Widget Duplicating Google ReviewsHi @lacadev, thanks for answering. Today we where going to update the widget as you recommended, but first we had the option to update our google reviews, so we opted to do this and after updating reviews all duplicated reviews dissapaeared.
Thank you for your time and attention 🙂
Hi @hendcorp thanks for answering and for being with us on this. But just a question before proceding with the V5 Migration Guide Video. We started to hear the video and it said that users with free licence will not receive any new updated since december 2025. Is this correct? as we are fee users and if this is going to happen, we preffer to take time searching for a new plugin instead of going thru the V5 Migration guide, being totally sincere with you.
Thank you once more for your time and attention.
Forum: Plugins
In reply to: [WP Job Manager] Listing renewalsThank you @ctdealba. We finally hired a developer who did the work for us, creating a simple plugin.
Now, users can RENEW their offers whenever they want, without any problems and as many times they need.
We’ve also included a schedule that will reset back to 90 days the expiration date when they renew their offers.
Thank you very much for leaving our post open during this time. I proceed to close it now.
Have a very nice time 🙂
Forum: Plugins
In reply to: [WP Job Manager] Listing renewalsThank you Cara, I know you don´t provide snippets, but could you please leve this thread open, so maybe someone can help me providing this code for us, as is critical in our business that companies can renew their job offers as plugin can´t by it self or only once per period, so we cannot bring our users this option to renew when they need, not for example every 90 days or 180 days, as its job offers and so they do not long so much. Thank you!
Forum: Plugins
In reply to: [Duplicate Post] PHP version plugin support?Hi @mixha thanks for asnwering so quick and for clarify this. We have updated to PHP 8.2 and everything works correctly.
Thank you!
Forum: Plugins
In reply to: [WP Rollback - Rollback Plugins and Themes] Is it compatible with PHP 8.+Hi @dlocc thanks for asnwering so quick and for clarify this. We have updated to PHP 8.2 and everything works correctly.
Thank you!
Forum: Plugins
In reply to: [Health Check & Troubleshooting] When will be plugin compatible with PHP 8.1Thank you @threadi, marking as resolved.
Have a very nice time and thanks once more for your nice attention.
Forum: Plugins
In reply to: [Health Check & Troubleshooting] When will be plugin compatible with PHP 8.1Hello @threadi, thank you so much for responding so quickly. We don’t know if the plugin is compatible with this version or higher. After thoroughly reviewing everything, we’d like to upgrade to PHP 8.2, but we’re not sure if the plugin would work properly before proceeding to update the PHP version to this higher version.
Thank you very much again and for your explanation, as far as I understand we can proceed without any problems 🙂
But the problem started after installing your plugin, before we never had to clean our caches as they where completly stable. So the mess seems to be your plugin, do you understand this point? We deactivated all our plugins in staging sites and the only polugin generating all that mess was yours, not any other, this is why we communicated with you. We spoke with other plugin developers and said:
“I just looked at the plugin on wordpress.org and it only creates cache for mobile devices. It does not appear to have a delete/purge cache option. Looks like it is a very new plugin. So at some point after enough people complain about the problem you are having the plugin author will add that option, which of course should have been a top priority that should have already been added in that plugin. You can manually delete transient DB cache in phpMyAdmin in your web host control panel, but that would be a pain to do on a regular basis.”
“Oh I checked Advanced View on the wordpress.org plugins page and that plugin has been around for a long time. It’s just not installed by many people.”
So, as I said, I think you should take care of the plugin and its parameters under the hood, before sharing it publicly and we, the users, are the ones who have to try to solve these problems, which should not occur in any way, but on top of that, we are blamed, who have been working with WordPress for 20 years, for our websites being a disaster, when the problem comes directly and solely from this plugin, due to its lack of correct development and lack of information regarding the configuration of the fields included in it.
And one more question please, about the cache_version, should we put 0, 1 or 5 for example. What do the number we place there do? Refreshes, you said the clients browser, but what range of activity does entering any type of number entail? What exactly does it do?
As suggestion, it would be needed a little information next to the plugin fields so that clients understand what they’re for or how to correctly configure their parameters. There’s nothing about that and we tryed to finds some help/feedback (instructions), but with no luck…
We checked a moment ago our transients, after configuring the cache time to 900 secs (15 minutes) an hour and 20 miutes ago and got same ammount of transients (more than 20.000) and we had cleaned them before configuring this new plugin cache cleaning option to those 15 minutes, so the cache wasn´t autocleaned. Any suggestion? Thank you.