jDelforge

My bad…

Disabling the plugin was breaking my angular framework for some reason and i did not see it.

So the main issue was somewhere else : angular was disabling the normal behaviour of the Woocommerce forms. So i just added the attribute ng-non-bindable to all woocommerce forms.

Hello Maciej,

Thank you very much for the update, it is working perfectly.
I might need further testing but if anything occurs I’ll come back with the debug data.

Greetz,
Johan

Maciej,

The issue occurs when the post is saved as published.
When saved as draft, the uri stays at /agenda/ with no slug afterwards. But it is not my main issue.

1. After the post is saved for the first time : screenshot

2. After the post is saved for the second time : screenshot

3. Permastructure settings : screenshot

… But now i realize i may be confuse with the URI concept: If i save only once the post as published, and i go to Permalink Manager/ Permalink editor and look at the “Full URI & Permalink”, it is not correct: screenshot

So, to sum, up: When i published only once, the permalink -looks- fine, but it is not, i need to save it twice.

Let me know if you need anything more.

Thank you,

Johan

• This reply was modified 7 years, 11 months ago by jDelforge.

Hi Shane.

1. user permissions
I understand, i have altered user permissions for years now. We the builders make websites for clients. And clients (editors) are able to add non-admin users. That is how it goes for our business, and for other firms i know. I guess it would be stronger for the plugin to rely on something else that ‘create_users’.

2. Disappearing of the dashboard
Not too fond of it either. I believe the future option should make it disappear if checked. Not the opposite. It does sound ‘gadget’.

3. Change root to current theme
OK

4. Find dialog
I’m on Chrome/Win7, and same result with Firefox. I’ve put my windows display of text settings back at 100%, and i get the same result. Here is a screenshot:
Screenshot

5. Opening folders is rather slow
I understand… i guess it is stronger to make an ajax new call every time so it acts like a refresh also. Css transition could be a bit faster…but this is not an issue.

6. Zipping progress bar
I’ve never tried a zipping library so i can’t be of any help right now.

7. Monokai
Yes it is an ace theme… or THE ace theme :). Anyway it can be changed already in the actual settings lightbox as ‘ace/theme/monokai’. I just meant that it would be more sexy to have it selected by default.

Thanx for the pretty complete reply…

Johan

• This reply was modified 7 years, 11 months ago by jDelforge.

Bingo, finally !!

I’ve answered my question here

• This reply was modified 8 years ago by jDelforge.

Bingo with road B, finally !!

I’ve answered my question here

Best regards…
Johan

?? I understand, especially when you use the ‘alien’ word.

Basically these last years I’ve been into 3 steps in terms of workflow :
1. WP PHP & jQuery (only once php ajax, big headache at that time)
2. WP PHP for back-end but only theme/index.php on the front, and Angular/UI-Router for everything front.
3. Full WP PHP + Angular but with no ng-routing/templates, only used as monster-jQuery, which is the best/fastest of both world, as it avoids the server rendering issue which leads to SEO problems.

So I’m using the WpRestApi since step 2, but always for GETs, and always with what it provides as default (except for menus & advanced wpml relations, which required additional plug-ins). So I’ve never code any additional endpoints nor specific permissions.

For the record the specific project I need POSTing was built on step2, that is why i cannot use something else than the Rest for Ajax calls (if I’m not mistaken), or i would need to refactor it to step3.

Now it seems there is 4 possible roads to solve my issue :
A. GhostLogin of ‘visitor’: Still a problem to make it work, and looks like unsafe road.
B. Find an authentication solution that finally works (not too excited, so much time in the bin already, i hope WP will finally provide a package solution)
C. Extend the WP RestApi with some endpoints & permissions (I might have found someone ready to write it)
D. Convert the project to step3 and work with PHP AJAX.

I find the WP Rest Api very easy to use, so i tend to road C, which from my point of view is more future friendly than PHP AJAX, yet it will need PHP coding to extend the rest.

I’ll let you know what happens.
Thank you very much for your input.

• This reply was modified 8 years ago by jDelforge.
• This reply was modified 8 years ago by jDelforge.
• This reply was modified 8 years ago by jDelforge.
• This reply was modified 8 years ago by jDelforge.
• This reply was modified 8 years ago by jDelforge.

?? Thank you.

… I’m pretty stuck on this project as it is all written in Angular / Ui-router, etc… So I would need to convert it to php to try something else than the REST approach… Or I’m missing something.

Wordpress is very weak by not giving a full solution with authentication for its REST… All solutions (OAuth, JWT… are never straight forward, I never had success with them)

Anyway thanx again for your generosity.

Johan.

• This reply was modified 8 years ago by jDelforge.

Thanx again for your reply.

Adding the filter with the correct user ID does not make the system work any better.

Anyway it looks that I’m working the wrong way…
I should focus on uphill problems: Angular $http posting is working great when logged in, but is always giving me a 401 Unauthorized response / “rest_cannot_create” when not logged in.

It’s crazy how much I’ve tried unlogged posting with the Rest Api without success…

There is a big lack of documentation / examples about it. The example on WP Rest Api Documentation using jQuery/AJAX is not working when not logged in, and overall very limited.

Cheerz anyway…

• This reply was modified 8 years ago by jDelforge.

Thank you very much for your logic reply.
I understand now that the initial login was not working properly, or happening too late, anyway it needed another reload to be strong enough to generate a working nonce.

Is there a solution out there to automatically shadowlogin ‘visitor’ properly if no one is logged in yet ? I guess if i solve this, my first wp_create_nonce will be working.

I’ve looked into the nonce_user_logged_out filter, but do not understand how to make it work & send a solid nonce to js variable… That is why I’m thinking i should better make a solid shadowlogin first.

… I’ve been spending weeks to understand how to allow any visitor to post stuff with $http, came to the conclusion that i needed that visitor to be logged in first… I’m very close to make it work, I’m on one reload away :)…

If you don’t have time for this, please let me know if i should have another way of seeing it.

Thank you,

Johan

• This reply was modified 8 years ago by jDelforge.
• This reply was modified 8 years ago by jDelforge.
• This reply was modified 8 years ago by jDelforge.

Perfect @vodnar !

Thank you & best regards from Belgium/Europa.

Thanx @vodnar.

I’ve looked in the files and indeed i saw the line.

Pardon my ignorance, but how could i modify the parameter without touching the original file, so it does not get reset when updates happen ?
Would u have some simple tips for me to add a modifier say in functions.php ?

Thanx a bunch,

Johan

OK, i got an answer from WPML…

The CPT plugin we are using makes direct queries to the database instead of calling functions from WordPress API.

WPML have developped a ‘Type’ plug-in, but is not completely compatible with ACF… So i’m actually brainstretching to hard code CPTs without any use of plug-ins… so i can be using WPML.

+1