katie

I just sent a ticket at the direct support link. This is the second time I’ve submitted this ticket there–when I submitted it, my computer remembered the subjects of my previous tickets, and one of them was entitled “Refund due to errors.” I just submitted another ticket at that same place, with the same title as before!

This is the second time I received no response when I submitted a ticket to your direct-response system. That’s why I started just emailing you directly at [email protected]. When I submitted my initial ticket with a question, back in January and just weeks after purchasing the plugin, I received no response. I then posted on this WordPress forum, and that was how I got your attention. That is what happened this time, too. There is something wrong with both your ticket request system and your email system…either that, or this unresponsiveness is intentional!

I will also forward you the thread with my two refund requests via email. All of those emails already went to [email protected]. I will send them again to that same place!

Sure, I will submit a support ticket. But I emailed you directly about this. The email thread is called “Error,” and I first emailed you on July 3 describing the latest error: the plugin had not posted my posts at all. You responded promptly on the same day, asking for a parrot report. I sent the parrot report on July 4. You didn’t respond. On July 10, after the plugin again failed, I replied to the same thread asking how I could get a refund. I repeated the question on August 5. Again I received no response from you!

Hi Vinod,

Thanks very much for this quick reply and assistance. There is still one problem: the position is fixed, but the typing is still hidden on the mobile device.

Here is what I currently have in the custom CSS:

li.is-menu path {
    fill: #fff;
}
@media screen and (max-width: 768px){
.is-menu.dropdown form {
display: block !important;
    position: static;
    top: 9px;
    right: auto;
    left: 18px;
    }
}

.main-navigation li.is-menu a {
    line-height: 8px;
    padding-top: 14px;
}

The first part (li.is-menu path { fill: #fff;}) is to make the icon white.

You can see that I have also inserted two more lines into your original suggested code:

display: block !important;
    position: static;

That’s because when I took those lines out, the icon worked fine on the desktop and tablet, but on the mobile it was not clickable at all. When I add those two lines back in, it becomes clickable again…but the typing is hidden by the keyboard popup.

So I am still looking for a fix to that problem. Let me know what to do; thanks again!

Thanks, Steve. Looking at the link you sent, the author was wanting to exclude all categories that weren’t top level, so that only the top-level categories would be returned by next_post_link. I’ve tried installing a plugin, Ambrosite Next/Previous Post Links (documentation here), that does the same thing. However, the problem is that when I exclude all but parent categories, the next_post_link code returns NO blog posts. That is, for some reason, this code is not considering my posts to be in parent categories in the first place, so excluding the child categories means that it finds posts to be in NO categories.

I suspect that this somehow relates to my using category pages to display my blogs. Clearly, WordPress knows that my posts ARE in parent categories–it’s those parent categories that are used to assign the posts to each of the three blog pages on my website. However, perhaps it’s then ignoring parent categories in next_post_link because single posts appear ON the parent category pages?

I’m not a coder, so I definitely need help sorting this out. (I also apologize if I’m not using the right terminology above.) Any other suggestions? Thank you!

Joy, thanks so much for this explanation. I’ll Google this next question right now, but do you know of any other way to turn blog posts into automatted emails, other than RSS? I.e., is there a way to send automated, *formatted* emails, or is RSS the only way to go?

P.S. I am using the Weaver II theme, and their tech support says that they cannot see any Weaver II CSS that might be causing the problem. They asked for more specifics, if you do think the theme is causing the problem–I’m not a coder, but it sounds like when they look at the code it is “marked hidden” by “MailChimp” (presumably by your plugin). Again, I’m not quite sure what that means–just passing it along to you. 🙂

Thanks for responding. It turns out I didn’t understand the basics of the widget–I didn’t know that I needed to go into “Pages” and check or uncheck the individual pages I wanted. Because “Posts” and “Page with posts” were options outside of their listing under “Pages” (if that makes sense), I thought I had already done all the “Yes/No” settings I needed to do. Someone on another forum explained this to me and the problem is resolved… Maybe you could create a basic tutorial, or if one already exists make it a little easier to find? 🙂

Thanks!