Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEE #10

Open
3 tasks
r-a-y opened this issue Jul 24, 2015 · 7 comments
Open
3 tasks

FEE #10

r-a-y opened this issue Jul 24, 2015 · 7 comments

Comments

@r-a-y
Copy link
Member

r-a-y commented Jul 24, 2015

I've created this issue just to track what we are doing with FEE.

In commit 5635e64, we are now relying on the wp.org version of FEE:
https://wordpress.org/plugins/wp-front-end-editor/

If we need to make changes to FEE for whatever reason, mods should be made in the CACSP_FEE class:
https://github.com/cuny-academic-commons/social-paper/blob/master/includes/class-cacsp-fee.php

CACSP_FEE extends the main FEE class so we should be able to make any overrides there. I believe I've ported all the changes that we previously made to our bundled version of FEE:
https://github.com/cuny-academic-commons/social-paper/commits/master/lib/wp-front-end-editor

@christianwach - I also have a question about the "Tags" button in FEE, but I'll reply in this thread:
789aa14

If anyone has any questions, let me know.


Todos:

@rjbaniel
Copy link
Collaborator

So I've taken FEE out of our code, and then added compatibility via functions.php: 740ba0d

@rjbaniel
Copy link
Collaborator

I also had a question about the styling on the edit button - for me adding in the extra relative positioning made the Edit button look strange with the rest of the Admin bar. Is that true for you all, too?

@r-a-y
Copy link
Member Author

r-a-y commented Jul 27, 2015

I also had a question about the styling on the edit button - for me adding in the extra relative positioning made the Edit button look strange with the rest of the Admin bar. Is that true for you all, too?

Can you post a screenshot, Dan?

At the moment, the admin bar shouldn't be displayed on a Social Paper page.

Here's what it should look like:
Screenshot of a Social Paper page

The styling of the "Enable Editing" button could use more work. It's temporary until we hand off the UX to the rest of the team later on. We might also bring back a version of the admin bar pending feedback as well.

@rjbaniel
Copy link
Collaborator

That's weird! Yeah I'm on master and I can see that admin-bar is being enqueued in cacsp_asset_enqueue_handler(), and the whole admin bar is showing, which seems to be covering up the button you added. And since the admin bar is visible, the "Edit Paper" button is to, but it's just positioned weirdly because of the extra styling. What do you think I'm missing here?

Also, took my first shot at adding admin notices to check for FEE here: 8cd8e0e

r-a-y added a commit that referenced this issue Jul 27, 2015
@r-a-y
Copy link
Member Author

r-a-y commented Jul 27, 2015

I can see that admin-bar is being enqueued in cacsp_asset_enqueue_handler()

Good catch! I've removed the two admin bar enqueues in commit ecebb2d.

and the whole admin bar is showing, which seems to be covering up the button you added

Hmm... maybe _cacsp_disable_admin_bar_on_social_paper_pages() is not working as intended. It's already firing at priority 1, which is pretty early. Maybe play around with the priority of the 'admin_bar_init' hook on your install and see if it works?

Update: I've moved the disable admin bar code to the 'wp' hook in commit 125dd06. Let me know if that works.

r-a-y added a commit that referenced this issue Aug 25, 2015
Removes the WP adminbar for real this time!

Addresses #10 (comment).

See related commit 125dd06.
r-a-y added a commit that referenced this issue Sep 1, 2015
The 'wplink' plugin received some updates in WordPress 4.3, which
unfortunately broke how FEE operates.

This commit temporarily removes the 'wplink' plugin until FEE addresses
what to do with 'wplink' for WP 4.3+.

See #10.
r-a-y added a commit that referenced this issue Sep 28, 2015
As of WordPress 4.3.1, this isn't necessary anymore.

See related commit 2fd3a25.

See #10.
r-a-y added a commit that referenced this issue Sep 28, 2015
- Add a hardcoded block in FEE to load its scripts for subscribers
- Comment out 'map_meta_cap' call in register_post_type().  This was
  breaking a few things...

See #10.
@r-a-y
Copy link
Member Author

r-a-y commented Oct 4, 2015

So in WordPress 4.3, FEE's floating toolbar doesn't show up when attempting to edit an "Add a block" item or when selecting some text.

I've hacked FEE's JS to temporarily fix this:
https://github.com/iseulde/wp-front-end-editor/pull/261/files

I'll be patching this on cdev just so our testers will have something to work with, but this needs a bit more work since the toolbar fades in and out when a button is clicked in the floating toolbar.

@r-a-y
Copy link
Member Author

r-a-y commented Oct 5, 2015

Found another issue - if the floating image toolbar is visible and you click on the "X" button multiple times, this will remove parent elements from view.

GIF

I have a fix for this and have added a PR for FEE here:
https://github.com/iseulde/wp-front-end-editor/pull/267/files

r-a-y added a commit that referenced this issue Oct 12, 2015
r-a-y added a commit that referenced this issue Oct 12, 2015
By default, FEE animates the URL box on certain events.  We do not want
the URL box to animate, so use CSS !important declarations to counteract
FEE's JS.

See #10.
@boonebgorges boonebgorges modified the milestone: 1.0 Oct 25, 2015
@boonebgorges boonebgorges removed this from the 1.0 milestone Nov 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants