Spanka
Forum Replies Created
-
Forum: Plugins
In reply to: [Custom Menu Wizard Widget] Simplest of CMS menu functionsForgot to add: you could also just add an option for “items to always show, regardless of filter”.
This would probably be the easiest of all to implement!
For 3 level deep menus, you’d only have to add “with siblings” to “include ancestors” to get the full hierarchical+roo rendering.
Forum: Plugins
In reply to: [Custom Menu Wizard Widget] Simplest of CMS menu functionsI might be crazy, but I think I’ve got v2 doing what you describe. I’m using:
Children of[curent item]… starting level[1]….for depth[1]….relative to current item[true]
Fallback[switch to current + incl parent + with siblings]
Output [incl. parent + siblings + ancestors]
- if 2.0 is current + widget shows: all root items plus immediate children of 2.0 to 1 level. Perfect. (1 + 2 + 2.1 + 2.2 + 2.3 + 2.4 + 3)
- If 2.1 is current + widget shows: 2.0 + 2.1 (+ 2.1.n) + 2.2 + 2.3 + 2.4 (“correct CMS hierarchical” + but isn’t showing all root items which IMO + would be proper)
- IF 2.1.1 is current + widget shows the same items – good. It’s not uber traversing parent siblings + but same issue with no root items
What I cannot seem to have is the 2nd item above, with all root items showing. IMO, unless you’re talking a massive site, all root items should always appear as they are always relevant to navigation. That’s why they’re root items (right?!!!)
The widget is fantastic. I think there are a couple of approaches to cover fringe cases that might be helpful – I don’t know if they’re doable…
- A “simple solution”: “always show root items”. This would beat the hierarchical issue I’m currently experiencing, but might not solve at the 4th+ levels.
- Probably the “real solution” (if doable): instead of a fallback for “switch to current parent item”:
- Include parent boolean (ie: divorce this setting from ‘switch to parent’)
- Include parent’s siblings boolean
- Include ancestors (should this even be optional! always on!)
- Include ancestor siblings up to what level of depth (0,1,2,3,4,5)
- (crazy talk option) Ancestor sibling depth (0,1,2,3,4,5)
For option 2 – including parent + parent siblings + ancestors + ancestor siblings (1, being my root) would do exactly what I’m personally after. But forget that it would help me, I think this is the logical solution if it is doable. It would amount to “drill down as far as you want, and expand the ancestral levels as much as you desire”.
Item 2e is just me dreaming 🙂 I doubt it would be used in 99.999% of cases. But theoretically, you might want ONE level of subs on all ancestors.
- 1.0
- 2.0
- 2.1
- 2.1.1
- 2.1.2
- 2.1.3
- 2.2
- 2.2.1
- 2.2.2
- 2.2.3
- 2.3
- 2.3.1
- 2.3.2
- 2.3.3
- 2.4
- 3.0
Forum: Fixing WordPress
In reply to: How to fix my host's database error?Sounds like your hosting environment doesn’t have FTP permissions set up well, so that once you ran the install script, you no longer had write permissions on the file.
This stuff can be messy if the hosting company isn’t good with CMS systems.
esmi is correct – this is a hosting issue.
@alexmalexm: I can promise you a LOT MORE pain if you tried to run Joomla in the same environment 🙂 Believe me – I’ve been there. Joomla is a nightmare if the hosting isn’t good for it. If the hosting is good, it’s great, but not as simple/easy as WP.
Forum: Plugins
In reply to: Lightbox Plus ColorBox – responsive?I use this plugin all the time and it is already responsive, it’s just not dynamically resizing to a changing screen size in real time.
It only calcs display width at the point it launches a lightbox.
Solution: dig into the CSS and change the outer divs to max-width: 100% – its exactly the same as handling images in a dynamic responsive environment.
Forum: Fixing WordPress
In reply to: How to fix my host's database error?Hey Airdisplays,
Having worked with Joomla for about 6 years now and wordpress for about 1 year, I can promise you: nearly everything (except very fine URL control) is easier with WordPress.
On to your question – database isn’t setup correctly. If you read the error message in plain english:
1. “WordPress database error”
2. “Table ‘markj_wam.wp_options’ doesn’t exist….I’ve never seen this before. I cannot imagine what caused it. Every WP install for me has been seamless and less than about 2mins.
If you’re working on a local machine (ie: the file paths in your errors indicate this), wipe out the folder, delete the db. Create a new DB and reinstall fresh – could be just an unzip mangle or something.
If that didn’t work, do a google search on the exact repeated error (include the quotes for exact matching):
“doesn’t exist for query SELECT option_value FROM wp_options”
From glancing through some of the pages, my best guess is that your environment is odd (doing something “cool” with CGI/FastCGI), or your environment does NOT meet WP’s requirements, which I presume you’ve fully checked 🙂
On your follow up post – unzip files to dir. Run config setup, which populates wp-config.php & the DB – there’s nothing actually ELSE to WP. It’s childishly straight forward. There are no other steps unless you want multi-site ability.
If it goes wrong, it’s always: your environment is unsuited, you put in an incorrect DB or similar, files got mangled or permissions for db/files are off. There’s not much else to WP.
Good luck with it.
I’m not good with this stuff, but I gave it a shot and think I have an answer.
In custom-post-type-permalinks.php, term_link():
$termlink = str_replace( $term->slug.'/', $this->get_taxonomy_parents( $term->term_id,$taxonomy->name, false, '/', true ), $termlink );If I comment this line out, taxonomy URLs are perfect, no 404’s, posts work etc. It is working. On the links below, the modification is in effect. However, you can see the value that WOULD have appeared – at “T11” on these pages:
parent tax page, child tax page, grandchild tax page.Hope this helps.
Ok, I’m crazy. It is NOT doing
{parent/child}/{child}The pattern is (tests & confirmations below)
{parent}/{child-full-hierarchy-segments}To confirm with a Level 3 category (/parent/child/grandchild/)
|- slug base -|-- parent ---|-- child segments --| /slug-p/slug-c/wCat-1/wCat-2/wCat-1/wCat-2/wCat-3/I made a new 4th level category to confirm it was linear, not recursive:
|- slug base -|------ parent ------|-------child segments------| /slug-p/slug-c/wCat-1/wCat-2/wCat-3/wCat-1/wCat-2/wCat-3/wCat-4/If it *was* recursively building full hierarchies for every segment, it would look like this:
|- slug base -|parent|--- child ---|---- grand child----| ---- great grandchild ----| /slug-p/slug-c/wCat-1/wCat-1/wCat-2/wCat-1/wCat-2/wCat-3/wCat-1/wCat-2/wCat-3/wCat-4/But this is NOT happening!
Just to follow up – documenting this here:
http://test3.lowcarbbreadcentral.com.au/uncategorized/take-2/ (see item 5 in first table). Posts are perfect, taxonomy pages past level 1 are odd.
Posts (perfect!)
L1 post: /slug-p/widgetcat-1/widget-1/
L2 post: /slug-p/widgetcat-1/widgetcat-2/widget-2/
L3 post: /slug-p/widgetcat-1/widgetcat-2/widgetcat-3/widget-3/Tax pages
L1 tax : /slug-p/slug-c/widgetcat-1/
L2 tax : /slug-p/slug-c/widgetcat-1/widgetcat-1/widgetcat-2/
L3 tax : /slug-p/slug-c/widgetcat-1/widgetcat-2/widgetcat-1/widgetcat-2/widgetcat-3/Tax pages (should be)
L1 tax : /slug-p/slug-c/widgetcat-1/
L2 tax : /slug-p/slug-c/widgetcat-1/widgetcat-2/
L3 tax : /slug-p/slug-c/widgetcat-1/widgetcat-2/widgetcat-3/The pattern seems to be: {parent/child}/{child} – it’s just pulling in the parent category segment as a full lineage, not just a URL segment of a single tax.
Forum: Plugins
In reply to: [Custom Post Type Permalinks] Parent taxonomy ignored in permalinkThanks very much! I can confirm operability – ran some tests on a messy test bed here:
http://test3.lowcarbbreadcentral.com.au/posts/ (no guarantees as to how long this is valid for as I’m doing a complete test run of a heap of customisations and URLs will be changing and breaking).
Sample URLs generated pretty effortlessly were:
Here’s some sample URL’s generated. All segments should be self documenting:
/catw-slug/widgetcat-1/
/catw-slug/widgetcat-1/widgetcat-2/
/catw-slug/widgetcat-1/widgetcat-2/widgetcat-3//tagw-slug/wtag1/
/post-slug/widgetcat-1/widget-1/
/post-slug/widgetcat-1/widgetcat-2/widget-2/
/post-slug/widgetcat-1/widgetcat-2/widgetcat-3/widget-3/All custom categories kept their structures, no 404. Ditto posts.
This (IMO) is a good improvement over the WP defaults as documented here http://test3.lowcarbbreadcentral.com.au/home/test-8-default-rewrites-redux/ which is probably enough.
This plugin now improves the “best” I could come up with on WP defaults alone, as documented here: http://test3.lowcarbbreadcentral.com.au/home/test-9-default-wp-urls-for-cts-and-cps/ – your plugin allows custom post URLs that (sort of) represent the hierarchy of content.
That first URL fragment is killing me!
Thanks again though ToroUnit – you guys are rocking it.
Forum: Plugins
In reply to: [Custom Post Type Permalinks] Parent taxonomy ignored in permalinkI have the same thing Ashworth. I’d be keen if you or anyone else has the solution for this!
I’ve only just installed this plugin about 2 seconds ago, however – on the permalink settings page, it says:
The tags you can use is WordPress Structure Tags and ‘%”custom_taxonomy_slug”%’. (e.g. %actors%)
%”custom_taxonomy_slug”% is replaced the taxonomy’s term.’.You don’t use %custom_taxonomy_slug%! you use whatever your custom taxonomy is called whether. So if your taxonomy is “actors”, use %actors% etc.