skarjune

https://wordimage.com/support/tickets/
[wsdesk_support display=”check_request”]

Shows the same two basic links without menu as here:https://wordimage.com/support/help-desk/
[wsdesk_support]

And I can’t find any documentation for external users. Do they need a WordPress account and with what permissions to view a ticket?

Thanks for the speedy advice. Yes the Cloudways SMTP connection was not good, switched to a WordPress plugin and also adjusted my GSuite Gmail API config, and it works with the custom support@mydomain… account nicely.

Thanks for the update! However, we are now using a plugin that has the features requested by the client. Another small issue was that there was not responsive resizing when a mobile user flips from landscape to portrait. No biggie, but something to review in your update.

This appears to be fixed in version 2.3.2, maybe with this item: 5) Fixed the issue with tags in the description, where empty symbols were displayed when description were added by tags.

I’m able to use both standard HTML tags along with classes for custom CSS. Works fine.

I just tested Relia on a WordPress site today with no problem whatsoever.

As SmartCat indicated, you need to contact your host as it appears that there is a problem supporting the required web server software for WordPress.
https://www.ads-software.com/about/requirements/

The FTP error has nothing to do with WordPress, as that comes from the web server at the host. WordPress sits on top of all that.

So, please refrain from anger with the developer offering a free theme and free support here. And, do contact your host as that appears to be the source of the problem.

Nice idea to have a print link to another page, where all toggle items are open, which can be set with this shortcode:
[toggle title="Item 1 Title" state="opened"]

Else, the accordion multiopen attribute allows a user to select which toggle items are open to print. Note that having the same content on two pages would be an SEO negative for Google search.

“Ideally” a programmer might write a JavaScript function to open or close all toggle items, but that’s not my area.

Accordions are a screen function, not related to the Print function, so your criticism is not really related to this particular plugin. The only way I know to adjust print output, differing from the screen, is to use a print style sheet. Maybe it’s possible to do some advanced Javascript/CSS tricks for your concern, but that would be a different plugin to handle those options, as this is simply a collection of handy styling functions taken from the developer’s theme work.

Still, it’s possible to print all content of a web page at one time with this shortcode setting, so that a user may open all toggle items simultaneously:

[accordion multiopen="true"]

Maybe that’s not “ideal,” but remember that simple free free plugins like this one are generic, and you always have the right to change the code to meet your needs.

Shortcodes in WordPress cannot be directly styled in the editor like normal content. Instead you need to add CSS style rules for the HTML created by the plugin. See my other responses here for examples on how to do this.

The printed page should be the same as what is currently displayed in the browser. So, opened Toggle items are printed as such, while closed Toggle items just have the title. If this is not the case for your website, please include a link to an example page, so someone can look at the problem.

You can add CSS styles to customize the look, as with anything else on your WordPress website. How you do that depends upon your theme and WordPress setup. Some themes have a CSS editor in options. Or, developers use a child theme and edit the style.css file. Or, the JetPack plugin provides a nice CSS Stylesheet Editor.

You need to add CSS style rules, and examine the HTML classes to alter using a tool like the Google Chrome DevTools.

Here is a style rule that will enlarge the Toggle item titles by 1.5:
.omsc-toggle-title {font-size: 1.5em;}

You can add CSS styles to customize the look, as with anything else on your WordPress website. How you do that depends upon your theme and WordPress setup. Some themes have a CSS editor in options. Or, developers use a child theme and edit the style.css file. Or, the JetPack plugin provides a nice CSS Stylesheet Editor.

You need to add CSS style rules, and examine the HTML classes to alter using a tool like the Google Chrome DevTools.

For example, here are style rules that will change the color of the toggle bar to yellow, red for a mouse hover, and keeping white for the toggle item background:

.omsc-toggle {background: #ffff00;}
.omsc-toggle:hover {background: #ff0000;}
.omsc-toggle-inner {background: #ffffff;}

I believe WordPress can remove plugin data upon deletion, so the extra step seems like extra work for user. Having the option in the installed plugin doesn’t help after it’s gone. I’m able to manage user roles in WordPress and I removed the Give plugin roles myself, but the casual user is left with your roles, and I did not see this mentioned in your documentation.

This plugin is simply a display of scheduled posts, it does not publish posts. Seems that failed scheduled posts is a minor anomaly of WordPress for some installations, due to Cron job issues, I believe. There is a popular plugin for this anomaly:
WP Missed Schedule
Note that there are a few complaints about it, and the developers have moved support off www.ads-software.com. Just saying, as with any free software, your mileage may vary.

More details about plugins to assist with scheduled posts here:
WPMUDEV – 10 WORDPRESS PLUGINS FOR MORE POWERFUL AND FLEXIBLE SCHEDULED POSTS

My issue was not a plugin. It was an options setting in the database made by the Headway framework theme. The theme was not in use, but it was legacy code from a previous developer. There was no indication in the table row what had set it, but I could tell from neighboring rows that it was the old theme. You may disrupt a theme or plugin that is still in use, so do this at your own discretion.

You need to search the database table wp_options to delete a row that has:
option_name: Submit
option_value: Save Changes

You’ll need to access the database on your server using something like phpMyAdmin.

Yes works with a fresh install but not with a clone of the production website with all plugins and custom themes deactivated and directories renamed. You are correct, as I did find a single row in wp_options with the setting that causes the problem with option_name: Submit set to option_value: Save Changes.

I can see in the table stack that this is a legacy Headway setting from an earlier developer, who actually never completed his design, and this proves my opinion that Headway sucks, like most page design frameworks that hijack WordPress to their own benefit.

Thanks for the tip David!!!