katart17

I just converted from the Types plugin to CPT UI because of a conflict with WooCommerce. I didn’t import any data. I just created a new Post Type in CPT UI but used the same slug and id so didn’t have to modify the theme files.

Does that make sense?

That makes sense. Thanks for the great plugin…

The only thing I wish for now is that the on slider init function would work.

@averta Is using custom CSS the answer to my question? It would be nice to have an option to change the position of the slide.

Thanks Archetyped,

I was just wondering if the slb_group shortcode could be used to hide groups of links to get the same effect as the Launch Slideshow from Single Link workaround. I tested the plugin and it looks as if that shortcode works to only group some images of a post and not all.

Are you still working on an internal way of Launching Slideshows from a Single Link instead of the above workaround?

Will the slb_group shortcode allow for hiding a group of links? Maybe adding a hidden attribute within the shortcode.

That fixed it. Thanks.

I decided to setup OAuth using the Gmail API to get this to work.

The plugin says the ports are closed but the STMP servers are successfully sending out emails. Any ideas why?

The reason I want on slider init to work is to append custom next/prev arrows and a numerical index to the slider (ie 2 of 5). Since on slider init doesn’t work, can you give us a workaround to append content to the slider and use the target api?

Thanks

Any updates on this?

I was wondering the same thing. All other callbacks are called, but not on slider init

@jason

This is what the server admin had to say:

You’re connecting to a remote SMTP server, under no circumstances if you have your plug-in setup correctly should you be connecting to localhost.

That’s like saying that I set up my Outlook, Thunderbird or Apple Mail to connect to gmail but instead it connects back my workstation. That would be an indication that I did something wrong in my email client.

There is nothing on the server that forces SMTP traffic through the local SMTP server. If you have PHP mail set-up to connect to a remote SMTP server it should not be communicating at all with the local email server.

The firewall having PORT 53 closed would prevent you from being able to connect to gmail as this would result in DNS lookup failures at the server.

The firewall on the server uses basic iptables rules to allow incoming or outgoing traffic. If a Port is blocked in the firewall it will fail to connect to any service on that port until that port is opened in the iptables.

As the developer suggested the opening of port 53 should not have had any affect on whether the script connects to localhost or remote host, port 53 being closed just blocked DNS lookups.

This is why I asked if there is a fail over mechanism in the the sites code that causes failed connections to fall back to localhost.

Does this make sense?

Jason, thanks for the response and the clarification. This is a little over my head and I might have incorrectly relayed the information from Support.

They “somehow” fixed the issue and maybe they didn’t know about the Advanced logs options.

I ran into a similar problem with my site and contacted Hosting support and they resolved it. It took them a while to figure it out. It seemed that they had to open up port 53.

The support rep also mentioned that the developer should give more information in the debug log about failed DNS lookup attempts (or outgoing queries). It seems as if the debug log only shows when a connection is made and then displays a Warning. I was receiving the following Warnings:

Warning: connected to mydomain.com instead of gmail.com

Does this make sense?

I used the WYSIWYG editor under the Slide Info tab to apply the <blockquote> to all text. I then apply the background:color to the <blockquote> via CSS.