frizzel

Is anyone monitoring this support section?

@builtbynorthby You seem to missing the point. That should be a BASIC feature for a REGISTRATION plug-in.

I think I know why you left it out: because most people would want that and thus upgrade. However, that makes this free version (despite it’s many features that no doubt lures people, including me) useless in most cases.

Thank you for your quick answer and offer. However, I’ve already found another plug-in (free) that does what I wanted.

@kriscronuk You had another review thread with bad comments on this plug-in removed and rightfully so. Because this plug-in does NOT have a big impact on performance.

I have been working with the paid version of this plug-in for years and now with the free version on a different site. Your remarks are totally off.

I suggest you take a look at your website’s setup, because, again, this plug-in does NOT impact the performance as you claim it does.

I’m having this same problem, working on a local install. Had a look at the database and all exif fields are empty, except for ‘Credit’, ‘Copyright’ and ‘Taken’. The test image I used also has details like ISO, Camera, and shutter_speed, but it seems these are not extracted from the exif data and put into the database.

Running latest WP 4.9.7 and PHP version 7.1.4

Thanks for the clarification.

As said, it’s not on a live site, yet, only a local install.
Maybe I’ll contact you again when it’s live.
But, just out of curiosity, what exactly do these
$old_keys
and
$new_keys
store and delete?

Hm, if I change line 859 from
$old_keys = get_post_custom_keys($post_id);
to
$old_keys = get_post_custom_keys($post->ID);
the warnings are also gone.
Could that be it?

I’m working on a local install. Just tried it on a fresh WP install with default theme (TwentySeventeen) and only this plug-in.
Changed web server from nginx to Apache.
Changed PHP version back to 5.6.20
All gave the same result as I described above.

If I comment lines 862-865 in ‘class-applyonline-admin.php’, the warnings are gone.
But that’s probably not the way it should be.
Anyhow, it seems to point to some code error right there.

• This reply was modified 6 years, 10 months ago by frizzel.

Update:
The warning when updating an existing ad only happens when I change something in the text area or in the excerpt, not when changing e.g. features.

• This reply was modified 6 years, 10 months ago by frizzel.

Thank you @cybr I’ll wait for the patch in an upcoming release.
And, uhm, TSF is already a great product, but yeah this thing bothered me.
Thanks a lot for being so responsive and helpful!

Thanks @cybr. I know I’m not using TSF on the live site, TSF is on the development site only for now.

When I try your suggestion on the development site, in both cases I get a sitemap for both languages, only the link at the very top in the sitemap (the Home link) changes for the expected language. The rest is just both EN and NL.
Maybe I’m missing something?

And yeah, the ‘smooth’ scroll is going to be removed in the new version… ??

Hi Sybre (@cybr), thanks for the quick response. The Dutch translation is in a subdirectory: /nl/. I know it would probably be better to have it in a subdomain, but it has been like this for years, so I’m a bit hesitant to change it.

The site url, hm, I know there are a few problems, that’s one of the reasons I’m working on an update, but anyway: English (main site) and Dutch

Thanks for your help.

Hi Sybre (@cybr), thanks for the quick response. The Dutch translation is in a subdirectory: /nl/. I know it would probably be better to have it in a subdomain, but it has been like this for years, so I’m a bit hesitant to change it.

The site url, hm, I know there are a few problems, that’s one of the reasons I’m working on an update, but anyway: English (main site) and Dutch

Thanks for your help.

FYI, I’ve opened a topic on AIO SEO support, too: it’s here

I see that you are using ob_start in the HTML Minify function which triggers AIO SEO to echo that line.

It’s probably more for their support forum, but FYI: it only happens when ‘Force Rewrite’ in AIO SEO is set to ‘on’ (using output buffering).
However, I don’t understand why they need to print that line as without it, it works just as well as far as I can see.

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