mrgad
Forum Replies Created
-
Forum: Plugins
In reply to: [Multipage] Searching Multipage ResultsThank you! My sketch for the function would look to see if the result page uses multipage. If so then does the resulting text occur, for example, after the nth iteration of multi page but before n+1? If so then the function would return [page url]/n/. That way clicking to view search results would take you right to the correct subpage.
Forum: Plugins
In reply to: [Multipage] Searching Multipage ResultsThank you for the quick response! Here is an example in which standard WordPress search is being used, as opposed to using a plugin such as SearchIQ that will display the context in which a search term is found.
https://wild.strangersofkindness.com/?s=denim
The above will correctly find the search term, but see it as occurring on the “page” as opposed to on the “subpage” #4 in the Dungaree section. The best UX would show the excerpt from the #4 subpage and the click to view more would jump to that subpage, as opposed to starting you at the beginning and having you guess on which subpage the result is to be found.
Thank you again for being so responsive!
Forum: Everything else WordPress
In reply to: how to validate digg digg pluginSame issue here, but only 8 errors and 3 warnings. Two of the warnings are easy to fix by editing dd-helper, but this work will be undone with the next update. Those two easy ones are the use of /../ within the generated URL for including the CSS stylesheet and the js plugin used by Digg Digg. Replacing the /../ phrase with the actual path will remove those 2 warnings. But there are still 8 actual errors thrown. This is with validating against HTML5 doctype. If you use XHTHML transitional, you’ll see vastly more errors.
Same problem here. Solution lies in changing DD_PLUGIN_URL, but can’t figure out how to change this to https:
Forum: Fixing WordPress
In reply to: Removing an author name from PermalinkHere is the code:
http://pastebin.com/wsrKiDJ6Forum: Fixing WordPress
In reply to: Trailing slash after index.html1. within WordPress, there is no Page created called “index.html” nor anything with that custom permalink.
2. When I originally posted my question, were you to visit http://www.example.com/index.html, your browser would redirect you to http://www.example.com/index.html/ (with slash)
3. As I did not figure out a way to fix this, I came up with a workaround. I took the entire source code of my home page, after loaded in a browser, and dumped it into a file I created outside of wordpress, and which I named index.html. Now the problem is solved – so you are not able to see index.html/ (with slash), but it has been solved with a rather clumsy workaround.
Forum: Fixing WordPress
In reply to: Trailing slash after index.htmlBut you won’t be able to see the error right now, as I’ve temporarily created a workaround. I have created a file called index.html outside of WordPress, so this page loads if someone browses to that specific adress.
Forum: Fixing WordPress
In reply to: Trailing slash after index.htmlOur permalink is custom structure:
/%postname%.html
But it is also to some extent modified by using the plugin “.html on Pages”.
I have created a temporary workaround. I created a file called index.html outside of WordPress, and populated it with the raw source code of our home page (which is a static page and never changes, so this is a safe practice, as long as we don’t alter site architecture).
Now, if someone navigates to index.html, it loads this page – and so the problem is “solved,” but of course not in the most efficient way.