captaincrash

Hi @charlescormier,

sorry to bring this back up, but would it be feasible to have the switch-to-vertical threshold adjustable per timeline?
Or is there a simple way I could do this in a child theme?

Thanks again.

Wow, that was fast. Thank you.

Thank you so very much and sorry for hijacking this support forum!

Please let me add that I am fully aware that this has hardly anything to do with your plugin and it is not your job to teach me WordPress.
I just hope you don’t mind sacrificing maybe a couple more minutes since, after quite a bit of research, your plugin has been among the few results that still work with WordPress 6.0 (i.e. remove the color scheme picker).

Hi @barryceelen,

thank you for the quick reply. Sorry, if I was being a bit unclear. Why does the recent move to admin-filters.php put the add_action so much later? Where do I see/find that in core’s code? Which lines would tell me that the calls in admin-filters.php run much later than the ones indefault-filters.php?

I’d really love to understand it better, not just copy/paste a solution. If you could please help me out once more, that would be awesome.

Thanks and best regards.

Thanks so much.

@anlino?

I’d like to add that basic body a and body a:hover are missing, too.

@buddyboss

This seems now fixed for me. The PHP DOM extension had been missing on my server (new DOMDocument() caused the error).

Is this a new requirement to the Edit Activity Plugin? As I believe it once worked without it?

It throws an error 500 Internal Server Error on admin-ajax.php when clicking the edit button.

@buddyboss
Any progress on this?
All of my edit buttons just start spinning after clicking, but nothing else happens.
Possibly connected to Minifying JS under Boss Theme Options -> Optimization.

Would be great, thank you.

Absolutely.

Excellent! Thank you!

This also fixes Contact Form 7 not properly enqueuing JS files as soon as Domain Mapping is active.

This and this need to make it into the plugin, please.

Yes, that pretty much sums it up.

A simple example complementing my posts 3. and 5. above. Let’s say

https://domain.com/subsite/testpage

gets mapped to

https://subsite.com/testpage

BUT links to the frontend within the admin area stay unmapped!

Statify only saves the absolute path in the DB /testpage – which is ok, I guess.

Currently, the admin widget links to just /testpage which results in

https://domain.com/testpage (missing /subsite)

but should prefix /testpage with home_url() to make it

https://domain.com/subsite/testpage

And, see side note in post 3. above, clicking from the admin on

https://domain.com/subsite/testpage

which gets mapped to

https://subsite.com/testpage

currently qualifies as a valid stat entry since referrer and target don’t share the same domain, however, these cases should not get logged.

Thanks again.