biberkopf

That’s an excellent tip, caimin. Didn’t know about that. Thanks.

I came up with a less elegant, but workable approach:

[events_list category=”Exhibition,-29″ scope=”future”]

That is: Excluding category id 29 from the list of the category “Exhibition”.

I believe, I have the exact same problem. I can’t find a way to keep current event (multi-day art exhibitions) out of the past and the future listings at the same time. It seems to be either-or: You seem to have to choose between letting a current event show in the past scope OR the future scope. Which is not so ideal in all situations.
So perhaps it would be an idea to add some kind of “exclude=current” shortcode variable?!
That would be nice.

There’s still quite a few reports of this problem in connection to Post Type Switcher from other users. Has anybody looked into this issue? The plugin is still in version 3.0.0 so the issue cannot have been solved through an update, I guess. I really love this plugin, but I don’t dare to activate the plugin until there’s a clear answer to this.
Please, let me know if there’s more that I can do to help clear this up.

• This reply was modified 8 years ago by biberkopf. Reason: Precision

I have just struggled a bit with controlling the image field, too.
Before you go on, please take a look at these to links. That shed some light on the issue for me:

https://wp-events-plugin.com/blog/2014/12/05/bye-timthumb/
https://wp-events-plugin.com/tutorials/caching-thumbnails-generated-by-timthumb/

Timthumb is the software that has been doing on-the-fly serversite scaling of images based on the url, e.g. https://image-url.com/image.jpg?w=600&h=400
But it’s no longer supported. When you add the {0,150} timthumb was supposed to take care of it. But the numbers still go into the image html tags as width and height.

Another point from these links is: You can make WordPress handle the scaling of the images or you can just get the full size image (which is probably not a good idea for lists). I managed to get {150,150} to work – maybe because wordpress already supported this size for my thumbnails. So perhaps, if you set your thumbnails to 0 and 150 and run a plugin like Regenerate Thumbnails you might be able to pull it off.

But take a look at the links and see if that helps. Good luck.

If your main concern is the narrow width of the css editor in the customizer, then here’s a solution, I just discovered by accident, and which will work fine for me for some time, I think.
1) Open a new window with Customizer -> Extra CSS.
2) Drag the border of the window to the size of 640 pixels or less.
3) The customizer will take up the full width of the window, and subsequently you now have a separate editor window of 640 pixels width – which is so much better than 299 pixels.
Enjoy!

I admire your evangelistic stamina, Jeremy. ?? Thanx for the outline, and for reminding us about the overall goodness of the Custom CSS. I’m looking forward to taking advantage of SASS/LESS, too.
I’ll take my whining elsewhere for now, hoping that eventually, we are enough people to stop the trend of stuffing too much of WordPress functionality into a 299px-wide strip.
Enjoy and endure!
(For now I have copied my css code, deactivated JPs Custom CSS and turned to another css editor plugin – which is still not as good as what yours was only one version bump ago. But thanx for the ride so far!)

Update: Nick Cernis’ github-dev-version mentioned here: https://www.ads-software.com/support/topic/spanish-translation-does-not-work?replies=3
seems to do the trick for me so far. Thanx to Nick for that! But it’s not an official release, and it would still be really nice with a status on the plans for an official, stable update.

Thanx for the fix. But perhaps it’s time to move to another plugin for this, I guess. ??

Hi Fresh-Media:
I obviously cannot say what aapc experienced, but perhaps this could be related info:
I’ve used another popular security plugin that used a method of automatically editing the htaccess file. When dubious access attempt was registered the attacking ip was immediately written to a blacklist in the htaccess file. The problem with this approach was that it often took place while the server was under most pressure. And eventually the server would fail to finish writing due to lack of ressources which resulted in a corrupted htaccess file (as described by aapc). This is impossible to replicate for a regular user like me, so it’s still only a theory, but I’ve corrollated the general server stats with the time of the file modification, so I think it’s the most likely explanation for this.
I’m no expert in htaccess, but I think one should avoid direct manipulation if possible. Or perhaps do the manipulation in a more thorough way (write to a temp file first, ensure integrity of the new file, and then swap the file by simply renaming/overwriting? Just some thoughts.
PS: Now I’m ranting anyway: How about a button i the GUI, that said “Whitelist my current IP-number (xxx.xxx.xx.xx)”? That would be user friendly.

Good work, Mat Lipe!
Realtm, we are really hoping for an update soon.
Any ETA yet?
??

Same problem here. Initially blamed it on qTranslate and mTranslate, but it turned out that SoundCLoud is Gold was the culprit. Really sorry to have to disable this plugin. Hoping for a quick solution to this bug. (I’m on WP3.9, not MS.)

The edit-content area on the post-edit-page was collapsed, hidden (display:none inline on the element along with a few other inline css-lines). It smelled like som javascript/JQ conflict. The solution seemed to be to deactivate the SoundCloud Is Gold-plugin.
Not sure excactly what’s the problem, though.

I second this question!
Is the actual OpenSSL code included in this plugin?

Hi Josep:
I’m not sure this actually solves my own little problem, but kudos for taking your time to sharing this inspiring piece of inventive thinking.
Respect. ??

Hugh, it’s a pity that you are not going to improve on this. The idea is excellent. So simple. I’m not able to decide how easy it would be to circumvent it automatically, but I really think you should give it another try.

I think that odjinud had the same problem I had. I, too, thought it broke on my iPhone, until I read some other jQuery-documentation telling to use the fall back mode:

1) click on the icon.
2) clik on the empty box.

I was mistakenly trying to drag’n’drop, which apparently doesn’t work. This – off course – has to be clear to the tablet user.

I suggest you make an instructions field for tablet and one for desktops. Or something similar. Otherwise we will loose too many users.