Kerry

The free version here on the repo is not translated yet. The pro version has a function that allows you to change most strings on the frontend and backend to something completely different.

An example to change most field labels is listed on the support docs here. Again only available in the Pro version.

Hi ctutu,

Do you have a live link to the page in question?

Hi JoePhilpott,

Are you referring to the testimonial slider ? You would need to adjust the CSS. Place the following in your theme’s custom css area or theme’s style.css file.

.bne-testimonial-slider-wrapper {
   border: none;
   box-shadow: none;
}

Hi thatryan,

Thanks for the request, and I totally understand but currently do not have any plans to implement an insert button into TinyMCE at this time.

Using WooThemes’s version would look like this:

.bne-testimonial-slider.flexslider .flex-direction-nav { width: 100%; top: 50%; left: 0; right: 0; }
.bne-testimonial-slider.flexslider .flex-direction-nav li { }
.bne-testimonial-slider.flexslider .flex-direction-nav li a {
	top: 50%;
	position: absolute;
	background: url(https://flexslider.woothemes.com/images/bg_direction_nav.png);
	width: 27px;
	height: 27px;
}
.bne-testimonial-slider.flexslider .flex-direction-nav .flex-prev { left: -30px; background-position: 0 0;}
.bne-testimonial-slider.flexslider .flex-direction-nav .flex-next { left: auto; right: -30px; background-position: 100% 0; }

Again you may need to adjust based on your theme and the background arrow image used. You also need to grab your own arrow background and not use the one directly from WooThemes, as in not linking directly to it such as the example above is.

CompuMatter, please see my answer your other comment.

Hi CompuMatter,

The navigation arrows shouldn’t be located there in the screenshot you provided. By default, they should be on the bottom right aligned with the pagination buttons. If your theme is using flexslider as well, it could be overriding the location in my plugin. If you have a live link of the page in question, then I can check for you.

In regards to moving them to the opposite sides, and using your own arrows, that is definitely possible with your own CSS modifications from your theme’s custom css area or style.css file. Below would be a starting place for you and should get the arrows to the opposite sides and vertically centered. Adjust to your needs.

/* Nav Arrows */
.bne-testimonial-slider.flexslider .flex-direction-nav { width: 100%; top: 50%; left: 0; right: 0; }
.bne-testimonial-slider.flexslider .flex-direction-nav li { }
.bne-testimonial-slider.flexslider .flex-direction-nav li a { top: 50%; position: absolute; }
.bne-testimonial-slider.flexslider .flex-direction-nav .flex-prev { left: -30px; }
.bne-testimonial-slider.flexslider .flex-direction-nav .flex-next { left: auto; right: -30px; }

Hi Marshmelly411,

The type of theme shouldn’t matter. However, where you are placing your CSS edit and when it is being enqueued from WordPress may be happening before the plugin’s css file. Have you tried adding !important tags to your changes?

.bne-testimonial-slider-wrapper {
border: none !important;
box-shadow: none !important;
}

If that doesn’t work, then I would be happy to take a look if you send a URL of the page that has it.

Have you tried Post Expirator? I have not tried it, but It looks to have support for custom post types which is what my plugin is. Not sure if it can go as far as the categories though.

Awesome. Thanks Ross. Looking forward to the pro version.

Awesome to hear. Looking forward to it ??

fran330, you can fix this by going to the Crayon admin settings page. Go to Ta Editor and uncheck:

Display the Tag Editor in any TinyMCE instances on the frontend (e.g. bbPress)

I found the solution.

1) Go to /wp-content/plugins/mp3-jplayer/js
2) open mp3-jplayer.js
3) go to around line 173 and change the location, status, scrollbars, resizable to either 0 for NO or 1 for YES.
4) line 174, change popup_width & open_at_height to your preferred width and height numbers , ex) newwindow.resizeTo( 300, 110 );

I hope this is fixed soon. I use the Redux register plugin and I need those additional fields exported.