tristanofalls

Ah, wow, good to know. Thank you for the concise explanation! That should be pretty easy to track down.

Thanks again for a great plugin!

So, was there an invisible change to the 1.2.7 version that addresses this issue, or are we still waiting on a 1.2.8 with a fix?

Thanks!

A similar problem happened to a site under my control. Any selection of a custom taxonomy filter produced broken URLs. I reverted back to version 1.2.6, and the problem went away. The URL generation update in 1.2.7 seems the likely culprit.

My permalink settings: /%category%/%postname%/

You can find older versions of the plugin on the developer’s tab:

https://www.ads-software.com/plugins/master-slider/developers/

Installing one of the older versions manually should fix the slider for the time being.

Edit: (Manually installing plugins generally requires some kind of FTP access to your server. If you can get that, it’s as simple as deleting the plugin’s folder: “/wp-content/plugins/master-slider/” …and then uploading the other version’s folder in its place.)

Both are running Windows 7. I was using the latest versions of both browsers. She was using the latest version of Chrome, but only version 31 of Firefox. (The problem first happened on Chrome, though.)

Thank you again for being such an attentive developer. I know unreplicable problems like this can be super annoying.

I’ll try to get access to her machine to try to replicate the problem there, but I’m not sure when our schedules will coincide.

Ah, also, I believe the new results pages had 0 and 100 in the numbers fields upon creation.

Given what the user has produced, it seems to be inconsistent. The new pages, when they first appear, seem to be normal “Enter your text here.” boxes.

I’ve observed this happen directly now; her process:

1. Add a few results pages.
2. Save results pages. Return to the results tab.
3. Customize the new pages from step 1.
4. Save again. Return to the results tab.

At this point, neither the actions in #1 or #3 appear, and everything has somehow been reset to pre-#1.

I’ve, oddly, not been able to replicate the problem on my machine, but she has had the problem crop up in both Chrome and Firefox on her machine. I’ve worked around it for now, but it would obviously be better if we could count on reliability in the future.

Thanks for looking into it!